[rfc-i] draft-flanagan-fiftyyears-00

Heather Flanagan <rse@rfc-editor.org> Sat, 20 October 2018 15:26 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFC812D4F0 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 20 Oct 2018 08:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 wUiLzxmqNq0x for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 20 Oct 2018 08:26:11 -0700 (PDT)
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 4AD4912958B for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sat, 20 Oct 2018 08:26:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1C602B80E99; Sat, 20 Oct 2018 08:25:42 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id CB66AB80E99 for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D04VquQ_lI9r for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:39 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 85D63B80E98 for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 135A11CA42E for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJX5qCw7pBAV for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:29 -0700 (PDT)
Received: from Heathers-MacBook-Pro-2.local (unknown [38.132.111.109]) by c8a.amsl.com (Postfix) with ESMTPSA id 271811C6297 for <rfc-interest@rfc-editor.org>; Sat, 20 Oct 2018 08:25:26 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
To: rfc-interest@rfc-editor.org
Message-ID: <beaf629b-a189-a2fb-0443-e5a6eeb4cd47@rfc-editor.org>
Date: Sat, 20 Oct 2018 08:25:57 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
Content-Language: en-US
Subject: [rfc-i] draft-flanagan-fiftyyears-00
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1235782523706963012=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

A -00 has been submitted for the Fifty Years of RFCs. This has been a 
fascinating document to pull together, and how did nearly fifty years 
pass since RFC 1 already??

https://datatracker.ietf.org/doc/draft-flanagan-fiftyyears/

The draft will definitely go through a few more iterations before it's 
ready for publication.  Feedback is, of course, always welcome.

FYI, the process for drafts coming from the RFC Editor is as follows:


0. RSE posts an individual submission, seeks public comment and review
1. After "sufficient" comment and review, the RSE asks the IAB to 
consider it for an IAB stream doc (all RFC Editor docs are published in 
the IAB stream)
2. The IAB doc process then kicks off (described in RFC 4845, relevant 
section included below).
3. Plan is to have this approved for publication at IETF 104, and 
actually published in April 2019.


-----

IAB publication process:

3. IAB RFC Publication Process

    The following is a description of the process used by the IAB to
    publish IAB documents as RFCs.

    1.  The document is determined to be an IAB document by the IAB, as
        described in Section 1.

    2.  The IAB publishes an IAB draft (draft-iab-*).  Comments on the
        draft are reviewed and may be integrated into successive
        iterations of the draft.  In addition to considering comments
        received on the draft, the IAB may elect to refer the document to
        individuals or groups and explicitly solicit comments as
        appropriate.

    3.  For documents intended to be published as BCPs, the document is
        passed to the Internet Engineering Steering Group (IESG) with a
        sponsoring Area Director (AD), and follows the process outlined
        in [SPONSOR].

    4.  For documents intended to be Informational RFCs, the remainder of
        this process is followed.

    5.  The chair of the IAB issues an IETF-wide Call for Comment on the
        IETF Announce mailing list.  The comment period is normally no
        shorter than four weeks.

    6.  Comments received are considered for integration into the
        document.  The IAB shall determine whether the document is ready
        for publication based on the comments received, or whether
        another round of document editing and, optionally, a further call
        for input is required.

    7.  The document is passed to the RFC Editor for publication as an
        IAB document Informational RFC.

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest