W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > February 2016

Fwd: UPDATED Call for Comment: RFC Format Drafts

From: Mark Nottingham <mnot@mnot.net>
Date: Sun, 14 Feb 2016 12:40:35 +1100
To: public-ietf-w3c <public-ietf-w3c@w3.org>
Message-Id: <CC54BF65-70FE-4FAE-BC5E-15740843A4BF@mnot.net>
This might be of interest to some W3C folks; in a nutshell, the RFC format is about to be modernised. 

Cheers,


> Begin forwarded message:
> 
> From: IAB Executive Administrative Manager <execd@iab.org>
> Subject: UPDATED Call for Comment: RFC Format Drafts
> Date: 13 February 2016 at 4:35:24 AM AEDT
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Cc: rfc-interest@rfc-editor.org
> Reply-To: ietf@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
> Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/IGnzylKKPhSvjjOsM-Lme8GdEfo>
> 
> 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.
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Sunday, 14 February 2016 01:41:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:10:24 UTC