[rfc-i] The upcoming transition to xml2rfc v3

RFC Editor <rfc-editor@rfc-editor.org> Fri, 06 September 2019 04:23 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4911A120B5C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 5 Sep 2019 21:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id cfYBoguJ6Otb for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 5 Sep 2019 21:23:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 826861208E4 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 5 Sep 2019 21:23:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9605DB80EAD; Thu, 5 Sep 2019 21:23:30 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 6000) id 6A02DB80EAD; Thu, 5 Sep 2019 21:23:26 -0700 (PDT)
Date: Thu, 05 Sep 2019 21:23:25 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: RFC Interest <rfc-interest@rfc-editor.org>, ietf@ietf.org
Message-ID: <20190906042325.GC12952@rfc-editor.org>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: [rfc-i] The upcoming transition to xml2rfc v3
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: irsg@irtf.org, rsoc@iab.org, IESG <iesg@ietf.org>, "RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org>, iab@iab.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>


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

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

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
rfc-interest mailing list