[rfc-i] Fwd: New Version Notification for draft-flanagan-plaintext-05.txt

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Mon Jan 12 13:42:22 PST 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hello all,

A revised draft for "Requirements for Plain-Text RFCs" has been posted.

- From the change log in the document:

   Abstract and Introduction: Revised for better readability; clarified
   the definition and implications of the term "plain-text"

   General Page Format Layout: Added explicit EOL detail and added some
   clarification regarding pagination

   Elements from the xml2rfc v3 vocabulary: section added


Discussion of new items or general points of confusion are welcome!
Heather


- -------- Forwarded Message --------
Subject:     New Version Notification for draft-flanagan-plaintext-05.txt
Date:     Mon, 12 Jan 2015 13:38:16 -0800
From:     internet-drafts at ietf.org
To:     Heather Flanagan <rse at rfc-editor.org>, Heather Flanagan
<rse at rfc-editor.org>



A new version of I-D, draft-flanagan-plaintext-05.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

Name:        draft-flanagan-plaintext
Revision:    05
Title:        Requirements for Plain-Text RFCs
Document date:    2015-01-12
Group:        Individual Submission
Pages:        8
URL:           
http://www.ietf.org/internet-drafts/draft-flanagan-plaintext-05.txt
Status:         https://datatracker.ietf.org/doc/draft-flanagan-plaintext/
Htmlized:       http://tools.ietf.org/html/draft-flanagan-plaintext-05
Diff:           http://www.ietf.org/rfcdiff?url2=draft-flanagan-plaintext-05

Abstract:
   In 2013, after a great deal of community discussion, the decision was
   made to shift from the plain-text, ASCII-only canonical format for
   RFCs to XML as the canonical format.  The high-level requirements
   that informed this change were defined in RFC6949, "RFC Series Format
   Requirements and Future Development."  Plain text is still an
   important format for many in the IETF community, and will still be
   one of the publication formats rendered from the XML.  This draft
   documents the rendering requirements for the plain-text RFC
   publication format.  These requirements do not apply to plain-text
   RFCs published before the format cut over.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUtD++AAoJEER/xjINbZoGNxEH/iC9Te7EqHlDG1vNz0TCQMSD
DUHAWi0k6CKEZIyxrunBS+w9ml2YrnOa5YM4T4884E9YQ1uNaUcTmifjL1oRgg1x
hNmHp/YYJshToYagoSlk3P0/atprn27RropFSz1hXmpv86HSZlYR+HuwZNf6O/OP
Dv1U7T3IVVEZ3VAMguU7nVOppZBVXEfCuBm3ORuSc2T7PW2ghzjIPKmA4hZUokjq
VnSSVBEwUigXyugpjyV/4sZ52wSH2Att2uQiOQTZJjeL2KWAsUIswZfMiBGdpRXd
FVe8Em/hFQ5JRY72YwX+x6XqOjXXDwS8LNuZQ61V1pJoHa5O4E0xUmTIdXSQ8eg=
=uDfY
-----END PGP SIGNATURE-----



More information about the rfc-interest mailing list