Re: [DNSOP] on private use TLDS

Ted Lemon <mellon@fugue.com> Tue, 26 November 2019 11:52 UTC

Return-Path: <mellon@fugue.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 A9C42120119 for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 03:52:30 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 fRmCDTNvq6tL for <dnsop@ietfa.amsl.com>; Tue, 26 Nov 2019 03:52:28 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 B407A12009E for <dnsop@ietf.org>; Tue, 26 Nov 2019 03:52:28 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id v23so7949218qkg.2 for <dnsop@ietf.org>; Tue, 26 Nov 2019 03:52:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=rb67SfTcXl2qnQvoZyrgrGqFttyDWyMtmQjP6yDKcLo=; b=RDI34qY37/S8B6DPnF76QihaKeV+87eXNbG8jtnh65dbzV+CmixHVocI02oItHIIJw D7N6nZNYMElbZb7/1vo8gL3rYSnHNmT6oWsrYWCYyXrshdkFoqR5laqnqVG72qewZeR4 6CSzvGzo+AYAH754Mm6NQsRYbuHtS0x+yvo3HQSiKzJm1Xn3HI8nRr3YPDWOYQWFnlEY tIPRZ0nugtGiXyKoJ+gLXSiKBjkyo4S9OaORxfoU/l7S0v572l9+gFIHlxc4N+S7arFY 8fMl7colUpeGOK40ydGXYO7scn3XQjFFT7sD9kom4v1PAmBjOuiQQbc6L6c8DF3DzfQf k3Mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=rb67SfTcXl2qnQvoZyrgrGqFttyDWyMtmQjP6yDKcLo=; b=c8j92H+rZI964tWohsF4zg+zf00E7j4Qyv5UKDTJ8/5B8S0FIXXok5UNv7YhkTk8se mFCeXe7QVlK9in2k/oo9deURmiQ6f54EqEmXF7uqUdjM1b+6eI98D8olCjyZYxvObzM3 Y9SDAuGrqI+DaNJGKHhZJ8HbSpCx4m/ifgQM2gzXghODJ0FAaqjSiKzQ8jqvl9ljKHKD h9X9EDcuhfVAzOO1I0YiE82sIn1jpkfrrYlubYFnANvYjsyBUyGMwf+fYSYkxOXaP/13 Qfif81VrvcfLxtCOD70yz1ymv9IeCV0SqaRAW6gwCP4shf9qN6qiILDiPGazRZ2qhuYC FNxQ==
X-Gm-Message-State: APjAAAXKByBMNman6ItsOAIvgPhOuN0y4I1Xxw4IxEUVkHgVNK1msUYB XxZ3tl1FEtNAXaJ+ffOAiJQWsn+V7HAeIQ==
X-Google-Smtp-Source: APXvYqwVQTOMX2jlBqiifaZ9NmI+7DvIgoYLoLrE7gcWew61xfIbcpAQhZKxJKs6goWmOdphXoyq9g==
X-Received: by 2002:a37:9f94:: with SMTP id i142mr20220073qke.244.1574769147252; Tue, 26 Nov 2019 03:52:27 -0800 (PST)
Received: from ?IPv6:2601:18b:300:36ee:78bc:830d:457c:7f64? ([2601:18b:300:36ee:78bc:830d:457c:7f64]) by smtp.gmail.com with ESMTPSA id r8sm5633713qti.6.2019.11.26.03.52.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Nov 2019 03:52:26 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 Nov 2019 06:52:25 -0500
Message-Id: <A3430DBF-949A-4A66-A83F-A602C6F69560@fugue.com>
References: <B679F326-54A0-4010-BD41-F2F317417169@dnss.ec>
Cc: dnsop <dnsop@ietf.org>
In-Reply-To: <B679F326-54A0-4010-BD41-F2F317417169@dnss.ec>
To: Roy Arends <roy@dnss.ec>
X-Mailer: iPad Mail (17E177)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/spZf5WIfefYPCaWCSEiHMsDrA9Y>
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 11:52:31 -0000

 It might be worth clarifying what the actual scope of this proposal is.  I think that the idea is to say “look, if you want to use a private name, these names are known to be safe.”   It’s not to say “the IETF hereby declares that the following names are safe,” but rather “the IETF is reporting that these names have been declared safe by this other SDO.”

The point of making this recommendation is that we know that people will have reasons to privately use domains that have not been allocated to them out of the global namespace, and we’ve seen the problems that such private allocations cause when they are done in an unsafe manner.  The advice here is on how to avoid making that mistake.   It’s not a TLD allocation by IETF: those TLDs are already effectively allocated.

Is that about right?