Re: The RFC Format docs are now RFCs

Eliot Lear <lear@cisco.com> Sun, 18 December 2016 09:18 UTC

Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432AC126579 for <ietf@ietfa.amsl.com>; Sun, 18 Dec 2016 01:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.621
X-Spam-Level:
X-Spam-Status: No, score=-17.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Y9tBFCvV5i-9 for <ietf@ietfa.amsl.com>; Sun, 18 Dec 2016 01:17:58 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 746BA12943E for <ietf@ietf.org>; Sun, 18 Dec 2016 01:17:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7827; q=dns/txt; s=iport; t=1482052677; x=1483262277; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=nI7z25sKFHmF17Sb+vYbFDGQBqO0+i3P0kyV7OQQb/E=; b=UHgT8tYo0hSGljFhQ50ji333qwndfLC6e70MQ++7bZ5MSWPz0Z7qYgFg mmGVvlsNixwHH4VcTIpAMx3xTl09K+shBsF2O5qNK14NotBGEzXhBCwrv Nu1UnIC2sGGtSfmUHKg9DIAcxq95UidSAj1zbhS8DTm1w1k83XhnZ9iYb 8=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D+AADZU1ZY/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzcBAQEBAXmOVXOVZI9phSWCCiaFfAKCVxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?pAQEEEhFmCxgqAgJXBgEMCAEBEA6ISQ6cdAGNdoIoL4pcAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBDgoFiDOCXIQRgzOCPx4FlQOFbYNjgXyEBYdQih6GL5IoHzeBAhU?= =?us-ascii?q?OhgI9iHUBAQE?=
X-IronPort-AV: E=Sophos;i="5.33,368,1477958400"; d="asc'?scan'208,217";a="650819080"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2016 09:17:55 +0000
Received: from [10.61.67.145] (ams3-vpn-dhcp913.cisco.com [10.61.67.145]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id uBI9HsIX004765; Sun, 18 Dec 2016 09:17:55 GMT
Subject: Re: The RFC Format docs are now RFCs
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, rfc-interest@rfc-editor.org, ietf@ietf.org
References: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org>
From: Eliot Lear <lear@cisco.com>
Message-ID: <1cc7fa0a-5f4f-0c08-071d-a1a9b1f7aa20@cisco.com>
Date: Sun, 18 Dec 2016 10:17:53 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="V7tIT5tf9ujqakkGv43D5s9JT8HNDWui5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ulTtsBLJwIeVMuDy_XifxJHEgGw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2016 09:18:01 -0000

Congratulations to all!

Eliot


On 12/16/16 6:14 PM, Heather Flanagan (RFC Series Editor) wrote:
>
> Hello all,
>
> The RFC Format requirements documents were published this morning.
> This represents an enormous amount of work on the part of the RFC
> Format Design Team, and an enormous amount of patience and feedback
> from the community. Of course, the work isn't quite done - all of
> these RFCs will undergo a -bis cycle so we can document the "as built"
> instead of just the "as proposed." But regardless of the amount of
> work still to come, this is a big milestone for the project!
>
> So, thank you all, and stay tuned for the next steps of code
> development, testing, and collecting feedback!
>
> -Heather Flanagan, RSE
>
> The RFC Format Design Team:
>
>   * Nevil Brownlee (ISE)
>   * Heather Flanagan (RSE)
>   * Tony Hansen
>   * Joe Hildebrand
>   * Paul Hoffman
>   * Ted Lemon
>   * Julian Reschke
>   * Adam Roach
>   * Alice Russo
>   * Robert Sparks (Tools Team liaison)
>   * Dave Thaler
>
>
> The RFCs, in suggested reading order:
>
>   * "RFC Format Framework " - https://www.rfc-editor.org/info/rfc7990
>   * "The "xml2rfc" Version 3 Vocabulary" -
>     https://www.rfc-editor.org/info/rfc7991
>   * "HTML Format for RFCs" - https://www.rfc-editor.org/info/rfc7992
>   * "Cascading Style Sheets (CSS) Requirements for RFCs" -
>     https://www.rfc-editor.org/info/rfc7993
>   * "Requirements for Plain-Text RFCs" -
>     https://www.rfc-editor.org/info/rfc7994
>   * "PDF Format for RFCs" - https://www.rfc-editor.org/info/rfc7995
>   * "SVG Drawings for RFCs: SVG 1.2 RFC" -
>     https://www.rfc-editor.org/info/rfc7996
>   * "The Use of Non-ASCII Characters in RFCs" -
>     https://www.rfc-editor.org/info/rfc7997
>   * ""xml2rfc" Version 3 Preparation Tool Description" -
>     https://www.rfc-editor.org/info/rfc7997
>