RFC 6635 on RFC Editor Model (Version 2)

rfc-editor@rfc-editor.org Mon, 11 June 2012 22:49 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 A81CD11E80C6 for <ietf-announce@ietfa.amsl.com>; Mon, 11 Jun 2012 15:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.32
X-Spam-Level:
X-Spam-Status: No, score=-104.32 tagged_above=-999 required=5 tests=[AWL=1.357, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V21t-MOw5+yI for <ietf-announce@ietfa.amsl.com>; Mon, 11 Jun 2012 15:49:18 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id D6CF011E80A3 for <ietf-announce@ietf.org>; Mon, 11 Jun 2012 15:49:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7D445B1E016; Mon, 11 Jun 2012 15:49:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6635 on RFC Editor Model (Version 2)
From: rfc-editor@rfc-editor.org
Message-Id: <20120611224912.7D445B1E016@rfc-editor.org>
Date: Mon, 11 Jun 2012 15:49:12 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Mon, 11 Jun 2012 22:49:18 -0000

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

        
        RFC 6635

        Title:      RFC Editor Model (Version 2) 
        Author:     O. Kolkman, Ed.,
                    J. Halpern, Ed.,
                    IAB
        Status:     Informational
        Stream:     IAB
        Date:       June 2012
        Mailbox:    olaf@nlnetlabs.nl, 
                    joel.halpern@ericsson.com, 
                    iab@iab.org
        Pages:      21
        Characters: 48170
        Obsoletes:  RFC5620

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

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

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 Administrative Oversight Committee (IAOC) and the
RSOC.  This document reflects the experience gained with "RFC Editor
Model (Version 1)", documented in RFC 5620, and obsoletes that
document.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

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
Association Management Solutions, LLC