LDP Bindings Refresh
draft-pelletier-mpls-ldp-bindings-refresh-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Andre Pelletier , Syed Raza | ||
| Last updated | 2013-08-29 (Latest revision 2013-02-25) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-pelletier-mpls-ldp-bindings-refresh-02.txt
Abstract
There are situations when there is a need for performing consistency checks for LDP binding state (address/label bindings) exchanged between LDP speakers. For instance, a state refresh may be required to detect and purge stale bindings received by an LDP speaker, which have resulted from an in-service software upgrade. This document specifies mechanics that allow a sender LDP speaker to enclose the initial binding advertisements (or re-advertisements) between explicit START and END of binding markers, thus helping the receiving LDP speaker to detect and purge any extra/stale binding state previously learnt from the sender. In addition to the definition of new LDP Notification message status codes for bindings refresh, this document also extends LDP base specification by introducing the concept of "Wildcard Address" and a new "Wildcard Address Request" message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)