Skip to main content

Segment Routing PCE Delegation in BGP
draft-wang-idr-sr-policy-pce-delegation-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Yang Wang , Hao Li , Yuanxiang Qiu , Liping Yang , Mengxiao Chen
Last updated 2021-08-06 (Latest revision 2021-02-02)
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 is a source routing paradigm that explicitly indicates the forwarding path for packets at the ingress node. An SR policy is a set of candidate SR paths consisting of one or more segment lists with necessary path attributes. The headend of an SR Policy may learn multiple candidate paths for an SR Policy. Candidate paths may be learned via a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP. The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multi Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. Currently, when a controller uses BGP to deploy an SR Policy, there is no way to encode PCE delegation related options. The only way to import a PCE delegation is through local configuration management, e.g., Netconf, CLI or gRPC. This document defines extensions to BGP to distribute PCE delegation information within an SR policy.

Authors

Yang Wang
Hao Li
Yuanxiang Qiu
Liping Yang
Mengxiao Chen

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