IETF Logo Mail Archive

Re: [rfc-i] The RFC Format docs are now RFCs

Eliot Lear <lear@cisco.com> Sun, 18 December 2016 13:59 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 ED1381294C0 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 18 Dec 2016 05:59:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.19
X-Spam-Level:
X-Spam-Status: No, score=-7.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 hX7sJFy36XVK for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 18 Dec 2016 05:59:37 -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 658381294B8 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sun, 18 Dec 2016 05:59:37 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 915E1B82998; Sun, 18 Dec 2016 05:59:34 -0800 (PST)
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 18F17B81EE4; Sun, 18 Dec 2016 01:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 aOYiAtbChNY4; Sun, 18 Dec 2016 01:17:59 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by rfc-editor.org (Postfix) with ESMTPS id 472B6B81EE3; 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=1482052678; x=1483262278; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=nI7z25sKFHmF17Sb+vYbFDGQBqO0+i3P0kyV7OQQb/E=; b=j2L1WKVaC3UT+EsJ2EKM2uYYUwPas194V9Zihprg0J1AYLigfs5sTmw1 XfsFmyWcqihHWORNh/5EB3jC5SBA6YDjt9QIGyDN2nY4uEs8hAw/IOVlr SMYKR2ri4tZZChvfUlfb6s6PX+qC7lM4FCGp7yugbzYOYSDjwK/7SeMyJ U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AADZU1ZY/xbLJq1dGQEBAQEBAQEBAQEBBwEBAQEBgzcBAQEBAXmOVXOVZI9phSWCCiaFfAKCVxQBAgEBAQEBAQFiKIRpAQEEEhFmCxgqAgJXBgEMCAEBEA6ISQ6cdAGNdoIoL4pcAQEBAQEBAQEBAQEBAQEBAQEBAQEBDgoFiDOCXIQRgzOCPx4FlQOFbYNjgXyEBYdQih6GL5IoHzeBAhUOhgI9iHUBAQE
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
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>
X-Mailman-Approved-At: Sun, 18 Dec 2016 05:59:33 -0800
Subject: Re: [rfc-i] The RFC Format docs are now RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
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="===============8642081462927248645=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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
>


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

v2.23.0 | Report a Bug | By Email