US claims jurisdiction over all .com/.net sites even if outside the US (2011)
web.archive.org
web.archive.org
https://www.icann.org/en/blogs/details/cheers-to-the-multist...
https://www.icann.org/en/announcements/details/stewardship-o...
by detecting and hindering domain name intellectual property
double plus based
As long as the namespace remains under the control of a centralized authority like the US, this will continue to be a reality. There may be some naysayers about solutions like Handshake, but frankly speaking, there's no person who would logically want their name to be able to be taken away by someone else. Your name is your identity and it is you. To be able to assert this with cryptography is a cypherpunk's dream.
[1] https://oag.ca.gov/news/press-releases/heels-ag-becerra-lett...
Since they are not under a country code TLD, I think it really makes sense migrate .com, .net and .org to be 'international' TLDs (I think many people internationality basically already consider them to effectively be so) and US companies should be able to access equivalents under the ccTLD like .com.us, .net.us etc. if they wanted a US-specific one, just like every other country does. Then also, I really think all .gov, .mil and .edu and the other US-only TLDs should be phased out (they could just become redirects to .gov.us, .mil.us etc.). Having those TLDs as US-only just smacks of American exceptionalism - I understand the history and it made sense at the time, but became inappropriate as all the other ccTLDs started becoming used. They should have migrated to .us domains back then and deprecated .mil, .gov and so on.
It would be a bit messy, since .us is already delegated and there are already heaps of domains in that namespace which would have to be either retained as legacy or migrated after some time. So really the sooner the better! The US Government would probably have to buy the .us ccTLD back, create ones like com.us, net.us, org.us under it and then re-delegate them while operating .mil.us, .gov.us, .edu.us themselves.
Have you seen what the DoD PKI chain looks like?
https://militarycac.com/images/fed_crosscert2Sm.jpg
Good luck migrating all of that to a new TLD in the next millennium.
> "DoD Subordinate CAs (SHA-1)"
> "DoD ECA Root CA 2 (SHA-1)"
> "DoD Root CA 2 (SHA-1)"
> -- https://militarycac.com/images/fed_crosscert2Sm.jpg
O___O
Might be worth considering a migration sooner than later.
If other countries don't like it... why connect and use an American network? Why not build their own (and foot the research bill!).
They can change protocols, but that would just lead to a fractured ecosystem fir the benefit of no one, American or otherwise.
Does Anguilla have the right to control .ai, or do people who want to use it to reference AI have a right to use it?
Domains like .io, .ly and .tv are also used for vanity URL. That was not something originally expected with these.
Immigration and Customs Enforcement has jurisdiction over customs enforcement.
My guess is that if you create a blockchain for registering DNS, and only the current registrars can issue coins on said blockchain, you might have a solution they would be willing to implement. You'd still have to pay them money to register a new domain or maintain it, but once you had the coin, you could register whatever you wanted and no government could stop you.
This has been the story for many sites, where domains are seized even if owned by a non-US person/company, with an order to the TLD that operates in the US. With a distributed DNS system like Handshake, 'in theory' this shouldn't be possible, since it would require multiple nodes to alter a domain's DNS records vs. a central TLD authority which has to abide by US law.
It's all interesting, but it still seems we are ways off from the DNS backbone (& my browser) operating with this kind of DNS architecture. It even appears it's becoming easier to take down a domain, not at the TLD/registrar level, but more so at the hosting level (e.g. Parler)
For instance, if the browser makers all started resolving certain TLDs via an alternate network, then people could start publishing websites using domains managed by that network without needing to engage with the root DNS servers at all.
With Handshake, you run your own authoritative server (or use a hosted one) for your own name and that authoritative server's information will be obtainable on chain. No middle-man, no rent seeking.
Many root servers operate outside of the US. If the blockchain were the authority on IP addresses, then even if they blocked the US roots the others would still have it.
Even today if all the US root servers go off-line every system would find the others and use them.
But it's not -- the root servers are -- by premise here. Premise is we assume zero config results in ICANN root servers having authority. My point is that given this premise, blockchain is ineffective. You are introducing ICANN as informational MITM and censor node in between user and blockchain validation.
True, you are excluding USA, if your only goal is exclude USA then this accomplishes that goal, but if your goal is censorship-proof then this is not it.
Installing plugins is well beyond the capabilities of most people, especially since the plugins for the default browsers come from a curated store run by US companies.
I'm not even talking any wishy washy inclusiveness mumbo jumbo either. I'm talking over complicating the boot chain, over complicating memory management/models/toolchains.
Browsers are a living nightmare of complexity, and I am continuously amazed at the number of programmers who have no clue about the gory details of networking.
I've thought much this same thing myself for ages now.
Not just "complicating the hell out of things" either. Complicating the hell out of things that should be simple ( or at least should be simplified, or automated, or something ). I see a lot of tedious activities in modern computing that appear to exist purely for the sake of the tedium time-wastery factor.
The flip-side of the same coin is the over-simplifying or "dumbing down" of some things that really should stay "complicated" (and hidden behind an "expert mode" toggle) to the point of allowing willfully uneducated morons to repeatedly "shoot themselves in the foot" and justify blaming everyone and everything but themselves for their error.
That sort of "computers should be an appliance like a toaster" mentality has contributed to a culture which seems convinced they should be able to magically jump from zero to "Hacker-Man" with no effort or learning required, the very same day they decide to "learn" programming.
The Handshake design still seems like a step in the right direction, but even with sound data, it's probably years away (if ever) for DNS resolution to "flip the switch" to use this kind of architecture.
There are, however, other reasons why one might think Handshake isn't up to par just yet. Those reasons might be, for example, even though it completes the internet, making it significantly more secure and sovereign, the current implementations including DANE aren't as fast. Of course, this too [1] will be addressed with time.
There are highly technical people working on these problems with a heavy lean on making sure the experience is comparable if not better than today's expected experience. I think things will only get better from here.
Seems like you might be caught on the infinite abstraction escalator though, as who will manage the DNSNS (Domain Name Service NameSpaces) servers, and who'll take the onus for making the standard selector or display for the user to decide which lookup to consider canon for the request? This would actually be a pretty exciting development.
This would greatly complicate domain squatting (or maybe intensify/arms race it), and add a layer of resilience in the form of building up the interfaces required for users to maintain their own private DNS namespaces. This would conclusively shut the door in terms of centralized seizability of domains, since the user would in effect be empowered to be their own registrar.
You could even keep the traditional stuff seizable I guess. However, you'd be able to ask the fellow down the street if he still had the old DNS entry for x.y.z
yeah okay
seen it for 20 years now...
.001% would be absolutely enormous, and the actual start of a thing.
the design and use case of it looks laughable to me. however, it does spark the imagination.
...I am wondering if it must also be a javascript project...
> even gnutella became The Pirate Bay.
Never thought about that.
It is my understanding that under US copyright law if you own a trademark you have some grounds to sue someone else that may be using/squatting "your" domain in order to acquire it.
What would happen, though, if the owner of the domain does not live in the US, does not operate in the US, nor has any other thing to do there aside from owning a .com domain?
[1] https://en.wikipedia.org/wiki/Uniform_Domain-Name_Dispute-Re...
I firmly believe that automated DMCA-style processes (and other slow, guilty-until-proven-innocent schemes) are going to become more prevalent around the world. Defending against all of them in a timely manner will become impossible for all but the biggest of players. Smaller players will have to use services like Tor to have any semblance of reliability.
Disclaimer: We're a registered llc (not US-based), and all our activities are 100% legitimate in most jurisdictions including the US.
This is one reason I always recommend avoiding obscure ccTLDs, especially if you have no presence there.
Keep in mind, they classify, for example 'scihub' as a piracy site [1]
[1] https://www.theverge.com/2017/11/7/16618874/court-pirate-sci...
To be clear, people have given their life for this cause.
The issue is that the jurisdiction bleeds into others' jurisdictions that might have different rules on these types of things, but the US doesn't really care since it has absolute power and exercises its authority over those outside of its jurisdiction.
It's a gift to mankind but it is still technically illegal (which I would vote to change every single second of the day, but still).
I'm aware of one, and if it's the one I'm thinking of, he didn't so much "give his life for the cause" as tragically commit suicide because he couldn't see a way out of legal pressure put on him (which other people have had put on them and didn't commit suicide over; depression is a terrible disease).
Is there someone else you're referring to that I haven't heard of?
You have described someone as having a weakness and committed suicide where others didn't. For you to know what was going on in whoever you speak of's mind is interesting to me to say the least.
That said, I don't know anyone like that; so I wasn't referring to the same person as you probably.
Sorry!
There are too many to count and far too many to name.
Who were you referring to?
Something something … "forget history" … "doomed to repeat past mistakes" ~ Someone Famous
The actual title is: "US claims all .com and .net websites are in its jurisdiction" which is virtually the same as the title of the HN thread.
The literal first sentence is:
"THE US Immigration and Customs Enforcement agency (ICE) wants to take down web sites that use the .com and .net top level domains (TLD) regardless of whether their servers are based in the US."
But this title does not capture the impact of the fact.
Every RCE exploit is just the ability to change a few bytes on your computer.
wasen't this why russia/ussr didn't adhear to US ip's on their local lan?
is this not the same as FAA wanting all the control, including foreign airspace and the space whithin your ceiling?
you physically do not have control over something but still want to say it's yours. that's what this is, no?
It looks as the same as international waters.
thought it was around 40-50 miles from dry ground. but idk
edit: (hope someone vouches for you else your free game.)