IETF Logo Mail Archive

Re: [DNSOP] [Ext] More input for draft-ietf-dnsop-dnssec-bcp?

Paul Hoffman <paul.hoffman@icann.org> Tue, 26 April 2022 19:04 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 99724C15E3EB for <dnsop@ietfa.amsl.com>; Tue, 26 Apr 2022 12:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ZcJECjsLr7so for <dnsop@ietfa.amsl.com>; Tue, 26 Apr 2022 12:04:30 -0700 (PDT)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.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 DA6C3C185764 for <dnsop@ietf.org>; Tue, 26 Apr 2022 12:01:35 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa5.dc.icann.org (8.16.0.43/8.16.0.43) with ESMTPS id 23QJ1X92013594 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 26 Apr 2022 19:01:33 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.22; Tue, 26 Apr 2022 12:01:32 -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.022; Tue, 26 Apr 2022 12:01:32 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Martin Hoffmann <martin@nlnetlabs.nl>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] More input for draft-ietf-dnsop-dnssec-bcp?
Thread-Index: AQHYWaAK+Xwutee7+02v1CnTzh7fLw==
Date: Tue, 26 Apr 2022 19:01:32 +0000
Message-ID: <122A099D-D872-47E3-8686-2445E6752FE5@icann.org>
References: <02759DA4-45AF-4021-BBD1-B8733CD85CE1@icann.org> <20220426160317.4f14f72e@glaurung.nlnetlabs.nl>
In-Reply-To: <20220426160317.4f14f72e@glaurung.nlnetlabs.nl>
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=_1C8E91B7-ACA5-44A9-A696-353552A65C58"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-04-26_05:2022-04-26, 2022-04-26 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/x35pRqUAVsgy9W9bE8IMhpzv6J8>
Subject: Re: [DNSOP] [Ext] More input for draft-ietf-dnsop-dnssec-bcp?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
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 Apr 2022 19:04:30 -0000

On Apr 26, 2022, at 7:03 AM, Martin Hoffmann <martin@nlnetlabs.nl> wrote:
> 
> Hi!
> 
> Paul Hoffman wrote:
>> Greetings. I posted the -01 about ten days ago, and have not heard
>> anything since then. The chairs indicated that they wanted this
>> fast-tracked, so I'll nudge here for more input, either on the WG
>> mailing list on in the repo
>> (https://github.com/paulehoffman/draft-hoffman-dnssec). If nothing
>> big comes up, I'll ask for WG Last Call.
> 
> The draft’s nature of listing all the relevant RFCs reminded me that
> back in 2009 the SIP working group published a similar document and
> called it ‘The Hitchhikers Guide to SIP.’
> 
> Maybe it would be a good idea to name this draft in a similar fashion?
> Not because the joke is particularly ... fresh but because if it would
> become a moniker across the entire IETF, it would be much easier to
> identify an RFC that provides an overview of all the relevant documents
> for a topic and thus a good starting point for research.

As a previous editor of the "Tao of the IETF", I assure you that cute names have a shelf life much shorter than we expect. Also, SIP was a *much* longer list of RFCs than DNSSEC is, and RFC 5411 was Informational. No one else in the IETF has adopted that naming convention, which I think is appropriate given how excellent the four books in the HHGTTG trilogy are.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email