Browse Prior Art Database

The IESG and RFC Editor Documents: Procedures (RFC3932)

IP.com Disclosure Number: IPCOM000031767D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-08
Document File: 9 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Alvestrand: AUTHOR

Abstract

This document describes the IESG's procedures for handling documents submitted for RFC publication via the RFC Editor, subsequent to the changes proposed by the IESG at the Seoul IETF, March 2004.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 17% of the total text.

Network Working Group                                      H. Alvestrand

Request for Comments: 3932                                  October 2004

BCP: 92

Updates: 3710, 2026

Category: Best Current Practice

             The IESG and RFC Editor Documents: Procedures

Status of this Memo

   This document specifies an Internet Best Current Practices for the

   Internet Community, and requests discussion and suggestions for

   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document describes the IESG's procedures for handling documents

   submitted for RFC publication via the RFC Editor, subsequent to the

   changes proposed by the IESG at the Seoul IETF, March 2004.

   This document updates procedures described in RFC 2026 and RFC 3710.

1.  Introduction and History

   There are a number of different methods by which an RFC is published,

   some of which include review in the Internet Engineering Task Force

   (IETF), and some of which include approval by the Internet

   Engineering Steering Group (IESG):

   o  IETF Working Group (WG) to Standards Track: Includes WG consensus,

      review in the IETF, IETF Last Call, and IESG approval

   o  IETF WG to Experimental/Informational: Includes WG consensus,

      review in the IETF, and IESG approval

   o  Area Director (AD) sponsored to Standards Track: Includes review

      in the IETF, IETF Last Call, and IESG approval

   o  AD Sponsored Individual to Experimental/Informational: Includes

      some form of review in the IETF and IESG approval

   o  Documents for which special rules exist

Alvestrand               Best Current Practice                  [Page 1]

RFC 3932       IESG and RFC Editor Documents: Procedures    October 2004

   o  RFC Editor documents to Experimental/Informational

   This memo is only concerned with the IESG processing of the last

   category.

   Special rules apply to some documents, including documents from the

   Internet Architecture Board (IAB), April 1st RFCs, and republication

   of documents from other standards development organizations.  The

   IESG and the RFC Editor keep a running dialogue, in consultation with

   the IAB, on these other documents and their classification, but they

   are outside the scope of this memo.

   For the last few years, the IESG has reviewed all RFC Editor

   documents (documents submitted by individuals to the RFC Editor for

   RFC publication) before publication.  In 2003, this review was often

   a full-scale review of technical content, with the ADs attempting to

   clear points with the authors, stimulate revisions of the documents,

   encourage the authors to contact appropriate working groups and so

   on.  This was a considerable...