LABEL-DB Synchronization Procedures for a PCE as a central controller(PCECC)
draft-palle-pce-controller-labeldb-sync-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Udayasree Palle , Dhruv Dhody | ||
| Last updated | 2016-11-16 (Latest revision 2016-05-15) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
[I-D.zhao-pce-pcep-extension-for-pce-controller] specify the procedures and PCEP protocol extensions for using the PCE as the central controller [I-D.zhao-teas-pce-control-function] where LSPs are calculated/setup/initiated and label forwarding entries are downloaded through a centralized PCE server to each network devices along the LSP path while leveraging the existing PCE technologies as much as possible. Labels downloaded to forwarding entries requires a reliable synchronization mechanism between the path computation clients (PCCs) and the PCECC. This draft specify the label database synchronization mechanism for managing of label database (LABEL-DB) at node (PCC) aligning with LABEL-DB at PCECC on initial session UP or session flap and specifies the required Path Computation Element Communication Protocol (PCEP) extensions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)