Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0

Robert Moskowitz <> Thu, 29 August 2019 20:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B014120077; Thu, 29 Aug 2019 13:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U_xO_Tr4iUGK; Thu, 29 Aug 2019 13:49:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B24EA120073; Thu, 29 Aug 2019 13:49:22 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id B976F6211C; Thu, 29 Aug 2019 16:49:20 -0400 (EDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with LMTP id dlENU0EwTcX7; Thu, 29 Aug 2019 16:49:13 -0400 (EDT)
Received: from (unknown []) (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 083E062110; Thu, 29 Aug 2019 16:49:12 -0400 (EDT)
To: Henrik Levkowetz <>,,
References: <> <> <>
From: Robert Moskowitz <>
Message-ID: <>
Date: Thu, 29 Aug 2019 16:49:03 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0
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: Thu, 29 Aug 2019 20:49:24 -0000

On 8/29/19 4:24 PM, Henrik Levkowetz wrote:
> Hi Bob,
> On 2019-08-29 21:22, Robert Moskowitz wrote:
>> On 8/26/19 8:44 AM, Henrik Levkowetz wrote:
>>> Hi,
>>> This is an automatic notification about a new xml2rfc release,
>>> v2.25.0, generated when running the mkrelease script.
>> Notes on my experience with the upgrade:
>> I get the standard warning:
>> DEPRECATION: Python 2.7 will reach the end of its life on January 1st,
>> 2020. Please upgrade your Python as Python 2.7 won't be maintained after
>> that date. A future version of pip will drop support for Python 2.7.
>> I have both Python2 and 3 installed on my Fedora 30 system.
> This warning indicates either that the default python is still 2.7, or
> that the pip command you are running is symlinked to pip-2.7.
>> What is causing this message?  An old version of pip or xml2rfc?
> Pip.  The pip that comes with Python 2.7 gives the warning above.
> Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7),
> the installed version of xml2rfc now supports vocabulary v3.

I just asked on the Fedora list.  I am suppose to be running pip3, not 
just pip.  There is also a  pip2, but don't use it as it is the same as pip.

The default version is still 2.7:

$ python --version
Python 2.7.16

But Python3 is installed.  I am going to have to dig more.  Just for my 
own 'sanity'.  Ha!

>> Is there a way to install xml2rfc v3 to start checking it out without
>> loosing v2?
> xml2rfc v2 and v3 are supported by the same install.  In order to produce
> v3 output, use 'xml2rfc --v3 ...'.

I tried this with both drafts that are 'ready' and both gave me the warning:

draft-moskowitz-hip-hierarchical-hit-00.xml(14): Warning: Setting 
consensus="true" for IETF STD document (this is not the schema default, 
but is the only value permitted for this type of document)

I need to find where 'consensus' is explained.

> In order to convert your v2 xml files
> to v3 xml, use 'xml2rfc --v2v3 ...'.

 From what you say below, this is something I should do.  I also foresee 
a possible challenge in that I do a lot of copy and paste from old 
drafts to new, and I could end up dragging something into converted 
draft that is not for v3 from an unconverted old file.

Actually I have a number of drafts in various stages.  Ugh.

> Note that when speaking about 'v3' xml2rfc, there is a certain need to
> indicate which aspect of xml2rfc v3 support you are referring to:
> There is both the matter of the v3 xml vocabulary, where many v2 constructs
> are deprecated; and there are the v3 formatters, which are completely
> rewritten to handle the v3 xml.
> Now, having made that clear, I'm afraid that the following may cause some
> blurring again, but it's been done in the interest of making forward progress
> easier:  If you invoke one of the v3 formatters, by saying for instance
> 'xml2rfc --v3 --text ...', but your input file uses deprecated v2 elements,
> those will be quietly converted internally, using the v2-to-v3 converter,
> and then handed to the v3 formatter.  This of course adds a bit of magic
> to the process, and you will have better control of your output if you work
> with clean v3 input files.  Converting your v2 files to v3 with --v2v3 should
> give you a good starting point for that.
> I hope that helps.
> Best regards,
> 	Henrik