[Rswg] Re: [Ext] Re: RFC 9280: success or failure? And how would we know?
Paul Hoffman <paul.hoffman@icann.org> Fri, 17 January 2025 01:55 UTC
Return-Path: <paul.hoffman@icann.org>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B41C16942D for <rswg@ietfa.amsl.com>; Thu, 16 Jan 2025 17:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 NiGW36QFaLYx for <rswg@ietfa.amsl.com>; Thu, 16 Jan 2025 17:55:01 -0800 (PST)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) by ietfa.amsl.com (Postfix) with ESMTP id 509D6C14F68C for <rswg@rfc-editor.org>; Thu, 16 Jan 2025 17:55:01 -0800 (PST)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa3.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 50H1sx9F030570 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Jan 2025 01:54:59 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 16 Jan 2025 17:54:58 -0800
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1544.011; Thu, 16 Jan 2025 17:54:58 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Ext] [Rswg] Re: RFC 9280: success or failure? And how would we know?
Thread-Index: AQHbO6gh7+v8l5sjQEejAy6tuwKCa7LBeJKAgFmF24CAABX+AA==
Date: Fri, 17 Jan 2025 01:54:58 +0000
Message-ID: <D9F44A79-6C74-4625-B71E-18A62BAD8A57@icann.org>
References: <d8c57185-147e-44a2-b244-de4f7952974f@lear.ch> <354A833D-3FD6-45E5-BCC8-FADC74296308@tzi.org> <6f5520da-79f7-4aa4-9e4b-284b76966e2c@gmail.com> <202c628a-59f7-4044-881c-dd0408645994@gmail.com>
In-Reply-To: <202c628a-59f7-4044-881c-dd0408645994@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2CDC5AB38386D040A079D1FEF5DCD074@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1057,Hydra:6.0.680,FMLib:17.12.68.34 definitions=2025-01-16_11,2025-01-16_01,2024-11-22_01
Message-ID-Hash: OE3NN4OU4GXVJP2K5BGF2PWLWCQW2SAR
X-Message-ID-Hash: OE3NN4OU4GXVJP2K5BGF2PWLWCQW2SAR
X-MailFrom: paul.hoffman@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: RSWG <rswg@rfc-editor.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Rswg] Re: [Ext] Re: RFC 9280: success or failure? And how would we know?
List-Id: "RFC Series Working Group (RSWG)" <rswg.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/agrBZJXyxXb4PRuPSMZAHF49GCc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Owner: <mailto:rswg-owner@rfc-editor.org>
List-Post: <mailto:rswg@rfc-editor.org>
List-Subscribe: <mailto:rswg-join@rfc-editor.org>
List-Unsubscribe: <mailto:rswg-leave@rfc-editor.org>
On Jan 16, 2025, at 16:36, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > > Hi, > > This unresolved thread has been nagging at me for many weeks. I would like to make a concrete proposal for a clarifying addition to section 3 of RFC 9280: > > Existing text: > > "Policies under the purview of the RSWG and RSAB might include, but are not limited to, document formats, processes for publication and dissemination of RFCs, and overall management of the RFC Series." > > Proposed addition: > > "Such policies will not include detailed technical specifications, for example specific details of text or graphical formats or XML grammar. Such matters will be decided and documented by the RPC along with its other working practices, as discussed in section 4.2 of [RFC9280], with community consultation as for other tools and services supported by IETF LLC [RFC8711]." > > I believe this would clarify the scope of the RSWG and allow the RPC to make progress on various technical issues that are currently in limbo. > > (At the same time we could also enact erratum #7795.) > > This could make a very short RFC updating RFC 9280] This could, but we already know that there are other additions that people in the WG have requested. I had started a 9280bis document last summer, but didn't submit it due to the WG going off in different directions. With your proposal above, and with the imminent publication of draft-rswg-rfc7990-updates, I have now submitted <https://datatracker.ietf.org/doc/draft-hoffman-rfc9280-updates/>, which the RSWG might adopt. Your text is in Section 3. If the WG wants to work on the material suggested in Sections 4 and/or 5, great, but if not, we could probably close out this draft fairly quickly. --Paul Hoffman
- [Rswg] RFC 9280: success or failure? And how woul… Eliot Lear
- [Rswg] Re: RFC 9280: success or failure? And how … Carsten Bormann
- [Rswg] Re: RFC 9280: success or failure? And how … Brian E Carpenter
- [Rswg] Re: RFC 9280: success or failure? And how … Robert Sparks
- [Rswg] Re: RFC 9280: success or failure? And how … Brian Rosen
- [Rswg] Re: RFC 9280: success or failure? And how … Pete Resnick
- [Rswg] Re: RFC 9280: success or failure? And how … Robert Sparks
- [Rswg] Re: RFC 9280: success or failure? And how … Jay Daley
- [Rswg] Re: RFC 9280: success or failure? And how … Martin J. Dürst
- [Rswg] Re: RFC 9280: success or failure? And how … Eliot Lear
- [Rswg] Re: RFC 9280: success or failure? And how … Carsten Bormann
- [Rswg] Re: RFC 9280: success or failure? And how … Eliot Lear
- [Rswg] Re: RFC 9280: success or failure? And how … S Moonesamy
- [Rswg] Re: RFC 9280: success or failure? And how … S Moonesamy
- [Rswg] Re: RFC 9280: success or failure? And how … Brian E Carpenter
- [Rswg] Re: RFC 9280: success or failure? And how … Alexis Rossi
- [Rswg] Re: [Ext] Re: RFC 9280: success or failure… Paul Hoffman
- [Rswg] Re: [Ext] Re: RFC 9280: success or failure… Brian E Carpenter
- [Rswg] Re: RFC 9280: success or failure? And how … Russ Housley
- [Rswg] Re: [Ext] Re: RFC 9280: success or failure… Paul Hoffman
- [Rswg] Re: RFC 9280: success or failure? And how … Brian E Carpenter
- [Rswg] Re: RFC 9280: success or failure? And how … Carsten Bormann
- [Rswg] Re: RFC 9280: success or failure? And how … Alexis Rossi
- [Rswg] Re: RFC 9280: success or failure? And how … Brian E Carpenter
- [Rswg] RFC9280 updates [was: Re: RFC 9280: succes… Mirja Kuehlewind (IETF)
- [Rswg] Re: RFC9280 updates [was: Re: RFC 9280: su… Eliot Lear
- [Rswg] Re: RFC9280 updates [was: Re: RFC 9280: su… S Moonesamy