IETF Logo Mail Archive

[tsvwg] Milestones for L4S work in TSVWG

Bob Briscoe <ietf@bobbriscoe.net> Mon, 27 March 2017 13:22 UTC

Return-Path: <ietf@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 5CA3112953F for <tsvwg@ietfa.amsl.com>; Mon, 27 Mar 2017 06:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 jydiYQiJ40_Q for <tsvwg@ietfa.amsl.com>; Mon, 27 Mar 2017 06:22:42 -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 3B99E127333 for <tsvwg@ietf.org>; Mon, 27 Mar 2017 06:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:To:Cc:References:Subject:Sender :Reply-To: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=S1nXKBaYajGfv8ncMxGjwsRF+zkdPwWpFc/lzCKTZnU=; b=la/OK830rr4j7Eobv/ErKjLtGa AXHvHG60V944vkqVhObODkiQPPjWRFGiqRwEwtNeHY2cIRdW8HDvvxhO5CkuG7TLSbCuI4ENxJFLh afPJAzG9QzLDdIkGfIOqiFc8zMjNIkUWrWsWyDyqK4Gs93g3wCj/XXdHIGLMDCYZ3ZX0hq3XJphYC Oq4ul3UPSKE3qSKkBtZeH8E5i9Is0CPrQ6d3toApvepynNochQOuvg1U6/P5/OY3Ra3HebZUZ3afn uLeA9gewLuuhIPUaHk/LL9NhoIu+H75o3e1GYUemxQRwLby3SXhKeJVyTemEJqW72A5zCF4KLNxKJ 6TJhhkkw==;
Received: from 203.6.208.46.dyn.plus.net ([46.208.6.203]:55832 helo=[192.168.0.3]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from <ietf@bobbriscoe.net>) id 1csUbY-0007FA-M1; Mon, 27 Mar 2017 14:22:40 +0100
References: <DB4PR07MB3489946F7C0D04B551F2E0EC25A0@DB4PR07MB348.eurprd07.prod.outlook.com> <CAJt_5EiTu3UaeZKZ08jTGeBntdyLrKK0z+=7r+w=Uy1PwKERhg@mail.gmail.com> <ba46bbc0-9cc4-60d9-6bd2-4bdbf2a5e201@bobbriscoe.net> <261f2bc5-8083-316d-f205-411548c7886f@mti-systems.com> <0a836ed7-7e56-5317-711b-2586af26bd6a@bobbriscoe.net> <070d08c0-51d2-4fe2-0522-4772adf7cb1e@mti-systems.com> <218817b8-53c0-7d6f-54b3-ef6d4df84fb7@bobbriscoe.net> <HE1PR0701MB21221DD33BBE43357958F429B9390@HE1PR0701MB2122.eurprd07.prod.outlook.com> <91ebe46d-3206-eeab-01fe-66c6d7cf1b7d@mti-systems.com> <9dc5409e-e7b3-def4-94fe-4d4a13a61326@bobbriscoe.net> <3773e2b6-fea3-70dd-63c1-910a993690f3@mti-systems.com>
Cc: Wesley Eddy <wes@mti-systems.com>, "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>, marcelo bagnulo braun <marcelo@it.uc3m.es>, tsvwg IETF list <tsvwg@ietf.org>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <83f5810e-9c54-859e-11b1-51079a50e8b7@bobbriscoe.net>
Date: Mon, 27 Mar 2017 14:22:40 +0100
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: <3773e2b6-fea3-70dd-63c1-910a993690f3@mti-systems.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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/HqM7Nc-sM22EHzA9YfD8wpr9GFg>
Subject: [tsvwg] Milestones for L4S work in TSVWG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
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, 27 Mar 2017 13:22:44 -0000

Ingemar,

Wes has been asking what are sensible milestones for the L4S work in TSVWG.
It occurred to me that there might be a particularly important deadline 
in the 3GPP's release schedule for introducing new queue management 
technology into eNodeB's.

Can you (or any other 3GPP-savvy person on this list) point us at where 
this schedule is, if it's public? And if necessary interpret the 
significance of any stages.

Cheers


Bob

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

v2.23.0 | Report a Bug | By Email