From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vsmta11-2.nsc.no (vip22scan.telenor.net [148.123.15.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E2B363B29E for ; Wed, 9 Aug 2017 04:36:32 -0400 (EDT) Received: from [153.110.251.168] ([153.110.251.168:39679] helo=ilp-smtp02.man.cosng.net) by vsmta11-2.nsc.no (envelope-from ) (ecelerity 3.6.22.53981 r(Core:3.6.22.0)) with ESMTPS (cipher=DHE-RSA-AES256-GCM-SHA384) id 32/FF-08967-E89CA895; Wed, 09 Aug 2017 10:36:30 +0200 Received: from TNS-SKO-24-201.corp.telenor.no (TNS-SKO-24-201.corp.telenor.no [10.179.59.69]) by ilp-smtp02.man.cosng.net (Postfix) with ESMTP id CA6FD1FCE0 for ; Wed, 9 Aug 2017 10:36:30 +0200 (CEST) Received: from TNS-SKO-24-208.corp.telenor.no (10.179.59.76) by TNS-SKO-24-201.corp.telenor.no (10.179.59.69) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 9 Aug 2017 10:36:29 +0200 Received: from TNS-SKO-24-208.corp.telenor.no ([fe80::b024:7a41:ba33:25b6]) by TNS-SKO-24-208.corp.telenor.no ([fe80::b024:7a41:ba33:25b6%12]) with mapi id 15.00.1263.000; Wed, 9 Aug 2017 10:36:30 +0200 From: To: Thread-Topic: Fast snack, QUIC CAKE? Thread-Index: AQHTEOqFRplJnFMcT0mSjrQdFm44zA== Date: Wed, 9 Aug 2017 08:36:29 +0000 Message-ID: <1502267789764.33636@telenor.com> Accept-Language: nb-NO, en-US Content-Language: nb-NO X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.181.50.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SCAN_VERDICT: inbox Subject: [Cake] Fast snack, QUIC CAKE? X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 08:36:33 -0000 Has anybody here done any experimentation on CAKE (and others) when using Q= UIC? Or other real world insights into other aspects of QUIC? For exampl= e proper CAKE and TCP version of youtube vs crappy quing/latency and QUIC. The overlapping design goals is making the user experience snappy, but QUIC= s approach is to control the end points with a new protocol to replace TCP.= (Or improve TCP in the future). https://en.wikipedia.org/wiki/QUIC -Erik