[saag] Re: [rfc-i] RFCs vs Standards

Carsten Bormann <cabo@tzi.org> Tue, 10 December 2024 20:28 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E5BC18DB8F for <saag@ietfa.amsl.com>; Tue, 10 Dec 2024 12:28:42 -0800 (PST)
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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 CKex5jpIHcRY for <saag@ietfa.amsl.com>; Tue, 10 Dec 2024 12:28:41 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29BE3C1840C8 for <saag@ietf.org>; Tue, 10 Dec 2024 12:28:40 -0800 (PST)
Received: from [192.168.217.145] (p548dc3ec.dip0.t-ipconnect.de [84.141.195.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Y79Ky2RjnzDCc7; Tue, 10 Dec 2024 21:28:38 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C74E3E9D-E892-48B4-87BE-CD634081AA23@akamai.com>
Date: Tue, 10 Dec 2024 21:28:37 +0100
X-Mao-Original-Outgoing-Id: 755555317.822336-5abc2123b9cee30eba9839db57656004
Content-Transfer-Encoding: quoted-printable
Message-Id: <030FD3D1-8BC9-4C92-84EE-9CD18F451E73@tzi.org>
References: <BE95E617-C929-43BA-BB40-41E189A8158B@akamai.com> <87ldxl5zp9.fsf@kaka.sjd.se> <26424.40383.605711.370013@fireball.acr.fi> <71bcb4f8-e147-a6cb-3c67-b6daef61f309@mindrot.org> <26439.33533.129915.244853@fireball.acr.fi> <SY8P300MB0711C796AB6095C788556516EE292@SY8P300MB0711.AUSP300.PROD.OUTLOOK.COM> <15450.1732763286@obiwan.sandelman.ca> <3029EB03-6E7A-47CB-9682-F511CB51EE17@akamai.com> <10065.1732826193@obiwan.sandelman.ca> <CACsn0cmWVeFdJ3dzMj5SV4XpJF4rssULtfQ1moeefoq-Evhk=g@mail.gmail.com> <CAGL5yWb=tLvMOYFKT3ffVbcy7BAD=i4B0VHEUdkvwRvZ3X3Bsw@mail.gmail.com> <m2mshh4v8l.wl-randy@psg.com> <CABcZeBMjxNbBMYU2p3_a8-5VCExgmY-7XLof7die05YOEX-38A@mail.gmail.com> <70419651-6443-4393-9ca1-8a1c98a68db0@cs.tcd.ie> <CABcZeBNtBRxi5zSf9OvUip2AtyVD6Wt9+kQESuUzo-=Kur9+ZQ@mail.gmail.com> <fac981d9-2fe9-4a84-8af1-845acd72af58@cs.tcd.ie> <14124.1733073164@obiwan.sandelman.ca> <d52ee080-814b-46fd-9e0f-41349941eeac@cs.tcd.ie> <GVXPR07MB9678DF2C14EA44B28C3DA372893D2@GVXPR07MB9678.eurprd07.prod.outlook.com> <F304B6BA-6969-4C62-A217-88E76F82CDC2@tzi.org> <C74E3E9D-E892-48B4-87BE-CD634081AA23@akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: HRCTNLKOLQSLLFQE3HD26TW3LAGMGG5Y
X-Message-ID-Hash: HRCTNLKOLQSLLFQE3HD26TW3LAGMGG5Y
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-saag.ietf.org-0; header-match-saag.ietf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>, IETF SAAG <saag@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [saag] Re: [rfc-i] RFCs vs Standards
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/UigKAv0NVBnx6JVgZbohj4rulNU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

On 2024-12-10, at 21:07, Salz, Rich <rsalz@akamai.com> wrote:
> 
> On 2024-12-10, at 13:52, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org <mailto:40ericsson.com@dmarc.ietf.org>> wrote: 
>> • Internet-drafts are obviously "permanent and readily available", I don’t see why that is debated. For registries wanting RFCs there is “RFC required”. I am against any registry saying that "permanent and readily available" internet-drafts are NOT OK, but pointing to a website outside of the IETF is…
> 
> On 12/10/24, 2:49 PM, "Carsten Bormann" <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
>> This.
>> There really can’t be any discussion on the facts here.
> 
> Except that the boilerplate in every internet draft says "It is inappropriate to use Internet-Drafts as reference material or to cite them other than as 'work in progress'" and some people have a problem with using a work in progress as the defining reference for an IANA registry. I think the solution to that is to fix the boilerplate somehow.

The boilerplate has indeed been “inappropriate” for a long time.
But that is more or less a religious discussion, not one about facts on the ground.
I wouldn’t mind if we fixed the text to better reflect its intention (= outcome now desired given we are no longer in the state that made the original wording attractive), but we don’t need to complete the (likely lengthy) process before acknowledging the above reality.

Grüße, Carsten