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

[rse at rfc-editor.org (Heather Flanagan (RFC Series Editor))]

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

FYI, another draft. Minor wording updates.

Please let me know if you have any questions!

- -Heather


- -------- Forwarded Message --------
Subject:     New Version Notification for
draft-flanagan-rfc-framework-04.txt
Date:     Sun, 21 Jun 2015 07:06:33 -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-04.txt
has been successfully submitted by Heather Flanagan and posted to the
IETF repository.

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

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

iQEcBAEBCAAGBQJVhscvAAoJEER/xjINbZoGZPQH/1bbhArwqfYMfVzo1ZV67FSD
T2oFvivR681lU49AQvctyGLFx6GpAbKFyQWdyipYAZYjBn2HVow1rSOWzox+ThCG
VMCjLkl7v/dDyePgkjo2/VX+smIrbY4msHN3K8FCQ6qdUqh4D29WRX8WruZurEZp
w0MB4MCXTg1TT2j7tcRY1YIySfJD0K/JfSe8CpihJrydjNnS/bub8FuQuhipQKGj
e97HHy/EGkPj1ZAxgN1wmyo5UouIllhEa7H5VOEtvsSYjG8W//zFarf5VtUVkrBw
opn2//ByoISRKJGoqoppDCIb+Di2CLZuXOyFZlvMml/lqh15xnsM7qCp2libHcw=
=Gl/O
-----END PGP SIGNATURE-----

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