Re: [DNSOP] Thoughts on the top level name space

Alain Durand <alain.durand@icann.org> Tue, 07 July 2015 23:00 UTC

Return-Path: <alain.durand@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2EF1B29F6 for <dnsop@ietfa.amsl.com>; Tue, 7 Jul 2015 16:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 KtaXggwwEXQN for <dnsop@ietfa.amsl.com>; Tue, 7 Jul 2015 16:00:44 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF50E1B2A30 for <dnsop@ietf.org>; Tue, 7 Jul 2015 16:00:43 -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.1044.25; Tue, 7 Jul 2015 16:00:41 -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.1044.021; Tue, 7 Jul 2015 16:00:41 -0700
From: Alain Durand <alain.durand@icann.org>
To: "steve@shinkuro.com" <steve@shinkuro.com>, dnsop WG <dnsop@ietf.org>
Thread-Topic: [DNSOP] Thoughts on the top level name space
Thread-Index: AQHQtxWSGRCCGWg1Y0aLbOCi0zAIxZ3Q1ZuA
Date: Tue, 07 Jul 2015 23:00:41 +0000
Message-ID: <D1C1951F.7A30%alain.durand@icann.org>
References: <0C60FA46-50FB-4F4A-9ABA-6CB2953305D8@shinkuro.com>
In-Reply-To: <0C60FA46-50FB-4F4A-9ABA-6CB2953305D8@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3519140439_2883247"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/KZSewg4ORbRbxUzAvzh6LcdipVI>
Subject: Re: [DNSOP] Thoughts on the top level name space
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Jul 2015 23:00:47 -0000

Putting the focus on this part of Steve¹s original email for now:

On 7/5/15, 7:26 AM, "DNSOP on behalf of Steve Crocker"
<dnsop-bounces@ietf.org on behalf of steve@shinkuro.com> wrote:

>
>o ICANN speaks indistinctly about subset 5.
>
>o Does the IETF have a process for moving a name from subset 2 to subset
>4?

Ideally, I would argue we may not need such a process. Beside
experimentation with strings like xx-Š, subset 2 should be empty or, at
least, not ground for consideration to move to subset 4. So, beside
grand-fathering a few strings, what is needed is a process that is less
ambiguous and simpler to evaluate than RFC6761 to reserve strings in
subset 4. Maybe something along the lines of IETF validates the technical
merits of the proposal and ICANN validates the suggested nameŠ That leads
us to the next point:

>o A process for coordination between the IETF and ICANN regarding subsets
>2, 4 and 5 would be helpful.


RFC6761 does not say anything about such a coordination process. We have
now learned a lot going through this round of 6761 candidates, so it is
time to work on 6761bis, with, among other things, this coordination
between ICANN and IETF on the agenda.

Alain.