[rfc-i] The upcoming transition to xml2rfc v3
rfc-editor at rfc-editor.org
Thu Sep 5 21:23:25 PDT 2019
With the RFC format transition approaching quickly, we want to share
some of the transition details.
The RFC Editor will be switching to using xml2rfc v3    to
create RFCs. (Authors do not have to change what they submit as an
There will be new publication formats (HTML, PDF, and text) and an XML
source file, which uses the v3 vocabulary as described in  and
Next week the RFC Editor's code base and database will be updated.
>From 16 September 2019, the RFC Editor will be ready to publish in the
new format. See the transition details  for more information.
For more details on why this change is taking place, see the "RFC
Format Framework” .
* How does this affect you?
Please see the transition details page , especially if you
currently have a document in the RFC Editor queue .
* What if you find a bug in xml2rfc?
Please add a ticket to the issue tracker  or send mail to the
xml2rfc-dev list .
 Tool: https://pypi.org/project/xml2rfc/
 Intro: https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html
 FAQ: https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html
 RFC 7991: https://www.rfc-editor.org/rfc/rfc7991
 Implementation Notes: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-09
 RFC 7990: https://www.rfc-editor.org/rfc/rfc7990.txt
 Transition Details: https://www.rfc-editor.org/rse/wiki/doku.php?id=v3implementation
 Current Queue: https://www.rfc-editor.org/current_queue.php
 Issue Tracker: https://trac.tools.ietf.org/tools/xml2rfc/trac/
 XML Development Mailing list: https://www.ietf.org/mailman/listinfo/xml2rfc-dev
More information about the rfc-interest