Search RFCs
RFC 6232
Purge Originator Identification TLV for IS-IS,May 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 5301,RFC 5304,RFC 5310
- Updated by:
- RFC 8918
- Authors:
- F. Wei
Y. Qin
Z. Li
T. Li
J. Dong - Stream:
- IETF
- Source:
- isis (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6232
Discuss this RFC: Send questions or comments to the mailing listlsr@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6232
Abstract
At present, an IS-IS purge does not contain any informationidentifying 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 topurges to record the system ID of the IS generating it. Since normalLink State Protocol Data Unit (LSP) flooding does not change LSPcontents, this TLV should propagate with the purge.
This document updates RFC 5301, RFC 5304, and RFC 5310. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.