IETF Logo Mail Archive

Re: [tsvwg] L4S work in TSVWG

Bob Briscoe <in@bobbriscoe.net> Mon, 13 March 2017 17:48 UTC

Return-Path: <in@bobbriscoe.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 2F953129986 for <tsvwg@ietfa.amsl.com>; Mon, 13 Mar 2017 10:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 HXkZp5PlkmS7 for <tsvwg@ietfa.amsl.com>; Mon, 13 Mar 2017 10:48:58 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (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 183A9129993 for <tsvwg@ietf.org>; Mon, 13 Mar 2017 10:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:Cc:References:Subject:Sender:Reply-To:To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=etklmn9PHHKjSU1rlgkvJPmp2NDFQB34qYJtM2D5SwA=; b=GCcvovrY3UNxwJ1IvgTbd+hnd PKwND4TiDK2iwJFe9c/bp9bwe+wzyfWD9+YGDOK1ofnDxB+CVlZ0H3FDg6cPjdQYJ+vxgtwhFueDm q+pRsdJhliOK4e4SBElHPrJXWhuDN2LQTxrIoCz0EfVP6Dc9QcDVxrOKP4r6BdX29qEb6HbYx8yzk aVMVuKQdSXTE9YwRJwpIJGOitlwSlxg0eLTzBV2fpFQtay0lf7Y9c5RCgMFtlCis83AQvhzh+QA6h FXf+qKPdMOXi+clRw5yBh6Gm0BSFYns74Eajg1mkxtyIT7m76tsEUCNGrPPc/fWlQkMJ8XGcwG+YQ GdFlSxPpQ==;
Received: from 203.6.208.46.dyn.plus.net ([46.208.6.203]:35482 helo=[192.168.0.5]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from <in@bobbriscoe.net>) id 1cnU5Y-0003s1-Hl for tsvwg@ietf.org; Mon, 13 Mar 2017 17:48:56 +0000
References: <DB4PR07MB3489946F7C0D04B551F2E0EC25A0@DB4PR07MB348.eurprd07.prod.outlook.com> <CAJt_5EiTu3UaeZKZ08jTGeBntdyLrKK0z+=7r+w=Uy1PwKERhg@mail.gmail.com>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Bob Briscoe <in@bobbriscoe.net>
Message-ID: <ba46bbc0-9cc4-60d9-6bd2-4bdbf2a5e201@bobbriscoe.net>
Date: Mon, 13 Mar 2017 17:48:55 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAJt_5EiTu3UaeZKZ08jTGeBntdyLrKK0z+=7r+w=Uy1PwKERhg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------762348653FFEDA218464B94D"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/uKeKdEK17_uNZvw2QmIV07Kp8CA>
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: Mon, 13 Mar 2017 17:48:59 -0000

Wes/tsvwg list,
I guess I ought to say I support this work, and I'm still interested in 
contributing.
I've been pushing forward on some next research steps, so sorry for the 
belated reply.
Bob

On 16/02/17 19:33, Pat Thaler wrote:
> I'm supportive of this going forward in TSVWG and interested in 
> contributing.
>
> On Thu, Feb 16, 2017 at 12:09 AM, Ingemar Johansson S 
> <ingemar.s.johansson@ericsson.com 
> <mailto:ingemar.s.johansson@ericsson.com>> wrote:
>
>     Hi
>
>     Yes, I am very interested in this work and will contribute to the
>     work.
>
>     /Ingemar
>
>     >
>     > Message: 1
>     > Date: Mon, 6 Feb 2017 23:13:32 -0500
>     > From: Wesley Eddy <wes@mti-systems.com <mailto:wes@mti-systems.com>>
>     > To: "tsvwg@ietf.org <mailto:tsvwg@ietf.org>" <tsvwg@ietf.org
>     <mailto:tsvwg@ietf.org>>
>     > Subject: [tsvwg] L4S work in TSVWG
>     > Message-ID:
>     <274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com
>     <mailto:274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com>>
>     > Content-Type: text/plain; charset=utf-8; format=flowed
>     >
>     > Hello, as a co-chair, I'm checking to make sure we have the
>     critical mass to go
>     > forward with L4S in TSVWG.
>     >
>     > 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
>     <https://tools.ietf.org/html/draft-briscoe-tsvwg-l4s-arch-00>
>     >
>     > 2.
>     https://tools.ietf.org/html/draft-briscoe-tsvwg-aqm-dualq-coupled-00
>     <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
>     <https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id-02>
>     >
>     > 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.
>     >
>     > Thanks!
>     >
>     >
>     >
>
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/

v2.23.0 | Report a Bug | By Email