IETF Logo Mail Archive

Re: [DNSOP] [Ext] on private use TLDS

Paul Hoffman <paul.hoffman@icann.org> Thu, 28 November 2019 22:15 UTC

Return-Path: <paul.hoffman@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 6F36B1208D5 for <dnsop@ietfa.amsl.com>; Thu, 28 Nov 2019 14:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level:
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_FMBLA_NEWDOM=1.499, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 H69Y2PGADFEv for <dnsop@ietfa.amsl.com>; Thu, 28 Nov 2019 14:15:09 -0800 (PST)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 5FE9F120033 for <dnsop@ietf.org>; Thu, 28 Nov 2019 14:15:09 -0800 (PST)
Received: from PFE112-CA-2.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) by ppa4.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id xASMF5p1019299 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 28 Nov 2019 22:15:07 GMT
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 Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 28 Nov 2019 14:15:03 -0800
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.1497.000; Thu, 28 Nov 2019 14:15:03 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Doug Barton <dougb@dougbarton.us>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] on private use TLDS
Thread-Index: AQHVpjlIPLmGqDu2mUWkWECnhdQzpQ==
Date: Thu, 28 Nov 2019 22:15:03 +0000
Message-ID: <FB09EF15-3F54-4EA2-B5EC-09D0D9B4DA30@icann.org>
References: <71ad677a-8c88-8916-fe02-7d0d8ae930b9@dougbarton.us> <E536A699-37A9-41D8-8ED1-10E116E18E4C@fugue.com> <793c7fc2-9f52-87ed-5ad1-99b3d03d3765@dougbarton.us>
In-Reply-To: <793c7fc2-9f52-87ed-5ad1-99b3d03d3765@dougbarton.us>
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.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_1B82E594-3EFB-48AC-B3FF-849FB88F6EDD"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-28_07:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yORZmacA8m_TyMF8ytisYgnTI38>
Subject: Re: [DNSOP] [Ext] on private use TLDS
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: Thu, 28 Nov 2019 22:15:10 -0000

On Nov 28, 2019, at 1:30 PM, Doug Barton <dougb@dougbarton.us> wrote:
> The IETF and ICANN share a sandbox on many topics, including the root zone. (But of course you already knew that.) And if you don't think ICANN has promised to not delegate HOME, CORP, and MAIL; you didn't read the reference I provided. Or, if you did read it, and still have concerns, that is that much more reason to work with them on a draft that memorializes it.

That document (https://www.icann.org/en/system/files/files/name-collision-mitigation-01aug14-en.pdf) doesn't have such a promise. And, yes, I did read it. (Disclaimer: I also wrote it.)

--Paul Hoffman

v2.23.0 | Report a Bug | By Email