Re: [DNSOP] Looking for IANA registry for --xn

Robert Edmonds <edmonds@mycre.ws> Thu, 06 October 2016 20:22 UTC

Return-Path: <edmonds@mycre.ws>
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 884A9129408 for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 13:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.898
X-Spam-Level:
X-Spam-Status: No, score=-4.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-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 RvII9kmiPDbz for <dnsop@ietfa.amsl.com>; Thu, 6 Oct 2016 13:22:58 -0700 (PDT)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 147C01293DF for <dnsop@ietf.org>; Thu, 6 Oct 2016 13:22:58 -0700 (PDT)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 3872812C0F5E; Thu, 6 Oct 2016 16:22:57 -0400 (EDT)
Date: Thu, 6 Oct 2016 16:22:57 -0400
From: Robert Edmonds <edmonds@mycre.ws>
To: dnsop@ietf.org
Message-ID: <20161006202257.qt4jfiwhbe24esze@mycre.ws>
References: <CAMm+LwjcC6pJ+-LzwGyoG=VVzT_QQ9UrvM3LcZM1121XqCccow@mail.gmail.com> <1329930975.314237.1475774676486@mail.yahoo.com> <CAMm+LwhnGFR6hqD2PbXyq4OiyLnfAy1K9TbaesmX3A7XVyCiiw@mail.gmail.com> <CAF4+nEGg9zGNzUkGz2_NgrxJnia7Wax6i_f3B-VNZw+1=KAEnA@mail.gmail.com> <F0F6F02A-F237-4D41-98D5-807B323DD3A3@rfc1035.com> <CAF4+nEERTNc0MuycRZLipahsoAWR7riMQB1BfD8qeu54KF0+0A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAF4+nEERTNc0MuycRZLipahsoAWR7riMQB1BfD8qeu54KF0+0A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0ePfGWOdKpEV4x4Y4nCqRGhWjE4>
Subject: Re: [DNSOP] Looking for IANA registry for --xn
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Oct 2016 20:22:59 -0000

Donald Eastlake wrote:
> Sure, you can consider the root zone to be the registry for TLDs but the
> point is the xn-- labels are recommended to be interpreted specially at the
> user interface at all levels...

Nor would this say anything about "CCHH" prefixed labels in general.

At the TLD level there seems to be an agreement at least(?) for new
gTLDs to reserve all "CCHH" prefixes in delegated names other than
xn--:

    SPECIFICATION 6

    REGISTRY INTEROPERABILITY AND CONTINUITY SPECIFICATIONS

    1. Standards Compliance

    1.1. DNS.  Registry Operator shall comply with relevant existing
    RFCs and those published in the future by the Internet Engineering
    Task Force (IETF), including all successor standards, modifications
    or additions thereto relating to the DNS and name server operations
    including without limitation RFCs 1034, 1035, 1123, 1982, 2181,
    2182, 2671, 3226, 3596, 3597, 4343, and 5966.   DNS labels may only
    include hyphens in the third and fourth position if they represent
    valid IDNs (as specified above) in their ASCII encoding (e.g.,
    “xn--ndk061n”).

    https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm

-- 
Robert Edmonds