From: Michael Richardson <mcr@sandelman.ca>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] new routing work at the IETF: Time Variant Routing
Date: Sun, 06 Nov 2022 18:45:56 +0000 [thread overview]
Message-ID: <68283.1667760356@dyas> (raw)
[-- 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 --]
reply other threads:[~2022-11-06 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68283.1667760356@dyas \
--to=mcr@sandelman.ca \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox