Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ietf-dns-alt-tld

Paul Hoffman <paul.hoffman@icann.org> Tue, 02 August 2022 19:11 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 DDB32C14CF02; Tue, 2 Aug 2022 12:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QnVrp-jImqkT; Tue, 2 Aug 2022 12:11:42 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.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 E4954C14CF0C; Tue, 2 Aug 2022 12:11:42 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa3.lax.icann.org (8.17.1.5/8.17.1.5) with ESMTPS id 272JBdgX007957 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 2 Aug 2022 19:11:39 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.26; Tue, 2 Aug 2022 12:11:38 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0986.026; Tue, 2 Aug 2022 12:11:38 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
CC: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>
Thread-Topic: [Ext] [DNSOP] draft-schanzen-gns and draft-ietf-dns-alt-tld
Thread-Index: AQHYpaK05wMW11QWnEWf13VDh85yta2ccXQA
Date: Tue, 02 Aug 2022 19:11:38 +0000
Message-ID: <5D598E6D-932F-4855-8D5F-C2DEDD20738C@icann.org>
References: <91abb9ac-9d3b-87bf-5639-174581d625fd@rfc-editor.org>
In-Reply-To: <91abb9ac-9d3b-87bf-5639-174581d625fd@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_0864FB29-2950-4DA8-B07B-37EFC6A5B0F9"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-08-02_14,2022-08-02_01,2022-06-22_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qjuPeQHox2HNwA46jAPhzDiM5ek>
Subject: Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ietf-dns-alt-tld
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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, 02 Aug 2022 19:11:47 -0000

The ISE started this thread with a discussion that included "Whether that means using TLD labels that begin with _ or whether that means suffixing them with ".ALT", I leave to you experts to sort." There is another forthcoming option that could be used in draft-schanzen-gns, namely the unallocated string that may be chosen as part of the process coming out of SAC113.

SAC113 <https://www.icann.org/en/system/files/files/sac-113-en.pdf>, published by ICANN's Security and Stability Advisory Committee, recommends that the ICANN board to pick a string that will never be put into the DNS root, and thus is usable for systems like GNS. The recommendation is moving forward, as can be seen on the SAC113 line on page 10 of <https://www.icann.org/en/system/files/files/board-advice-status-report-pdf-30jun22-en.pdf>. A string that is guaranteed to never appear in the DNS root can be used as the basis of private-use names, even if that guarantee doesn't come from the DNSOP Working Group.

(I was not part of the SAC113 work, but am reporting here so that the ISE and GNS can see that they will have additional options.)

--Paul Hoffman