LABEL-DB Synchronization Procedures for a PCE as a central controller(PCECC)
draft-palle-pce-controller-labeldb-sync-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-09-05 (latest revision 2018-03-04) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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) | ||
https://www.ietf.org/archive/id/draft-palle-pce-controller-labeldb-sync-03.txt
Abstract
PCE as a central controller specifies the procedures and PCEP protocol extensions 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 PCE. The basic mechanism for label database (LABEL-DB synchronization is part of the PCE as a central controller specification. This document presents motivations for optimizations to the LABEL-DB synchronization and the corresponding PCEP procedures and extensions.
Authors
Udayasree Palle
(udayasreereddy@gmail.com)
Dhruv Dhody
(dhruv.ietf@gmail.com)
Satish Karunanithi
(satishk@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)