BGP Request for Advertising Candidate Path of Segment Routing TE Policies
draft-li-ldr-bgp-request-cp-sr-te-policy-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Zhenbin Li  , Lei Li
Last updated 2020-01-09 (latest revision 2019-07-08)
Stream (None)
Formats
Expired & archived
pdf 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-li-ldr-bgp-request-cp-sr-te-policy-00.txt

Abstract

An SR Policy is a set of candidate paths. The headend of an SR Policy may learn multiple candidate paths for an SR Policy via a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP. BGP distribute candidate paths has been defined in [I-D.ietf-idr-segment-routing-te-policy]. This document defines an extension of BGP to request BGP speaker(controller) advertise the candidate paths. The goal is to unify the protocol when the candidate path of SR Policy provision is via BGP to reduce the network complexity and potential bugs cause by different protocol interactions.

Authors

Zhenbin Li (lizhenbin@huawei.com)
Lei Li (lily.lilei@huawei.com)

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