[Rswg] Making progress on evolving the XML format

Eric Rescorla <ekr@rtfm.com> Mon, 13 February 2023 20:28 UTC

Return-Path: <ekr@rtfm.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 B3209C151536 for <rswg@ietfa.amsl.com>; Mon, 13 Feb 2023 12:28:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com
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 fOC8a1ilOONx for <rswg@ietfa.amsl.com>; Mon, 13 Feb 2023 12:28:19 -0800 (PST)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 D7523C15257D for <rswg@rfc-editor.org>; Mon, 13 Feb 2023 12:28:19 -0800 (PST)
Received: by mail-pf1-x42c.google.com with SMTP id 16so8764344pfo.8 for <rswg@rfc-editor.org>; Mon, 13 Feb 2023 12:28:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; t=1676320099; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YkkXBNthKJeggIuvwOyj7T+XYIVuWopMvMyqV0Z14wY=; b=EX9X6deCiw+QGoGxnNzjJ4naTUyuGfu0ch8OB82OOOuyfbDdbU8dyeYh9R8tdBwXzW ehHYYy5qO3u/gZTv0csGfC12Vm3ZwnAABP5+8wvN9HVIDuaGvOgc4ROVvHMQsF0apVas muMf1RfDSmseSnyH6qGyKl74Bqq140gwbo3kcebFrHS3is/nfRsZ8nVY/K2o0m/H+UQz ISVnURc25qxXF1RTmwg9BAKZdc0C2WkopFlfTaA/GCzVvJYPJsVK9exDc4ObpZd9XtPP s+A30zcvFSJFDSoHSF3B4cZCXqgdRW/9YVQoJITItazJ1ZCvMn7nUDrD55ajhB9ltxJm IaXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1676320099; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YkkXBNthKJeggIuvwOyj7T+XYIVuWopMvMyqV0Z14wY=; b=eSxb3SEP9Lbcjjtf0B/wwvrGrY37i1ZIWtNx6ZXxGCGSTctiXJwKQFLojHMOFj/zDz afCw/IRvoA4FgR5AZaGIe0vFCPTVzBQjfey+EluhfOrcpCRRjj2oavROX9ztLhpJrorH qqgW/a8K8D2XBTDTAN7LE63ldWRMVA9jGQD8V8+KQekgcLuXLxeLuQFCotKAouK73ook sDcRum7hq9ZZ+/QD6aPzw5UPaSnsgA35JgFEr4R9xvrJKmg1bn+WGPBEo3iwd4oih4MP 9c5QLi2dfl1d7zMSqzs0QtqYSAuYjpGmg3QroVeybN3W/wQrFfrULYXF4aJ0NLagTVh7 jKaA==
X-Gm-Message-State: AO0yUKUPn4MNiR4UfFDo0Zy2gtPct6A8zV+IIqSIaZEjxpO3He/Sz6rj mTph7dzJLCMkBguE1SHwQYq9sAMwGwU8BQHn+Y2bf8JvjVSD4FUl
X-Google-Smtp-Source: AK7set+cJupHnzJSKPs3SN5SVuB+TUhwj1qCyGkLYCdd2OWdlhqWdI6gm4foCXNNhIF6xfi14XfFvGjAN1ad/jwf30o=
X-Received: by 2002:a05:6a00:27aa:b0:5a8:be0a:5293 with SMTP id bd42-20020a056a0027aa00b005a8be0a5293mr824922pfb.56.1676320098833; Mon, 13 Feb 2023 12:28:18 -0800 (PST)
MIME-Version: 1.0
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 13 Feb 2023 12:27:43 -0800
Message-ID: <CABcZeBM1TKqRkXJ8JErVijoKhEKOa+ebWDpxfERuq1NhUrSG4g@mail.gmail.com>
To: RSWG <rswg@rfc-editor.org>
Content-Type: multipart/alternative; boundary="00000000000005702605f49ab0d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/ufw8EVsCfHLpDkAQwsPBzUf-Rvg>
Subject: [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: Mon, 13 Feb 2023 20:28:20 -0000

Hi RSWG members,

Pete and I have been chatting about the best way forward for evolving
the XMLv3 grammar. We think that there's broad agreement that:

1. We need some document that describes the "as-is" xmlv3 format.
   - That document should be published in some form that implies
     it doesn't have consensus.
   - The WG should do the work of making sure that happens
2. We need to work on a new format (v3.1?) that will have consensus.

I think people are assuming that the new format will need an RFC but
there is not agreement on whether the "as-is" should be.


Pete and I would like to propose the following way forward, based
on a suggestion from Martin Thomson in January.

- 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.

- If necessary, we can also update the I-D to make consensus changes
  to the as-is version on an "emergency" basis, though hopefully
  this will not be needed often.

At the end of this process, we will have a document which describes
the consensus format and also an appendix which describes how "as
implemented" differs from the consensus format. These can be published
together as an RFC, which will provide archival forms of both but
without requiring that we publish an RFC of the current document while
the consensus version is still in flux. In the meantime, the ID
can serve as the definition of the current format.

What do people think of this proposal?
-Ekr