Re: [Rfc-markdown] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon

Carsten Bormann <> Mon, 20 July 2020 19:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9CEB93A0E34; Mon, 20 Jul 2020 12:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aRRKPuOQvCl9; Mon, 20 Jul 2020 12:24:52 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 62C6D3A0E41; Mon, 20 Jul 2020 12:24:50 -0700 (PDT)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4B9WrX4kXDzyXk; Mon, 20 Jul 2020 21:24:44 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Mon, 20 Jul 2020 21:24:43 +0200
Cc: Tools Team Discussion <>, IETF <>,, XML2RFC Interest Group <>, XML Developer List <>
X-Mao-Original-Outgoing-Id: 616965883.96795-cdae1ba58884b308ca21f79ef4572961
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Henrik Levkowetz <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 20 Jul 2020 19:24:55 -0000

On 2020-07-20, at 19:41, Henrik Levkowetz <> wrote:
> The longer answer is that (as indicated below) the default _output_ format
> will change to use the v3 renderer.  xml2rfc will continue to accept v2 input,
> but by default it will send it through the v2-to-v3 converter, and process
> the resulting v3 xml through the v3 formatters.
> If you want to use the v2 formatters directly from the v2 XML, you will need
> to give the --legacy switch to xml2rfc.

Makes a lot of sense to me.
The v2-to-v3 converter seems to work very well, and continuing to support all the XML2RFCv2 files lying around (and still being generated) is the right approach as well.

Thank you, Henrik!

Grüße, Carsten