IETF Logo Mail Archive

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

Martin J. Dürst <duerst@it.aoyama.ac.jp> Wed, 09 October 2019 06:52 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 CF3C31200E3; Tue, 8 Oct 2019 23:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 4MvsJsY-CYgU; Tue, 8 Oct 2019 23:52:46 -0700 (PDT)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-eopbgr1400095.outbound.protection.outlook.com [40.107.140.95]) (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 8DD8C120108; Tue, 8 Oct 2019 23:52:46 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Tnfe23Lyu0SQg7PgfiS+EP78182FZSSQIcLQXdvsGM0pL4CMSu6BBpK4nNgDrPK4aDO5sxNkEHUxVZoGW4KZigb+PW9HFUxKIzO1DmxGxVLJ5Td//pV9q43D4C1v16DfzGLcjRN5cuU4eki0FgmnQj1ScANjr2Jlxll+1bjPjrXf2axqYyySIP46iM65JuZGr3He5nMRIkmgA32B0gKkE8WJwkh25TmsFGEOEIo1deWCulT9KswC/1W9tUO2us3oLwpgUsrr0BCdJ1w4EtcpI4c9YW7R389FaBwEFyG8TQNS48L0Lx/6RHbY/2zWzT/sqlZAd8+Kp6I4keP+TnhiPw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fOg+PDuhYVcprDge44ixo+7gC5Hwes5WONqPo7LIIJE=; b=VzYinOV7WQfNYJyBrO+KkrzZq4MlYmy3ukNDSjDsSmqUw2E9jh/9JU15dh7gMOPT0Q04LmaJEScmUPfope+tIsO3mPDU+rOEjm2NnmfuhNTceKZOJNxdLgn+0dXk5PIvBwdbcEQ3kSljwU9abisIEwp3jveIst8TNvBaI5pqcQtoD65bFLCeeoCnC7j4TAu4/fPNJXWdQJri+Tl0mKE7NcvdaOlXlskiXtVifw81CtAkNxduD/p6UOjdH0FuOufs2oH4qMKt9Xtf/MONCkl80WXOOrX28RIsHWWxI+Bg5NggiSIy74J8EVTqNg3knI0ThwFwAyWBzsHKifK8/paNQw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fOg+PDuhYVcprDge44ixo+7gC5Hwes5WONqPo7LIIJE=; b=O7n4L8Fgk9Te2u8FIS10qqoip4fcB9CcYqlfQr//V6CaoaL3l32y1IAaHHZnnMvjcgc3iNqRbSdsOfIB2d3otwvruJVF65FMORgT41JOvMK1K0n/E+iuQzPoYwqyLOih+LWSeg3jDQTtHm7BOxX482XGEcF1p2s5kCessUWSA74=
Received: from OSAPR01MB2193.jpnprd01.prod.outlook.com (52.134.235.146) by OSAPR01MB4545.jpnprd01.prod.outlook.com (20.179.176.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.24; Wed, 9 Oct 2019 06:52:44 +0000
Received: from OSAPR01MB2193.jpnprd01.prod.outlook.com ([fe80::a418:e2c6:45b5:dc38]) by OSAPR01MB2193.jpnprd01.prod.outlook.com ([fe80::a418:e2c6:45b5:dc38%7]) with mapi id 15.20.2327.026; Wed, 9 Oct 2019 06:52:43 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: 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>, Fred Baker <fredbaker.ietf@gmail.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
Thread-Topic: [xml2rfc-dev] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon
Thread-Index: AQHVfiH/y0WtOkFie0+XuTKWAq7XJ6dRUamAgAAbFgCAAFccAA==
Date: Wed, 09 Oct 2019 06:52:43 +0000
Message-ID: <fc581783-1629-0a18-7c9c-0e5daeb425b8@it.aoyama.ac.jp>
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>
In-Reply-To: <CACWOCC-uuYGz54dExA5CwftowbpcBq4kQHJwCBWHNC1za_q70w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYCPR01CA0104.jpnprd01.prod.outlook.com (2603:1096:405:4::20) To OSAPR01MB2193.jpnprd01.prod.outlook.com (2603:1096:603:17::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [133.2.0.65]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8b82439f-e3c5-4666-4169-08d74c854901
x-ms-traffictypediagnostic: OSAPR01MB4545:
x-microsoft-antispam-prvs: <OSAPR01MB45450A74CF4F6C8E5C62B451CA950@OSAPR01MB4545.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 018577E36E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(39840400004)(346002)(376002)(189003)(199004)(81156014)(26005)(66556008)(64756008)(66446008)(31696002)(85182001)(85202003)(86362001)(4744005)(81166006)(66476007)(66946007)(6246003)(4326008)(6512007)(31686004)(6436002)(5660300002)(6486002)(8936002)(2906002)(486006)(229853002)(3846002)(6116002)(2616005)(786003)(99286004)(256004)(11346002)(446003)(102836004)(76176011)(386003)(6506007)(53546011)(52116002)(8676002)(54906003)(186003)(476003)(71190400001)(305945005)(71200400001)(66066001)(7736002)(508600001)(14454004)(316002)(25786009)(110136005); DIR:OUT; SFP:1102; SCL:1; SRVR:OSAPR01MB4545; H:OSAPR01MB2193.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5y4bepYZzmb823vHL0/Um1h+YWa6qirIgD7/9CfYd+2d1ovv6JGBD74viWMc51ecV4yBeOAuTVtu9efNgMrDov3dKTpB1D+nrzAe/izzTbm569xDG7T/o7hXQhP390s3mFoTz4Ck4nFRD/1cH4HdLJ7Sp64+7cTYZtCcjavG6T/RQyxD8zRFKQ8JFXeiuM25BsSQZ9mUYX05hMaYqRfgN9AYGpzSv0Z5lqaqDFoAasRJZsBjjZIhD1sQB36nCCvo85Kfv4mXT0ql3344mjqZP+WgPW7WsILfzXzZabn+dB9PrhKHolI70hLMRh+5mPMEkhPJ+k0ltsxVDWdeuhL4dHQ551E3pH8zdbA1PxJxj/kwN+gY9dF/HSU7fABTCxwLcyaZ2NgBPISk3i9SDl43ErWzA+jld8vDFeMtGlGorE4=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <4DECC6D5B063E140BB6BF6A599050DAC@jpnprd01.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: 8b82439f-e3c5-4666-4169-08d74c854901
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2019 06:52:43.7663 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /g9mCdKVFGERU37SAs3/+g9tYXJXy5srqtHUnUz5bLncHPXUr+jdiBre3kRXFUUhkYs0tz8g85qE/1hfaQKEPQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB4545
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/G2HiCFnKYyqxnTj9Wu19KziVkQU>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] 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: Wed, 09 Oct 2019 06:52:49 -0000

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 :-).

Regards,   Martin.

v2.23.0 | Report a Bug | By Email