Re: [tsvwg] L4S work in TSVWG

John Leslie <john@jlc.net> Tue, 07 February 2017 14:44 UTC

Return-Path: <john@jlc.net>
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 EFD53129C69 for <tsvwg@ietfa.amsl.com>; Tue, 7 Feb 2017 06:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 4Uo7GOPpHThB for <tsvwg@ietfa.amsl.com>; Tue, 7 Feb 2017 06:44:12 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 2604D129C45 for <tsvwg@ietf.org>; Tue, 7 Feb 2017 06:44:12 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 18BA39091C7; Tue, 7 Feb 2017 09:44:11 -0500 (EST)
Date: Tue, 07 Feb 2017 09:44:11 -0500
From: John Leslie <john@jlc.net>
To: Wesley Eddy <wes@mti-systems.com>
Message-ID: <20170207144411.GR10525@verdi>
References: <274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/euMikGCPp8HG6NTqtvDLB_xnojI>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] L4S work in TSVWG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 07 Feb 2017 14:44:14 -0000

Wesley Eddy <wes@mti-systems.com> wrote:
> 
> Hello, as a co-chair, I'm checking to make sure we have the critical 
> mass to go forward with L4S in TSVWG.

   I'm happy to add my 66 kilograms. ;^)

> Over time, there has been good discussion on this spread across several 
> lists and groups (ICCRG, AQM, TCP-Prague, etc.).  The ADs have asked 
> that going forward TSVWG be the home for this work, so I think we can 
> limit discussion to TSVWG now (assuming relevant parties are on-list).
> 
> The three documents at present around this are:
> 
> 1. https://tools.ietf.org/html/draft-briscoe-tsvwg-l4s-arch-00
> 2. https://tools.ietf.org/html/draft-briscoe-tsvwg-aqm-dualq-coupled-00
> 3. https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id-02

   Bob has done pretty well on these: I don't want to criticize his work;
but I'd be happy to join in the discussion.

> There was interest in working these in TSVWG at the last IETF meeting 
> (noted in the minutes), and we want that discussion to continue on the 
> mailing list.

   :^)

> Please respond if you're interested in participating in this work by 
> helping to review, analyze, implement, test, simulate, deploy, etc. and 
> agree that TSVWG should add milestones on the L4S problem, based on the 
> current drafts.  Or if you have other thoughts, those would be 
> interesting too.

   I'll do what you tell me to; but my day-job will keep me pretty busy
until February 20.

--
John Leslie <john@jlc.net>