Transitioning to xml2rfc v2

RFC Series Editor <rse@rfc-editor.org> Fri, 20 December 2013 00:07 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0321AED42 for <ietf-announce@ietfa.amsl.com>; Thu, 19 Dec 2013 16:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 mA01Y2tMTHQZ; Thu, 19 Dec 2013 16:07:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E11E1AED40; Thu, 19 Dec 2013 16:07:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: RFC Series Editor <rse@rfc-editor.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Transitioning to xml2rfc v2
X-Test-IDTracker: no
X-IETF-IDTracker: 4.84
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131220000719.20383.59699.idtracker@ietfa.amsl.com>
Date: Thu, 19 Dec 2013 16:07:19 -0800
Cc: rfc-interest@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2013 00:07:20 -0000

In 2006, the RFC Editor began using xml2rfc v1 (if authors submitted an XML 
file) as part of the editing process for RFCs.  The code base for xml2rfc v1, 
however, was not easily supported and so work began on creating a much more 
supportable version of the code.  This new code base, xml2rfc v2, has been in 
testing for over a year and is now ready for production use by authors.  Starting 
1 January 2014, authors are encouraged to use the xml2rfc v2 software.  This 
software is available for use online at  http://xml.resource.org, or it can be 
installed locally.   

The new xml2rfc includes a validation step against the DTD, making the tool 
much more strict in what it will accept.  An XML file that you used with xml2rfc 
v1 may need some updates in order to run with xml2rfc v2.

We strongly encourage the use of xml2rfc v2, but the RFC Editor will continue 
to accept Internet-Drafts created using v1 that are approved for publication 
until 30 June 2014.  After that date, all XML files submitted to the RFC Editor 
must be compliant with xml2rfc v2.  Authors may also continue to submit 
documents in nroff or txt.

If you have questions about xml2rfc v2, please send them to the xml2rfc 
mailing list <xml2rfc@ietf.org>.

Heather Flanagan, RFC Series Editor
Jari Arkko, IETF Chair