Moved to Historic: RFC 3716 on IETF in the Large: Administration and Execution

rfc-editor@rfc-editor.org Thu, 27 February 2020 20:27 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 221F63A0B6E for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 12:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvCyyDHgNCW4 for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 12:27:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5DCC3A0B6B for <ietf-announce@ietf.org>; Thu, 27 Feb 2020 12:27:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9614BF40711; Thu, 27 Feb 2020 12:27:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Moved to Historic: RFC 3716 on IETF in the Large: Administration and Execution
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200227202736.9614BF40711@rfc-editor.org>
Date: Thu, 27 Feb 2020 12:27:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-ewoi11emg5UFhNkkJkGiDWTfYU>
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: Thu, 27 Feb 2020 20:27:52 -0000

RFC 3716 has been reclassified as Current Status.

See RFC 8717 and the IAB minutes for details 
<https://www.iab.org/documents/minutes/minutes-2019/iab-minutes-2019-03-06/>.
        
        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

        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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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