Re: [DNSOP] on private use TLDS
Matthew Pounsett <matt@conundrum.com> Tue, 26 November 2019 17:17 UTC
Return-Path: <matt@conundrum.com>
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 66E891210ED for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 09:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.com
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 IfB2QeFx26n4 for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 09:17:08 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09EF11210E6 for <dnsop@ietf.org>; Tue, 26 Nov 2019 09:17:07 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id k15so21160870lja.3 for <dnsop@ietf.org>; Tue, 26 Nov 2019 09:17:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k5nux7GMpjZNb+RDMIFG4FcI1AVRHT58/jHsw1lHkho=; b=DREoFeSGvw51uaxoELz3xsdCaFw7Ab2F5yckwKH/SzPy6urZg05ePodPxMmRNP67wt yR08Jwk+Mzy8pkzjBCazKKdGjvuG04fOXtEJkYMc/Qvb74F7T9CF2zZsQOhLu8qNydnu KDlfhswDN/AKV5gJLVp7iBtw8v/MimhrmCq4ycI2zEBymrRwNZPeOj8FYEJfONtdPNjx B7wWB0q2v1U5OwLOKkBGifuJSARVml+aYvrqw+a2mWwUJjF/4VoHa66Wq6264eG1rJ2B yqq/Kk/GvTBV6tE4qjocxhaCT+QFH2m4FTsOnaoVoCeAwwNHq0phvaxKqiap0MlOk9qZ 4E1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k5nux7GMpjZNb+RDMIFG4FcI1AVRHT58/jHsw1lHkho=; b=PtyLMbwqhVoSDwWD7FgmEVg3fGX88iyw9ALD/7jfrHFDRzf3eyt+7sgRnFOg7Dt9eV ZD6FY1owSC7sobjLZgdqULtkohxbUcYtm/UBlA3ZyxGfEtbm+ZZqZ/+w1SNgJmbtHox7 +A2QmPdxPvnz5DALJryvZq/p1hWjMUBHqbXpT1wsTuu1kkzQJSPkoD6x4Vgbi/Zr3NDR vRTfGYCLGRQuZ2VEEMUAoP4VT7DjVYxkEBfDfZzgx3VuxuvJU8YN9Xyndtbl7I/3naag wElq975G1vXn0gkyPulIv2WF+SJfkC4Qn6K9CDf8FoUe8byB2L8wvXTZ5Z4ENkvy5SSM xiLA==
X-Gm-Message-State: APjAAAWYO8Ple/IbKwaZL8gMTmIfyKruCwbOJfOEuqwoJvw3fcGE3Ayx fgGhdP9sn37FlQwiOYxy/AInyNChohUdhc6qD9++j2Mpee4=
X-Google-Smtp-Source: APXvYqwcyTCX+iA9ge/qIFeLLLgeBWjXbyGDqEjQkPcwczSe9AgNFJdTbJEYaAP+JbvmHViqZXrWkjR2JoQZtUsAu2M=
X-Received: by 2002:a2e:2c1a:: with SMTP id s26mr27880266ljs.239.1574788626016; Tue, 26 Nov 2019 09:17:06 -0800 (PST)
MIME-Version: 1.0
References: <B679F326-54A0-4010-BD41-F2F317417169@dnss.ec>
In-Reply-To: <B679F326-54A0-4010-BD41-F2F317417169@dnss.ec>
From: Matthew Pounsett <matt@conundrum.com>
Date: Tue, 26 Nov 2019 12:16:54 -0500
Message-ID: <CAAiTEH8U=N_wkgGitxZWySBJT2TWnWHdeqA4hUs0YFgDZHv8Tw@mail.gmail.com>
To: Roy Arends <roy@dnss.ec>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6839d0598430c4f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ic7ryFOWTGmxg-byairDwo4W-dQ>
Subject: Re: [DNSOP] 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:17:10 -0000
On Tue, 26 Nov 2019 at 05:19, Roy Arends <roy@dnss.ec> wrote: > “ZZ” was used in my presentation as an example. Since this bikeshedding is > siphoning attention from the important part of the discussion, I’ll try to > re-focus on the question here: > > "Is it safe to use ISO3166-1 Alpha-2 code elements from the User Assigned > range as top level domains for my own private use?" > Thanks for the context, Roy. Speaking as someone who was not at the IETF meeting this week, I found the earlier thread confusing. But, it looks like the assumed context of bringing up "what can we use this for" as "can we assign this string in an RFC?" was correct. It seems like reassignment of anything in the User Assigned range is unlikely, however that is the purview of the iSO 3166 maintenance agency, and not the IETF. However unlikely it is, we cannot be absolutely certain they will never reassign those, and so we should not include them in any standard (note the lower-case) published by the IETF. Even if the IETF is just cut & pasting their current advice, I think it's unwise. 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. Even though they're not specifically proposed, only mentioned in passing, I'd also like to point out that the referenced potential uses of things like XH instead of home.arpa. is even more risky, because that fixes that string for a specific use, even if it's private. Using XH as an example, if that had been chosen it would run the risk of colliding with some legitimate use of XH already being used by a User.. if that user then also needed to interoperate with Homenet technologies they'd be hosed. I think, instead of an RFC, what you really want is a Best Current Practices document, outside of the IETF, that is simply a redirect to the current ISO 3166 document. Instead of DNSOP, I'd suggest you have a chat with one or more of the BCOP efforts at the NOGs.
- [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