numeric (ascii) labels (was: Re: draft-liman-tld-names-00.txt and bidi)
jefsey at jefsey.com
Mon Mar 9 19:05:27 CET 2009
Thank you for this clear and refreshing KISS wording.This certainly reflects
the common lead user understanding.
2009/3/9 Eric Brunner-Williams <ebw at abenaki.wabanaki.net>
> My personal view is that broken code that isn't a defacto specification
> of the DNS, or broken specifications of things other than the DNS, need
> to go find their authors and get fixed, and not become dejure nuances of
> the "corrected" specifications of the DNS. In particular, it is
> reasonable for any zone admin, the IANA included, to make a
> registry-local rule reflecting momentary annoyance at the existence of
> well-known bugs, but that no such "rule" should be internalized to the
> DNS specs, with a vastly longer shelf-life than the random DNS
> (mis)using application.
> Yes, there is a bug (actually, a shared bug with multiple, possibly
> independent interoperable implementations of obvious brokenness), but
> 666 is no different from AAA, and a five label sequence composed of
> numeric (or octal or hex) character values is safe as houses (if ugly),
> and it is possible to constrain allocation of label sequences so that
> label sequences terminating in numeric (or octal or hex) character
> values, and having fewer than five labels, are also not incorrectly
> interpreted by this bug-set as dotted quads.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update