metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6232: Purge Originator Identification TLV for IS-IS

Still current, but amended. Parts of this document are changed or extended by RFC 8918. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6232
Published
May 2011
Authors
F. Wei; Y. Qin; Z. Li; T. Li; J. Dong
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
6
Also known as
—
Updates:
RFC 5301, RFC 5304, RFC 5310
Updated by:
RFC 8918

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6232-purge-originator-identification-tlv-for-is-is