[rfc-dist] BCP 92, RFC 3932 on The IESG and RFC Editor Documents: Procedures

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Oct 8 16:43:50 PDT 2004

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

        BCP 92
        RFC 3932

        Title:      The IESG and RFC Editor Documents: Procedures
        Author(s):  H. Alvestrand
        Status:     Best Current Practice
        Date:       October 2004
        Mailbox:    harald at alvestrand.no
        Pages:      8
        Characters: 17093
        Updates:    3710, 2026

        I-D Tag:    draft-iesg-rfced-documents-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3932.txt

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 is a product of the Internet Engineering Steering Group.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list