IAB approves RFC format-related drafts for publication

Robert Sparks <rjsparks@nostrum.com> Fri, 05 August 2016 19:43 UTC

Return-Path: <rjsparks@nostrum.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 18C2312D78F for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2016 12:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.186
X-Spam-Level:
X-Spam-Status: No, score=-3.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287] 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 nuL5VPz8-UTj for <ietf@ietfa.amsl.com>; Fri, 5 Aug 2016 12:43:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B04C12D7AE for <ietf@ietf.org>; Fri, 5 Aug 2016 12:43:02 -0700 (PDT)
Received: from unnumerable.local ([173.57.161.14]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u75Jh1mq003929 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for <ietf@ietf.org>; Fri, 5 Aug 2016 14:43:02 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [173.57.161.14] claimed to be unnumerable.local
From: Robert Sparks <rjsparks@nostrum.com>
Subject: IAB approves RFC format-related drafts for publication
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <5ad432b0-b312-0ec0-593f-7e621d595eae@nostrum.com>
Date: Fri, 5 Aug 2016 14:43:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------93E7DAF7141A17BE6FE65F3F"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u0sn9TCZIpojuKPqJ4KS_1KzqxE>
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: Fri, 05 Aug 2016 19:43:12 -0000

On 3 August 2016, the IAB approved the drafts [1] documenting the 
requirements for the new RFC format for publication. The RFC Format 
project goals include:

  * Supporting XML as the unchanging, underlying format
  * Creating TXT, PDF/A-3, and HTML as the outputs
  * Allowing SVG line art (black and white) as per a limited SVG profile
  * Allowing Non-ASCII characters in a controlled fashion

An FAQ about the new RFC Format is available online: 
https://www.rfc-editor.org/rse/format-faq/

With the approval of the drafts, an RFP will be posted shortly covering 
the tools required to make this new format a reality. The RFP will be 
posted on the IETF announce list, rfc-interest, and will be found on the 
IAOC's RFP website (https://iaoc.ietf.org/rfps.html). As the tools are 
developed, tested, and used, all the existing documents will go through 
a -bis process to capture what we learn through implementation. Please 
join rfc-interest@rfc-editor.org to participate in the discussion on the 
new format.

Many thanks to the RFC Format Design Team for their extraordinary efforts!

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

[1] Format Document reading order:

# The big picture

  * Flanagan, H. and N. Brownlee, "RFC Series Format Requirements and
    Future Development", RFC 6949, DOI 10.17487/RFC6949, May 2013,
    <http://www.rfc-editor.org/info/rfc6949>.

  * Flanagan, H., “RFC Format Framework”, Work in Progress,
    draft-iab-rfc-framework-06
    <https://datatracker.ietf.org/doc/draft-iab-rfc-framework/>, June 2016.

# The underlying vocabulary

  * Hoffman, P., “The ‘XML2RFC’ version 3 Vocabulary”, Work in Progress,
    draft-iab-xml2rfc-04
    <https://datatracker.ietf.org/doc/draft-iab-xml2rfc/>, June 2016.

# The outputs

  * Hildebrand, J. and P. Hoffman, “HyperText Markup Language Request
    For Comments Format”, Work in Progress, draft-iab-html-rfc-02
    <https://datatracker.ietf.org/doc/draft-iab-html-rfc/>, February 2016.

  * Flanagan, H. “CSS Requirements for RFCs”, Work in Progress,
    draft-iab-rfc-css-01
    <https://datatracker.ietf.org/doc/draft-iab-rfc-css/>, July 2016.

  * Flanagan, H., “Requirements for Plain Text RFCs”, Work in Progress,
    draft-iab-rfc-plaintext-03
    <https://datatracker.ietf.org/doc/draft-iab-rfc-plaintext/>, May 2016.

  * Hansen, T., Masinter, L., and M. Hardy, “PDF for an RFC Series
    Output Document Format”, Work in Progress,
    draft-iab-rfc-use-of-pdf-02
    <https://datatracker.ietf.org/doc/draft-iab-rfc-use-of-pdf/>, May 2016.

  * Brownlee, N., “SVG Drawings for RFCs: SVG 1.2 RFC”, Work in
    Progress, draft-iab-svg-rfc-02
    <https://datatracker.ietf.org/doc/draft-iab-svg-rfc/>, February 2016.

# Generalized requirements

  * Flanagan, H., “The Use of non-ASCII Characters in RFCs”, Work in
    Progress, draft-iab-rfc-nonascii-02
    <https://datatracker.ietf.org/doc/draft-iab-rfc-nonascii/>, April 2016.

# Workflow and tools

  * Hildebrand, J. and P. Hoffman, “RFC v3 Prep Tool Description”, Work
    in Progress, draft-iab-rfcv3-preptool-02
    <https://datatracker.ietf.org/doc/draft-iab-rfcv3-preptool/>,
    September 2015.

  * Hoffman, P. and T. Hansen, “Examples of the ‘XML2RFC’ Version 2 and
    3 Vocabularies”, Work in Progress, draft-hoffman-rfcexamples-04
    <https://datatracker.ietf.org/doc/draft-hoffman-rfcexamples/>, May
    2015. *Not to be published as an RFC.*