RFC 8728 on RFC Editor Model (Version 2)
rfc-editor@rfc-editor.org Thu, 27 February 2020 18:20 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029263A0799 for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 10:20:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5OvFIo24hyZ for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 10:20:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2145C3A07D8 for <ietf-announce@ietf.org>; Thu, 27 Feb 2020 10:20:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D84EFF40765; Thu, 27 Feb 2020 10:20:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8728 on RFC Editor Model (Version 2)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200227182000.D84EFF40765@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:20:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/r4NUNWRBRRXhSrlUZvcyQB5aGZU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 18:20:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8728
Title: RFC Editor Model (Version 2)
Author: O. Kolkman, Ed.,
J. Halpern, Ed.,
R. Hinden, Ed.
Status: Informational
Stream: IAB
Date: February 2020
Mailbox: kolkman@isoc.org,
joel.halpern@ericsson.com,
bob.hinden@gmail.com
Pages: 19
Obsoletes: RFC 6635
I-D Tag: draft-ietf-iasa2-rfc6635bis-04.txt
URL: https://www.rfc-editor.org/info/rfc8728
DOI: 10.17487/RFC8728
The RFC Editor model described in this document divides the
responsibilities for the RFC Series into three functions: the RFC
Series Editor, the RFC Production Center, and the RFC Publisher.
Internet Architecture Board (IAB) oversight via the RFC Series
Oversight Committee (RSOC) is described, as is the relationship
between the IETF Administration Limited Liability Company and the
RSOC. This document reflects the experience gained with "RFC Editor
Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to
replace all references to the IETF Administrative Support Activity
(IASA) and related structures with those defined by the IASA 2.0
Model.
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
- RFC 8728 on RFC Editor Model (Version 2) rfc-editor