[Cellar] The upcoming transition to xml2rfc v3 (fwd) RFC Editor: The upcoming transition to xml2rfc v3
Michael Richardson <mcr@sandelman.ca> Sun, 08 September 2019 11:55 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DA4120018 for <cellar@ietfa.amsl.com>; Sun, 8 Sep 2019 04:55:51 -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, SPF_HELO_NONE=0.001, 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 cKlay48wpWbP for <cellar@ietfa.amsl.com>; Sun, 8 Sep 2019 04:55:48 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E37712001E for <cellar@ietf.org>; Sun, 8 Sep 2019 04:55:48 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [88.214.187.115]) by relay.sandelman.ca (Postfix) with ESMTPS id 4FD021F459 for <cellar@ietf.org>; Sun, 8 Sep 2019 11:55:47 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 574BC2025; Sun, 8 Sep 2019 12:56:09 +0100 (WEST)
From: Michael Richardson <mcr@sandelman.ca>
To: cellar@ietf.org
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: message/rfc822
Content-Disposition: inline; filename="977"
Content-Transfer-Encoding: 8bit
Content-Description: forwarded message
Date: Sun, 08 Sep 2019 12:56:09 +0100
Message-ID: <28860.1567943769@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/7SGH_DXo3ehLY9y6wl32yQVqNBY>
Subject: [Cellar] The upcoming transition to xml2rfc v3 (fwd) RFC Editor: The upcoming transition to xml2rfc v3
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Sep 2019 11:55:51 -0000
--- Begin Message ---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--- End Message ---
- [Cellar] The upcoming transition to xml2rfc v3 (f… Michael Richardson
- Re: [Cellar] The upcoming transition to xml2rfc v… Steve Lhomme