I am thinking this FYI is important for the users and administrators to be aware of if the WG go with any laguage tagged scheme at all. Since:
It may lead to inconsistent exception conditions due to changes in language specific normalization procedure. For example, a UCS code point A in language tag T is excluded in Version X, as there is no blocking for any UCS code points in place yet. Due to upgrade Version X+1, T(A) has been newly included tagged code blocks, then an input contains A fail in Version X, but will succeed in Version X+1. Due to failure in X will be coded with a defaulted ACE as a legal name, then the same input will not be fail in X+1, an inconsistency will resulted. If the WG has consensus on NOT using language tag mechanism, it is better to voice this and let VeriSign users go ahead. I am upgrade idn-map draft to address this problem too, I need to know the above too, so that I don't need work for this group any more. Thank you all for saving my time. Liana On Fri, 28 Sep 2001 16:18:12 -0400 [EMAIL PROTECTED] (J. William Semich) writes: > Haven't heard anything on the IDN list since Sept 1, so I'm wondering > if > maybe the list has gone dark? > > FYI, this just in from Verisign > > -- Bill Semich > > > >X-Authentication-Warning: imx3.pvt.lks.verisign-grs.net: majordomo > set > >sender to [EMAIL PROTECTED] using -f > >Reply-To: <[EMAIL PROTECTED]> > >From: "VeriSign Global Registry Services" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Subject: [IDNList] Registrar Advisory: AMC-ACE- Z in the zones > >Date: Fri, 28 Sep 2001 14:10:00 -0400 > >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) > >Importance: Normal > >Sender: [EMAIL PROTECTED] > >X-MIME-Autoconverted: from 8bit to quoted-printable by > verisign-grs.com > id > >OAA23352 > > > >To All IDN-Certified Registrars: > > > >VeriSign Global Registry Services (GRS) intends to move forward in > the > >Internationalized Domain Name Testbed by placing the IDNs directly > into > the > >.com, .net and .org zones. The zones will be populated with the > AMC-ACE-Z > >v0.3.1 representation of the IDNs. Registrars do not need to > modify > any of > >their current registration processes to support this change. All > existing > >IDNs originally registered with RACE will be valid under the > AMC-ACE-Z > >encoding. > > <snip> > > > > >
