IETF Logo Mail Archive

Re: [xml2rfc] Current xml2rfc produces errors on published RFCs

Julian Reschke <julian.reschke@gmx.de> Tue, 03 August 2021 07:05 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1CA03A16C2 for <xml2rfc@ietfa.amsl.com>; Tue, 3 Aug 2021 00:05:40 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 786ZLMAuWhps for <xml2rfc@ietfa.amsl.com>; Tue, 3 Aug 2021 00:05:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 466D23A16C0 for <xml2rfc@ietf.org>; Tue, 3 Aug 2021 00:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627974330; bh=rLZwbxgvHqEvV5u/hacFjRBI2zAzS92GGaENQbxqOOU=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=RjIA1C79J+EBkcwEXd0SUey+z7K7bmPr4cWVHELzzJSDm2nVIj4Ouh2hZmMthznL9 G8QfPqW1mNioxvRc9IaddonVoFFF5YDOsxmnTmzkTg2i3WXgeyjgasosyfJMa5P01m MQnBuJUQUcTqZpBW6XMgdjee3UKQOhpV/630xlx4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.4.172] ([212.205.152.82]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mkpav-1msMEf0yul-00mGY3 for <xml2rfc@ietf.org>; Tue, 03 Aug 2021 09:05:30 +0200
To: xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de> <se9imc$j1e$1@gal.iecc.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ae33c49d-6503-fdae-c6f1-ca0cadc7c177@gmx.de>
Date: Tue, 03 Aug 2021 09:05:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <se9imc$j1e$1@gal.iecc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:v9hIxoiRnYhc7MSe6gTigSJYT+J+PyJRhVwblwgHxv7n2xIs+mg wZzHcRAlG6i1G0elb2PwsQi5lSARXtOMfSvgnoRZ81b31HO3Q8fdVaX1Jp1Rqb44WgT7GB9 yY7sFMPNH5cAO12g/8qNqWl7wb2vwidt4TSeJK8jq38VvEvPtu9QDmPqtSz7/KPl2L1lix9 0Nx+1s8uhoqO+XoK9IpAQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:1iocRX0Xllo=:2wOMJmdVZgDolePoMbEEhE mtQnvV79DtgBhwv4vfwwad8VBXIP6a9gJxoT1vWYX6Auyn5Qa2UaThrjoolknRpp4t+RADOMe JXEDetWWfHvWBqGz9qpHCwWy9e7nOuT3Fi4SB5VgkOxFJAt1pkqfgXCQABOHHvlDZtXVa6jH5 svi2h2VwS8zsJSZX++icRG327f0A9clETeqyX8BqCDljaTV6usVx5az5CRkXDIW5bxR5Y0/3v YXQG0LTkT0hTo5IvCbJtkl8MsuYyFgyPs8L8/Ok0KiifBzDKRTi/VYdeBbrMDMsyYVzdhE9ui eiWLPUAo4yh07HMUmBiNe0O0kkZAX7ZGwbgQ/tqGHDDUk0AoLexfctivRTw8KTu82Uy4SXTyQ TmGARVIbxlA1jfz5EWrgM/cars6G+nXdrBdhHX5i4NIkcGAZBO3rACc9bpelaTOtOKhtdn1L5 3dc+QOBwH+nVMRXTGwdoyMVMy5wiyJt6tqHpVOAvanQsPRJiHaD87o+C3HanaNDScDRVjxJS8 8yMUOLohTET0ub8GU/FrD8IAPL0ZSzGgyMiIkmBaWN0hWxHSonEZ/LJyXc1Zyocq4cvy1pQ7g MrzJ+wCXfYwvTf7EafuZfEIxJ0n9MFoQH+XwWE37aW5LdJVgGvKSw13KvXOqjimehm0eVVRho gs7lkCbLeY3029VgJ0IGLhHjkOjtLje5DeTQUpHvGZuvlCcpWGo7UcI/69odnz/kW7xSuzNyN M7EITwW7v4ZHleyeb8G7h3qEcwEdwjofc5icyXS2nCPjXq02O54UioE14IxUpPjE2+iaolK4c 3E7NIo8DjLcKOc690O3Mw7ekYkjDu0IUeyhPC80m7lD3Bvlfw1vHCI9qoI3qqSVq6Ck6jh3IN xxp3Kkw2DymQWdpfEjh3sk/X/0xmaYCLX1lXnJxBvhf5j1FADeSV+ShRLS4BZYJnUf1LDc3La zcSApToqxjDehckK9zzkyBMp1kXsLHZ2VqZ+t6BpQQPXKIndl8j9LBTm15EL9/qBt1zEtEPs2 U7G7Fcvc9IPdWgv3Ymxp3a85JegGNmt9MjDSfN6OOJLWWVM49AdYTWp0WL9KbCwuQwep9aIOd fK7ERbKCmoUNu/JDRu0BJ2Z7RvcyjMvBwEX5Qeu9IMbPlnPuXO8kZv0wQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XoaLcT_rukUR4phugZeM87DegpE>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 07:05:41 -0000

Am 02.08.2021 um 21:57 schrieb John Levine:
> According to Julian Reschke  <julian.reschke@gmx.de>:
>>> Not just those two, all of them.  I've run the entire set of published
>>> RFCs through xml2rfc.  It takes maybe half an hour.  We definitely
>>> should do that before releasing each new version.
>>
>> So if anything breaks with published canonical XML, we can't make that
>> change?
>
> Maybe, maybe not, but we can at least make the change knowing what the consequences will be.

+1

> This gets back to the unresolved issue of whether we're going to update the XML in published
> RFCs once we agree on what v3.1 is.

True. And I continue to believe that we should do that.

Best regards, Julian

v2.23.0 | Report a Bug | By Email