BCP 101, RFC 4071 on Structure of the IETF Administrative Support Activity (IASA)

rfc-editor@rfc-editor.org Wed, 20 April 2005 23:11 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOOM5-0002Fh-E1; Wed, 20 Apr 2005 19:11:37 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOOM2-0002Eu-Ht for ietf-announce@megatron.ietf.org; Wed, 20 Apr 2005 19:11:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03830 for <ietf-announce@ietf.org>; Wed, 20 Apr 2005 19:11:31 -0400 (EDT)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOOXL-0003aM-Pn for ietf-announce@ietf.org; Wed, 20 Apr 2005 19:23:16 -0400
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j3KNAR625077; Wed, 20 Apr 2005 16:10:27 -0700 (PDT)
Message-Id: <200504202310.j3KNAR625077@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: Wed, 20 Apr 2005 16:10:27 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: rfc-editor@rfc-editor.org
Subject: BCP 101, RFC 4071 on Structure of the IETF Administrative Support Activity (IASA)
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 101
        RFC 4071

        Title:      Structure of the IETF Administrative Support
                    Activity (IASA)
        Author(s):  R. Austein, Ed., B. Wijnen, Ed.
        Status:     Best Current Practice
        Date:       April 2005
        Mailbox:    sra@isc.org, bwijnen@lucent.com
        Pages:      20
        Characters: 48614
        SeeAlso:    BCP 101

        I-D Tag:    draft-ietf-iasa-bcp-07.txt

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

This document describes the structure of the IETF Administrative
Support Activity (IASA) as an activity housed within the Internet
Society (ISOC).  It defines the roles and responsibilities of the
IETF Administrative Oversight Committee (IAOC), the IETF
Administrative Director (IAD), and ISOC in the fiscal and
administrative support of the IETF standards process.  It also
defines the membership and selection rules for the IAOC.

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

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.
IETF-Announce mailing list