Browse Prior Art Database

RFC Editor Model (Version 1) (RFC5620)

IP.com Disclosure Number: IPCOM000186411D
Original Publication Date: 2009-Aug-01
Included in the Prior Art Database: 2009-Aug-19
Document File: 38 page(s) / 41K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

O. Kolkman: AUTHOR [+3]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group                                    O. Kolkman, Ed. Request for Comments: 5620                                           IAB Category: Informational                                      August 2009

                       RFC Editor Model (Version 1)

Abstract

   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.

Status of This Memo

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

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents in effect on the date of    publication of this document (http://trustee.ietf.org/license-info).    Please review these documents carefully, as they describe your rights    and restrictions with respect to this document.

Kolkman & IAB                Informational                      [Page 1]
 RFC 5620              RFC Editor Model (Version 1)           August 2009

 Table of Contents

   1. Introduction ....................................................3

   2. IAOC Implementation .............................................4

      2.1. Expenses for the RFC Editor ................................4

   3. RFC Editor Model ................................................5

      3.1. RFC Series Editor ..........................................6

      3.2. Independent Submission Editor ..............................8

      3.3. RFC Production Center ......................................9

      3.4. RFC Publisher .............................................11

   4. Committees .....................................................11

      4.1. RFC Series Advisory Group (RSAG) ..........................11

           4...