[Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission
Carsten Bormann <cabo@tzi.org> Mon, 26 July 2021 09:04 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86CED3A21D2 for <rfc-markdown@ietfa.amsl.com>; Mon, 26 Jul 2021 02:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 g3xAE5hHg0lQ for <rfc-markdown@ietfa.amsl.com>; Mon, 26 Jul 2021 02:04:01 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888FA3A206B for <rfc-markdown@ietf.org>; Mon, 26 Jul 2021 02:04:01 -0700 (PDT)
Received: from smtpclient.apple (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYDVy0GH3z2xMV; Mon, 26 Jul 2021 11:03:54 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <777A0822-6C16-4967-ABD0-BD35359B9FC5@tzi.org>
Date: Mon, 26 Jul 2021 11:03:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <974739FF-7EB8-475B-A6A9-CB096D567E91@tzi.org>
References: <20210712034838.B461E209AFFB@ary.qy> <6c781dab-7a40-7031-be1c-d77a182f4cf4@gmail.com> <DE0CD982-D4BE-44A6-9234-B53A756E9717@mnot.net> <bbb8302a-4041-35db-ce61-d2a18b8ebeee@taugh.com> <AB6E5013-C14E-4962-8907-17F241971F9D@tzi.org> <20210719171839.GB24216@faui48e.informatik.uni-erlangen.de> <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org> <777A0822-6C16-4967-ABD0-BD35359B9FC5@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ayLOKJsXeIGb5rBViEDMuj7kd98>
Subject: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2021 09:04:07 -0000
Public service announcement: The, er, characteristic of the submission process explained below has been fixed during the pre-111 moratorium. So, starting from yesterday, you can now directly submit the kramdown-rfc generated hybrid v3 XML as Internet-Drafts; no additional step via -3c is needed any more. (The improvement of course also lets non-markdown drafts benefit that are edited directly in RFCXMLv2 or hybrid v3 XML.) Thanks to the tools team! Grüße, Carsten >> With the --v3 (-3) flag, kramdown-rfc2629 produces XML that xml2rfc can process, and that --v2v3 can turn into the current version of v3. > > … and if you want to submit this as an I-D, use > > kdrfc -3c foo.md > > and submit the foo.v2v3.xml *ONLY*. > > (I’ll probably add API submission soon.) > > Grüße, Carsten [1]: <https://mailarchive.ietf.org/arch/msg/wgchairs/EikOARXSYfKz9-D-YLSjNaVN7MU> * Merged in [19242] from jennifer@painless-security.com: Run v2v3 converter internally when v2 XML is submitted. Fixes #3305. (My more detailed description of the problem in <https://mailarchive.ietf.org/arch/msg/ietf-and-github/-neyBKvA24nCKh1r2ELz4taGz7s> contains a recommendation to do the v2v3 conversion locally before submission — this is of course still possible, but unless the I-D relies on a very recent xml2rfc fix that you have installed locally but may not have found its way into datatracker, no longer necessary.)
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Michael Richardson
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Miek Gieben
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Jay Daley
- Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary o… Carsten Bormann
- [Rfc-markdown] V3 weird stuff, was: Carsten: Re: … Julian Reschke
- Re: [Rfc-markdown] V3 weird stuff, was: Carsten: … Carsten Bormann
- [Rfc-markdown] No longer need to run xml2rfc --v2… Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Mark Nottingham
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Julian Reschke
- Re: [Rfc-markdown] No longer need to run xml2rfc … Carsten Bormann
- Re: [Rfc-markdown] No longer need to run xml2rfc … Julian Reschke