Skip to main content

Encapsulation of Path Segment in SRv6
draft-li-6man-srv6-path-segment-encap-06

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Cheng Li , Weiqiang Cheng , Yongqing Zhu , Zhenbin Li , Dhruv Dhody
Last updated 2021-11-09 (Latest revision 2021-05-08)
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

Segment Routing (SR) allows for a flexible definition of end-to-end paths by encoding an ordered list of instructions, called "segments". The SR architecture can be implemented over an IPv6 data plane, called SRv6. In some use-cases such as end-to-end SR Path Protection and Performance Measurement (PM), an SRv6 path needs to be identified. An SRv6 Path Segment can be used for identifying an SRv6 path. This document defines a P-flag in the Segment Routing Header to indicate the appearence of SRv6 Path Segment.

Authors

Cheng Li
Weiqiang Cheng
Yongqing Zhu
Zhenbin Li
Dhruv Dhody

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)