[tcpPrague] Enough energy for an L4S/TCP Prague BoF?
Bob Briscoe <research@bobbriscoe.net> Wed, 01 June 2016 10:53 UTC
Return-Path: <research@bobbriscoe.net>
X-Original-To: tcpprague@ietfa.amsl.com
Delivered-To: tcpprague@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3111E12D098 for <tcpprague@ietfa.amsl.com>; Wed, 1 Jun 2016 03:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 FJwNgxBzKMQi for <tcpprague@ietfa.amsl.com>; Wed, 1 Jun 2016 03:53:25 -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 104E412D0C6 for <tcpPrague@ietf.org>; Wed, 1 Jun 2016 03:53:25 -0700 (PDT)
Received: from [31.185.187.76] (port=45454 helo=[192.168.0.10]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <research@bobbriscoe.net>) id 1b83m6-0001SO-Qq for tcpPrague@ietf.org; Wed, 01 Jun 2016 11:53:23 +0100
To: TCP Prague List <tcpPrague@ietf.org>
From: Bob Briscoe <research@bobbriscoe.net>
Message-ID: <574EBEA2.8080705@bobbriscoe.net>
Date: Wed, 01 Jun 2016 11:53:22 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
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: <http://mailarchive.ietf.org/arch/msg/tcpprague/e8nzOFjJvXW8oQ0eAJNskNKOkzg>
Subject: [tcpPrague] Enough energy for an L4S/TCP Prague BoF?
X-BeenThere: tcpprague@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "To coordinate implementation and standardisation of TCP Prague across platforms. TCP Prague will be an evolution of DCTCP designed to live alongside other TCP variants and derivatives." <tcpprague.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpprague/>
List-Post: <mailto:tcpprague@ietf.org>
List-Help: <mailto:tcpprague-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 10:53:27 -0000
All, Can some folks respond on whether they think it is right to hold a BoF on this topic in Berlin. Back in Jul 2015, when we had the first ad hoc meeting about evolving DCTCP (the one where Matt Mathis suggested we call it TCP Prague), there was a huge amount of energy and excitement in the room. However, I've noticed that the discussion on this list seems to move in fits and starts. Can anyone suggest why? I see much more discussion off-list about building projects, around the enabling idea of the dualQ. Perhaps it's just that it takes a long time for some people to be able to to shift the focus of their work. If that's so, then I guess it is still worth the core proponents pressing ahead. Because others only need to influence the direction of travel of a project if it is moving! Thoughts? Bob PS. The BoF proposal deadline is on Friday. I'm guilty for not having yet delivered what I promised: a problem statement draft - working on it now. -- ________________________________________________________________ Bob Briscoe http://bobbriscoe.net/
- Re: [tcpPrague] Experimental dual-queue ECN Black, David
- Re: [tcpPrague] Experimental dual-queue ECN Michael Welzl
- Re: [tcpPrague] Experimental dual-queue ECN Gorry Fairhurst
- Re: [tcpPrague] Experimental dual-queue ECN John Leslie
- Re: [tcpPrague] Experimental dual-queue ECN Michael Welzl
- [tcpPrague] Experimental dual-queue ECN John Leslie
- Re: [tcpPrague] Experimental dual-queue ECN Gorry Fairhurst
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Gorry Fairhurst
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Spencer Dawkins at IETF
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Gorry Fairhurst
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Gorry Fairhurst
- [tcpPrague] Enough energy for an L4S/TCP Prague B… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… John Leslie
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Mirja Kühlewind
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… John Leslie
- [tcpPrague] Too fast for Google? Bob Briscoe
- Re: [tcpPrague] Enough energy for an L4S/TCP Prag… Bob Briscoe
- [tcpPrague] L4S BoF Proposal on the wiki Bob Briscoe