UPDATED Call for Comment: RFC Format Drafts

IAB Executive Administrative Manager <execd@iab.org> Fri, 12 February 2016 17:35 UTC

Return-Path: <execd@iab.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68B001A802D; Fri, 12 Feb 2016 09:35:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IAB Executive Administrative Manager <execd@iab.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: UPDATED Call for Comment: RFC Format Drafts
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160212173524.31336.62857.idtracker@ietfa.amsl.com>
Date: Fri, 12 Feb 2016 09:35:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/IGnzylKKPhSvjjOsM-Lme8GdEfo>
Cc: rfc-interest@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 17:35:24 -0000

This is an announcement of an IETF-wide Call for Comment on the RFC 
Format Drafts. These documents are being considered for publication as 
Informational RFCs within the IAB stream.  The suggested reading order 
is:

1. The big picture

- - - Flanagan, H., "RFC Format Framework",
   http://datatracker.ietf.org/doc/draft-iab-rfc-framework/

2. The underlying vocabulary

- - - Hoffman, P., "The 'XML2RFC' version 3 Vocabulary",
    https://datatracker.ietf.org/doc/draft-iab-xml2rfc/

3. The outputs

- - - Hildebrand, J. and P. Hoffman, "HyperText Markup
   Language Request For Comments Format”,
   https://datatracker.ietf.org/doc/draft-iab-html-rfc/

- - - Flanagan, H., "Requirements for Plain Text RFCs",
   https://datatracker.ietf.org/doc/draft-iab-rfc-plaintext/

- - - Hansen, T., Masinter, L., and M. Hardy, "PDF for
   an RFC Series Output Document Format”,
   https://datatracker.ietf.org/doc/draft-iab-rfc-use-of-pdf/

- - - Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC",
   https://datatracker.ietf.org/doc/draft-iab-svg-rfc/

4. Generalized requirements

- - - Flanagan, H., "The Use of Non-ASCII Characters in RFCs",
   https://www.ietf.org/id/draft-iab-rfc-nonascii-00.pdf

- - - Flanagan, H., “CSS Requirements for RFCs”,
   https://datatracker.ietf.org/doc/draft-iab-rfc-css/

5. Workflow and tools (note that the examples draft will
   not become an RFC, but is necessary for the project)

- - - Hildebrand, J. and P. Hoffman, "RFC v3 Prep Tool Description",
   https://datatracker.ietf.org/doc/draft-iab-rfcv3-preptool/

- - - Hoffman, P. and T. Hansen, "Examples of the ‘XML2RFC'
   Version 2 and 3 Vocabularies”,
   http://datatracker.ietf.org/doc/draft-hoffman-rfcexamples/

6. The Statements of Work

- - - http://www.nostrum.com/~rjsparks/rfced/

The Call for Comment will last until 2016-03-11. Please send comments to
rfc-interest@rfc-editor.org and iab@iab.org. Please note that messages 
sent to rfc-interest from addresses that are not subscribed to the list 
will have to wait for moderation. To subscribe to rfc-interest, go to 
https://www.rfc-editor.org/mailman/listinfo/rfc-interest.

[The initial call for comments sent 2016-03-10 requested feedback only 
to iab@iab.org, which is not a public list. The feedback received to 
date will be forwarded to rfc-interest.]

For comments on individual drafts, please include the relevant document 
filename in the subject line.