> > [ Moderators note: Post was moderated, either because it was posted by > a non-subscriber, or because it was over 20K. > With the massive amount of spam, it is easy to miss and therefore > delete relevant posts by non-subscribers. Please fix your > subscription addresses. ] > > > > On Tuesday, February 01, 2005 06:43:09 PM -0500 The IESG > <iesg-secretary@xxxxxxxx> wrote: > > > The IESG has received a request from the DNS Extensions WG to consider > > the following document: > > > > - 'Domain Name System (DNS) Case Insensitivity Clarification ' > > <draft-ietf-dnsext-insensitive-05.txt> as a Proposed Standard > > > The document in question states: > > One typographic convention for octets that do not correspond to an > ASCII printing graphic is to use a back-slash followed by the value > of the octet as an unsigned integer represented by exactly three > decimal digits. > > > While this is literally true, the _common_ convention is to use a backslash > followed by the value of the octet as an unsigned integer represented by > exactly three _octal_ digits. This is the syntax used by programming > languages like C and perl. For example, ASCII ESC (0x1b) is represented as > \033, not \027. The C convention also has \t, \r, \f, \n none of which are the special in domain labels. We are not trying to change conventions here. It is irrelevent that C has a different convention. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@xxxxxxx _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf