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 CC3C73B2A4 for ; Sun, 6 Nov 2022 13:46:00 -0500 (EST) Received: from dyas.sandelman.ca (dynamic-046-114-140-198.46.114.pool.telefonica.de [46.114.140.198]) by relay.sandelman.ca (Postfix) with ESMTPS id D20831F44E for ; Sun, 6 Nov 2022 18:45:58 +0000 (UTC) Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 9426FA0DED; Sun, 6 Nov 2022 18:45:56 +0000 (GMT) Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 8FED6A0C73 for ; Sun, 6 Nov 2022 18:45:56 +0000 (GMT) From: Michael Richardson To: starlink@lists.bufferbloat.net X-Attribution: mcr X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Sun, 06 Nov 2022 18:45:56 +0000 Message-ID: <68283.1667760356@dyas> Subject: [Starlink] new routing work at the IETF: Time Variant Routing 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: Sun, 06 Nov 2022 18:46:00 -0000 --=-=-= Content-Type: text/plain https://datatracker.ietf.org/meeting/115/materials/agenda-115-tvr-01 https://datatracker.ietf.org/doc/html/draft-taylor-tvr-prb-stmt-00 1. Introduction Existing Routing Protocols expect to maintain contemporaneous, end- to-end connected paths across a network. Changes to that connectivity, such as the loss of an adjacent peer, are considered to be exceptional circumstances that must be corrected prior to the resumption of data transmission. Corrections may include attempting to re-establish lost adjacencies and recalculating or rediscovering a functional topology. However, there are a growing number of use-cases where changes to the routing topology are an expected part of network operations. In these cases the pre-planned loss and restoration of an adjacency, or formation of an alternate adjacency, should be seen as a non- disruptive event. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAmNoAOQACgkQlUzhVv38 QpCtkwf/dopmUKhTM3ZtNlIzX7ze2R98oHsILQSaT2AJNzweriyG6rtjnB9yaN/F z8JnDDCh1EANuUju+4pYifzw8tzXvolbvoN+1xDIM5VHnkbdNrSsWYFjYmRGTweR 1V5Pqw8P9oshe8MkjJTKmdeiUyelyRA7f+byUqlkBCZObN17I083X37kUUgT1mqY RO8snp+86SKTyWGKx8lfH3a9y8APy5daDpYxgeolM99Sq1Nrbb4h3Td9rMvx0rGR BeOOBXdlE/ea0mY4UcvZJcgSZcZCdr31+xj7iLpBPKXIdGrF4fyFLNyKno0d8Qtb oVBxIJ34MrJbsC2JK5fCkayRcth5sQ== =Gbin -----END PGP SIGNATURE----- --=-=-=--