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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 16 March 2018 17:54 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 49AE812D7E8; Fri, 16 Mar 2018 10:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 qriQBmsjZ6x0; Fri, 16 Mar 2018 10:54:32 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 803CB12D7E6; Fri, 16 Mar 2018 10:54:32 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id r66so7506608ywh.10; Fri, 16 Mar 2018 10:54:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mtk+s49+zVOxt4RXknwdwqFcJnosMysXjaUC2ijkK9c=; b=iB4WtLkgZADQoYrpgy/X02FMPEMsmnt5q0iHxJKy1b6exeX+p5p/E4xTI2d4UFQbHm yeq8YvlS/4tXOT+rJqkDeXNuV8xKbSbYXYsq8cVdr/g28Q4TE67S3AOUwly+FhluvoPa Jsff7ATWt9PH5FnIoIGiHbRorolMxuyZ438A7Vdpe5BId/4sFIlnQsSbPjF046956T2d o+iI2wPI5G08oeBsapPYl/M3uzKwjXb49AXwe7wZIRRo1/mG5g85x5XpSxay3hYGxJRp 8EoVGv0/mb2GdBQNRVlelw8LY68awZzUI0Jb9AIU0HjeWor41uTj8Vn6/3pDcPjdjEkO mKeQ==
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=mtk+s49+zVOxt4RXknwdwqFcJnosMysXjaUC2ijkK9c=; b=ExCQ8unA3npz3e2PgIuSUbnIGKCHQA61cco4RIb2Fo/q5gGuME/vMiK1KnmLIHPq2q DD6YYZs6wtzOSpf72NquJXzu9lpXxZR/Jh/21f7BekCCauFoZiO5hPrMpJOVNaXeyPqs LwmY4ejUuv49LZpwfXEXY20dWHIVO2ANVpcEqKqcSsgSLYp3QxKHmAq19KBYP5A2BUSq H4At0+ufIKQd9bevaUk/60H5BFUI6nr1S7Puiz1R6QZ+TGk6fHkosVNcjLMWL+X48VG9 Hwc+WUvXtR7TmW9QPAeaY43L3WWhV+8GTDZ/X1vKhE5dywDgFu1WYWDQXnTN3UscDTfC BMBA==
X-Gm-Message-State: AElRT7GIUHPXANGRV8xKqvsJZL+DlqRp8n69TYTCv0aqxDYWtlnNXmAX q7lWwlxWpndhzz+KrdcK9RkhqqZHE+bcXB7wOeM=
X-Google-Smtp-Source: AG47ELtVHIuyDfjnepSvHkOpdjTRJ90SZJcKsZjrPygHga/hYvce/1ZpKcemU1z/maDHXHeeHMSZKPEjh4gI+Uq/XBA=
X-Received: by 10.13.192.132 with SMTP id b126mr1729152ywd.52.1521222871260; Fri, 16 Mar 2018 10:54:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:5f0f:0:0:0:0:0 with HTTP; Fri, 16 Mar 2018 10:54:30 -0700 (PDT)
In-Reply-To: <20180316164450.GA31123@faui40p.informatik.uni-erlangen.de>
References: <AM5PR0701MB25474AC4A52E38B43E543FA193DA0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <CABY-gOMJf-4GKkbmYMJScrafO44NEfy0hoq5KXJ0uVA+QUXGiA@mail.gmail.com> <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>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 16 Mar 2018 17:54:30 +0000
Message-ID: <CAKKJt-eunWaw7xDUjGkP5mErqLcvQyGiN1pZwD76SYGQGy5YbQ@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
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>
Content-Type: multipart/alternative; boundary="001a114e6454dda54905678b4c93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Bq-fB-IE5Bdi_d9zogdkngjQD1I>
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 17:54:35 -0000

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 ...