Carrying Binding Label/Segment-ID in PCE-based Networks.
draft-sivabalan-pce-binding-label-sid-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Siva Sivabalan , Clarence Filsfils , Stefano Previdi , Jeff Tantsura , Jonathan Hardwick , Mohan Nanduri | ||
| Last updated | 2017-04-16 (Latest revision 2016-10-13) | ||
| Replaced by | draft-ietf-pce-binding-label-sid, draft-ietf-pce-binding-label-sid, draft-ietf-pce-binding-label-sid | ||
| RFC stream | (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
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
Clarence Filsfils
Stefano Previdi
Jeff Tantsura
Jonathan Hardwick
Mohan Nanduri
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)