IETF Logo Mail Archive

Re: [DNSOP] [Ext] Call for Adoption: draft-belyavskiy-rfc5933-bis

Paul Hoffman <paul.hoffman@icann.org> Fri, 19 June 2020 15:38 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 E4AFE3A0819 for <dnsop@ietfa.amsl.com>; Fri, 19 Jun 2020 08:38:09 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3WZKalRuxB9M for <dnsop@ietfa.amsl.com>; Fri, 19 Jun 2020 08:38:08 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 B06033A0AEC for <dnsop@ietf.org>; Fri, 19 Jun 2020 08:38:08 -0700 (PDT)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa2.lax.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 05JFc73T020505 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 19 Jun 2020 15:38:07 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 19 Jun 2020 08:38:05 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1497.006; Fri, 19 Jun 2020 08:38:05 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Martin Thomson <mt@lowentropy.net>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] [Ext] Call for Adoption: draft-belyavskiy-rfc5933-bis
Thread-Index: AQHWRYEcUoh5DWNcfECeWUoumkosw6je9SkAgADXJICAAL1IgA==
Date: Fri, 19 Jun 2020 15:38:05 +0000
Message-ID: <431980F9-988B-4212-8FF5-8A64436C8392@icann.org>
References: <CADyWQ+H4713BnZDntTuVW0FrO59zZ9NFJ=J=n9JFFq2zmfy2pQ@mail.gmail.com> <A930F8C6-9C33-4933-AC37-579ACEF5B325@ogud.com> <7FF83D52-F20B-4FF2-82AA-416835FCA5F4@isc.org> <CADqLbzJsJ6etv-eZuabLsMO4g+XYgktgpuP-fTNSi1cFTwdOGg@mail.gmail.com> <68eb8413-8704-40a3-9765-7eb19ebd0e78@www.fastmail.com> <CABcZeBORz-ustvXvrYaMm15rAHUfA3zR8Sr3ZscLWB6YJ6-s8w@mail.gmail.com> <CADyWQ+EOcTWX6PrbQUmqM6=Z442bE7itFAG6No0b9MZdcARbOg@mail.gmail.com> <CABcZeBOwxO6=Qpoyk=_cDsP5G__3CfjKV8p+boGY4-9OX=Gh8w@mail.gmail.com> <CADyWQ+Ge7AmGKT3PZ9SQDkHWi9315T=xbLcx4vQ23e=4T=zmNg@mail.gmail.com> <C2C9BDB4-AA7B-47B8-8735-2A529B37B4BA@icann.org> <CADqLbzLdu-ceWDKk5aUYTe3WzAntJKh5QTncHyy137W=nyDSfQ@mail.gmail.com> <7269525A-5376-48AA-B9DC-84BE9D84BA36@icann.org> <40d8663d-5f39-4900-b1c6-e78d73ebffcd@www.fastmail.com>
In-Reply-To: <40d8663d-5f39-4900-b1c6-e78d73ebffcd@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_5AD85AE8-7800-4420-9641-53D89E714CBC"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-19_16:2020-06-19, 2020-06-19 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qIzaxXgOlgD3CzyJHInVVr_IJ7M>
Subject: Re: [DNSOP] [Ext] Call for Adoption: draft-belyavskiy-rfc5933-bis
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: Fri, 19 Jun 2020 15:38:10 -0000

On Jun 18, 2020, at 9:20 PM, Martin Thomson <mt@lowentropy.net> wrote:
> 
> On Fri, Jun 19, 2020, at 01:30, Paul Hoffman wrote:
>> It might be better, and faster, for this WG to adopt a one-paragraph 
>> draft that makes the DS registry "RFC required", like the other 
>> DNSSEC-related registries.
> 
> I think you mean "Specification Required".

I do not.

>  RFC required has the same net effect, but the side effect being that you burden the ISE with these requests.

"RFC required" forces the specification to be stable enough for the ISE (or the IESG, for individual submissions) to approve publication. Using "specification required" means that someone can write an Internet Draft, get the code point, then realize that their draft was wrong due to lack of community review. The result is either:
- Two code points for similarly-named algorithms
- A code point whose definition is a moving target
Using "RFC required" is not perfect (due to errata and RFC updates), but it does mean that there is at least some community review before the code point is allocated.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email