LABEL-DB Synchronization Procedures for a PCE as a central controller(PCECC)
draft-palle-pce-controller-labeldb-sync-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Udayasree Palle  , Dhruv Dhody 
Last updated 2016-11-16 (latest revision 2016-05-15)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
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-palle-pce-controller-labeldb-sync-00.txt

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

Udayasree Palle (udayasree.palle@huawei.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.)