[rfc-i] Update: The transition to xml2rfc v3 (today!)

Heather Flanagan <rse@rfc-editor.org> Mon, 16 September 2019 16:50 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2AE120856 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 16 Sep 2019 09:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYvfs8SAqFEg for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 16 Sep 2019 09:50:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4863B120867 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Mon, 16 Sep 2019 09:50:17 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 07E14B817A3; Mon, 16 Sep 2019 09:50:07 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9B0C8B817A2; Mon, 16 Sep 2019 09:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pWYx6T3Ybx75; Mon, 16 Sep 2019 09:50:04 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id F405DB817A1; Mon, 16 Sep 2019 09:50:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 5F95B202186; Mon, 16 Sep 2019 09:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30N3zEdLHY-W; Mon, 16 Sep 2019 09:50:07 -0700 (PDT)
Received: from [10.198.42.38] (c-71-231-216-10.hsd1.wa.comcast.net [71.231.216.10]) by c8a.amsl.com (Postfix) with ESMTPSA id C7AA2202185; Mon, 16 Sep 2019 09:50:06 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <20190906042325.GC12952@rfc-editor.org>
Date: Mon, 16 Sep 2019 09:50:12 -0700
Message-Id: <7585D2DD-A910-400C-94BF-11CD75C7345B@rfc-editor.org>
References: <20190906042325.GC12952@rfc-editor.org>
To: RFC Interest <rfc-interest@rfc-editor.org>, IETF discussion list <ietf@ietf.org>, wgchairs@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Subject: [rfc-i] Update: The transition to xml2rfc v3 (today!)
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 <rsoc@iab.org>, IESG <iesg@ietf.org>, "RFC ISE \(Adrian Farrel\)" <rfc-ise@rfc-editor.org>, IAB IAB <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>

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 <rfc-editor@rfc-editor.org> 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
> 

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest