Optimizations of PCEP Link-State(LS) Synchronization Procedures
draft-kondreddy-pce-pcep-ls-sync-optimizations-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Venugopal Reddy Kondreddy , Mahendra Singh Negi | ||
| Last updated | 2016-04-11 (Latest revision 2015-10-09) | ||
| Replaces | draft-kondreddy-pcep-ls-sync-optimizations | ||
| 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
For a Path Computation Element (PCE) to perform its computations, it is important that Link-State (and TE) information be complete and accurate each time. This requires a reliable Link-State Synchronization mechanism between the PCE and path computation clients (PCCs), and between cooperating PCEs. The basic mechanism for Link-State Synchronization is part of the PCEP Link-State (and TE) draft. This draft presents motivations for optimizations to the base PCEP Link-State (and TE) procedure and specifies the required Path Computation Element Communication Protocol (PCEP) extensions.
Authors
Venugopal Reddy Kondreddy
Mahendra Singh Negi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)