On the table at 2.1.4 you need to add LATNIC that seems to be also reserved by ICANN, not sure why they missed it on the DAG but it's on every single Registry Agreement. For 2.2.4, I believe all the names listed in 2.1.4 are also reserved for second level domains and you are still missing a place where to record the names reserved by each Registry (if any) and listed on each individual Registry Agreement (http://www.icann.org/en/registries/agreements.htm), for example ABOUT.INFO, not sure if IANA has to be responsible to keep the list for them but it would be nice if they are all listed in a single place. What about tagged domain names like "bq--1k2n4h4b" or "xn--ndk061n" and one or two character names ? Regards Jorge On Tue, Jan 5, 2010 at 12:20 AM, John Levine <johnl@xxxxxxxx> wrote: > I've done another version of my reserved names draft. > > This time it proposes four registries: > > 1. Reserved and special top level names. ARPA is special, the others > are reserved. > > 2. Reserved and special second level names. EXAMPLE.COM, ORG, and > NET are reserved in the RFCs. ICANN has many more that I'd hope they > would add to the regsistry, e.g., EXAMPLE.<everything else>. I'm not > aware of any special 2LDs, but who knows what might be lurking. > > 3. Names in .ARPA. This updates the list in RFC 3172 and makes it a > registry. They're all special unless SINK.ARPA is approved in which > case it would be reserved. > > 4. Names that are special elsewhere. _service, _DOMAINKEY, etc. I'd > be delighted to take this out if the project to codify service and > protocol names agrees to include the handful of other _blah names > defined in RFCs. > > http://www.ietf.org/internet-drafts/draft-levine-reserved-names-registry-01.txt > > R's, > John > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf