1、Purge Originator Identification TLV for IS-IS,Fang WeiYue QinZhenqiang Li China MobileTony Li Cisco Systems Jie Dong Huawei Technologies,Content,MotivationsCases to Generate Purge PacketProposed Purge Originator Identification TLVSecurity ConsiderationsNext Step,Motivations,IS-IS protocol floods pur
2、ges throughout an network, regardless of which IS initiated the purge. At present an IS-IS purge does not contain any information identifying the IS that generates the purge. This makes it difficult to locate the source IS.We suggest a TLV be added to purges to record the system ID of the IS generat
3、ing the purge.,Cases to Generate Purge Packet,Legitimate casesAn IS purges its own LSPA LSP owned by another IS ages outA new DIS is elected.Improper casesAn implementation misunderstanding ISO 10589 or predating TC1 generates a purge when it receives a corrupted LSP.An implementation with bugs trie
4、s to purge one of its LSPs and makes a truly egregious mistake.An implementation fails to retain the LSP header after purging while flooding is still in progress.,The Purge Originator Identification TLV,This document defines a TLV to be included in purges. This TLV carries the system ID of the IS ge
5、nerating the purge.This makes it much easier for the network administrator to locate the origin of the purge and thus the cause of the purge.It is also helpful to developers in lab situations.,CODE - XX (to be assigned) LENGTH - total length of the value field.VALUE - System ID of the Intermediate S
6、ystem that initiated the purge.,Security Considerations,If the proposed TLV is used in conjunction with IS-IS authentication mechanisms, the purge LSP is constructed by removing the original contents of the LSP, leaving only the LSP header, adding the Purge Originator Identification TLV and then adding the IS-IS authentication TLV.This document amends the behavior specified in RFC5304 and RFC5310.,Next Step,Any comments are welcome.Move it forward to be a working group draft?,
