BCP 10, RFC 3777 on IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees

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

        BCP 10
        RFC 3777

        Title:      IAB and IESG Selection, Confirmation, and Recall
                    Process: Operation of the Nominating and Recall
                    Committees
        Author(s):  J. Galvin, Ed.
        Status:     Best Current Practice
        Date:       June 2004
        Mailbox:    galvin+ietf@elistx.com
        Pages:      34
        Characters: 76395
        Obsoletes:  2727
        SeeAlso:    BCP 10

        I-D Tag:    draft-ietf-nomcom-rfc2727bis-09.txt

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

The process by which the members of the IAB and IESG are selected,
confirmed, and recalled is specified.  This document is a
self-consistent, organized compilation of the process as it was known
at the time of publication.

This document is a product of the Operation of the IESG/IAB
Nominating and Recall Committees Working Group of the IETF.

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.