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

Julian Reschke <julian.reschke@gmx.de> Mon, 02 August 2021 09:25 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 1C8FC3A155B for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 02:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 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_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 GKb0AGv-Ozbh for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 02:25:19 -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 E27493A1558 for <xml2rfc@ietf.org>; Mon, 2 Aug 2021 02:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627896313; bh=RY0SBm4NCWxWMFL/TgtDtfDaePenDJ55pa3h8+t5m4M=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=iOzGPuiVUjh0EvYpyty3WrA/6gE+vag583PEwRBB1RDaEg/AZxGRWMnyujmo6UTxA /ExvzVBeu3m27AcOEjX1nsQzhOmba15gL5PZ27jmPTCmxrJCTlDA2mCComzsaQOZQ9 yxqwpS4p7pGW5tSQfRiUs0uvp7CG4KxsZYfpv/P4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1McpNo-1mizvu3qiY-00ZvjN; Mon, 02 Aug 2021 11:25:13 +0200
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: xml2rfc <xml2rfc@ietf.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
Date: Mon, 02 Aug 2021 11:25:10 +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: <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:Vd4JGcEKl2EGXmnyzist1OODJAHdI2OrTtxea5CiafiChr7Ba/J lIZ2YSWiT0sxYWaJR4vptGW+g1S3etIXjKMbbbeNbP+FkGOXYEANFiJAE0BEtk8eh60AHWB BgCAQ8/7gQX9bIIVpStmKKGx2aJ2NRtMmy0nE2lxK135ovNavvDThPc6rvH7ICJmL7DOzuJ pUqOSW81W4yOYF76cGLsw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:mruVBQ6xZvA=:VfG1Gx7zemvefa5slpVM6L NhZZDxz5lhw0sz9xjn/ZLJWIqlxzw1xOAjBIhGU49qAppO/QP7I420pjh+nAudSlwB02DCClX Wa50lKTpozUYufdkD8c3loAzPZ63hX6QgzC1paARX0XVBvP/n5ywssLaDzS9w1vuQOhBu4WCo 7Z+pcUlxPDeh3oCA8vs0vjiK+YzQWWEl+QtN2Fhw2PoiX3AmHRSpBcBpXwNoOR34MV07sXhw7 dLz/+GGhhMDTTl5EVgsM9HEgTPpVuWEz9mS0tu2apOgeWVu2LfquUPXRGIIDr1bn5GvZIC0/R sCKd3l1MydyUn/41avPi7B/pCHg4gHk3Xyqt74lQn4MXtPdgKkFgbJ8rU7p+/JXzKGfpjF3Pj G2d5JNjykCRU6bCR67zdgNv9oHwqRNfcxd2hv8bbxyS8vA2goOpmasWk3v6SNcHfQEtnWL7vw fuHBjAfqs+sV7pMBarNEVWm2YC7eNDYn7tF9+xApkgNZwosnRokPkDfP2Qes7PtyEECToFWRc dakuPWQt32+LuBw7T56sP8PicqheC0j/zOpWSukh12wvrdYqRrZNJMr+MUQjoH4UEEJG0lEHo xQIsZKYRPJhR7X7dxw2JqHXuAqr2QZayzIX+IgvPnUynqc75R9i3ViwuaEhYLisX5hoNspCGl v0O814wfoA3SxTFDR2QhqH/wlG5g0kIK/WfUExLJHmfYN/5ggdfu7dWAQd3VuIEXwoZZ/cRy5 JVKCSd6Pxdk+GFidqUpNDKyjuPluLdK/uGV0BD1Mo5xI4Z3A9BGn3v6c037tkaVId3oNoI1vT z2E0jeqsPbF4/PJxqrFNv/AqkzSPHcfzVmvK3Jy+J+EZtpFDknQV+NNYiE3w+42WBMEiWrXPk xOHVPQlnIRIBekDI14gIcuPKpVvRCXoZ7zOGGM4QQBCiNh2ux59frrgsvNV7wpPc8ypZBAkrK aO4kSyv69I3ygz1WxWdWuUkzk9FSzKzC2RnyvPkJsqRTEWlndRouY86Buxzubx4C3+rNPmRYp 65UHTjWbU4/vEyXE5vSmcDYYvNgTIY+efRchLdFmZ505wzJbvV6+P3jx0fMUrDznjvB72nRVv Gbc991QBopM7WlkSbdFtDjLGDdC57zYZeLMNwTfVLGc2VClXU1UxozjHw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/cFQ1DqhdFKdutmCUqUhSHZVHVCg>
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: Mon, 02 Aug 2021 09:25:24 -0000

Am 02.08.2021 um 10:08 schrieb Brian Carpenter:
> I think that's a red herring. The processor is not recognizing pn="xxx",
> that's all.

Nope.

The issue is that the document uses xref/target to point to sections
indentified by their "pn" attribute, and that one's value is different
under the new version of xml2rfc (and gets replaced).

We wouldn't have this issue if the ToC wasn't inlined in the first
place. So a bad implementation decision now causes breakage in
"canonical XML".

This could be worked around by xml2rfc rewriting the inlined ToC as
well... (but that would be a workaround on top of a bad implementation
choice which leaked into the user-visible grammar).

Best regards, Julian