IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Mon, 02 August 2021 19:57 UTC

Return-Path: <johnl@iecc.com>
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 5F2123A19F3 for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 12:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.707
X-Spam-Level:
X-Spam-Status: No, score=-3.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, PP_MIME_FAKE_ASCII_TEXT=0.292, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=MdAXytMr; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=lOScLtr9
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 JtAr6IquaQ9n for <xml2rfc@ietfa.amsl.com>; Mon, 2 Aug 2021 12:57:04 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 8F69D3A1A3B for <xml2rfc@ietf.org>; Mon, 2 Aug 2021 12:57:01 -0700 (PDT)
Received: (qmail 21261 invoked by uid 100); 2 Aug 2021 19:57:00 -0000
Date: Mon, 02 Aug 2021 19:57:00 -0000
Message-ID: <se9imc$j1e$1@gal.iecc.com>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=5306.61084e0c.k2108; i=news@user.iecc.com; bh=KxPgCTexNYxGGayLkyeG+0WI4oXhpZc26z6d98JgOQY=; b=MdAXytMrbl9/Zi0zgneUt2V0IuOykl41A7GELER7CqZGmYaKOeNYmTpM1dmRfnUZGwxr6KoRkHFhuEM55tkxAKpOVedNq6ReLOqmwgsq8LH2VELhzStVR2cAYAvChs2feBWFet7Cx3EInn7oiv4r8kfARIzLSzdmutTF31VAntCHEydqwNvjuQoBZ63z46vjzgtW4jcjatNttucs6nc9qT76tDOHfPTrprqUzoX9cg702RHY3q3yQdXqSudwAOVcmxNgZgUBrKzhDHL5jKCr687bU4dztdwBs4uESPFs+1b/TOm0R6mMJ4RcSNtz32G2AjX9tTddLzh0o5fh6kYn7A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=5306.61084e0c.k2108; olt=news@user.iecc.com; bh=KxPgCTexNYxGGayLkyeG+0WI4oXhpZc26z6d98JgOQY=; b=lOScLtr9wk3Kdm09zuwBXekLoDocjt+g8dwpuLlVlb/Tdn4nNNuGh/Xk2BQLSCeyrSmn5efWSKTajvBFVMu1BFdW9EWP8Btnh+g4bE4hD1IoqVZEgxzJqSaZZIfPbA0262DziDwqDslhb6lSlTR0o0IvvkMyiinShwTjK+9w5IesLMSrU+WQt30pqptcQafr80FxJ4Kfs9E6L6WATjqXenvOP75E8GwwOkhLKkzoqSy6BYutRkcntQGMtHujIoskTZjD/5jkrJS/DcJ9s8yAITqTyQ2/v1q0WnfXGLG1N6WeIMalfRFCvmvvU5AM+4Lha7ktMvvmOPOnRpU4Qt9HqA==
Organization: Taughannock Networks
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>
In-Reply-To: <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>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/94vl1hEk2iwfqgop1kax6XpKqaM>
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 19:57:19 -0000

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.

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.

R's,
John
-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email