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

Paul Hoffman <paul.hoffman@icann.org> Tue, 07 March 2023 02:04 UTC

Return-Path: <paul.hoffman@icann.org>
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 C10B6C14F74A for <rswg@ietfa.amsl.com>; Mon, 6 Mar 2023 18:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
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 7JP3jo2-RqFn for <rswg@ietfa.amsl.com>; Mon, 6 Mar 2023 18:04:51 -0800 (PST)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 9110EC14EB12 for <rswg@rfc-editor.org>; Mon, 6 Mar 2023 18:04:51 -0800 (PST)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa3.lax.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 32724ouG008185 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <rswg@rfc-editor.org>; Tue, 7 Mar 2023 02:04:51 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.25; Mon, 6 Mar 2023 18:04:49 -0800
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.025; Mon, 6 Mar 2023 18:04:49 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: RSWG <rswg@rfc-editor.org>
Thread-Topic: [Ext] [Rswg] Making progress on evolving the XML format
Thread-Index: AQHZUJkyR621K0GHwkqjio/buQx3oQ==
Date: Tue, 07 Mar 2023 02:04:49 +0000
Message-ID: <B42D714A-8FCE-4092-AFC3-758658C9C70F@icann.org>
References: <CABcZeBM1TKqRkXJ8JErVijoKhEKOa+ebWDpxfERuq1NhUrSG4g@mail.gmail.com> <848FE9F0-5A0F-4FAA-9B7A-4E402871916E@episteme.net>
In-Reply-To: <848FE9F0-5A0F-4FAA-9B7A-4E402871916E@episteme.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C84973982C84E14FB235763146A9AB76@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-06_14,2023-03-06_01,2023-02-09_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/nfB6KWCdhSTBROmp6Bb7S78cC0w>
Subject: Re: [Rswg] [Ext] 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, 07 Mar 2023 02:04:55 -0000

On Mar 3, 2023, at 11:09 PM, Pete Resnick <resnick=40episteme.net@dmarc.ietf.org> wrote:
> 
> Thanks everyone for your comments.
> 
> The chairs have asked John Levine and Paul Hoffman to serve as co-editors of this draft and they have kindly agreed. John, Paul, please submit a revision of
> 
> https://datatracker.ietf.org/doc/draft-irse-draft-irse-xml2rfcv3-implemented/
> 
> as a WG document with the appropriate changes to indicate deviations from the RFC grammar at your convenience.

We have done so:
   https://datatracker.ietf.org/doc/draft-rswg-xml2rfcv3-implemented/
On the mechanical side, this is not really a WG document because the Datatracker doesn't know about the Editorial stream, so we might need to do a new naming with draft-editorial-rswg-... at some point. Also, xml2rfc does not accept a stream of "editorial" yet, so we said "IETF" even though that is very definitely a lie.

The diff from the last draft can be seen here:
   https://author-tools.ietf.org/iddiff?url1=draft-irse-draft-irse-xml2rfcv3-implemented-03&url2=draft-rswg-xml2rfcv3-implemented-00&difftype=--html

Regardless, the draft is there. The WG (hopefully with the help of the chairs) will make a final determination about:
- Will this become an RFC, a perma-draft, or a draft encapsulated in carbonite somewhere
- Will there be a 3.1 that has certain restrictions
- Will there be a 4.0 that has no restictions

--Paul Hoffman