In message <[email protected]>, Stephane Bortzmeyer writes: > On Wed, Nov 17, 2010 at 11:20:56AM +0000, > Tony Finch <[email protected]> wrote > a message of 63 lines which said: > > > That is blatantly broken. > > Yes. > > > There is no need for any heuristic to tell IP addresses and host > > names apart. > > To elaborate on that: if a program receives the string 192.0.2.4 and > the TLD ".4" is delegated, the tie is broken by application of a > requirment of RCF 1123 "The host SHOULD check the string syntactically > for a dotted-decimal number before looking it up in the Domain Name > System." > > So, there is no ambiguity: 192.0.2.4 is always an IP address, even if > ICANN delegates ".4".
Except there are plenty of applications that don't do this so it is a real problem. > [My point is that draft-liman-tld-names is probably unecessary but, > anyway, it should not introduce new rules such as forbidding digits in > ASCII TLDs. A simpler document saying "The sentence 'the highest-level > component label will be alphabetic' in RFC 1123 was a statement of > fact at this time, NOT a normative protocol requirment." would have > been sufficient.] > > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
