>>>>> Stephane Bortzmeyer <[email protected]> writes: […]
> But there is another way, register the TLD in the special TLD > registry: > http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xml > Technically, it would be a better fit. And it's much cheaper :-) > The rules for this registry are in a document which will be published > as a RFC any day now. Basically, you need to write a standard RFC or > to get the approbation of IESG. If you are Apple (the first > registration, for its .local), it helps. ACK, thanks for the pointer! Now, however, I see that there're at least /two/ flavors of TLD's as employed by P2P networks. More widespread are “pseudo” TLD's, which aren't intended to map DNS names to one or more conventional DNS resource records. Instead, they name “hosts” (or other entities) in a completely protocol-specific manner (such as: via a public key digest.) Examples of such are Tor's .onion, GNUnet's .zkey, etc. (The .uucp beast of the days long gone also belongs to this category, BTW.) The other TLD's allow for conventional DNS zones, although without the usual delegation rules inherent to the DNS design. Such is the GNUnet's user-managed .gnunet hierarchy, as well as the soon to be standardized mDNS' .local, and perhaps other. It may make sense to consider these two cases separately of each other, and perhaps reserve one TLD's for each of the categories (such as, e. g., .app or .asei, for application-specific entity identifiers, vs. .dec, .site, or .ana for “alternative naming authority”, “decentralized”, “site-specific” zones.) Alternatively, given enough application-specific DNS RR types, these could be under a single TLD. (Though, of course, such a decision won't make AAAA or A queries to an .onion.app domain name something sensible in some magical way.) -- FSF associate member #7257 _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
