RE: Single-letter names (was: Re: Update of RFC 2606 based on therecent ICANN changes?)

2008-07-08 Thread John C Klensin
--On Monday, 07 July, 2008 09:47 -0700 Ted Hardie <[EMAIL PROTECTED]> wrote: > At 9:25 AM -0700 7/7/08, [EMAIL PROTECTED] wrote: >> > However, many concepts in modern Chinese >> dialects require multiple syllables to express them and >> therefore multiple characters to write them. So there isn't

Re: Single-letter names

2008-07-08 Thread Eric Brunner-Williams
Ted, As Edmond pointed out, the position at present is that: "Single and two-character U-labels on the top level and second level of a domain name should not be restricted in general." I personally expect that for applications made as "IDN ccTLD", whether "fasttrack" or not, will be reviewed

RE: Single-letter names (was: Re: Update of RFC 2606 based on therecent ICANN changes?)

2008-07-07 Thread Ted Hardie
At 9:25 AM -0700 7/7/08, [EMAIL PROTECTED] wrote: > > However, many concepts in modern Chinese >dialects require multiple syllables to express them and >therefore multiple characters to write them. So there isn't >really a one to one mapping of word, syllable, concept as >many people suppose. Whil

RE: Single-letter names (was: Re: Update of RFC 2606 based on therecent ICANN changes?)

2008-07-07 Thread michael.dillon
> Alphabetic scripts such as Latin mostly represent sounds used > to make up words. While one can certainly find some > legitimate single-character words (such as the article "a" or > the personal pronoun "i") And lest someone might think that this curiosity of single character words only app

RE: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-07 Thread Edmon Chung
ECTED] On Behalf Of Vint Cerf > Sent: Saturday, July 05, 2008 3:33 AM > To: John C Klensin > Cc: James Seng; [EMAIL PROTECTED]; ietf@ietf.org; Lyman Chapin > Subject: Re: Single-letter names (was: Re: Update of RFC 2606 based on the > recent ICANN changes?) > > john, > &g

Re: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-07 Thread Vint Cerf
oretic reasons to insist on more information in domain name labels in order to lower the risk of false positive matches to be fully as "technical" as something that would have obvious lower-level network consequences. Others --frankly especially those who see commercial advantage in getting

Re: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-07 Thread William Tan
o set policy. Even though the mismatches > would obviously not cause the network to explode or IP to stop > working, at least some of us consider the informational > retrieval and information theoretic reasons to insist on more > information in domain name labels in order to lower the risk

RE: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-04 Thread JFC Morfin
I feel that Edmon's report of the ICANN/GNSO point of view and the positions of James Seng are shared by most of the groups we relate with (Internet @large, open roots, ISO lobbies, Multilinc, MINC, Eurolinc, ISOC France, ccTLDs, etc.). If this WG does not think they are technically adequate th

Re: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-04 Thread John C Klensin
--On Friday, 04 July, 2008 15:01 -0400 William Tan <[EMAIL PROTECTED]> wrote: > John, > > To add to your point, one should also consider the question of > embedded semantics in a single-character label. > > Alphabetic scripts such as Latin mostly represent sounds used > to make up words. While

Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

2008-07-04 Thread John C Klensin
ing that would have obvious lower-level network consequences. Others --frankly especially those who see commercial advantage in getting single-letter names-- have argued that this position is just a policy decision in disguise. Note that, with slight modifications, the second and third arguments apply