I just describe the possible methods even it is very strange. For CJK code point switch off temporary , another approach may be that we can let code point of Hangel and Kana go forward but let ideograph part (Han character) delayed , so Korean and Japan can use their own pure national language to reduce the troubles come from delay.
L.M.Tseng ----- Original Message ----- From: "ben" <[EMAIL PROTECTED]> To: "cc-www.com (Ben)" <[EMAIL PROTECTED]>; "tsenglm@計網中心.中大.tw" <[EMAIL PROTECTED]>; "Kenny Huang" <[EMAIL PROTECTED]>; "IETF-IDN" <[EMAIL PROTECTED]>; "Paul Hoffman / IMC" <[EMAIL PROTECTED]> Sent: Tuesday, January 22, 2002 12:21 AM Subject: Re: [idn] Prohibit CDN code points > Hi Tseng, > > Actually... now that I read your suggestion more carefully, are you > suggesting to change Verisign's current ASCII(.com) to ML(.com)? > Hmmmm... what a strange suggestion. > > Thanks, > Ben > > ----- Original Message ----- > From: "cc-www.com (Ben)" <[EMAIL PROTECTED]> > To: "tsenglm@計網中心.中大.tw" <[EMAIL PROTECTED]>; "Kenny Huang" > <[EMAIL PROTECTED]>; "IETF-IDN" <[EMAIL PROTECTED]>; "Paul Hoffman > / IMC" <[EMAIL PROTECTED]> > Sent: Monday, January 21, 2002 11:10 AM > Subject: Re: [idn] Prohibit CDN code points > > > > Hi Tseng / Paul, > > > > I like Tseng's idea for a new type of ML-gTLD very very very very > very > > much! :-) > > > > Unfortunately, I don't think it answers the problem Paul and I > brought > > up- which is what to do about the *current situation* with the gTLD > > that has registered domains in Chinese, Japanese, Korean (even a > > mixture of them) if infact we want to prohibit CDNs and let the > other > > IDNs move forward. > > > > Thanks, > > Ben > > > > > > > > ----- Original Message ----- > > From: "tsenglm@計網中心.中大.tw" <[EMAIL PROTECTED]> > > To: "ben" <[EMAIL PROTECTED]>; "Kenny Huang" <[EMAIL PROTECTED]>; > > "IETF-IDN" <[EMAIL PROTECTED]>; "Paul Hoffman / IMC" > <[EMAIL PROTECTED]> > > Sent: Monday, January 21, 2002 9:58 AM > > Subject: Re: [idn] Prohibit CDN code points > > > > > > > It is possible if we assume the ccTLD implied the language used . > > So, they > > > can be treated with different way based on the ccTLD name implied > > language. > > > Now, only gTLD has this problems. If only ASCII ".com" is used, > > it can > > > not identify which language is used in hostname part. But if > > ML-gTLD is > > > available , the ML(com) can be classfied by the implied language > > characters > > > in ML(com). Especially , ML(gTLD) is very small and can be > > predefined . > > > > > > L.M.Tseng > > > ----- Original Message ----- > > > From: "Paul Hoffman / IMC" <[EMAIL PROTECTED]> > > > To: "ben" <[EMAIL PROTECTED]>; "Kenny Huang" > <[EMAIL PROTECTED]>; > > > "IETF-IDN" <[EMAIL PROTECTED]> > > > Sent: Monday, January 21, 2002 2:00 AM > > > Subject: Re: [idn] Prohibit CDN code points > > > > > > > > > > At 12:30 PM -0500 1/20/02, ben wrote: > > > > >Is it possible to let the > > > > >Japanese and Korean domains names go forward and prohibit > Chinese > > > > >domain names? > > > > > > > > No, and that one of the main problems that the CDN community > > faces. > > > > In the ISO/IEC 10646 repertoire (which is the same as the > Unicode > > > > repertoire), it is impossible to differentiate between Chinese > > > > characters and Korean characters and Japanese characters. Thus, > > any > > > > proposal to remove the characters for one language removes them > > for > > > > all. > > > > > > > > --Paul Hoffman, Director > > > > --Internet Mail Consortium > > > > > > > > > > > > > >
