Re: [DNSOP] Status of IDNA

Francisco Arias <francisco.arias@icann.org> Thu, 13 April 2017 01:22 UTC

Return-Path: <francisco.arias@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B16E6128D19 for <dnsop@ietfa.amsl.com>; Wed, 12 Apr 2017 18:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8Qu1G6zh3OW for <dnsop@ietfa.amsl.com>; Wed, 12 Apr 2017 18:22:54 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 278C3126C7B for <dnsop@ietf.org>; Wed, 12 Apr 2017 18:22:54 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 12 Apr 2017 18:22:52 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Wed, 12 Apr 2017 18:22:51 -0700
From: Francisco Arias <francisco.arias@icann.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "dnsop@ietf.org" <dnsop@ietf.org>
CC: Sarmad Hussain <sarmad.hussain@icann.org>
Thread-Topic: [DNSOP] Status of IDNA
Thread-Index: AQHSs/R3YXI6VcxUDkOxq+4Fv48OEQ==
Date: Thu, 13 Apr 2017 01:22:51 +0000
Message-ID: <66429AE7-8934-437C-8267-943E7C6EED47@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E95B686224554443BCD59775CE3D3E6C@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/L-L6Y6iPdsBk1pN25VCPw80SW9I>
Subject: Re: [DNSOP] Status of IDNA
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 13 Apr 2017 01:22:56 -0000

The draft guidelines are still in public comment until 2 May at https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en. I think since, at least, the current version (3.0 published in 2011) IDNA 2008 is the rule for new registrations. I believe both the current version and the draft that is public comment grandfather existing IDNA 2003 registrations.

-- 
Francisco

On 4/12/17, 4:18 PM, "DNSOP on behalf of Andrew Sullivan" <dnsop-bounces@ietf.org on behalf of ajs@anvilwalrusden.com> wrote:

    >Is there an ongoing effort to reconcile application behavior?  Different
    >TLDs appear to expect different IDNA implementations.
    
    ICANN's rules require IDNA2008.  There is a new version of the
    guidelines out -- I can't recall whether the public comment is closed.
    Many ccTLDs voluntarily conform to the guidelines also, but ICANN
    can't compel it.  And of course ICANN has no control of other things
    down the tree.