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

John Levine <johnl@taugh.com> Mon, 01 August 2022 22:21 UTC

Return-Path: <johnl@iecc.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 DE3FAC13CCEA for <dnsop@ietfa.amsl.com>; Mon, 1 Aug 2022 15:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.863
X-Spam-Level:
X-Spam-Status: No, score=-6.863 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=q1slIxsd; dkim=pass (2048-bit key) header.d=taugh.com header.b=Z9pqkQRs
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 B0h3b0goVzzv for <dnsop@ietfa.amsl.com>; Mon, 1 Aug 2022 15:21:26 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22E18C13CCE7 for <dnsop@ietf.org>; Mon, 1 Aug 2022 15:21:25 -0700 (PDT)
Received: (qmail 6148 invoked from network); 1 Aug 2022 22:21:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1802.62e851e4.k2208; bh=fP6584448R8f4GCpLoq0xsrXMQLlB/gVf7ck4h06txI=; b=q1slIxsdv+e+KVKUPAwrEBSJ5oWqm5M/IpKNV/4z8UeprcOZtHrX/rGNT61dji1RXVM7WDu/cJ34f2iveVkZPQBuAaC2dn6VjmEtscr5YFXXLWWAZTMZm4nQhA4T14rd9+5Q3okqEYAiPSN1psU/3RSS7racfXlPq7Tzamo23vouFBO6aALuQTdtVmKtYir9nDjgEQLtdBnc3qxNxjWzfiYGeLo4MIY1loiRUFfp3b+lDf/NC/95W4ddW8l0J8YVJbCAkZKuw7R1XLUi03RZDtbpqGFVb0MYPIOeBH3I570hwR15HXqRLMsNDOCz7BzEcdCfajw5Q3xe27jb3GMOhA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1802.62e851e4.k2208; bh=fP6584448R8f4GCpLoq0xsrXMQLlB/gVf7ck4h06txI=; b=Z9pqkQRsc6BoL6Nv/vN9cyY+Kbqgs8OYq0UMbwK3RxMrvZNFrry2XLDf4FOnAYW0szEx28zQSFuO3y8ktT0b0IVCsSR2PCPAx51XeUT/Vn2cT5rlDmJQiemTiAeiGgWbMiRCzrWA1D95H2xqSeMOlWnFYmm1Dv4Re4was6TK9QjMfPb9CcE2waR/6usAHvEYzhVYFZanQcQ+WsL+xGiCQdcI8pTxFpVsrS4CW3igIdMEzvbf4m4f8k9XCjsa4zTj6Dry2RF4/82j8jis0Jxs3NO+NkCNN2YbEhaMP8VF0jhuA74QMtDdCTZqkHAYdqPHItT9AB1PO4jSfAhzKwDsAQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 01 Aug 2022 22:21:23 -0000
Received: by ary.qy (Postfix, from userid 501) id E18D146EF990; Mon, 1 Aug 2022 18:21:22 -0400 (EDT)
Date: Mon, 01 Aug 2022 18:21:22 -0400
Message-Id: <20220801222123.E18D146EF990@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: rfc-ise@rfc-editor.org
In-Reply-To: <91abb9ac-9d3b-87bf-5639-174581d625fd@rfc-editor.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6n6OjvkViLHKyH4rXlRJ8Cg6Oco>
Subject: Re: [DNSOP] 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: Mon, 01 Aug 2022 22:21:31 -0000

It appears that Independent Submissions Editor (Eliot Lear) <rfc-ise@rfc-editor.org> said:
>  On the one hand, we need to find a 
>way for people to explore alternative namespaces that look a bit like 
>domain names.  On the other hand, we don't want to create problems with 
>user expectations.

It is fine for people to look at other ways to do naming on the
Internet, but that does not mean they get to squat on the DNS
namespace.

Look at the handle system or I guess DONA now. It has its own
namespace or numberspace, and it has its own way to look stuff up.
Some of their registry-like-things have made their own arrangements to
do DNS gatewaying, like https://dx.doi.org/10.2345/blah, which is fine
and neither our problem nor ICANN's.

GNS is welcome to set up their own name space and provide their own
resolution system. If they want to do a GNS->DNS gateway, that's fine.
But the DNS is the DNS, and things that aren't the DNS don't go there.

R's,
John

PS: Yeah, I know about .onion, but one unfortunate decision does not a policy make.