Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
* [Starlink] new routing work at the IETF: Time Variant Routing
@ 2022-11-06 18:45 Michael Richardson
  0 siblings, 0 replies; only message in thread
From: Michael Richardson @ 2022-11-06 18:45 UTC (permalink / raw)
  To: starlink

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]


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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-11-06 18:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-06 18:45 [Starlink] new routing work at the IETF: Time Variant Routing Michael Richardson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox