Re: Reserving the .bit TLD
Posted: Mon Jun 22, 2015 1:42 pm
For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
The first secure, decentralized, human-meaningful naming system.
https://forum.namecoin.org/
Thanks. I'm at a conference this week, but will review when I'm back.phelix wrote:For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
Who could have guessed they would say that explicitly?Some of these are attacks on the way that the DNS works
...and thus a bad idea
If you don't use the domain name space rules, you don't get a name
Don't ask the IETF to help you compete with the DNS business model
phelix wrote:For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
This is a bit unclearly worded. The threat described *is* real, since .bit can be used to point to .onion, and this would be very dangerous if, say, the .bit domain that points to a whistleblower submission .onion were leaked. Unfortunately, the way this is worded, it might give the impression that this passage is a relic of .onion being in the same draft previously. I think this should be slightly reworded to make clear that since .bit can be used to direct to anonymously routed networks, the consequences of a DNS leak can be just as bad as for .i2p or .onion.Starting on Line 363 wrote:For example, if
a DNS operator would decide to override NXDOMAIN and send
advertising to leaked .onion sites, the information leak to the
DNS would extend to the advertising server, with unpredictable
consequences.