[DNSOP] new version submitted for draft-arends-private-use-tld

Roy Arends <roy.arends@icann.org> Sat, 02 May 2020 14:09 UTC

Return-Path: <roy.arends@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 1E8BA3A1277 for <dnsop@ietfa.amsl.com>; Sat, 2 May 2020 07:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 aqPrMkyZUvaa for <dnsop@ietfa.amsl.com>; Sat, 2 May 2020 07:09:25 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 282A53A1279 for <dnsop@ietf.org>; Sat, 2 May 2020 07:09:25 -0700 (PDT)
Received: from PFE112-VA-1.pexch112.icann.org (out.east.pexch112.icann.org [162.216.194.7]) by ppa5.dc.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 042E9MGd011104 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Sat, 2 May 2020 14:09:23 GMT
Received: from PMBX112-E1-VA-1.pexch112.icann.org (162.216.194.24) by PMBX112-E1-VA-1.pexch112.icann.org (162.216.194.24) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 2 May 2020 10:09:18 -0400
Received: from PMBX112-E1-VA-1.pexch112.icann.org ([162.216.194.24]) by PMBX112-E1-VA-1.PEXCH112.ICANN.ORG ([162.216.194.24]) with mapi id 15.00.1497.006; Sat, 2 May 2020 10:09:18 -0400
From: Roy Arends <roy.arends@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: new version submitted for draft-arends-private-use-tld
Thread-Index: AQHWIItE05+QJLlxTkKndWwLM3CT3g==
Date: Sat, 2 May 2020 14:09:18 +0000
Message-ID: <91A33B60-7B70-4231-8ED8-662CFBB70445@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_9EBE6BDB-6DF1-4459-8926-B877904A7742"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-05-02_07:2020-05-01, 2020-05-02 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gyE9Eef1fam5FFZ0KITgYu6RinI>
Subject: [DNSOP] new version submitted for draft-arends-private-use-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 02 May 2020 14:09:28 -0000

Hi,

Ed and I just submitted a new version of our private-use TLD draft. 

https://www.ietf.org/id/draft-arends-private-use-tld-01.txt

This draft has substantial more information than the first draft. It explains that a private-use namespace does not exist, why it is needed, and how a namespace aligned with the user-assigned alpha-2 code elements in the ISO-3166-1 standard can be used as private-use namespace.

It contains plenty of examples of how user-assigned code elements are used in the field, including other ISO standards, the UN, UNICODE, CAB/forum, and the IETF itself.

This new version came about after fruitful discussions with peers inside and outside the IETF. Most discussions were productive. This has lead to the removal of the advice/example to use ZZ, as it was distracting from the point of the draft: these two-letter top level domains are available for private-use. 

Warmly,

Roy