IETF Logo Mail Archive

[Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)

Eliot Lear <lear@lear.ch> Thu, 30 June 2022 19:35 UTC

Return-Path: <lear@lear.ch>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87F9EC15948D for <rfced-future@ietfa.amsl.com>; Thu, 30 Jun 2022 12:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 fxmAwZ5uev4M for <rfced-future@ietfa.amsl.com>; Thu, 30 Jun 2022 12:35:16 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF328C15948C for <rfced-future@iab.org>; Thu, 30 Jun 2022 12:35:14 -0700 (PDT)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 25UJZAYR513049 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for <rfced-future@iab.org>; Thu, 30 Jun 2022 21:35:11 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1656617711; bh=//7JXX725uEsjGfFZ1A1Aj9xX4y2WXTqK5bbCBf56qI=; h=Date:Subject:References:To:From:In-Reply-To:From; b=q1TcydCFjzl3kLpY8jupM8LdvecrDWfk19HOeXBPaeJClOkCc+TQrO+3PFJvo+bj6 lY+oVqADGL0jhFpsDv/9UmZ5hEmh/9tXvL2dGvK6gnjm3xuYZlmhqR0mwIyfKX42k6 ymzn7NWOcULdZYVExtYLFjHYqm5RNvALuE46DjUs=
Message-ID: <94872e69-aadc-c73a-db7b-728127451176@lear.ch>
Date: Thu, 30 Jun 2022 21:35:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
References: <20220630185204.F0908289E0@rfcpa.amsl.com>
Content-Language: en-US
To: "rfced-future@iab.org" <rfced-future@iab.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <20220630185204.F0908289E0@rfcpa.amsl.com>
X-Forwarded-Message-Id: <20220630185204.F0908289E0@rfcpa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------JmXzuLE2OFkU8qx7QmGahY3L"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/T14PnpHzydhgiKkjFTmanvHR4LM>
Subject: [Rfced-future] Fwd: RFC 9280 on RFC Editor Model (Version 3)
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2022 19:35:20 -0000

Colleagues,

I'd like to congratulate you on your hard work.  This wasn't easy- there 
was a lot of give and take by everyone.  Now the fun begins.  I hope to 
see you all in the RSWG!

Eliot



-------- Forwarded Message --------
Subject: 	RFC 9280 on RFC Editor Model (Version 3)
Date: 	Thu, 30 Jun 2022 11:52:04 -0700 (PDT)
From: 	rfc-editor@rfc-editor.org
To: 	ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: 	rfc-editor@rfc-editor.org, drafts-update-ref@iana.org



A new Request for Comments is now available in online RFC libraries.

RFC 9280

Title: RFC Editor Model (Version 3) Author: P. Saint-Andre, Ed.
Status: Informational
Stream: IAB
Date: June 2022
Mailbox: stpeter@stpeter.im
Pages: 27
Obsoletes: RFC 8728
Updates: RFC 7841, RFC 8729, RFC 8730

I-D Tag: draft-iab-rfcefdp-rfced-model-13.txt

URL: https://www.rfc-editor.org/info/rfc9280

DOI: 10.17487/RFC9280

This document specifies version 3 of the RFC Editor Model. The model
defines two high-level tasks related to the RFC Series. First, policy
definition is the joint responsibility of the RFC Series Working
Group (RSWG), which produces policy proposals, and the RFC Series
Approval Board (RSAB), which approves such proposals. Second, policy
implementation is primarily the responsibility of the RFC Production
Center (RPC) as contractually overseen by the IETF Administration
Limited Liability Company (IETF LLC). In addition, various
responsibilities of the RFC Editor function are now performed alone
or in combination by the RSWG, RSAB, RPC, RFC Series Consulting
Editor (RSCE), and IETF LLC. Finally, this document establishes the
Editorial Stream for publication of future policy definition
documents produced through the processes defined herein.

This document obsoletes RFC 8728. This document updates RFCs 7841,
8729, and 8730.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

v2.23.0 | Report a Bug | By Email