Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission
Mark Nottingham <mnot@mnot.net> Mon, 26 July 2021 23:58 UTC
Return-Path: <mnot@mnot.net>
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 8685E3A00F7
for <rfc-markdown@ietfa.amsl.com>; Mon, 26 Jul 2021 16:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=mnot.net header.b=wluW3LLE;
dkim=pass (2048-bit key)
header.d=messagingengine.com header.b=h+O5+lOW
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 rDIgyg2-Op3x for <rfc-markdown@ietfa.amsl.com>;
Mon, 26 Jul 2021 16:58:28 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
[66.111.4.26])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 196C13A00E5
for <rfc-markdown@ietf.org>; Mon, 26 Jul 2021 16:58:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
by mailout.nyi.internal (Postfix) with ESMTP id 14F605C00F2;
Mon, 26 Jul 2021 19:58:25 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
by compute3.internal (MEProxy); Mon, 26 Jul 2021 19:58:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=
content-type:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to; s=fm3; bh=/
z3OLrBKuYoc7zuhiVI7rl1vl+3MgXZdpWDI4a2e9og=; b=wluW3LLEabqPQftej
/aR7uwygs97J1DFYn8eq/TL8an+DaaJpBHqpvIcKgdJVC7E/HHeCeqcG/ZmYxJlr
DfOkSMgqyCQkNqrYDYNzBva6R1Wi9gcK0bhXLVoSqIB2Fu/xlLjUFV+vFW49+OzR
FPdJ/+iojP8T+SLpFozvE9BxfSF8JGm7qQBMj3lnUr4+b13PA3h6IFnGhcDeHQFL
YygOrZKV21GUoSjDkkpPhGZZbvL9dvmk1zyMYQhCrY825cfapTpodnmJYwGVlabl
XjcpnSWKCWtWJ/vxHHl9WRqk3D2+9y7YIK16YhOtWE+WzNmlvBut/Q4VK14kDL1V
MCZiQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:content-transfer-encoding:content-type
:date:from:in-reply-to:message-id:mime-version:references
:subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
:x-sasl-enc; s=fm3; bh=/z3OLrBKuYoc7zuhiVI7rl1vl+3MgXZdpWDI4a2e9
og=; b=h+O5+lOWqHsbrMDft9d07VjZjRezHLssQZm+gVFChYNtlGpfXmRYDOv4a
IN9jKUtMjag1Dq3g9wTjy2lNNhMS1flIRXrlUjR9VvFPT2RN2s1zScmHTfDyZtEM
fNNSfJinmZnvwGmuNRX334Xv26wdACQDnUDwW65tES58QKQqQlzsodUc2a1kcN1W
ggsVSuifv29lAX2KyUP6i4IOyVu1CkiZv4/8r8VkAZfqwMYQFiqhPjMk4NYbD5DY
DrF4thQp5zJ0EQNY/Xo2fZumqdobCdxi3hUbI7notzvt+J6THqLim2UtabcAW2j4
ub3qtgjuqIYQRfDjdHype4zhIzOOA==
X-ME-Sender: <xms:H0z_YKPqp9MYdKkJ44181UPovQzD4qwOhYjfmvE-NjWEmxJgDS2nqw>
<xme:H0z_YI91h-sb3-WB13YxItXBgPWTBXqNuWaU6MNSuhaQVP4TssyZNe6v9_-x1R2G3
jnJ2t3KZCznLVBneQ>
X-ME-Received: <xmr:H0z_YBTgf1Xc8z6Hky9-b63LV4qrcMq90Yg2hd00P04D7GI-zbBnipPaMSxdRvvBA14vivZc5GkarPXCSfhqCfPgRgdC0DpLG5m6hTTAcaHkPkOo4prOaVOO>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrgeeigddvtdcutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu
pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg
hrnhepfeegvdfgjeegvdetuedukeevfefhheelieevjeejkefhffehkeejieekjedtheej
necuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhsthgvrh
fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgv
th
X-ME-Proxy: <xmx:H0z_YKvMF3q1EKafJeAMNjkRwfondOm4X702_vYzqgZ5j8NDkw4ppQ>
<xmx:H0z_YCeL65GzEhWJVi1NTLaRIIw215cX3-ovgzCv2t5ltcFYU4UP2w>
<xmx:H0z_YO3lKVt8sX1c6Mc4cLT579KK_5uVqvkC7kWgoo3cBRlpHjyd6w>
<xmx:IUz_YC48Hhp6waJQrQikc6Ca3Md-8kxxxHiZakI2XNoKfriIFA2LfA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon,
26 Jul 2021 19:58:22 -0400 (EDT)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <974739FF-7EB8-475B-A6A9-CB096D567E91@tzi.org>
Date: Tue, 27 Jul 2021 09:58:20 +1000
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <10368632-F4A3-4876-A4F0-81C3DDBE002F@mnot.net>
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>
<974739FF-7EB8-475B-A6A9-CB096D567E91@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/KiSbkP9WnPBFd8J_SwawscKDAgU>
Subject: Re: [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 23:58:34 -0000
Thanks, Carsten! I've converted one of my drafts' toolchain to use this, and it seems to work well (with some differences in the XML, which is to be expected). One question: do you have any plans to tidy the XML output (e.g., with indentation, etc.)? Cheers, > On 26 Jul 2021, at 7:03 pm, Carsten Bormann <cabo@tzi.org> wrote: > > 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.) > > > _______________________________________________ > Rfc-markdown mailing list > Rfc-markdown@ietf.org > https://www.ietf.org/mailman/listinfo/rfc-markdown -- Mark Nottingham https://www.mnot.net/
- 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