<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-isis-purge-tlv" target="https://datatracker.ietf.org/doc/html/draft-ietf-isis-purge-tlv-05">
   <front>
      <title>Purge Originator Identification TLV for IS-IS</title>
      <author initials="Y." surname="Qin" fullname="Yue Qin">
         <organization>China Mobile</organization>
      </author>
      <author initials="Z." surname="Li" fullname="Zhenqiang Li">
         <organization>China Mobile</organization>
      </author>
      <author initials="F." surname="Wei" fullname="Fang Wei">
         <organization>China Mobile</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="T." surname="Li" fullname="Tony Li">
         <organization>Cisco Systems</organization>
      </author>
      <date month="October" day="25" year="2010" />
      <abstract>
	 <t>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]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-isis-purge-tlv-05" />
   
</reference>
