Skip to main content

Carrying Binding Label/Segment-ID in PCE-based Networks.
draft-sivabalan-pce-binding-label-sid-07

Document Type Replaced Internet-Draft (candidate for pce WG)
Expired & archived
Authors Siva Sivabalan , Clarence Filsfils , Jeff Tantsura , Jonathan Hardwick , Stefano Previdi , Cheng Li
Last updated 2019-08-20 (Latest revision 2019-07-08)
Replaced by draft-ietf-pce-binding-label-sid
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-pce-binding-label-sid
Consensus boilerplate Unknown
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

In order to provide greater scalability, network opacity, and service independence, SR utilizes a Binding Segment Identifier (BSID). It is possible to associate a BSID to RSVP-TE signaled Traffic Engineering Label Switching Path or binding Segment-ID (SID) to Segment Routed (SR) Traffic Engineering path. Such a binding label/SID can be used by an upstream node for steering traffic into the appropriate TE path to enforce SR policies. This document proposes an approach for reporting binding label/SID to Path Computation Element (PCE) for supporting PCE-based Traffic Engineering policies.

Authors

Siva Sivabalan
Clarence Filsfils
Jeff Tantsura
Jonathan Hardwick
Stefano Previdi
Cheng Li

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