IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Thu, 10 October 2019 13:22 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3E56120099; Thu, 10 Oct 2019 06:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 3W648m_BTGfJ; Thu, 10 Oct 2019 06:22:16 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7B16120026; Thu, 10 Oct 2019 06:22:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1570713707; bh=rdWLgoEI8IZsEkIAggGEBLn6IN5zv8pS3N+EdUzweBc=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=OGr9+bK9LCEth32QUIa7+YkXeHZd3JelKlzt95Tf0+UkHOERJAhDrFK2wJHX7KAZ7 cvs2UgEXsrKHbJ3ZIx449Q5k9L8JW7sIviyTVOpcONSpcxa2lG8vRlpfB5o6uVxER+ wHq6m8MPBExtgIpZH3tGhuMa6k2V7abFjwpP9GnE=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.147.247]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mt79F-1hyhDW1Vgf-00tQWJ; Thu, 10 Oct 2019 15:21:47 +0200
Subject: Re: [Rfc-markdown] [Tools-discuss] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon
To: Henrik Levkowetz <henrik@levkowetz.com>, Robert Moskowitz <rgm@htt-consult.com>, Carsten Bormann <cabo@tzi.org>
Cc: RFC Markdown <rfc-markdown@ietf.org>, XML2RFC Interest Group <xml2rfc@ietf.org>, xml2rfc-dev@ietf.org, IETF <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <02046145-9455-4C01-9F6E-246D3940C86E@tzi.org> <96647ed8-2627-4434-ad51-b373eadfade6@levkowetz.com> <347055CD-74C9-479B-B7FC-BA78580C37B5@tzi.org> <b5d94182-4d5f-4a4c-18e5-d4443a8a5416@htt-consult.com> <2383ca8d-efde-168b-3485-597b25ba6782@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1a576c17-f648-a230-393e-d97c17f43ad7@gmx.de>
Date: Thu, 10 Oct 2019 15:21:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <2383ca8d-efde-168b-3485-597b25ba6782@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:r/7sSsppW14ii9FR3GVLko/d6s2taiOSGYaZN4KEBQIVNUt3QhN 8ryaP31k6gGxnOd7VTvMdnmMLDHa+keut+l961ySyql/EEaV3cis21AJsKMC5QXej6v7TR+ D9BxTxlQM9aiNM2Dq3kI9DlK++8RfgGpDINmfusgRmV19qa4FGlEoNCYOr781iHyasoR27k eYIZtCB7DwqRS4GRCqxwA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:PciloICq+lM=:vkokfFwZTolP4eRHzg03yh 7wcaB8FyZD/+IAeEOUeafdCLRyRYcRHp67spUgUdO+AKSuK7sgFyzjUBdD57bO/JI+FP0ONGm b6noi9yJNn6w9ApxmGX/BD3P66MmkkPHEbJ7+Vt6YsCRwqrqOS0sYc4aXsZLLE7mDPGEYGkE3 SKj1xvrUEUCun6k9y1cdBVzPNeJ9qlIULljAa8pc2FlasMloWZB83kZnuz9V/aq2iOOrlyeaS 2+fC8hUIz91Vi04g0hDvJyPk2+tRio3vEElERib44cvAfNJGHRb5C/MBeAONRMkf/rv+hUHmp 40HR5Z/qAel6FbQIV/yzBPOAKYtl9zCp6NIarFSmVM3T0EKJyOAaLiRXpkizQOnbnMclas3Ay EN/HR3stFE54uV6qRMycYCYBa78hJDbnNjamBEfP+b7zPGPscmmP/C3hHj7m+qSLWAKSp8vU9 Jb3HHIY3O9v6CQsMYt5Z21DbivaddfuQ3jLJF8006J+lw9pYA1aO2KcFFYV7mMIWAgTiOaQQp 7ywSaGZJSlVA3GTrkjmTpzmvYt8Pr4fymA8zkEyPqFHm1u/AtDgCPSMD2Bw2zdW01wGxZjfmX a6+tRZrZt1v7xikJ8CQ6vbf781NDa06tnqNTmKaaddXAI3ZZNxqsXapMGc6N5Mhvg5AqsTM0E PW2b0VgZ3I3nIwar6J+/F1u1hHBdhSzLJWC7nXnXhgq0sXVhzv8xVqWAa7+Zg6fIaOGVGz5x6 P3kkqKAsUXN/PIHbQyj+QK4j0PYM/tWbBcOyCQofYqwVcjr4Gyn4z7WsEXqBhDczCBhD/Fc3u 8ocDl2IsxPKejDrI1YffypBxcRyIQaaMtxYRZCde0oBnclbj7w0FcqEDRC0PuwyPuoaF8Dm9O 07y2xbsy4w0U4E7da+UcuqnMDeAMkTQ9G/v/s5liDCAO8msNjYxbOwLcsyr+mKC/5ucuDBLFP 4MWxoJ+6Ybdt8ycrzgPmDlA2MBI0fksDsJh55sfsr1m3x1SQY4bAJfn//PW1OGIHEHQm5Bl4D os+HVzM8pth9SZhfT7BZzxjVk1HHjIhKpoyi21hcsaIo0NGC1McRy8i1Wz0YAOFvMVetYsZIn eSFBkBjF8ahRfhB9hhPBgilHzBpZi3NNXWB/90OvS3UFRp5Ll0/B61G50Hg8v1fsvXFfCW1+r itNgJ5s+Cu66XNxI1nNWSJBXF6DEANlCCO/RWdk6dyHDOYoDtMGS8xcun45k69ocj8XwonEUt Nd5Ao9rCIvHVdje3nt9lqviylYABiCTSU1/0ag6rkz8O4BLJjeDT3VunHX60=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LV7035dCHYkCf-n-Cm3abLtRB1s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 13:22:19 -0000

On 10.10.2019 14:59, Henrik Levkowetz wrote:
> Hi Bob,
>
> On 2019-10-10 14:49, Robert Moskowitz wrote:
>>
>> I have encounter:
>>
>> draft-moskowitz-hip-new-crypto-02.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)
>>    Created file draft-moskowitz-hip-new-crypto-02.txt
>>
>> when using the--v3 switch.
>>
>> I have been told not to worry about this, but so far I have not found
>> any documentation on "consensus".\
>
> See:
>
> 	https://tools.ietf.org/html/rfc7749#appendix-A.4
> 	https://tools.ietf.org/html/rfc7991#section-2.45.2
> ...

...and...: <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/420>

Best regards, Julian

v2.23.0 | Report a Bug | By Email