[rfc-dist] RFC 3710 on An IESG charter

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Fri, 20 Feb 2004 15:07:03 -0800


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

        RFC 3710

        Title:      An IESG charter
        Author(s):  H. Alvestrand
        Status:     Informational
        Date:       February 2004
        Mailbox:    harald@alvestrand.no
        Pages:      12
        Characters: 24912
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iesg-charter-03.txt

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

This memo provides a charter for the Internet Engineering Steering
Group (IESG), a management function of the Internet Engineering Task
Force (IETF).  It is meant to document the charter of the IESG as it
is presently understood.

This document is a product of the Internet Engineering Steering

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@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@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@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.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <040220150550.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3710

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <040220150550.RFC@RFC-EDITOR.ORG>