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

Carsten Bormann <> Tue, 08 October 2019 22:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8C7BB1200B6; Tue, 8 Oct 2019 15:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id o5UwNnSKky6w; Tue, 8 Oct 2019 15:46:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9D8F8120072; Tue, 8 Oct 2019 15:46:39 -0700 (PDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 46nssR6GdTz10rL; Wed, 9 Oct 2019 00:46:35 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Wed, 9 Oct 2019 00:46:32 +0200
Cc: Tools Team Discussion <>, RFC Markdown <>, XML2RFC Interest Group <>,, IETF <>
X-Mao-Original-Outgoing-Id: 592267588.8788-baefa19dd9071f150dc18e6ec4c3da9a
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Henrik Levkowetz <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [Rfc-markdown] [Tools-discuss] [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: Tue, 08 Oct 2019 22:46:42 -0000

On Oct 9, 2019, at 00:18, Henrik Levkowetz <> wrote:
> Signed PGP part
> Hi Carsten,
> On 2019-10-08 23:48, Carsten Bormann wrote:
>> On Oct 8, 2019, at 23:23, Russ Housley <> wrote:
>>> (2) The default output formatters will change to v3.  The v2 formatters
>>>   will still be available by using a --legacy switch.
>> Please do this in a way that will not randomly break scripts and
>> other programs that need to run xml2rfc. (A calling script/program
>> has no idea what version of xml2rfc is installed locally.) [Actually,
>> that is also true of people calling xml2rfc…]
> Does it work for you if we say 'if you want v2 output, please add --legacy
> to your scripts already now’?

It sure works for me, but I don’t know all the other users of my software.

> The --legacy switch to force v2 output (for compatible input) has been
> available for around 6 months, so even if you don't have the bleeding
> edge version installed, this should work as a compatibility path, I think?

6 months is very short in the grand scheme of things.

Generally people will upgrade tools like kramdown-rfc and xml2rfc on different timelines.
(And there are also a few hundred makefiles in some repositories somewhere that call xml2rfc.)

With that out of the way, I must admit I don’t even understand what this means:

  Format Options:
    --v3                                with --text and --html: use the v3
                                        formatter, rather than the legacy one.
    --legacy                            with --text and --html: use the legacy
                                        text formatter, rather than the v3

Does the choice of “legacy” and “v3” formatter have an influence on the accepted XML vocabulary?  On the output format?  Both?  How?

Grüße, Carsten