Re: [tcpPrague] Enough energy for an L4S/TCP Prague BoF?

John Leslie <john@jlc.net> Wed, 01 June 2016 15:29 UTC

Return-Path: <john@jlc.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 5C15812D5BD for <tcpprague@ietfa.amsl.com>; Wed, 1 Jun 2016 08:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.026
X-Spam-Level:
X-Spam-Status: No, score=-4.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426] 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 QgHVRL28OeyF for <tcpprague@ietfa.amsl.com>; Wed, 1 Jun 2016 08:29:11 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 70F5C12D5B7 for <tcpPrague@ietf.org>; Wed, 1 Jun 2016 08:29:11 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 43456C9423; Wed, 1 Jun 2016 11:29:08 -0400 (EDT)
Date: Wed, 01 Jun 2016 11:29:08 -0400
From: John Leslie <john@jlc.net>
To: Bob Briscoe <research@bobbriscoe.net>
Message-ID: <20160601152908.GB1754@verdi>
References: <574EBEA2.8080705@bobbriscoe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <574EBEA2.8080705@bobbriscoe.net>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpprague/A9mlW73FvwNQPvXi9trpJC87HKc>
Cc: TCP Prague List <tcpPrague@ietf.org>
Subject: Re: [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 15:29:13 -0000

Bob Briscoe <research@bobbriscoe.net> wrote:
> 
> Can some folks respond on whether they think it is right to hold a BoF 
> on this topic in Berlin.

   I must admit I see little reason for a non-WG-forming formal-BoF.

   The formal-BoF process is really organized around forming a WG. An
informal-BoF can be organized entirely outside this process; and were
I to attend Berlin, I would certainly want to participate.

   It's getting awfully late to start organizing a WG-forming BoF, so
I'd tend to set my sights on an informal-BoF.

   We should definitely note draft-khademi-tsvwg-ecn-response, recently
submitted to TSVWG, presumably intended to become adopted as a WG draft,
and setting a basis for relaxing the "same-as-drop" rule of RFC3168.

   It mentions draft-khademi-tcpm-alternativebackoff-ecn, which presumably
is intended to become a TCPM WG draft and offers a different experiment
from dualq which we've been discussing here.

   I think it's more important to get involved in those discussions
than to try for a formal-BoF in Berlin.

   Obviously, YMMV...

--
John Leslie <john@jlc.net>