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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-09-06 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
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-sivabalan-pce-binding-label-sid-04.txt

Abstract

It is possible to associate a binding label to RSVP-TE signaled Traffic Engineering Label Switching Path or binding Segment-ID (SID) to Segment Routed 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 TE 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 (msiva@cisco.com)
Jeff Tantsura (jefftant.ietf@gmail.com)
Clarence Filsfils (cfilsfil@cisco.com)
Stefano Previdi (stefano@previdi.net)
Jonathan Hardwick (jonathan.hardwick@metaswitch.com)
Dhruv Dhody (dhruv.ietf@gmail.com)

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