>> 4. It's been pointed out that the maintenance of the special use names >> registry is complicated by the fact that people used to be able to >> assume the root zone was relatively stable, and this assumption has >> become less defensible. (ICANN is not currently accepting new >> applications for TLDs, and has no announced schedule for opening an >> application window again, but has said they plan a future application >> round.)
The current round is far from over. There are nearly 700 gTLDs currently in the root, and about 600 more names with applications still in process. There are still 8 names with pending auctions among multiple applicants, and 21 that are "on hold" for various reasons. This last group includes .corp, .home, and .mail. >> Is there something that the IETF should be doing to help DNS >> implementers and operators handle this change in the environment? > >Yes - and I've not been following the effort closely, but I believe it's >being done over in DBOUND in their work to replace the Public Suffix List. DBOUND is indeed trying to come up with something less bad than the current PSL, but ... >Because (AIUI) DBOUND is intended to specify security-relevant zone cuts >*in DNS* using it to specify names that are reserved in DNS but not _in_ >DNS might come out a little weird... but it seems like the most relevant >place to at least take the idea and discuss it. Sorry, that's just wrong. DBOUND has nothing whatsoever to do with zone cuts or reserved names. There's plenty of ambiguity about what we're trying to do, but neither of those are on or even near the table. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
