From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 80A423B2A4 for ; Fri, 2 Sep 2022 14:34:33 -0400 (EDT) Received: from dooku.sandelman.ca (unknown [75.98.19.151]) by relay.sandelman.ca (Postfix) with ESMTPS id 131EE1F48B; Fri, 2 Sep 2022 18:34:29 +0000 (UTC) Received: by dooku.sandelman.ca (Postfix, from userid 179) id CDBAF1A01FC; Fri, 2 Sep 2022 14:34:17 -0400 (EDT) Received: from dooku (localhost [127.0.0.1]) by dooku.sandelman.ca (Postfix) with ESMTP id CBF901A0017; Fri, 2 Sep 2022 14:34:17 -0400 (EDT) From: Michael Richardson To: Sebastian Moeller cc: =?us-ascii?Q?=3D=3Fus-ascii=3FB=3FPT9VVEYtOD9RP0RhdmlkX0Zlcm49QzM9QTFu?= =?us-ascii?Q?ZGV6Pz0=3D=3F=3D?= , starlink@lists.bufferbloat.net In-reply-to: References: <16193.1662062192@localhost> Comments: In-reply-to Sebastian Moeller message dated "Fri, 02 Sep 2022 14:27:03 +0200." X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Fri, 02 Sep 2022 14:34:17 -0400 Message-ID: <105644.1662143657@dooku> Subject: Re: [Starlink] Starlink "beam spread" X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2022 18:34:33 -0000 --=-=-= Content-Type: text/plain Sebastian Moeller wrote: >> sadly, they aren't doing IP processing. I don't think that they ever >> will decide to for NIH reasons. I suspect that their SDN hardware >> probably can, and I think that SR6 is probably ideal for their use, >> but... > Why would SR6 be better than any other "underlay" encapsulation here, > like MPLS or SR-MPLS? Naively put this seems to trade 4 byte per label > with a full 40 byte IPv6 header plus 8 bytes plus 16 bytes per SR6 collapses all those things into a single IPv6 forwarding engine. The idea is that it's converged. As for the 44 byte header, as envisioned by the SR6 people, they would use the original header, but that's against the Ipv6 architecture. There are ways to compress that header down if you need to do that. > "label". Asking out of genuine curiosity what are those additional > bytes in overhead actually buying (except the freedom from MPLS). IPv6 all the way down. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAmMSTKkACgkQlUzhVv38 QpCHGAgAhSg9k0l8BcRmtstytG4PJsQ7B9BeFMbQsdYp8SO1TEglAw19uwi/Qo5D xwWdn37yWcBj8xsZfeDVEAmis6dVVcrbrtkajAVKkO7vl0XqsmhiJGGpqxmxaPaq VRnnygqO/duna3WwCXP95iUEPRB50ERQBKDS57gne28+IfNjt3luRWMSadYU16GZ uAPQjWbChAtrSC1nE27rFYuZmGkEUrtYjJEnmOrkPzOdy/eK9VtryiGFWevouB0p dKWtlrkjbTPUJMkIOzDdTfzmoM7JdfNwiKkNs4V7+uDXo8PawVr18W6HZwhbUEO7 YwkYvnC9YScsBgsIMYgZgY90rUtf2w== =vgcu -----END PGP SIGNATURE----- --=-=-=--