From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tn-mailgw-01.telenor.no (tn-mailgw-01.telenor.no [153.110.76.4]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 36CDD3B2A4 for ; Thu, 24 Oct 2019 07:51:38 -0400 (EDT) X-IronPort-AV: E=Sophos;i="5.68,224,1569283200"; d="scan'208";a="29166398" Received: from tns-sko-24-205.corp.telenor.no ([10.179.59.73]) by tn-mailgw-01.corp.telenor.no with ESMTP; 24 Oct 2019 11:51:37 +0000 Received: from TNS-SKO-24-210.corp.telenor.no (10.179.59.78) by TNS-SKO-24-205.corp.telenor.no (10.179.59.73) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 24 Oct 2019 13:51:36 +0200 Received: from TNS-SKO-24-208.corp.telenor.no (10.179.59.76) by TNS-SKO-24-210.corp.telenor.no (10.179.59.78) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 24 Oct 2019 13:51:36 +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.1473.005; Thu, 24 Oct 2019 13:51:36 +0200 From: To: Thread-Topic: [Bloat] Bufferbloat on 4G Connexion Thread-Index: AQHViZjpeFGGgCG8TKe8oActC1aSOadoYIkAgAFN95E= Date: Thu, 24 Oct 2019 11:51:36 +0000 Message-ID: <1571917896021.11761@telenor.com> References: <0876C235-C6D3-42B0-9D93-114DB75D4204@gmail.com>, In-Reply-To: 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.12] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Bloat] Bufferbloat on 4G Connexion X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2019 11:51:38 -0000 > The key thing in both BQL and AQL is that instead of treating all packets= the=0A= > same, you account for how long it will take to transmit them.=0A= >=0A= > In Wifi, your transmission rate can vary by a factor of 1000x (1Mb to ove= r 1Gb=0A= > per second), so just counting bytes as BQL does is no longer good enough.= =0A= >=0A= > how much does the actual over-the-air transmission rate vary in 4G? I'd b= et that=0A= > it varies less than wifi does because wifi must retain compatibility with= the=0A= > earliest equipment while 4G no longer supports 2G protocols.=0A= =0A= So in a scenario with a fixed (wall mounted outdoor unit) LTE device BQL co= uld work =0A= quite well as the radio will not fluctuate too much. =0A= =0A= But for a mobil "pocket router" being carried around an AQL approach would = be needed? =0A= =0A= =0A= -Erik=