[tsvwg] Call for comments on the suggested publication timeline for draft-white-tsvwg-l4sops

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 21 March 2022 14:28 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F4E3A12B7 for <tsvwg@ietfa.amsl.com>; Mon, 21 Mar 2022 07:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 f0JijbvcnhQc for <tsvwg@ietfa.amsl.com>; Mon, 21 Mar 2022 07:28:26 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 880783A0A9C for <tsvwg@ietf.org>; Mon, 21 Mar 2022 07:28:25 -0700 (PDT)
Received: from [31.133.129.61] (dhcp-813d.meeting.ietf.org [31.133.129.61]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C2FF11B001AD for <tsvwg@ietf.org>; Mon, 21 Mar 2022 14:28:17 +0000 (GMT)
Message-ID: <28c48d28-3110-d3a8-d405-b13dcbb224c9@erg.abdn.ac.uk>
Date: Mon, 21 Mar 2022 15:28:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/hCteR8oPP1h31fG0wBVwBeA3N94>
Subject: [tsvwg] Call for comments on the suggested publication timeline for draft-white-tsvwg-l4sops
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2022 14:28:29 -0000

The presentation in TSVWG on Monday 21st March 2022 indicated that the 
authors thought the document was complete and ready for review. The 
chairs previously indicated that publication could be delayed to wait 
for initial experience.  The chairs would appreciate feedback, to help 
decide.

So, does the WG have a  preference regarding when to publish the L4S Ops 
draft:

(1)  If the work is thought complete, there could be value in having a 
frozen draft while experience is gained, this could be updated with 
initial experience, before requesting publication as an RFC.

(2) The WG would not intentionally delay the request for the IESG to 
publish: If the work is thought complete, then we can finish this draft 
and publish in the short-term. The WG retains the option to decide to 
subsequently publish an updated RFC in the future.

Please could send an email to tsvwg, or to the tsvwg chairs by 8th March 
2022.

Before any publication, the ID will be subject to normal review and WGLC 
comments.

Best wishes,

Gorry Fairhurst
(tsvwg co-chair)