Extended Community Call for Comments: <draft-rswg-rfc7990-updates-10> (RFC Formats and Versions)
IETF Secretariat <ietf-secretariat@ietf.org> Mon, 24 June 2024 08:37 UTC
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from [10.244.2.13] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id BF074C151072; Mon, 24 Jun 2024 01:37:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Extended Community Call for Comments: <draft-rswg-rfc7990-updates-10> (RFC Formats and Versions)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.16.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171921822728.293711.198107652266569098@dt-datatracker-ff65ff8f7-whn7d>
Date: Mon, 24 Jun 2024 01:37:07 -0700
Message-ID-Hash: TAWLEK77XGJY6LWYD4PIJEKRIIKP3ECW
X-Message-ID-Hash: TAWLEK77XGJY6LWYD4PIJEKRIIKP3ECW
X-MailFrom: ietf-secretariat@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-interest@rfc-editor.org, irtf-announce@irtf.org, iab@iab.org, rswg@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Reply-To: rsab@rfc-editor.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QJ7OaUblLp0KeNM4MQmJmlM4f_8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The RSAB is extending the community call for comments for draft-rswg-rfc7990-updates-10. This draft allows the RPC to change the XML of RFCs that have already been published. The RFC Series Approval Board (RSAB) has received a request from the RFC Series WG (RSWG) to approve the following document as informational RFC on the editorial stream: <draft-rswg-rfc7990-updates-10> (RFC Formats and Versions) Following RFC 9280, the RSAB solicits final comments from a wide range of communities. Please send substantive comments to the rsab@rfc-editor.org mailing lists by 2024-07-08. Please retain the beginning of the Subject line to allow automated sorting. Abstract In order to improve the readability of RFCs while supporting their archivability, the definitive version of the RFC Series transitioned from plain-text ASCII to XML using the RFCXML vocabulary; different publication versions are rendered from that base document. This document describes how RFCs are published. This document obsoletes RFC 7990. This document also updates the stability policy in RFC 9280. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-rswg-rfc7990-updates/ The RSAB would like to bring special attention to the fact that this document, which replaces RFC7990 to update the terminology and current RFC publication practice, also changes to the properties of the RFC series as currently outlined in RFC9280. This change means that once an RFC is published, the definitive and publication versions of an RFC will no longer be immutable, but may be updated by the RPC, with the utmost care being given to preserve the original semantic content.
- Extended Community Call for Comments: <draft-rswg… IETF Secretariat