RFC 5620 on RFC Editor Model (Version 1)

rfc-editor@rfc-editor.org Tue, 18 August 2009 23:25 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4F233A6943 for <ietf-announce@core3.amsl.com>; Tue, 18 Aug 2009 16:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.013
X-Spam-Level:
X-Spam-Status: No, score=-17.013 tagged_above=-999 required=5 tests=[AWL=0.586, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myBYjDVnIZuS for <ietf-announce@core3.amsl.com>; Tue, 18 Aug 2009 16:25:06 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id ADD413A6CD8 for <ietf-announce@ietf.org>; Tue, 18 Aug 2009 16:25:05 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id DBFC130B8CB; Tue, 18 Aug 2009 16:25:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5620 on RFC Editor Model (Version 1)
From: rfc-editor@rfc-editor.org
Message-Id: <20090818232506.DBFC130B8CB@bosco.isi.edu>
Date: Tue, 18 Aug 2009 16:25:06 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 18 Aug 2009 23:25:06 -0000

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

        
        RFC 5620

        Title:      RFC Editor Model (Version 1) 
        Author:     O. Kolkman, Ed.,
                    IAB
        Status:     Informational
        Date:       August 2009
        Mailbox:    olaf@nlnetlabs.nl, 
                    iab@iab.org
        Pages:      19
        Characters: 40744
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-rfc-editor-model-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5620.txt

The RFC Editor performs a number of functions that may be carried out
by various persons or entities.  The RFC Editor model presented in
this document divides the responsibilities for the RFC Series into
four functions: The RFC Series Editor, the Independent Submission
Editor, the RFC Production Center, and the RFC Publisher.  It also
introduces the RFC Series Advisory Group and an (optional)
Independent Submission Stream Editorial Board.  The model outlined
here is intended to increase flexibility and operational support
options, provide for the orderly succession of the RFC Editor, and
ensure the continuity of the RFC series, while maintaining RFC
quality and timely processing, ensuring document accessibility,
reducing costs, and increasing cost transparency.  This memo 
provides information for the Internet community.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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
USC/Information Sciences Institute