Re: [DNSOP] [Ext] on private use TLDS
Paul Hoffman <paul.hoffman@icann.org> Tue, 26 November 2019 17:35 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 ADA62121123 for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 09:35:45 -0800 (PST)
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 MsrPTe0lGOkL for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 09:35:44 -0800 (PST)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.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 45C5E12092E for <dnsop@ietf.org>; Tue, 26 Nov 2019 09:35:44 -0800 (PST)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa2.lax.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id xAQHZhgM024365 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Tue, 26 Nov 2019 17:35:43 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; Tue, 26 Nov 2019 09:35:41 -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; Tue, 26 Nov 2019 09:35:41 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] on private use TLDS
Thread-Index: AQHVpH/se+lGd4DIb0uPrzPO5uNgdQ==
Date: Tue, 26 Nov 2019 17:35:41 +0000
Message-ID: <4A315612-5E68-432C-9FBF-28DAC7F877C0@icann.org>
References: <B679F326-54A0-4010-BD41-F2F317417169@dnss.ec> <CAAiTEH8U=N_wkgGitxZWySBJT2TWnWHdeqA4hUs0YFgDZHv8Tw@mail.gmail.com>
In-Reply-To: <CAAiTEH8U=N_wkgGitxZWySBJT2TWnWHdeqA4hUs0YFgDZHv8Tw@mail.gmail.com>
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=_F7FB1813-4C31-4347-BF0F-AF6D4863465E"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-26_05:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/W6I3_h8Sd-VqmKZ0zFcZgVjA3Zk>
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: Tue, 26 Nov 2019 17:35:46 -0000
On Nov 26, 2019, at 9:16 AM, Matthew Pounsett <matt@conundrum.com> wrote: > I'm also persuaded by Bill's argument that the IETF has already stated that ISO 3166 has control over that bit of the namespace, and trying to take back part of it is confusing, bad form, and risky. For those who read the draft, ypu'll see that "trying to take back part of it" is not there. The same was made clear in the presentation to the WG. "If you want a private name, here's one to consider; ones like it are already being used as private names in dozens of other contexts" is far from "taking" anything. --Paul Hoffman
- [DNSOP] on private use TLDS Roy Arends
- Re: [DNSOP] on private use TLDS Jim Reid
- Re: [DNSOP] on private use TLDS Bill Woodcock
- Re: [DNSOP] on private use TLDS Ted Lemon
- Re: [DNSOP] on private use TLDS David Conrad
- Re: [DNSOP] on private use TLDS Matthew Pounsett
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] [Ext] on private use TLDS Matthew Pounsett
- Re: [DNSOP] [Ext] on private use TLDS Brian Dickson
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] [Ext] on private use TLDS Petr Špaček
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Ted Lemon
- Re: [DNSOP] on private use TLDS John Levine
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] on private use TLDS Paul Vixie
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] [Ext] on private use TLDS Paul Hoffman
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] [Ext] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Roy Arends
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Joe Abley
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS John R Levine
- Re: [DNSOP] on private use TLDS John R Levine
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Doug Barton
- Re: [DNSOP] on private use TLDS Jaap Akkerhuis
- Re: [DNSOP] on private use TLDS Brian Dickson
- Re: [DNSOP] on private use TLDS Brian Dickson
- Re: [DNSOP] on private use TLDS David Conrad
- Re: [DNSOP] [Ext] on private use TLDS David Conrad