IETF Logo Mail Archive

Re: [tsvwg] L4S work in TSVWG

Pat Thaler <pat.thaler@broadcom.com> Thu, 16 February 2017 19:33 UTC

Return-Path: <pat.thaler@broadcom.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 21AD41295A5 for <tsvwg@ietfa.amsl.com>; Thu, 16 Feb 2017 11:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 8uFKFMsceZpo for <tsvwg@ietfa.amsl.com>; Thu, 16 Feb 2017 11:33:07 -0800 (PST)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 142AB12955E for <tsvwg@ietf.org>; Thu, 16 Feb 2017 11:33:07 -0800 (PST)
Received: by mail-qt0-x235.google.com with SMTP id k15so23449315qtg.3 for <tsvwg@ietf.org>; Thu, 16 Feb 2017 11:33:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RLs6+sUCITTrHr7bIuZLDH3/shYmji+cWY7cvA5Txec=; b=WNbEa4mYPn/+614Be1/DYqI09fDQEYWq9/e+t83Pp+L0nDmAnxNKauPojhe22wevmC wm3F4V0zD4FYvfRvuUcM+XlFgFrbfoqEzHnP91LUnCC8L9Or7e8EAVO6ADRB1sR0A2Ho XGH8VJ4PCpsvuUh6y5HZmec4yFw6ja2zsLBMk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RLs6+sUCITTrHr7bIuZLDH3/shYmji+cWY7cvA5Txec=; b=cZ1n/gD9wskkIGxua7p5BKwXa6a9JU07S2U+mkInQslx5WMDIg/ZmXprV145kI3an7 AKzTXS8dTDIgs5sQZ+EwLPy97d/fdiv9zLXuLHMuA8Wq+DfzdP2jAd2Zcr3kF4g62TNF rDIGEfMm9jTSu9FQ7gCiFFu0klU5xmpKSrZiuroJLL5iK1CiTfcEyyi+rKLrpfn1y4R0 aDcxE0bWqK3YuwbC7o3/Eu3pjwAc3Ht/I5gERD6gbKeDqA4o0L7HvCwpPAAq6YgXBb03 e1eUgm/H0SY71BysjK0ft6Af9BmhC9IsNj73asRC3ls+fzB/aNNdkxaqTT42cNiIWeKp VNDw==
X-Gm-Message-State: AMke39l457LIkXJkhx7+Cj7iVdp5Ej1YwLEb5w3tHMHs9p4bWiyJB0wxH7ZqqzAvg1u3tmFZ7mGMFsti7qK7Ws/b
X-Received: by 10.200.45.211 with SMTP id q19mr3720841qta.115.1487273585935; Thu, 16 Feb 2017 11:33:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.41.75 with HTTP; Thu, 16 Feb 2017 11:33:05 -0800 (PST)
In-Reply-To: <DB4PR07MB3489946F7C0D04B551F2E0EC25A0@DB4PR07MB348.eurprd07.prod.outlook.com>
References: <DB4PR07MB3489946F7C0D04B551F2E0EC25A0@DB4PR07MB348.eurprd07.prod.outlook.com>
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Thu, 16 Feb 2017 11:33:05 -0800
Message-ID: <CAJt_5EiTu3UaeZKZ08jTGeBntdyLrKK0z+=7r+w=Uy1PwKERhg@mail.gmail.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11401d2ac6d7540548aaddd0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/GvKB6GpMRyqY7zCqrR3ibpNVWVc>
Cc: "tsvwg@ietf.org" <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: Thu, 16 Feb 2017 19:33:09 -0000

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> 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>
> > To: "tsvwg@ietf.org" <tsvwg@ietf.org>
> > Subject: [tsvwg] L4S work in TSVWG
> > Message-ID: <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
> >
> > 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.
> >
> > Thanks!
> >
> >
> >
>
>

v2.23.0 | Report a Bug | By Email