On Nov 29, 2010, at 10:41 AM, Eric Brunner-Williams wrote:
> as there are two roots right now,
Huh?
> and my preference is for no i-d at all at this point. i don't want to be in
> cartagena next week or san francisco next spring or ... and hear someone say
> "the ietf made us do it" for some unfortunate value of "it".
Err, no. The IETF already did it. What is already happening is that people
accuse ICANN of violating the DNS specifications and/or are refusing to update
their hostname parsing software. Having personally been in discussion in which
1123's statement
"However, a valid host name can never
have the dotted-decimal form #.#.#.#, since at least the
highest-level component label will be alphabetic."
was taken to mean that the highest-level component label was required to be
alphabetic despite the existence of IDNs in the root would suggest to me that a
clarifying RFC that says you can have numbers and hyphens in TLDs would be
helpful. I believe the current draft is sufficiently sensitive to the policy
vs. protocol distinction to make its publication warranted.
I would be willing to participate in drafting a follow-on RFC that expands on
this draft, but I believe it would be useful to stop the bleeding first.
Regards,
-drc
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
