BCP 10, RFC 2727 on IAB and IESG Selection

RFC Editor <rfc-ed@ISI.EDU> Wed, 23 February 2000 23:18 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04697; Wed, 23 Feb 2000 18:18:44 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA07951 for ietf-123-outbound.10@ietf.org; Wed, 23 Feb 2000 18:15:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07902 for <all-ietf@loki.ietf.org>; Wed, 23 Feb 2000 18:05:15 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04582 for <all-ietf@ietf.org>; Wed, 23 Feb 2000 18:05:12 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA12144; Wed, 23 Feb 2000 15:05:13 -0800 (PST)
Message-Id: <200002232305.PAA12144@boreas.isi.edu>
To: IETF-Announce:;
Subject: BCP 10, RFC 2727 on IAB and IESG Selection
Cc: rfc-ed@ISI.EDU, poised@lists.tislabs.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 23 Feb 2000 15:05:13 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        BCP 10
        RFC 2727

        Title:	    IAB and IESG Selection, Confirmation, and Recall
                    Process: Operation of the Nominating and Recall
                    Committees 
        Author(s):  J. Galvin
        Status:     Best Current Practice
	Date:       February 2000
        Mailbox:    galvin@elistx.com
        Pages:      15
        Characters: 33396
	Obsoletes:  2282
        I-D Tag:    draft-ietf-poisson-nomcom-v2-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2727.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 Process for Organization of Internet
Standards ONgoing 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.
ftp://ftp.isi.edu/in-notes/rfc2727.txt"><ftp://ftp.isi.edu/in-notes/rfc2727.txt>