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

Robert Moskowitz <rgm@htt-consult.com> Thu, 10 October 2019 13:12 UTC

Return-Path: <rgm@htt-consult.com>
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 BAEF212002E; Thu, 10 Oct 2019 06:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KrwvO2LOlNT; Thu, 10 Oct 2019 06:12:36 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6BD120026; Thu, 10 Oct 2019 06:12:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id BBC376211F; Thu, 10 Oct 2019 09:12:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HqqMajTfPWN2; Thu, 10 Oct 2019 09:12:29 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id CFC726211C; Thu, 10 Oct 2019 09:12:25 -0400 (EDT)
To: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, Job Snijders <job@instituut.net>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, IETF <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <858628DA-84DA-4982-89D7-D652E04ACA10@gmail.com> <da8ffcbf-33dd-6fe9-e251-0e3de47c611f@levkowetz.com> <CACWOCC-uuYGz54dExA5CwftowbpcBq4kQHJwCBWHNC1za_q70w@mail.gmail.com> <fc581783-1629-0a18-7c9c-0e5daeb425b8@it.aoyama.ac.jp>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <7c90f3be-901c-ff3a-ff68-b226d9084592@htt-consult.com>
Date: Thu, 10 Oct 2019 09:12:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <fc581783-1629-0a18-7c9c-0e5daeb425b8@it.aoyama.ac.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/AvKPryd42BpIo3xLknAsXGSk1dw>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] End of support for xml2rfc on Python 2.x is coming soon
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: Thu, 10 Oct 2019 13:12:38 -0000


On 10/9/19 2:52 AM, Martin J. Dürst wrote:
> On 2019/10/09 09:00, Job Snijders wrote:
>
>> Between the name of the tool (note the 2 in "xlm2rfc"), the industry's
>> transition from python 2 to python 3, and IETF's transition from the
>> v2 to the v3 RFC XML format, it is no surprise to me end users easily
>> become confused. A simple strong message that python2 can't be used
>> might be helpful, even if it appears somewhat unforgiving.
> What about changing xml2rfc's name to xml3rfc? That way, xml3rfc, python
> 3, v3 of RFC XML, and pip3 would all align :-).

because it is suppose to be translated as "xml formatting TO RFC 
formatting"?

And there is some confusion?  It was xml2rfc back in v1.

Finally who remembers that originally it was called Blutooth after King 
Harald Blutooth?  (or somesuch spelling), and despite considerable 
documentation as to the origin of the name, the press won and it became 
Bluetooth?

:)