--- draft-liman-tld-names-04-orig.txt 2010-11-21 18:51:33.000000000 -0800 +++ draft-liman-tld-names-04.txt 2010-11-21 19:30:48.000000000 -0800 @@ -255,24 +255,24 @@ #.#.#.#, since at least the highest-level component label will be alphabetic.' [Section 2.1] - Some implementers may have understood the above phrase 'will be + Some implementers may have incorrectly understood the above phrase 'will be alphabetic' to be a protocol restriction. Neither [RFC0952] nor [RFC1123] explicitly states the reasons for these restrictions. It might be supposed that human factors were a consideration; [RFC1123] appears to suggest that one of the reasons was to prevent confusion between dotted-decimal IPv4 addresses and - host domain names. In any case, it is reasonable to believe that the - restrictions have been assumed in some deployed software, and that - changes to the rules should be undertaken with caution. + host domain names. The Internationalised Domain Names in Applications 2008 specification (IDNA2008) [RFC5891] [RFC5892] provides a protocol for encoding Unicode strings in DNS-Labels. The Unicode string used by applications is known as a U-Label; its corresponding encoding in the - DNS is known as an A-Label. The terms A-Label and U-Label are used - in this document as defined in [RFC5890]. Valid A-Labels always - contain non-alphabetic characters. + DNS is known as an A-Label. + In addition to alphabetics valid A-Labels may contain + digits and always contain the minus sign. For example at the time + of this writing XN--P1AI is the Country-code top-level domain + designated for Russian Federation. @@ -454,7 +454,7 @@ While this document makes no requests of the IANA, management of the root zone is an IANA function. This document expands the set of strings permitted for delegation from the root zone, and hence - establishes new limits for the corresponding IANA policy. + establishes new limits for the corresponding IANA procedures.