Re: [rsab] [Editorial Errata Reported] RFC9280 (7795)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Mon, 05 February 2024 18:16 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: rsab@ietfa.amsl.com
Delivered-To: rsab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0387EC14F5FA; Mon, 5 Feb 2024 10:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 Az6Ik16s8y4P; Mon, 5 Feb 2024 10:16:47 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6FF3C14F5EF; Mon, 5 Feb 2024 10:16:46 -0800 (PST)
Received: from dslb-002-205-175-185.002.205.pools.vodafone-ip.de ([2.205.175.185] helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rX3WO-0008OT-Sk; Mon, 05 Feb 2024 19:16:44 +0100
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Message-Id: <4122E8BF-8706-4FF3-95C2-64A78E180451@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CE077790-C6AD-45E5-B5A1-A19DEB8C0CEF"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Mon, 05 Feb 2024 19:16:34 +0100
In-Reply-To: <8C3F8D65-A1B3-499B-BCAF-BCDC782E8D41@kuehlewind.net>
Cc: "rsab@rfc-editor.org" <rsab@rfc-editor.org>
To: Eliot Lear <lear@lear.ch>, RSWG <rswg@rfc-editor.org>
References: <20240203084054.24DBB11821EE@rfcpa.amsl.com> <3f525194-e353-4c21-b4d6-8839c7f5e780@lear.ch> <8C3F8D65-A1B3-499B-BCAF-BCDC782E8D41@kuehlewind.net>
X-Mailer: Apple Mail (2.3731.700.6)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1707157006;198d9c54;
X-HE-SMSGID: 1rX3WO-0008OT-Sk
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/9iNdwr1FTG2cs3fekfsK73YK4I4>
Subject: Re: [rsab] [Editorial Errata Reported] RFC9280 (7795)
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Approval Board \(RSAB\)" <rsab.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rsab>, <mailto:rsab-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rsab/>
List-Post: <mailto:rsab@rfc-editor.org>
List-Help: <mailto:rsab-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rsab>, <mailto:rsab-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2024 18:16:51 -0000

Sorry my statement below was actually not right or at least not clear. draft-rswg-rfc7990-update does need to update RFC9280 but only section 7 and that does not need any additional IESG or IAB approval.



> On 5. Feb 2024, at 18:21, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote:
> 
> To the errata itself, I don’t think this addition is needed because as section 7 says " Proposals that affect these properties are possible within the processes defined in this document” this changing procedure for section 7 is actually a procedure defined in this document and therefore is valid.  However, I guess the change proposed below in the errata would probably make it more clear.
> 
> But in summary, I don’t think there is an errata and draft-rswg-rfc7990-update does not need to update RFC9280 (without or without the proposed changed in the errata below).
> 
> 
> 
> 
> 
> 
>> On 3. Feb 2024, at 09:43, Eliot Lear <lear@lear.ch> wrote:
>> 
>> FYI and for discussion.
>> 
>> 
>> 
>> -------- Forwarded Message --------
>> Return-Path:	<wwwrun@rfcpa.amsl.com> <mailto:wwwrun@rfcpa.amsl.com>
>> Authentication-Results:	upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=rfc-editor.org
>> Received:	from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPS id 4138et9h1897964 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <lear@lear.ch> <mailto:lear@lear.ch>; Sat, 3 Feb 2024 09:40:57 +0100
>> Received:	by rfcpa.amsl.com (Postfix, from userid 499) id 24DBB11821EE; Sat, 3 Feb 2024 00:40:54 -0800 (PST)
>> To:	rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
>> Subject:	[Editorial Errata Reported] RFC9280 (7795)
>> From:	RFC Errata System <rfc-editor@rfc-editor.org> <mailto:rfc-editor@rfc-editor.org>
>> Cc:	lear@lear.ch <mailto:lear@lear.ch>, stpeter@stpeter.im <mailto:stpeter@stpeter.im>
>> Content-Type:	text/plain; charset=UTF-8
>> Message-Id:	<20240203084054.24DBB11821EE@rfcpa.amsl.com> <mailto:20240203084054.24DBB11821EE@rfcpa.amsl.com>
>> Date:	Sat, 3 Feb 2024 00:40:54 -0800 (PST)
>> 
>> 
>> The following errata report has been submitted for RFC9280,
>> "RFC Editor Model (Version 3)".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid7795
>> 
>> --------------------------------------
>> Type: Editorial
>> Reported by: Eliot Lear <lear@lear.ch> <mailto:lear@lear.ch>
>> 
>> Section: 8
>> 
>> Original Text
>> -------------
>> Updates, amendments, and refinements to this document can be produced
>> using the process documented herein but shall be published and
>> operative only after (a) obtaining the agreement of the IAB and the
>> IESG and (b) ensuring that the IETF LLC has no objections regarding
>> its ability to implement any proposed changes.
>> 
>> Corrected Text
>> --------------
>> Updates, amendments, and refinements to this document can be
>> produced using the process documented herein but, unless otherwise
>> specified in this document, shall be published and operative only
>> after (a) obtaining the agreement of the IAB and the IESG and (b)
>> ensuring that the IETF LLC has no objections regarding its ability
>> to implement any proposed changes.
>> 
>> 
>> Notes
>> -----
>> Section 7 explicitly states:
>> 
>> "Proposals that affect these properties are possible within the processes defined in this document."
>> 
>> And it goes on from there to discuss RSWG/RSAB review.
>> 
>> Therefore, it should not be necessary for the IAB, IESG, and LLC to approve changes in Section 7. That is just a for-instance. There may be other examples.
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary.
>> 
>> --------------------------------------
>> RFC9280 (draft-iab-rfcefdp-rfced-model-13)
>> --------------------------------------
>> Title : RFC Editor Model (Version 3)
>> Publication Date : June 2022
>> Author(s) : P. Saint-Andre, Ed.
>> Category : INFORMATIONAL
>> Source : IAB
>> Area : N/A
>> Stream : IAB
>> Verifying Party : IAB
>> 
>> <OpenPGP_0x87B66B46D9D27A33.asc>-- 
>> RSAB mailing list
>> RSAB@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rsab
> 
> -- 
> RSAB mailing list
> RSAB@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rsab