IETF Logo Mail Archive

Re: [tsvwg] L4S work in TSVWG

"De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia-bell-labs.com> Wed, 15 February 2017 10:03 UTC

Return-Path: <koen.de_schepper@nokia-bell-labs.com>
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 073F51299D2 for <tsvwg@ietfa.amsl.com>; Wed, 15 Feb 2017 02:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.787
X-Spam-Level:
X-Spam-Status: No, score=-8.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-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 z-2WdUjUeKa9 for <tsvwg@ietfa.amsl.com>; Wed, 15 Feb 2017 02:03:46 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 F2C2E129ACE for <tsvwg@ietf.org>; Wed, 15 Feb 2017 02:03:45 -0800 (PST)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 21C14CC6453C4; Wed, 15 Feb 2017 10:03:42 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id v1FA3hF2002424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Feb 2017 11:03:43 +0100
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id v1FA3dK3006418 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Feb 2017 10:03:41 GMT
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.65]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0301.000; Wed, 15 Feb 2017 11:03:38 +0100
From: "De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia-bell-labs.com>
To: Wesley Eddy <wes@mti-systems.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] L4S work in TSVWG
Thread-Index: AQHSgPiTLsOzqZT4CkS/64snsNwqu6Fp3lRg
Date: Wed, 15 Feb 2017 10:03:37 +0000
Message-ID: <BF6B00CC65FD2D45A326E74492B2C19FB7803FF6@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com>
In-Reply-To: <274f4ce5-d7da-75f3-5a84-751f87864962@mti-systems.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/1rS_SDNUtwBkPMOFwWItPIE2WM4>
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: Wed, 15 Feb 2017 10:03:48 -0000

Hi,

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Wesley Eddy
> Sent: dinsdag 7 februari 2017 5:14
> To: tsvwg@ietf.org
> Subject: [tsvwg] L4S work in TSVWG
> 
> Hello, as a co-chair, I'm checking to make sure we have the critical
> mass to go forward with L4S in TSVWG.

I am continuing working on the L4S topics (DualQ, PI2 and TCP-Prague).

> 
> 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
> 
> 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'm involved in most of the above.

Koen.

> 
> Thanks!
> 
> 
>

v2.23.0 | Report a Bug | By Email