xml2rfc v2 transition
RFC Series Editor <rse@rfc-editor.org> Thu, 03 July 2014 20:39 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 873AF1B2A1E for <ietf-announce@ietfa.amsl.com>; Thu, 3 Jul 2014 13:39:45 -0700 (PDT)
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 IN6iRjS7pFet; Thu, 3 Jul 2014 13:39:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 861F41B2A1B; Thu, 3 Jul 2014 13:39:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: RFC Series Editor <rse@rfc-editor.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: xml2rfc v2 transition
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140703203944.25295.49227.idtracker@ietfa.amsl.com>
Date: Thu, 03 Jul 2014 13:39:44 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/ImiU070fCSVejR-zIfB1Lh0PkE8
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: Thu, 03 Jul 2014 20:39:45 -0000
As a reminder to the community, the RFC Editor is transitioning completely to xml2rfc v2 for processing XML source for drafts this month. If your XML file does not parse using xml2rfc v2, it may be returned to you with a request to update the XML. Since we do appreciate receiving XML source for the drafts which are approved for publication, we encourage those who are still working with a tool-chain based on xml2rfc v1 (the TCL releases) to transition to v2 (the Python releases). The xml2rfc v2 processor is more strict about handling non-wellformed or invalid XML. Please see <http://xml2rfc.ietf.org> for more detail regarding strict handling of XML. The RFC Editor will continue to accept XML source for Internet-Drafts created using v1 that were approved for publication by 30 June 2014. Authors may also continue to submit documents in nroff or txt if an XML source is not available. The original announcement is available here: <http://www.ietf.org/mail-archive/web/ietf-announce/current/msg12251.html> If you have questions about xml2rfc v2, please send them to the xml2rfc mailing list <xml2rfc@ietf.org>. Heather Flanagan, RFC Series Editor
- xml2rfc v2 transition RFC Series Editor