<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hello all,<br>
<br>
An updated framework draft for the format effort has been submitted.<br>
<br>
- From the changelog for the draft:<br>
<br>
* XML for RFCs: additional details on changes added<br>
* Fixed references<br>
<br>
Thanks,<br>
Heather Flanagan<br>
- -------- Forwarded Message --------<br>
Subject: New Version Notification for
draft-flanagan-rfc-framework-03.txt<br>
Date: Mon, 12 Jan 2015 12:16:20 -0800<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br>
To: Heather Flanagan <a class="moz-txt-link-rfc2396E" href="mailto:rse@rfc-editor.org"><rse@rfc-editor.org></a>, Heather
Flanagan <a class="moz-txt-link-rfc2396E" href="mailto:rse@rfc-editor.org"><rse@rfc-editor.org></a><br>
<br>
<br>
<br>
A new version of I-D, draft-flanagan-rfc-framework-03.txt<br>
has been successfully submitted by Heather Flanagan and posted to
the<br>
IETF repository.<br>
<br>
Name: draft-flanagan-rfc-framework<br>
Revision: 03<br>
Title: RFC Format Framework<br>
Document date: 2015-01-12<br>
Group: Individual Submission<br>
Pages: 15<br>
URL:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-flanagan-rfc-framework-03.txt">http://www.ietf.org/internet-drafts/draft-flanagan-rfc-framework-03.txt</a><br>
Status:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-flanagan-rfc-framework/">https://datatracker.ietf.org/doc/draft-flanagan-rfc-framework/</a><br>
Htmlized:
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-flanagan-rfc-framework-03">http://tools.ietf.org/html/draft-flanagan-rfc-framework-03</a><br>
Diff:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-flanagan-rfc-framework-03">http://www.ietf.org/rfcdiff?url2=draft-flanagan-rfc-framework-03</a><br>
<br>
Abstract:<br>
The canonical format for the RFC Series has been plain-text,
ASCII-<br>
encoded for several decades. After extensive community
discussion<br>
and debate, the RFC Editor will be transitioning to XML as the<br>
canonical format, with different publication formats rendered
from<br>
that base document. These changes are intended to increase the<br>
usability of the RFC Series by offering documents that match the<br>
needs of a wider variety of stakeholders. With these changes,<br>
however, comes an increase in complexity for authors, consumers,
and<br>
the publisher of RFCs. This document serves as the framework
that<br>
describes the problems being solved and summarizes the many
documents<br>
that capture the specific requirements for each aspect of the
change<br>
in format.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of
submission<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
The IETF Secretariat<br>
<br>
<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2<br>
Comment: GPGTools - <a class="moz-txt-link-freetext" href="http://gpgtools.org">http://gpgtools.org</a><br>
<br>
iQEcBAEBAgAGBQJUtCxYAAoJEER/xjINbZoGlYwIAI5tfpcnSDEnRxSAYwLRsWRw<br>
oyVwjsI3Ad6nMs/Cmvw7VJYFiPa/NUESsyugQe/vdNBEKw+XU3WntauI1XLp3QAR<br>
4BwyvY9zxrv7fZnoJOIZ7A3nc05ndBAlKBlmQgasSAA3poI6kAErCdRx7tdpVUYT<br>
hkPh2ne8NHGYZgw5rnB4oGLbxnFO0nSjdbzX3kvQHUcdJ29R2NSN+NLVGPuAn6fg<br>
M8gCBZJKmTSeC3canhUZX8IB4k+h+qrp//8hL1r1autN4x3zRzUPYRzxCvMUEycK<br>
OezoL60fkZehz2lxH3goNF6q0iszHz7FBstgq4+qt7X7LSCJ7aDIkkwEU4dZm3M=<br>
=AtHh<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>