Skip to main content

Advertising Segment Routing Policies in BGP
draft-ietf-idr-segment-routing-te-policy-08

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Stefano Previdi , Clarence Filsfils , Ketan Talaulikar , Paul Mattes , Eric C. Rosen , Dhanendra Jain , Steven Lin
Last updated 2020-05-21 (Latest revision 2019-11-18)
Replaces draft-previdi-idr-segment-routing-te-policy
Replaced by draft-ietf-idr-sr-policy-safi, draft-ietf-idr-bgp-sr-segtypes-ext
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Yes
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

This document defines a new BGP SAFI with a new NLRI in order to advertise a candidate path of a Segment Routing (SR) Policy. An SR Policy is a set of candidate paths, each consisting of one or more segment lists. 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. This document specifies the way in which BGP may be used to distribute SR Policy candidate paths. New sub-TLVs for the Tunnel Encapsulation Attribute are defined for signaling information about these candidate paths.

Authors

Stefano Previdi
Clarence Filsfils
Ketan Talaulikar
Paul Mattes
Eric C. Rosen
Dhanendra Jain
Steven Lin

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