Forwarding in the context of Time-Variant Routing(TVR)
draft-blanchet-tvr-forwarding-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marc Blanchet | ||
| Last updated | 2023-09-14 (Latest revision 2023-03-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Some networks, such as in space, have links that are up and down based on a known schedule. In this context, IP Packets or Bundle Protocol Bundles should then be saved locally until the destination becomes reachable again. This document describes forwarding node policies regarding how to manage the local store as well as forwarding decisions. This specification applies to both IP packets or Bundle Protocol bundles.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)