Re: [tcpm] [tsvwg] inband signaling (was: Re: Agenda requests for TSVWG@IETF101)

Toerless Eckert <tte@cs.fau.de> Fri, 16 March 2018 19:20 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E9812D7ED; Fri, 16 Mar 2018 12:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level:
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 nh43EtgtjJzF; Fri, 16 Mar 2018 12:20:18 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22706127871; Fri, 16 Mar 2018 12:20:17 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 956D058C4C6; Fri, 16 Mar 2018 20:20:13 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 786E0B0DD4B; Fri, 16 Mar 2018 20:20:13 +0100 (CET)
Date: Fri, 16 Mar 2018 20:20:13 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Thomas Nadeau <tnadeau@lucidvision.com>, "tcpm@ietf.org" <tcpm@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, Katsushi Kobayashi <ikob@acm.org>, Yingzhen Qu <yingzhen.qu@huawei.com>
Message-ID: <20180316192013.GB31123@faui40p.informatik.uni-erlangen.de>
References: <050065D2-5F2E-4E79-9BD1-E1DC03F13900@acm.org> <5AA79C2E.1040808@erg.abdn.ac.uk> <20180313164928.GA17042@faui40p.informatik.uni-erlangen.de> <AM5PR0701MB2547C46DDFBD295F34989C0D93D70@AM5PR0701MB2547.eurprd07.prod.outlook.com> <1D30AF33624CDD4A99E8C395069A2A162CDBBA47@sjceml521-mbs.china.huawei.com> <VI1PR0701MB255831A406C1EA3493FD0EF193D70@VI1PR0701MB2558.eurprd07.prod.outlook.com> <1D30AF33624CDD4A99E8C395069A2A162CDBBA8E@sjceml521-mbs.china.huawei.com> <VI1PR0701MB2558DAB3AF5AF8AF43DBA73393D70@VI1PR0701MB2558.eurprd07.prod.outlook.com> <20180316164450.GA31123@faui40p.informatik.uni-erlangen.de> <CAKKJt-eunWaw7xDUjGkP5mErqLcvQyGiN1pZwD76SYGQGy5YbQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKKJt-eunWaw7xDUjGkP5mErqLcvQyGiN1pZwD76SYGQGy5YbQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/jCvU67_RZPhFEi0hmfydbJJH91o>
Subject: Re: [tcpm] [tsvwg] inband signaling (was: Re: Agenda requests for TSVWG@IETF101)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 19:20:21 -0000

Thanks, Spencer!

Is there any newer formalistic reference for "TCP friendly CC" or "Internet fair CC"
that one could reference ? Or are we down to the battle ground of coming
up with a random CC algorithm and showing through testing that it will
be within +- 10x speed of some "internet CC mix - Reno, QBR? BBR, nada, ..." ?

If so, is there any defined "Internet CC mix" to do testing with ?

how else... ;-))

Cheers
    Toerless

On Fri, Mar 16, 2018 at 05:54:30PM +0000, Spencer Dawkins at IETF wrote:
> I'm watching this thread, in all its variations across mailing lists, with
> great interest, but not participating, except to say ...
> 
> On Fri, Mar 16, 2018 at 4:44 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> > Michael:
> >
> 
> deleted down to
> 
> 
> > Maybe using a rather older refeence CC scheme like reno to define an easily
> > implementable version of the CIR..PIR goal is not the right approach,
> > but the description shuold be more abstract ? Or just use as Emmanual did
> > rely on TFRC as a reference ? Given how i think ( i may be wrong) that
> > TFRC is
> > not really applied to TCP, i thought another approch would have to be used.
> 
> 
> I wouldn't use TFRC as a reference unless you can find people who are
> actively using it as if it was a good thing.
> 
> I was still on the IAB when RMCAT was chartered, but I was also on the IAB
> program committee for https://www.iab.org/activities/workshops/cc-workshop/,
> which was the immediate predecessor activity for RMCAT, and IIRC, we
> couldn't find anyone who actually used TFRC for serious work. It was
> apparently being used as a fig leaf because prior to TFRC we had no advice
> for non-TCP rate control at all. So, at least people could say "do
> something, and TFRC is something", in their drafts without being flushed
> out of the IESG.
> 
> IMO, of course.
> 
> Spencer, speaking NOT as an AD, in this case ...

-- 
---
tte@cs.fau.de