Return-Path: <kim.davies@icann.org>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
 with ESMTP id 75A6628C1B8 for <dnsop@core3.amsl.com>;
 Fri,  6 Nov 2009 10:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VoU-lelT8uSx for
 <dnsop@core3.amsl.com>; Fri,  6 Nov 2009 10:19:21 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org
 [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id B897E3A6998 for
 <dnsop@ietf.org>; Fri,  6 Nov 2009 10:19:21 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by
 EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi;
 Fri, 6 Nov 2009 10:19:45 -0800
From: Kim Davies <kim.davies@icann.org>
To: Andrew Sullivan <ajs@shinkuro.com>, "dnsop@ietf.org" <dnsop@ietf.org>
Date: Fri, 6 Nov 2009 10:19:43 -0800
Thread-Topic: [DNSOP] draft-yao-dnsop-idntld-implementation-01.txt
Thread-Index: AcpfC4m+2YArTk4ZRUS+V68SivN/+wAAix9e
Message-ID: <C719A8BF.17EA6%kim.davies@icann.org>
In-Reply-To: <20091106180340.GS17456@shinkuro.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [DNSOP] draft-yao-dnsop-idntld-implementation-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>,
 <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>,
 <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2009 18:19:22 -0000

On 6/11/09 10:03 AM, "Andrew Sullivan" <ajs@shinkuro.com> wrote:
>=20
>> since ICANN has approved the IDN ccTLD track, in a few months, there
>> will have some IDN tld and its variant appearing in the root soon.
>=20
> I am aware that ICANN has made that decision.  It bothers me when
> ICANN makes policy decisions with technical implications without,
> apparently, having worked through all the technical implications.

To be clear, ICANN has not made a decision to insert variants in the root,
precisely because there are implications that haven't yet been resolved. Th=
e
language of the implementation that was approved at ICANN's meeting last
week reads:

"The topic of delegation of variant TLDs and management of variant TLDs has
been discussed broadly in the community. ICANN staff has proposed a few
models, none of which were agreeable across the policy and technical
community reviewing the topic.

In order to stay within ICANN's mandate for ensuring a stable and secure
operation of the Internet, the following will be the case for the Fast Trac=
k
Process launch:=20

1. Variant TLDs desired by the requester for delegation must be indicated b=
y
the requester=20

2. Desired variant TLDs will be allocated to the requester (if successfully
evaluated). This does not mean that the variant TLD will be delegated in th=
e
DNS root zone. It will be allocated to the requester in order to be reserve=
d
to the entitled manager for potential future delegation in the DNS root
zone. =20

3. A list of non-desired variants will be generated based on the received
IDN Tables.  Non-desired variants will be placed on a blocked list by ICANN=
.
Subsequent application or request for non-desired variants will be denied."

kim

