ObsoletedBEST CURRENT PRACTICEIETF stream

RFC 3932: The IESG and RFC Editor Documents: Procedures

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5742.

Current version: RFC 5742IESG Procedures for Handling of Independent and IRTF Stream Submissions

In plain English — editorial summary, not part of the RFC

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. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC3932
Published
October 2004
Authors
H. Alvestrand
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
Pages
8
Also known as
Obsoleted by:
RFC 5742

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3932-the-iesg-and-rfc-editor-documents-procedures