To: "Hollenbeck, Scott" <email@example.com>
From: George Belotsky <firstname.lastname@example.org>
Date: Mon, 16 Apr 2001 16:44:43 -0400
In-Reply-To: <DF737E620579D411A8E400D0B77E671D75094C@regdom-ex01.prod.netsol.com>; from email@example.com on Fri, Apr 13, 2001 at 10:25:40PM -0400
Subject: Re: A Comment on 9.  of the requirements document.
Thanks for making this change, Scott. George. On Fri, Apr 13, 2001 at 10:25:40PM -0400, Hollenbeck, Scott wrote: > > -----Original Message----- > > From: George Belotsky [mailto:firstname.lastname@example.org] > > Sent: Friday, April 13, 2001 7:25 PM > > To: Hollenbeck, Scott > > Cc: email@example.com > > Subject: Re: A Comment on 9.  of the requirements document. > > > > [snip] > > > In sum, RFC 1035 says 2 things: > > > > (i) store names into DNS as per the ABNF in 2.3.1. > > (ii) when implementing DNS software, ensure that it > > will be able to support all 8 bits per character > > (except the null) as per 2.3.3. > > Last time I checked, this WG was dealing with (i) and not (ii), and the ABNF > very clearly defines domain and host names using 7-bit US-ASCII characters. > However, in the interest of concluding this discussion I am willing to > concede that the requirement text saying "the encoding of Internet host and > domain names in the DNS" might be misunderstood since 1035 does also > describe labels in more liberal terms. How about this for a rewording: > > "[RFC1035] describes Internet host and domain names using characters > traditionally found in a subset of the 7-bit US-ASCII character set." > > If anyone objects, please include single-sentence alternative wording that > explains why there is an internationalization issue with domain and host > names. > > <Scott/> -- ----------------------------- George Belotsky Senior Software Architect Register.com, inc. firstname.lastname@example.org 212-798-9127 (phone) 212-798-9876 (fax)