At present an IS-IS purges do 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, the purge-tlv document defines a TLV to
be added to purges to record the system ID of the IS generating it.
Since normal LSP flooding does not change LSP contents, this
TLV should propagate with the purge.
This reg-purge draft documents which TLVs can appear in different types
of IS-IS PDUs, but does not document which TLVs can be found in zero
Remaining Lifetime LSP (a.k.a., purges). This document extends the
existing registry to record the set of TLVs that are permissible in
Working Group Summary
The idea of the purge TLV was first discussed in Dublin at IETF 72. The
initial view of the Working Group was that the extension was not
necessary. After a couple years of discussion and work on the idea,
consensus has been achieved.
There is one known implementation.
David Ward is the Document Shepherd for this document.
Stewart Bryant is the Responsible Area Director.
RFC Editor Note
In the Abstract
Since normal LSP flooding does not change LSP contents, this TLV
should propagate with the purge.
Since normal Link State Packet (LSP) flooding does not change LSP
contents, this TLV should propagate with the purge.
This document updates RFC5301, RFC5304 and RFC5310.
In Introduction (para 3)
receive a corrupted LSP.
receive a corrupted Link State Packet (LSP).