[rfc-i] Fwd: Call for Comment: RFC Format Drafts

rse at rfc-editor.org (Heather Flanagan (RFC Series Editor)) Fri, 12 February 2016 15:42 UTC

From: "rse at rfc-editor.org"
Date: Fri, 12 Feb 2016 07:42:51 -0800
Subject: [rfc-i] Fwd: Call for Comment: RFC Format Drafts
In-Reply-To: <20160211173901.28789.59265.idtracker@ietfa.amsl.com>
References: <20160211173901.28789.59265.idtracker@ietfa.amsl.com>
Message-ID: <56BDFD7B.4020803@rfc-editor.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Hello all,

In case you missed yesterday's post to regarding the status of the
format documents, they are now out for community comment. Please send
comments of support, concern, or other feedback to the IAB
(iab at iab.org). If you have never posted to that list, it will be
temporarily held in moderation until your address can be put on the
white list.

Discussion on specific drafts or requests for clarification can always
be sent here to rfc-interest or to the draft authors.

Thank you for your time and interest,
Heather

- -------- Forwarded Message --------
Subject: Call for Comment: RFC Format Drafts
Date: Thu, 11 Feb 2016 09:39:01 -0800
From: IAB Executive Administrative Manager <execd at iab.org>
Reply-To: ietf at ietf.org, iab at iab.org
To: IETF Announcement List <ietf-announce at ietf.org>

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-10. Please send comments to
iab at iab.org. For comments on individual drafts, please include the
relevant document filename in the subject line.



-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJWvf17AAoJEJlIWQlAXuk2qdkP+wWPZdC4bZC6cl4urJuX2oUL
FZrP1zMNgylMAeBM+yfoUhA298Ml12rPlmQI+L5GE6YBUmPMs5tkw7KgZnw7djXj
9W8qgZoAzMmT9VJW08qeZLsX9IT/bwpLmWDdwyBeMqnETBJpnGePI5X2BScNeW5q
/Hmx7EUFCb9bjAS8yvfSMFr3hOPyJz/+9wUZjgXdnQ6/mEwvboXGmlWvgmDCmPWq
yCESDAJxE04LpCCQtdmM0ZDn3kMl9U3XKKq6WzxWcKfWlhjYcumCvTu2ihq2smSh
JlwatO61ey0GW3cldfksjfrK97/3ZffXPWRsuMVVlW+8eGlk1TGSuCr0+g/LGCug
hz91uAnBpRScDyFMW1BHKdPgnwa/IX/rQRsn0B037SxV3EuKqqZg18H9p9LuG47W
ICRfkyFJ18Z2QBlkJKjuGF0hdDwcvf4Gy/JHmbFbm+gOLy4ppOUkJsnY03HQ+48u
4uplH5JKrA/S8RVQQHq5l38UjD/6Ck7GbrLVhp+bhia0Hrnt222Y4K6xnDbs9ePs
DaGehF59b4OHRKi1BkaxneYg0JU2jwB5C87xLTgf0gAy2O6ois+z+1oKg9iYWLeK
Ol6Li8L/MWhnODGfsp/LDAsSOr9oMH2BG1ZfJEJAUQVzj/ZoOeoBHVG9OBapkrD2
7WO4DJGzP5HpgEpBPBEy
=jIJH
-----END PGP SIGNATURE-----