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

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Fri Sep 12 07:57:11 PDT 2014


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

Hello all,

I've tried to incorporate the feedback received so far, and have added a
change log to try and highlight what changes were made and where. 
Hopefully that will be helpful to you, and thank you to the person who
suggested.

As per usual, top-to-bottom reviews are more than welcome, but if you
have a particular issue you would like to see discussed in more detail
by the community, please pull it out into its own thread on this list.

- -Heather


- -------- Original Message --------
Subject:     New Version Notification for
draft-flanagan-rfc-framework-01.txt
Date:     Fri, 12 Sep 2014 07:53:25 -0700
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-01.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

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

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.

   Discussion of this draft takes place on the rfc-interest mailing list
   (rfc-interest at rfc-editor.org), which has its home page at
   https://www.rfc-editor.org/mailman/listinfo/rfc-interest.

                                                                                
 


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.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUEwnHAAoJEER/xjINbZoG9pIH/0NyOAuhsX87vwhj4/CHsBLc
6YnrIClUfXIzL5GfSRQEwgfONvjnpGDGjwGs9BlmdTI8tn5F0rNjFS4SqIYwPUfW
vEXkwLcYhBLcE5Vh9RqSlVB9DepsM/D6B7FQTVPh8Rbz20k1KHPjS/zpMmuNmS7U
gn32w70lQ9O7l31C4CCtrhkNte0V3Eu5UG0D9P16iEJW0mLdrqce4LHt2EqhzEnb
anuHOUNW+gLBVF18Hc5Vw8yoO3PNxGE4dFahkSWQKgoL9UGPdFC359/zcjdZIBD+
9Svcng6K3uMhrvVxvgzbINT8NqFnxFiE1rwB3gk0uRQxLgs05J0b+dDJgUd/xUw=
=tLjR
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20140912/375e4d7a/attachment-0001.html>


More information about the rfc-interest mailing list