The topic discussed in draft-liman-tld-names-00 has two angles, the
application angle and the DNS angle. The "requirements" can be
different depending on which angle we are looking at. From Section
11 of RFC 2181:
"The DNS itself places only one restriction on the particular labels
that can be used to identify resource records. That one restriction
relates to the length of the label and the full name. The length of
any one label is limited to between 1 and 63 octets. A full domain
name is limited to 255 octets (including the separators). The zero
length full name is defined as representing the root of the DNS tree,
and is typically written and displayed as ".". Those restrictions
aside, any binary string whatever can be used as the label of any
resource record."
"Note however, that the various applications that make use of DNS data
can have restrictions imposed on what particular values are
acceptable in their environment."
"Clients of the DNS can impose whatever restrictions are appropriate
to their circumstances on the values they use as keys for DNS lookup
requests, and on the values returned by the DNS. If the client has
such restrictions, it is solely responsible for validating the data
from the DNS to ensure that it conforms before it makes any use of
that data."
The title of the document is "Top Level Domain Name
Specification". If it is about gTLDs, some may see this as a matter
for some other organization instead of the IETF. Section 4 of the
draft requests IANA to change its registration process to use the
specification. Is the registration process set by the IETF or an
other organization?
There are some clarifications about the syntax of an Internet host
name in Section 2 of RFC 1123. The "Discussion" part of that section mentions:
"However, a valid host name can never have the dotted-decimal
form #.#.#.#, since at least the highest-level component label
will be alphabetic."
According to Section 2 of draft-liman-tld-names-00, the top level
domain label can be numeric only. This can lead to confusion if we
cannot determine whether the string is a FQDN or an IP address.
From Section 2.1 of RFC 1912 (Informational):
"You should also be careful to not have addresses which are valid
alternate syntaxes to the inet_ntoa() library call. For example 0xe
is a valid name, but if you were to type "telnet 0xe", it would try
to connect to IP address 0.0.0.14. It is also rumored that there
exists some broken inet_ntoa() routines that treat an address like
x400 as an IP address."
The word "whether" is not spelled correctly in Section of the draft.
There is ongoing work in the IDNAbis Working Group on
IDNA. draft-ietf-idnabis-protocol-10 proposes to obsolete RFC 3490.
Regards,
-sm
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
