BCP 113, RFC 4333 on The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process

rfc-editor@rfc-editor.org Tue, 20 December 2005 01:48 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EoWcX-0007m2-Ok; Mon, 19 Dec 2005 20:48:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EoWcV-0007lu-Tj for ietf-announce@megatron.ietf.org; Mon, 19 Dec 2005 20:48:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19846 for <ietf-announce@ietf.org>; Mon, 19 Dec 2005 20:47:48 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EoWeo-0007ZN-8M for ietf-announce@ietf.org; Mon, 19 Dec 2005 20:51:16 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jBK1liw15146; Mon, 19 Dec 2005 17:47:44 -0800 (PST)
Message-Id: <200512200147.jBK1liw15146@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Mon, 19 Dec 2005 17:47:44 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: rfc-editor@rfc-editor.org
Subject: BCP 113, RFC 4333 on The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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


        BCP 113
        RFC 4333

        Title:      The IETF Administrative Oversight Committee (IAOC)
                    Member Selection Guidelines and Process
        Author(s):  G. Huston, Ed., B. Wijnen, Ed.
        Status:     Best Current Practice
        Date:       December 2005
        Mailbox:    gih@apnic.net, bwijnen@lucent.com
        Pages:      9
        Characters: 15396
        SeeAlso:    BCP0113

        I-D Tag:    draft-iab-iesg-iaoc-selection-03.txt

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


This memo outlines the guidelines for selection of members of the
IETF Administrative Oversight Committee, and describes the selection
process used by the IAB and the IESG.

This document is a product of the Internet Architecture Board. 

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.

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/rfc4333.txt"><ftp://ftp.isi.edu/in-notes/rfc4333.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce