IETF Logo Mail Archive

Re: [Rswg] Making progress on evolving the XML format

John Levine <johnl@taugh.com> Tue, 14 February 2023 05:06 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F135C14CF1E for <rswg@ietfa.amsl.com>; Mon, 13 Feb 2023 21:06:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.847
X-Spam-Level:
X-Spam-Status: No, score=-6.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="HEE9p5Ip"; dkim=pass (2048-bit key) header.d=taugh.com header.b="TGGIN2Th"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jq6C4VmL8Oqz for <rswg@ietfa.amsl.com>; Mon, 13 Feb 2023 21:06:48 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B527C14F6EB for <rswg@rfc-editor.org>; Mon, 13 Feb 2023 21:06:47 -0800 (PST)
Received: (qmail 29091 invoked from network); 14 Feb 2023 05:06:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=719f.63eb16e5.k2302; bh=L+PbcH7dnjyezLT/UJM3Nk4suLdwcHhayYIwfeFCo+k=; b=HEE9p5IpFAcJnKhaZhHsLjdJLeiyPvHiA3yY5LAMPsRXwziM6n6liWTDYLqHV3CLIZlsG5gJ4PFKvmzu8vVlhru8UoRnUxoB8J6OUmNwbWTmxUixpZym4lrOi0pVupo4OKDfqn49vbDX1lqT8QhH/KFFi3hWknKpmquA1MlSt6oW0O9KrHSShE6oyI14LfE7ep9tNUjqpozz1JD1dTE5IKdFP3YabusvxHEln4Hl9XWT+RVxYHmXq0P8KXF8j08Ct0SVQ6HA4BoQAFleVFEYt+oU73UtL2by8Q/5Eh5aTIICJviRLLYa2EIsX1sr6DUfyFhE6EIaVk3GooVpoZJsAA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=719f.63eb16e5.k2302; bh=L+PbcH7dnjyezLT/UJM3Nk4suLdwcHhayYIwfeFCo+k=; b=TGGIN2ThlDsH9EOr1JuShnzhR03NzXOW5P3aCeCSDa4d0wSx7unO/ftEFzX+4lTKVw3B9yLcVSdWL5hbz43KFSpCBSZwlLLcAnrzhyZaazwjiRlHAg8AroaKgjZAzFmAnKZw/nDevnUC4I60BEfZ90izSUpIRw07kn2YMV9OxPTn404tHxUf45QD687S7HEKO24xBIg4WGALMpFhSXxXmy3VcE+FJY69US699zcDxxcKsxd3HcgKJO96RM369v0d5h3r9zBo7x10nx87qQECIrkfbaKfMmjPNa9xc8G+fyixaHVjyUXKwMbK32rKayZ8SocY/acIe2L0qyUjtTOXMQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 Feb 2023 05:06:44 -0000
Received: by ary.qy (Postfix, from userid 501) id 342E39884DA2; Tue, 14 Feb 2023 00:05:52 -0500 (EST)
Date: Tue, 14 Feb 2023 00:05:52 -0500
Message-Id: <20230214050644.342E39884DA2@ary.qy>
From: John Levine <johnl@taugh.com>
To: rswg@rfc-editor.org
Cc: ekr@rtfm.com
In-Reply-To: <CABcZeBM1TKqRkXJ8JErVijoKhEKOa+ebWDpxfERuq1NhUrSG4g@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/TJjpe3d859ut94Zxj6cgP_X8X3o>
Subject: Re: [Rswg] Making progress on evolving the XML format
X-BeenThere: rswg@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Working Group \(RSWG\)" <rswg.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rswg>, <mailto:rswg-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg/>
List-Post: <mailto:rswg@rfc-editor.org>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rswg>, <mailto:rswg-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2023 05:06:53 -0000

It appears that Eric Rescorla  <ekr@rtfm.com> said:
>- Adopt draft-irse-draft-irse-xml2rfcv3-implemented as a WG document
>  to use as the basis for v3.1.
>
>- Everything that doesn't match RFC 7990 will be marked as
>  "provisional". We go through all of these and either adopt them as
>  having consensus or decline to make the change, in which case we
>  move them to an Appendix.

Sure would have been nice to have this plan before I went through
and put all the changes in-line in the document, but OK.

Keeping in mind that the current document describes (give or take a few
nits) what xml2rfc actually accepts, if we reject a change, then what?
How does this affect the tooling?  

To be clear, there are a fair number of changes I would reject, and a
few to make the grammar more regular that we might consider sneaking
in.

R's,
John

v2.23.0 | Report a Bug | By Email