PCEP extension to support Segment Routing Policy Candidate Paths
draft-barth-pce-segment-routing-policy-cp-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2020-05-02 (latest revision 2019-10-30)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-barth-pce-segment-routing-policy-cp-04.txt

Abstract

This document introduces a mechanism to specify a Segment Routing (SR) policy, as a collection of SR candidate paths. An SR policy is identified by <headend, color, end-point> tuple. An SR policy can contain one or more candidate paths where each candidate path is identified in PCEP via an PLSP-ID. This document proposes extension to PCEP to support association among candidate paths of a given SR policy. The mechanism proposed in this document is applicable to both MPLS and IPv6 data planes of SR.

Authors

Mike Koldychev (mkoldych@cisco.com)
Siva Sivabalan (msiva@cisco.com)
Colby Barth (cbarth@juniper.net)
Cheng Li (chengli13@huawei.com)
Hooman Bidgoli (hooman.bidgoli@nokia.com)

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