RFC 3716 on IETF in the Large: Administration and Execution

rfc-editor@rfc-editor.org Tue, 10 March 2020 20:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8486A3A0C5E for <ietf-announce@ietfa.amsl.com>; Tue, 10 Mar 2020 13:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id izrRcZd7bt9a for <ietf-announce@ietfa.amsl.com>; Tue, 10 Mar 2020 13:29:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7823F3A0C5C for <ietf-announce@ietf.org>; Tue, 10 Mar 2020 13:29:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1ECF8F4071D; Tue, 10 Mar 2020 13:29:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDM3MTYgb24gSUVURiBpbiB0aGUgTGFyZ2U6ICBBZG1pbmlzdHJhdGlvbiBhbmQgRXhlY3V0aW9uIA==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200310202904.1ECF8F4071D@rfc-editor.org>
Date: Tue, 10 Mar 2020 13:29:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/p6ZwQPYnYmkCmUBCyb6nQQk3haY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 20:29:10 -0000

RFC 3716 has been reclassified as Historic.

RFC 8717 updates RFCs 2028, 2418, 3005, 3710, 3929, 4633, and 6702. 
In addition, with the authorization of the IAB, it requested that 
the Informational RFC 3716 be made Historic (see Section 4).

By the process documented in
there should have been a Last Call for the status change and an
associated status-change document. Due to this being a somewhat
unusual case (RFC 3716 is an IAB document, and the changes was
approved by the IAB), this step was missed.

This "Moved to Historic" announcement has been reissued to note this fact.

        RFC 3716

        Title:      IETF in the Large: Administration 
                    and Execution 
        Author:     IAB Advisory Committee
        Status:     Historic
        Stream:     IAB
        Date:       March 2004
        Mailbox:    iab@iab.org
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-advcomm-01.txt

        URL:        https://www.rfc-editor.org/info/rfc3716

        DOI:        10.17487/RFC3716

In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB Advisory Committee (AdvComm), with a mandate to review the existing IETF administrative structure and relationships (RFC Editor, IETF Secretariat, IANA) and to propose changes to the IETF management process or structure to improve the overall functioning of the IETF.  The AdvComm mandate did not include the standards process itself.  This memo provides information for the Internet community. 

This document is a product of the Internet Architecture Board.

HISTORIC: This memo defines a Historic Document 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC