Reserving the .bit TLD

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: Reserving the .bit TLD

Post by phelix »

For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
Attachments
draft-grothoff-iesg-special-use-p2p-bit-00.xml
(22.93 KiB) Downloaded 394 times
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

biolizard89
Posts: 2001
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Reserving the .bit TLD

Post by biolizard89 »

phelix wrote:For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
Thanks. I'm at a conference this week, but will review when I'm back.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: Reserving the .bit TLD

Post by phelix »

Christian's perception of the P2P TLD discussion at dnsop at IETF 93: https://gnunet.org/ietf93dnsop

Also here: https://tools.ietf.org/wg/dnsop/minutes
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
Who could have guessed they would say that explicitly? :mrgreen:

We should always have .b working parallel to .bit as suggested by vinced and if they will sell that, too, we can still go for some special characters. So I don't think it is a big deal for us.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

biolizard89
Posts: 2001
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Reserving the .bit TLD

Post by biolizard89 »

phelix wrote:For some political (?) reason they separated the drafts. Find the splice Christian created for us attached. He asks us for feedback.
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.
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.

Everything else in the draft looks okay to me, from the first read through.

Major thanks to the GNUnet guys for sticking with this.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Post Reply