Subject: Update: The transition to xml2rfc v3 (today!)

From: Heather Flanagan <[email-masked]>
Date: Mon, 16 Sep 2019 09:50:12 -0700

Hola a todos!

After many years of hard work by a very dedicated crew of volunteers, developers, and the RFC Editor team, the RFC Editor is now using xml2rfc v3 to publish RFCs. The RFC Editor will handle the conversion from v2 XML to v3 XML where necessary.

As for when the first document will actually be published using the v3 processes and outputs, that largely depends on the time it takes the authors and editors to get through AUTH48. We expect this to take a bit longer as everyone familiarizes themselves with the changes being made. I can say that all RFCs from RFC-to-be 8650 will be published in the new publication formats.

The xml2rfcv3 vocabulary specification is being updated now to reflect the changes made during implementation. The first -bis document for the vocabulary will be posted before IETF 106.

Additional information regarding the tools, transition details, and useful FAQs are included in the original message below.

Thank you all for your support!
Heather Flanagan, RSE

> On Sep 5, 2019, at 9:23 PM, RFC Editor <[email-masked]> wrote:
> 
> Greetings,
> 
> 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 [0] [1] [2] to
> create RFCs. (Authors do not have to change what they submit as an
> Internet-Draft.)
> 
> There will be new publication formats (HTML, PDF, and text) and an XML
> source file, which uses the v3 vocabulary as described in [3] and
> [4]. 
> 
> 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 [6] for more information.  
> 
> For more details on why this change is taking place, see the "RFC
> Format Framework” [5]. 
> 
> * How does this affect you?  
> Please see the transition details page [6], especially if you
> currently have a document in the RFC Editor queue [7].
> 
> * What if you find a bug in xml2rfc? 
> Please add a ticket to the issue tracker [8] or send mail to the
> xml2rfc-dev list [9].
> 
> [0] Tool: https://pypi.org/project/xml2rfc/
> [1] Intro: https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html
> [2] FAQ: https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html
> [3] RFC 7991: https://www.rfc-editor.org/rfc/rfc7991
> [4] Implementation Notes: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-09
> [5] RFC 7990: https://www.rfc-editor.org/rfc/rfc7990.txt
> [6] Transition Details: https://www.rfc-editor.org/rse/wiki/doku.php?id=v3implementation 
> [7] Current Queue: https://www.rfc-editor.org/current_queue.php
> [8] Issue Tracker: https://trac.tools.ietf.org/tools/xml2rfc/trac/
> [9] XML Development Mailing list: https://www.ietf.org/mailman/listinfo/xml2rfc-dev
> 
> Thank you.
> RFC Editor
>