Re: [aqm] [tcpPrague] L4S status update
Matt Mathis <mattmathis@google.com> Tue, 29 November 2016 22:30 UTC
Return-Path: <mattmathis@google.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF00F129C9F for <aqm@ietfa.amsl.com>; Tue, 29 Nov 2016 14:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 xv-XwiiEemiQ for <aqm@ietfa.amsl.com>; Tue, 29 Nov 2016 14:30:33 -0800 (PST)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 DE1CB129CA7 for <aqm@ietf.org>; Tue, 29 Nov 2016 14:30:32 -0800 (PST)
Received: by mail-io0-x236.google.com with SMTP id m5so179307127ioe.3 for <aqm@ietf.org>; Tue, 29 Nov 2016 14:30:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8hEvW8tRU64aiKC+JSEHPL5HZlhaT06F1EHGLu7fGS0=; b=Gh8YxKCUlFq9/7ocX4pWn6IXnGNwyjrCZZnZistxtXVqmEKu0kOhn1V84+XNjppqxL 8W1m15bao95idFfJ9e5a0BO+AHTMS9iG5OkUuQdCUXTolONE5HNuaTfA2LL7LajhXObP 7UQ+uGlfTXBo27aMiNCi6cbKBjCkn7K+iDxVvNiW3QdO/CG+YwrJeFyg+LH4X9+OtswH y07dXAYBEWfDirH+ohkpOUuKIKDHK6IenAtbRht/3MfrxabXIyxOtcb8iBMQyxzpzjNP +b1BykZW45HHOAmuYEhLLcsVT4/J3EKVbemY1Y5Qt1RPRY3VMOQzCYTcJW87Jb/bQAG3 Gm3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8hEvW8tRU64aiKC+JSEHPL5HZlhaT06F1EHGLu7fGS0=; b=nE3DPQFQZ6aAFAKUC06FCUZsDduc6/1v+Yznkr6JS0IMe40cGAvoktZ0v8V7Tk8uU7 MVmMthcoCbZRQtAnCoDEkKcNICBRzJs+gRX3hpbkCK/7z49ixL2upAsh6FHGPeCz11NA kEGWyJOUX8y3TDDarlICgMypaJnBxr/9UjcI8A3N1Vxf/bq4Hn1U3VouQKgEER3wTrSn 66Zi8CKPNuTEQxKhhqkg8q2btwYYP1pue0dETBADkThPSS5zIZL1S1rR6eNVfFJkBnWS dsXc6ToWs0Oe/fa5GQtQGYdUrRaXelgXjLvOhfaW3jYSawJqoXV7nhDnlc8mex+s3sB1 3E2w==
X-Gm-Message-State: AKaTC032+pGUcFjuWDiaIagScrRsHKUS+8hk5wGjZb5SIYnfjYwugNf0NkEub+p5nw83IAAdQ/P/TDaiC4Q8Tgts
X-Received: by 10.107.128.194 with SMTP id k63mr26982101ioi.223.1480458632071; Tue, 29 Nov 2016 14:30:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.252.199 with HTTP; Tue, 29 Nov 2016 14:30:11 -0800 (PST)
In-Reply-To: <369bc3dc-c012-f149-d18c-a58f9c75ccf1@rogers.com>
References: <be67928d-e1f7-2495-147d-1d42d6783cc8@bobbriscoe.net> <f6b89407-14d8-b532-b793-7490cb5a2117@kit.edu> <f16c9830-f97a-64e0-76e6-66f146576616@bobbriscoe.net> <627c9db2-a41f-917d-e639-c27df25bdc51@kit.edu> <39e0cfa7-2650-9d98-a933-7e7c016dc276@bobbriscoe.net> <E615574E-2C76-4BAB-9481-E5FCF84659B3@gmail.com> <CAH56bmDoQ9OnjrrDD2XQ94AQ=G=y4U6KZh+q+q-sF6o1VvsdVQ@mail.gmail.com> <E745BC4F-2B4A-4D02-989B-247898500F65@gmail.com> <369bc3dc-c012-f149-d18c-a58f9c75ccf1@rogers.com>
From: Matt Mathis <mattmathis@google.com>
Date: Tue, 29 Nov 2016 14:30:11 -0800
Message-ID: <CAH56bmDYv4VN41Dehzgdj-Tkut43ih+5oN-4fNpLO+tuzxD6ZQ@mail.gmail.com>
To: David Collier-Brown <davecb@spamcop.net>
Content-Type: multipart/alternative; boundary="001a113fbb5adee3a70542782276"
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/9MZNaJWy_tA98Jm2BnHRveeBFRY>
Cc: AQM IETF list <aqm@ietf.org>
Subject: Re: [aqm] [tcpPrague] L4S status update
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2016 22:30:35 -0000
> > “Economic domain” only works if there is a financial cost borne by the > causer of the congestion. Good luck making that work, in a world where IoT > device manufacturers don’t bear the costs of DDoSes launched through them. I said that. If *everybody* was charged for the downstream congestion that they caused, everything would be fair and equitable. The owner of the IoT devices would receive a humungo bill and would have free choice to preserve the device and contribute to financing the target's capacity upgrade or to have the IoT device repaired. Assuming that the cost feedback is real time and various other details, my option #1 leads to a provably optimal economic solution. However, as we both noted, it is not deployable. Deploying FQ (and various virtual FQ systems, such as AFD) locks out all of these solutions due to replacing "per packet fairness" at the network layer (which enables the signaling between flows) with some sort of flow isolation. The flow isolation means more control by the network at the expense of less signalling between flows. Clearly the Internet already has some of each: we can't easily go 100% in either direction but which do we want more of? How can we partially deploy optimal systems, which are particularly nonoptimal under partial deployment? For me the deciding point was realising that 1) at the last mile all flows are local to the consumer: the competition is self inflicted. In this environment is straightforward to make DSCP/TOS controlled SFQ sort of solutions optimal from the user's perspective. Generally you want all small flow to take away from large flows, with perhaps a few large flows that are deprioritized. This is where WiFI and DOCIS, etc need to focus. And 2) congestion not at the edge almost always reflects a problem that can only be fixed by adding more capacity. Even with omniscient capacity allocation all schemes lead to "Somebody can't watch HD video* during primetime." If you size the network to (almost always) support HD during prime time, the core does not need sophisticated TE. Yes something is needed during transient overloads *In some areas substitute other services for HD video. Thanks, --MM-- The best way to predict the future is to create it. - Alan Kay Privacy matters! We know from recent events that people are using our services to speak in defiance of unjust governments. We treat privacy and security as matters of life and death, because for some users, they are. On Tue, Nov 29, 2016 at 4:41 AM, David Collier-Brown <davec-b@rogers.com> wrote: > On 28/11/16 10:42 PM, Jonathan Morton wrote: > >> On 29 Nov, 2016, at 04:55, Matt Mathis <mattmathis@google.com> wrote: >>> >>> Bob's point is that fq_anything forfeits any mechanism for an >>> application or user to imply the value of the traffic by how much >>> congestion they are willing to inflict on other traffic. >>> >> Yes, it does. >> >> I actually consider that a good thing, because most applications will, >> given the choice, choose to inflict more congestion on other traffic in >> order to boost their own performance. There are honourable exceptions, but >> it’s not a behaviour we can solely rely on. >> >> For example, Steam uses between four and eight parallel TCP streams (I >> can’t figure out what the number depends on) to receive game updates, when >> one or two would already saturate most domestic Internet connections. This >> magnifies the impact on other things the user might be doing with that >> connection, such as - ironically enough - playing multiplayer games. You’d >> think Valve, of all companies, would keep that in mind. >> > > Valve is like a lot of companies in "exciting" areas, and doesn't stop to > think. Like a lot of other game companies just throw resources at problems, > willy-nilly. The excessive tuning of Steam is typical. > > The gamers know better, but treat the problem as a game and think up cool > workarounds (;-)) > > Neither of them falls into any kind of economic domain. > > --dave (at WorldGaming) c-b > > -- > David Collier-Brown, | Always do right. This will gratify > System Programmer and Author | some people and astonish the rest > davecb@spamcop.net | -- Mark Twain > > > _______________________________________________ > aqm mailing list > aqm@ietf.org > https://www.ietf.org/mailman/listinfo/aqm >
- [aqm] L4S status update Bob Briscoe
- Re: [aqm] [tcpPrague] L4S status update hiren panchasara
- Re: [aqm] L4S status update Bless, Roland (TM)
- Re: [aqm] [tcpPrague] L4S status update Ingemar Johansson S
- Re: [aqm] [tcpPrague] L4S status update Bless, Roland (TM)
- Re: [aqm] L4S status update Bob Briscoe
- Re: [aqm] [tcpPrague] L4S status update Dave Täht
- Re: [aqm] L4S status update Jonathan Morton
- Re: [aqm] [tcpPrague] L4S status update Mario Hock
- Re: [aqm] L4S status update Bless, Roland (TM)
- Re: [aqm] [tcpPrague] L4S status update Bob Briscoe
- Re: [aqm] [tcpPrague] L4S status update De Schepper, Koen (Nokia - BE)
- Re: [aqm] [tcpPrague] L4S status update Bob Briscoe
- Re: [aqm] L4S status update Bob Briscoe
- Re: [aqm] L4S status update Jonathan Morton
- Re: [aqm] [tcpPrague] L4S status update Matt Mathis
- Re: [aqm] [tcpPrague] L4S status update Jonathan Morton
- Re: [aqm] [tcpPrague] L4S status update David Collier-Brown
- Re: [aqm] [tcpPrague] L4S status update Matt Mathis
- Re: [aqm] [tcpPrague] L4S status update Dave Täht
- Re: [aqm] [tcpPrague] L4S status update Dave Täht
- Re: [aqm] L4S status update Dave Täht
- Re: [aqm] [tcpm] L4S status update John Leslie
- Re: [aqm] [tcpm] L4S status update David Collier-Brown
- Re: [aqm] [tcpm] L4S status update Jonathan Morton