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

Henrik Levkowetz <henrik@levkowetz.com> Thu, 10 October 2019 13:00 UTC

Return-Path: <henrik@levkowetz.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 52C7C1201DE; Thu, 10 Oct 2019 06:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.095
X-Spam-Level:
X-Spam-Status: No, score=-1.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 UFRhiUbOuM2V; Thu, 10 Oct 2019 06:00:01 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A554120170; Thu, 10 Oct 2019 06:00:01 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:53794 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iIY2x-0003Lf-Br; Thu, 10 Oct 2019 05:59:59 -0700
To: Robert Moskowitz <rgm@htt-consult.com>, Carsten Bormann <cabo@tzi.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>
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>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <2383ca8d-efde-168b-3485-597b25ba6782@levkowetz.com>
Date: Thu, 10 Oct 2019 14:59:50 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <b5d94182-4d5f-4a4c-18e5-d4443a8a5416@htt-consult.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HHeSmouxCXP9DT0tKgiuf0DnNVIcOCIri"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: tools-discuss@ietf.org, ietf@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, cabo@tzi.org, rgm@htt-consult.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/LImrgvD9iiLEmbVSHk18d9Ahki4>
Subject: Re: [Rfc-markdown] [Tools-discuss] [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: Thu, 10 Oct 2019 13:00:03 -0000

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


Best regards,

	Henrik