Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draft-ietf-dns-alt-tld
Christian Huitema <huitema@huitema.net> Mon, 08 August 2022 00:25 UTC
Return-Path: <huitema@huitema.net>
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 CD11BC15A72E for <dnsop@ietfa.amsl.com>; Sun, 7 Aug 2022 17:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 2Lq2nEyPVRrx for <dnsop@ietfa.amsl.com>; Sun, 7 Aug 2022 17:25:49 -0700 (PDT)
Received: from mx36-out21.antispamcloud.com (mx36-out21.antispamcloud.com [209.126.121.69]) (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 137D3C159497 for <dnsop@ietf.org>; Sun, 7 Aug 2022 17:25:48 -0700 (PDT)
Received: from xse417.mail2web.com ([66.113.197.163] helo=xse.mail2web.com) by mx258.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1oKqaS-000Cl2-R9 for dnsop@ietf.org; Mon, 08 Aug 2022 02:25:48 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4M1H6V2njLzBHB for <dnsop@ietf.org>; Sun, 7 Aug 2022 17:25:38 -0700 (PDT)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1oKqaQ-0001JB-8x for dnsop@ietf.org; Sun, 07 Aug 2022 17:25:38 -0700
Received: (qmail 18093 invoked from network); 8 Aug 2022 00:25:37 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.58.43.187]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <rfc-ise@rfc-editor.org>; 8 Aug 2022 00:25:37 -0000
Message-ID: <ff5ba10a-edb8-8e88-de4b-c68ff70d57d1@huitema.net>
Date: Sun, 07 Aug 2022 17:25:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>, David Conrad <drc@virtualized.org>, "Schanzenbach, Martin" <mschanzenbach@posteo.de>
Cc: dnsop <dnsop@ietf.org>
References: <91abb9ac-9d3b-87bf-5639-174581d625fd@rfc-editor.org> <YufxYmxz9L8zG9hS@nic.fr> <1659368624-sup-8402@werkbank> <CAH1iCirbMBqSkE_+bTtWisEm_LxXj-3n2d1F1qL67_X+U7v7Jg@mail.gmail.com> <1659591584-sup-6027@werkbank> <39865554.5880.1659614798712@appsuite-gw2.open-xchange.com> <DEE9FECE-2647-4B8B-A64A-6D6E0E25F3FE@posteo.de> <595181228.6895.1659622649037@appsuite-gw2.open-xchange.com> <0F155C86-71D5-49AD-807F-D27314964574@posteo.de> <CB70361A-6B80-4DBF-B7EA-875A5DD9396C@virtualized.org> <e50cc265-f875-89d4-b109-9c10951c8896@rfc-editor.org>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <e50cc265-f875-89d4-b109-9c10951c8896@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: 66.113.197.163
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.06)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT8EplXWVrp5Q4k/cOZcyFaOPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zUgvzNCu/tqNXO2HgXp/PwfYzfQXcfqmra3dmoHS4ygtmT 76zUFiD70V8HK/IacRBWuRWrkPihq53YqAd1ENNqBHtNXu1E6L4+KyOXc4QYanQOD0r6/AaHZiEt dTMtMlia0Lmg/jgHfCNZd+W+PXf6ikm9n6fa9zroTlNfwLIeEyue9TLOhN8AYRsvkjfngQDCCqjo gBy6Z7Z1H0a6XOEbzDkBvlIN1pUDU5DU5DggD98cjIN3reG9z0FKKQ5m2Qpw7sOVVcM1Xk+Tdz6g /UMvfWqyN3veeFIMJz/vumcqAwMU9kjfE7EFo+kP5riIEUmxU01QhuxnshSbl6nxbLZ35/xY0uvo WBEOfzq3RG28wI7w4vcwqZanLHsZM8r4s5ZjlHoGly8aneNxj+pRyx6DAzHPcWsnfqGSaNoXhWPo OpFVgpT1b21uZVckGp0ccOZtuBWXiK6eoWgQZnNLL6SbpUc7peFeo3eDQNYbhOKhzzgqmaDn5SlD Y9mmtv6e91aWBLor1oCWetcUjeG94V2XTy8q18r5F7mwejpNkMpMQ8IQulZLBAEuXQM0vR94FKcW Dy/ZVgkPPcmObwWz0hCMDRojSVizNl0ce/s7u0P9b7Oijoc3SCZfWp1RjkjWCw/vIUzTXkDAiiJi mGhLUFuS2lhaIetXfCg1JdAVrOwKfERVgs33jAIe2Fi2YghgDeVUoFIvD3sIcP1fhJPM6B/84qsL XnU7bpv/gzUagMH9DqGHmIiASzFQNxKUW9MMRlyJ+dym1L8cD17Js0v4cp1Mz8lySecF/qR+B5MM BaGS8jcKVNeVJ9BXyu9+ceCqThTYg2px1fSoqxQCCHnLMo/m9VKh99btUAanjnMCAH2co+fBoeG+ Hs0afhsY/5zhNYWRVYKU9W9tbmVXJBqdHHDmZEKhyNAv1N35kYWaEdgLurFV5oTvAcwA4rM3FkfW 8/1kE/e7sUnsVpINvARNxpFO
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rzMU4gBbYk4RJiPqvOWkRLwrNX4>
Subject: Re: [DNSOP] [EXT] Re: 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, 08 Aug 2022 00:25:53 -0000
On 8/4/2022 1:52 PM, Independent Submissions Editor (Eliot Lear) wrote: > Dave, > > To answer the question, “What is the ISE process?”: > > On 04.08.22 21:28, David Conrad wrote: >> Martin, >> [...] > >> I see 4 options: >> >> 1) Wait for ICANN to fix their processes >> 2) Wait for the IETF to figure out whether/how to reopen the “Special >> Use Domains” registry >> 3) Try to bypass (1) and/or (2) by publishing through the ISE (I >> don’t know enough about the ISE process to guess whether this is >> appropriate or feasible) > > For information about independent submissions, please see > https://rfc-editor.org/about/independent and RFC 4846 (among others). As Eliot gently hints at, the purpose of the ISE is not to bypass established processes, or indeed force a code point allocation against established processes. I think that experimenting with "pet names", as proposed in draft-schanzen-gns, is a perfectly fine idea. The concept of per names has been proposed for a long time, see discussions about Zooko's triangle, etc. It is a tradeoff: doing away with registration implies either ugly names (hashes of keys) or names that resolve differently in different contexts (pet names). Many here posit that the tradeoff is too ugly to be useful, but that should not preclude Martin & al from trying that experiment. (I also think that we should avoid comments like "you should be damned" in a technical debate.) Of course, anyone who does an experiment like that will want to somehow reuse existing software and existing clients. They will want to open something like "http://<my-fancy-new-name>/index.html". They will want to stick their fancy new names at places where existing API or interfaces expect a fully qualified domain name. Which means they will need a simple way to differentiate the new names from actual domain names. And for that, the simplest way is to pick a final name part that is reserved for the project. That was indeed what RFC 6761 was allowing. But we have an issue, because for all practical matters the IETF wants to obsolete RFC 6761. The IETF wants that for good reasons, based on past experience with allocating TLD outside of ICANN. Indeed, part of that experience is surfacing in the the use of "example.pet" in draft-schanzen-gns. It turns out that ICANN has already allocated the TLD ".PET" (see https://data.iana.org/TLD/tlds-alpha-by-domain.txt), so using that outside of the DNS would not be good. Arm-twisting the IETF to revive RFC 6761 is probably not going to work, so I could think of only three alternatives: 1) Have the GNS project directly ask ICANN to register their preferred name string. That would get the desired UI, but probably require money and time, for a somewhat uncertain result. 2) Register something like "gnu.arpa" or "pet.arpa". RFC 3172 requires that the IETF endorses new registrations in some kind of standard, which is a higher bar than an ISE registration. But it probably could be arranged. 3) Squat under ".test". This breaks a couple of "should not" in RFC 6761, but is in line with the general philosophy that "Users are free to use these test names as they would any other domain names" and "there is no central authority responsible for use of test names". -- Christian Huitema
- [DNSOP] draft-schanzen-gns and draft-ietf-dns-alt… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Ben Schwartz
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Joe Abley
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Stephane Bortzmeyer
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Paul Vixie
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Martin Schanzenbach
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Peter Thomassen
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… John Levine
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… John Levine
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Paul Wouters
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… George Michaelson
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Martin Schanzenbach
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Joe Abley
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Joe Abley
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Vladimír Čunát
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Martin Schanzenbach
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Vladimír Čunát
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Schanzenbach, Martin
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Geoff Huston
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… David Conrad
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Paul Hoffman
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Andrew Sullivan
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… John R. Levine
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Martin Schanzenbach
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Paul Vixie
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Schanzenbach, Martin
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Paul Hoffman
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Schanzenbach, Martin
- Re: [DNSOP] [Ext] draft-schanzen-gns and draft-ie… Paul Hoffman
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Brian Dickson
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Martin Schanzenbach
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Vittorio Bertola
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Schanzenbach, Martin
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Vittorio Bertola
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Schanzenbach, Martin
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Schanzenbach, Martin
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… David Conrad
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Schanzenbach, Martin
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Brian Dickson
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Christian Huitema
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… George Michaelson
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Christian Huitema
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… John Levine
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… George Michaelson
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Christian Huitema
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Joe Abley
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Independent Submissions Editor (Eliot Lear)
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Vittorio Bertola
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Paul Wouters
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Paul Wouters
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Jim Reid
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… John R Levine
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Paul Hoffman
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Paul Wouters
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Paul Vixie
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Ray Bellis
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Vladimír Čunát
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… John Levine
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Stephen Farrell
- Re: [DNSOP] [EXT] Re: draft-schanzen-gns and draf… Christian Huitema
- Re: [DNSOP] draft-schanzen-gns and namespace mech… Brian Dickson
- Re: [DNSOP] draft-schanzen-gns and namespace mech… Schanzenbach, Martin
- Re: [DNSOP] draft-schanzen-gns and namespace mech… Schanzenbach, Martin
- Re: [DNSOP] draft-schanzen-gns and draft-ietf-dns… Harald Alvestrand