SRv6 Migration Scenarios
draft-hegde-spring-srv6-migration-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shraddha Hegde , Rajesh Shetty , Bharath radhakrishna Bhat , Daniel Voyer | ||
| Last updated | 2024-04-25 (Latest revision 2023-10-23) | ||
| 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
SRv6 forwarding plane requires devices to support processing newly defined Segment Routing extension header. All devices in the network may not be capable of processing this new header and may require gradual upgrade. This document specifies mechanisms that to deploy features such as TI-LFA, in the presence of SRH incapable devices in the network.
Authors
Shraddha Hegde
Rajesh Shetty
Bharath radhakrishna Bhat
Daniel Voyer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)