Segment Identifiers in SRv6
draft-krishnan-6man-sids-00
| Document | Type |
Replaced Internet-Draft
(candidate for 6man WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Suresh Krishnan | ||
| Last updated | 2022-04-12 (Latest revision 2022-02-10) | ||
| Replaced by | draft-ietf-6man-sids | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-sids | |
| Consensus boilerplate | Unknown | ||
| 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
The data plane for Segment Routing over IPv6 (SRv6) [RFC8754] is built using IPv6 as the underlying forwarding plane. Due to this underlying use of IPv6, Segment Identifiers (SIDs) used by SRv6 can resemble IPv6 addresses and behave like them [RFC8754][RFC8986] while exhibiting slightly different behaviors in some situations. This document intends to explore the characteristics of SRv6 SIDs and to clarify the relationship of SRv6 SIDs to the IPv6 Addressing Architecture [RFC4291].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)