IETF Logo Mail Archive

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

"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Fri, 16 December 2016 17:14 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 03B6B12986F for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 09:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, 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 ChyYcTY7rGvH for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 09:14:31 -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 20F91129408 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Dec 2016 09:14:31 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D18DAB806C8; Fri, 16 Dec 2016 09:14:30 -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 7335CB806C8 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 09:14:29 -0800 (PST)
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 jedJ__-usorm for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 09:14:28 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 2CFB4B806A3 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 09:14:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 951E21E5661; Fri, 16 Dec 2016 09:13:17 -0800 (PST)
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 oxMWVTOACr43; Fri, 16 Dec 2016 09:13:17 -0800 (PST)
Received: from Heathers-MacBook-Pro.local (c-50-159-75-65.hsd1.wa.comcast.net [50.159.75.65]) by c8a.amsl.com (Postfix) with ESMTPSA id 52F351E55BB; Fri, 16 Dec 2016 09:13:17 -0800 (PST)
To: rfc-interest@rfc-editor.org, ietf@ietf.org
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
Message-ID: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org>
Date: Fri, 16 Dec 2016 09:14:27 -0800
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
Subject: [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="===============0263937882673894880=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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