Re: [tsvwg] tsw/ospa: Internet phone-in-QoS ?

Sebastian Moeller <moeller0@gmx.de> Wed, 15 April 2020 09:15 UTC

Return-Path: <moeller0@gmx.de>
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 5F5333A0848; Wed, 15 Apr 2020 02:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.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 fVV8ydh3-fvS; Wed, 15 Apr 2020 02:15:22 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 6D54E3A0844; Wed, 15 Apr 2020 02:15:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1586942115; bh=5LAaPLmS1qcNSqbc0iLTzGfRuLPNsBiADSX16NRJc3w=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=D+QZ+qhixqEeF6SUcBWXbJZtJtDd4Q4Mu91DH2p41L025MV0d9L/i3JMei8CeoHaR G/UpIlELus19nPvQbtxaF+Hzxi/JbKEmnc/6KvxZmfm8c5TlMW7+EzE//nUJkMYB0G xwaQ968qOyoXu/7G76l/VuRHclmRaWbBf2hjt1dg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from hms-beagle2.lan ([77.1.70.235]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MLQxX-1jfuAj3bz1-00IWKj; Wed, 15 Apr 2020 11:15:14 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <1F9CDC71-594A-48AD-959D-B70A72DEE9DD@gmail.com>
Date: Wed, 15 Apr 2020 11:15:13 +0200
Cc: Toerless Eckert <tte@cs.fau.de>, opsawg@ietf.org, tsvwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3EF056C-D67E-4EBB-8813-417756A3EA10@gmx.de>
References: <20200414194641.GA29328@faui48f.informatik.uni-erlangen.de> <1F9CDC71-594A-48AD-959D-B70A72DEE9DD@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-Provags-ID: V03:K1:3h33WXimn2Wnon1H8ySxjMNmv+jcGHW9BmMV8C+crhibZG3HLum ZjXTz2mrN1mKztwb/TV7mVX7QA01U4myqivC3geEr3W5twZ8xrbVltEmMi1nhsSqfKSL/YU xJX+FktW8xx4U9k00IIzwkiJPsgtcRF5M7/IyWy85eWS2pBbTqVdeCcCLsRg1nWbvOyVotZ KNn+gboynWSEjHU2Z/owA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:RIvZ78HlDE4=:1FT+fM+MJ50VILLqzYjoKg nxi1EsCkAEvaQoSVuDZTikdF2/MRX1zr3LSmY8QxzBojGqaCPx6TfYsPWtdLMf+xCJQTBMRAr wagnX2bbpn0lYaDlODFEinO1vY7lxYOfRvi+w1QVLIeXsRIOtmMdnCZCVy1KHt9FJKW8aak1S 5yKsT/S53voLZNpCGi8VClzDuFhOnBCR9icd7gaSpnHAFQe7/GkV/f38f3+6MmuCPBCwNXsob zkWTNYxR45qagoeOyMW1IakqoDzG8HPCYSOYFyU1jVRPkXSBWYm5iXsMqcDNvhWMuY6xaBPcM BCkT8eVLbbFcEYrHE7CfG1sxy4o2OQs9PjqQxGx9ViGgjrO7NchJQ2PIKpJLcJacMHquw+47J ZlZNXJVshhwwln2/+NfzcrIcb3zKuvTnz3Xo6yYS0U/8Eks85U25ZeYSqhtCTuyZlN/QCNoaE RNEqpjscpEhBWtO9nN1BaKnoThJV72WmC+GQVa3/9pmkixZNEL6dv5PtG0nywK2ACIwt89GRK U/maIS3uq4JjGrQw1Gq9XHEJCTVKbTMeAIVXxb1ysJFhOA2Bi8B8nljgmNx50d/oDQ85Yb2kY 0FX6TaqAWi+5sIbBZSxiANS6xDBEo3AY1NQFe4EqC/oFDJk1vzScvRXcmeAOz0rl4mErhT/ne qWjlg5to6m6qLPjwAlgZdLwBm6ieZuUqPqaopGCjU9ziv/H9oxtZ3My+a8vOiNO0lN5Hg29+u G+GizaX6y8/qzR4L1gt8j/IkYEitKrPLLoMqkhZPuH638W71aquIl7TxC0fLgsfntzGKQo6y4 b4sd0v95KdnWgETms1frTvp4qs2BeklfUWXZqV047aM4BmkgODaUyT5ZAgJormW7XfJmwAa/4 Adp1IB8yOnI2y/5p0uAQ5U+Giz5aw1skpJ6UnDlWtcTT5RSwierjbkV8t2dFpQFj8p0ZDEccd 1lGQVHAaKdbf9Mp1xwrWCjPhinRDOJP3tqD+k4erMHdbK4DKipcTbTA7aLHyC4xlcAZFgQzKu i662sGtKt0mhA+LZFgfqBvD9+m3is2wnqJg8mYNhRrar6ybf2qY0xPEIvr8oC/t0PgYDvkF4E QJ9gqAzCfDSBgjPpdkxp9DzQJYjlgMT2RsZX/5srCgoeyyIXrS7Ts4T5e4/q5lEX2qXYl2vch N9Hw2KILkL/GTz2otLt51Bgg1rW2Oe7PPKvzPcvrA0yd/WkvwbrtKWAX4aohKrQ9HzJju8o68 Gm00llD706rN1QlPK
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Pz2S2IzmP54c6Y6hw2Y4Ga1Y-nM>
Subject: Re: [tsvwg] tsw/ospa: Internet phone-in-QoS ?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 15 Apr 2020 09:15:25 -0000

Hi Jonathan,


> On Apr 14, 2020, at 22:44, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
>> On 14 Apr, 2020, at 10:46 pm, Toerless Eckert <tte@cs.fau.de> wrote:
>> 
>> I have been somewhat following how in the face of COVID-19,
>> the appropriate way to manage congestion control in the Internet 
>> seem to be heads of countries reaching out to the one large content provider
>> they know (Netflix) and ask him to reduce bandwidth pressure on the
>> Internet. Of course, heads of states with differently aged children
>> would know that Disney+ or Apple might be other relevant streaming
>> providers to reach out to, but alas, we have forgotten to elect 
>> those heads of states on such key criteria.
>> 
>> That was of course tongue in cheek of course, but i was somewhat surprised
>> that nobody took up the opportunity so far to ask something like "how are we
>> doing on Net Neutrality" ?, or "what the heck would we actually want it to be" ?
>> 
>> I can see a lot of operational short term workarounds to
>> approximate solutions less silly than phoning CEOs of random companies,
>> but it really strikes me as highly strange that events like the
>> ones we're in right now should not have us re-think to what extend
>> our current presumed strategy is sufficient…
> 
> I'm pretty sure that if ISPs implemented congestion control measures correctly at layer 3, there would be no need to take traffic-source-specific actions so high up the stack (beyond the machine layers) to merely ensure that backhaul networks and peering arrangements are not flooded into oblivion.  I'm talking about simple, well-understood measures such as:

	I disagree a bit, we are witnessing a policy decision by the EU that assumed purely recreational streaming traffic shall take a back-seat to assumed work related "home-office" traffic IFF the network experiences congestion. This is as much about how to distribute available bandwidth between different traffic "classes" as it is about avoiding the undesirable side-effects of congestion, just dealing with the second is not sufficient to solve the first.


> 
> 1: Implement AQM at every potential bottleneck, to limit effect of excess traffic on latency & reliability.  In this context, even WRED without ECN is better than nothing, but doing better would be nice.

	+1

> 
> 2: Share bottleneck capacity fairly between subscribers, so that one household's heavy traffic doesn't unduly impact the service to other households.  Want to download three Steam games, five Netflix streams and a 500-peer BitTorrent swarm all at once?  Go right ahead, but your next-door neighbour will get just as much bandwidth for his videoconference call about keeping a factory production line going.

	+1; and not because equal sharing is optimal in any sense, but because it is the best an intermediate hop can do with its limited information (and even there people complain that per-something queueing is too expensive computationally to do at scale in high speed gear)...
	in a sense fair sharing is the "democracy" of schedulers with Winston Churchill's citation (gently ammended) applicable:
"No one pretends that democracy/FQ is perfect or all-wise. Indeed it has been said that democracy/FQ is the worst form of Government/scheduling except for all those other forms that have been tried from time to time.…"


> 
> If those two measures were widely implemented, there would be no need for data caps, and streaming services' existing quality adjustment algorithms would automatically adjust to match available capacity.

	It is argued, that most streamers use adaptive streaming already, so in essence will scale back under load (but that does not work as well as it should, and due to the existence of over-sized and under-managed queues in the internet creates transient latency excursions that make interactive traffic types like vide-conferencing and gaming suffer).

> 
> There are already published RFCs detailing all the necessary technology to make this work.  It's already available in many end-hosts and CPE boxes.  It's just not widely deployed and switched on in ISPs' networks, where it can do the most good.  But there *are* a few ISPs who have done it, and thus might be good sources of practical expertise on the subject, if only the industry at large was willing to listen.

	+1; but again that is mainly orthogonal to the EU/BEREC action that ruffled a few feathers in the tech community, no?

Best Regards
	Sebastian


> 
> - Jonathan Morton