[rfc-i] Fwd: New Version Notification for draft-flanagan-rfc-framework-03.txt

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


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

Hello all,

An updated framework draft for the format effort has been submitted.

- From the changelog for the draft:

  * XML for RFCs: additional details on changes added
  * Fixed references

Thanks,
Heather Flanagan
- -------- Forwarded Message --------
Subject:     New Version Notification for
draft-flanagan-rfc-framework-03.txt
Date:     Mon, 12 Jan 2015 12:16:20 -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-rfc-framework-03.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

Name:        draft-flanagan-rfc-framework
Revision:    03
Title:        RFC Format Framework
Document date:    2015-01-12
Group:        Individual Submission
Pages:        15
URL:           
http://www.ietf.org/internet-drafts/draft-flanagan-rfc-framework-03.txt
Status:        
https://datatracker.ietf.org/doc/draft-flanagan-rfc-framework/
Htmlized:       http://tools.ietf.org/html/draft-flanagan-rfc-framework-03
Diff:          
http://www.ietf.org/rfcdiff?url2=draft-flanagan-rfc-framework-03

Abstract:
   The canonical format for the RFC Series has been plain-text, ASCII-
   encoded for several decades.  After extensive community discussion
   and debate, the RFC Editor will be transitioning to XML as the
   canonical format, with different publication formats rendered from
   that base document.  These changes are intended to increase the
   usability of the RFC Series by offering documents that match the
   needs of a wider variety of stakeholders.  With these changes,
   however, comes an increase in complexity for authors, consumers, and
   the publisher of RFCs.  This document serves as the framework that
   describes the problems being solved and summarizes the many documents
   that capture the specific requirements for each aspect of the change
   in format.

                                                                                
 


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

iQEcBAEBAgAGBQJUtCxYAAoJEER/xjINbZoGlYwIAI5tfpcnSDEnRxSAYwLRsWRw
oyVwjsI3Ad6nMs/Cmvw7VJYFiPa/NUESsyugQe/vdNBEKw+XU3WntauI1XLp3QAR
4BwyvY9zxrv7fZnoJOIZ7A3nc05ndBAlKBlmQgasSAA3poI6kAErCdRx7tdpVUYT
hkPh2ne8NHGYZgw5rnB4oGLbxnFO0nSjdbzX3kvQHUcdJ29R2NSN+NLVGPuAn6fg
M8gCBZJKmTSeC3canhUZX8IB4k+h+qrp//8hL1r1autN4x3zRzUPYRzxCvMUEycK
OezoL60fkZehz2lxH3goNF6q0iszHz7FBstgq4+qt7X7LSCJ7aDIkkwEU4dZm3M=
=AtHh
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150112/4db15d5f/attachment.html>


More information about the rfc-interest mailing list