charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: [EMAIL PROTECTED] Precedence: bulk
AM [EMAIL PROTECTED] Re: IDN Registration Integrity As an individual concerned with the future of IDNs, I would like to recommend that ICANN seriously consider incorporating a clause in their registry agreements that ensures registrants that their IDN = registrations will be valid through all changes in registry operators, through all standards' progressions, through to the day when multi-lingual domains = will be incorporated into zone files as are ASCII domains. Though confident in ICANN, the IETF, and Registry Operators, individuals = are concerned that their IDNs are the work of proprietary standards put = forth by the Registry Operators. Plug-in applications used as a link between = ASCII names and their multi-lingual equivalents further this suspicion. = Though the suspicion is false, I learned the truth only after speaking to a = number of individuals at my registrar, Verisign-GRS, ICANN and the IETF working group. Still, they could not be completely certain that "your name = would always be your name." =20 The question at hand is are my current IDN registrations so-called "ICANN-certified" registrations, as are the ASCII domains of today? In ASCII registrations, I am confident that through all registry operator changes, through any accidental deletions or transfers of my domain, I = can be assured that my domain name will be valid and governed by ICANN = policies. I would like to be assured that not just my ASCII "bq--" or "xn--" = string will be "ICANN-certified" but that its multi-lingual equivalent will = always be a constant registration, valid and governed by ICANN policies, = through to the day when multi-lingual domains will be incorporated into zone files = as are ASCII domains. Again, after learning about the issue, I am most confident that "my registration will most likely always be my registration." This is = probably not a major issue. Still, it may be worth clarification from ICANN. = Any discussions or statements by the applicable IDN committees in future meetings would be most appreciated. Thank you for your consideration. Best wishes, AM ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 27, 2003 10:45 AM Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from ["AM" <[EMAIL PROTECTED]>] > From [EMAIL PROTECTED] Wed Mar 26 18:45:02 2003 > Received: from dav42.sea1.hotmail.com ([207.68.162.100] helo=hotmail.com) > by psg.com with esmtp (Exim 3.36 #1) > id 18yNO1-000F3k-00 > for [EMAIL PROTECTED]; Wed, 26 Mar 2003 18:45:01 -0800 > Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; > Wed, 26 Mar 2003 18:45:01 -0800 > Received: from 68.63.184.139 by dav42.sea1.hotmail.com with DAV; > Thu, 27 Mar 2003 02:44:56 +0000 > X-Originating-IP: [68.63.184.139] > X-Originating-Email: [EMAIL PROTECTED] > From: "AM" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: Re: IDN Registration Integrity > Date: Wed, 26 Mar 2003 19:44:48 -0700 > Message-ID: <[EMAIL PROTECTED]> > MIME-Version: 1.0 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook, Build 10.0.4510 > Importance: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > X-OriginalArrivalTime: 27 Mar 2003 02:45:01.0077 (UTC) FILETIME=[DCC87450:01C2F40A] > X-Spam-Status: No, hits=-5.8 required=5.0 > tests=BAYES_10 > version=2.50 > X-Spam-Level: > X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) > > AM > [EMAIL PROTECTED] > Re: IDN Registration Integrity > > > As an individual concerned with the future of IDNs, I would like to > recommend that ICANN seriously consider incorporating a clause in their > registry agreements that ensures registrants that their IDN = > registrations > will be valid through all changes in registry operators, through all > standards' progressions, through to the day when multi-lingual domains = > will > be incorporated into zone files as are ASCII domains. > > Though confident in ICANN, the IETF, and Registry Operators, individuals = > are > concerned that their IDNs are the work of proprietary standards put = > forth by > the Registry Operators. Plug-in applications used as a link between = > ASCII > names and their multi-lingual equivalents further this suspicion. = > Though > the suspicion is false, I learned the truth only after speaking to a = > number > of individuals at my registrar, Verisign-GRS, ICANN and the IETF working > group. Still, they could not be completely certain that "your name = > would > always be your name." =20 > > The question at hand is are my current IDN registrations so-called > "ICANN-certified" registrations, as are the ASCII domains of today? In > ASCII registrations, I am confident that through all registry operator > changes, through any accidental deletions or transfers of my domain, I = > can > be assured that my domain name will be valid and governed by ICANN = > policies. > I would like to be assured that not just my ASCII "bq--" or "xn--" = > string > will be "ICANN-certified" but that its multi-lingual equivalent will = > always > be a constant registration, valid and governed by ICANN policies, = > through to > the day when multi-lingual domains will be incorporated into zone files = > as > are ASCII domains. > > Again, after learning about the issue, I am most confident that "my > registration will most likely always be my registration." This is = > probably > not a major issue. Still, it may be worth clarification from ICANN. = > Any > discussions or statements by the applicable IDN committees in future > meetings would be most appreciated. > > Thank you for your consideration. > > > > Best wishes, > AM > >
