From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2E5663B2A4 for ; Fri, 14 Feb 2020 09:18:56 -0500 (EST) Received: from dooku.sandelman.ca (unknown [46.183.103.8]) by relay.sandelman.ca (Postfix) with ESMTPS id CBAEE1F459; Fri, 14 Feb 2020 14:18:48 +0000 (UTC) Received: by dooku.sandelman.ca (Postfix, from userid 179) id 6634E1A2B90; Fri, 14 Feb 2020 15:18:19 +0100 (CET) From: Michael Richardson To: Daniel Sterling cc: bloat@lists.bufferbloat.net In-reply-to: References: Comments: In-reply-to Daniel Sterling message dated "Tue, 11 Feb 2020 23:55:55 -0500." X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.2.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Fri, 14 Feb 2020 15:18:19 +0100 Message-ID: <19192.1581689899@dooku> Subject: Re: [Bloat] is extremely consistent low-latency for e.g. xbox possible on SoHo networks w/o manual configuration? 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: Fri, 14 Feb 2020 14:18:56 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Daniel Sterling wrote: > I am looking for input / discussion on how to achieve: > * on a "regular" SoHo network > * first and foremost, to the exclusion of all other goals, consistent > low-latency for non-bulk streams from particular endpoints; usually > those streams are easily identified and differentiated from all other > streams based on UDP/TCP port number, > * and assuming the identified and prioritized streams behave > themselves and stay non-bulk, decent throughput for all other traffic. > That is to say, some endpoints are more important than others; and > moreover some apps on some endpoints are most important. Distinguishing between apps is difficult in IPv4. IPv6 lets you naturally have many IP addresses, so it could be easier, but apps need to be taught to use "their" source address. Or OSes need to force them, or "containers". In the specific case of a single network, I'd just do static DHCPv4 allocation and change the parameters on the qos scripts. In general, I'd want RFC8520 to announce the type of the device, and suggest a particular class of service. In the old days, we'd be talking RSVP to signal desired Diffserv behaviour ("DiffEdge"), but that specification did not, unfortunately, gain market momentum. > I put a linux laptop between CPE (WAN) and LAN. AT&T fiber in my case, > 100+ mbit up and down. It's not a terrible thing to use a laptop, but at 100Mb/s, an Omnia Turris = or equivalenet running latest OpenWRT may be more foolproof. (I'm always the f= ool) =2D-=20 ] Never tell me the odds! | ipv6 mesh network= s [=20 ] Michael Richardson, Sandelman Software Works | network architect= [=20 ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [=20 =09 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAl5GrCsACgkQlUzhVv38 QpBr6Af/Qq2OLOIEtmkOKssQMNzAJkrBAS2kEMR/RQrwxzfiWDBZCtKLoEC503oq CO+uaHD2VsdzEWDr0cL2EoBqqb0eHSzi3enPKE7e4mP86KeyCF3/BvfU9O/1eeBW V44CVJe8vUAJGsDibCiSHR1LJtu3h9kySqt0KE6KQ326U4a1L1qqj3M9L2KwACB6 tQoEkh7wxY0xvkRAYtZXaMe8gy/6pVWPd75WIAWPWHSkJ69dgvEq6jRCEwzK/oWp aqwCy5250qYolcKvP0rTGIAGGiug6AAN+b8p3lgdZjnqj2x7CcWs9a6LWn/8vv8m OVw6Y4Uo5esfdI71XXAZZlmXEuSYjQ== =1MGj -----END PGP SIGNATURE----- --=-=-=--