database logo graphic

RFC 6232

"Purge Originator Identification TLV for IS-IS", May 2011

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6232.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Updates:
RFC 5301, RFC 5304, RFC 5310
Authors:
F. Wei
Y. Qin
Z. Li
T. Li
J. Dong
Stream:
IETF
Source:
isis (rtg)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

At present, an IS-IS purge does not contain any information identifying the Intermediate System (IS) that generates the purge. This makes it difficult to locate the source IS. To address this issue, this document defines a TLV to be added to purges to record the system ID of the IS generating it. Since normal Link State Protocol Data Unit (LSP) flooding does not change LSP contents, this TLV should propagate with the purge. This document updates RFC 5301, RFC 5304, and RFC 5310. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.