Purge Originator Identification TLV for IS-IS
RFC 6232
Document | Type |
RFC - Proposed Standard
(May 2011; No errata)
Updated by RFC 8918
|
|
---|---|---|---|
Authors | Yue Qin , Zhenqiang Li , Fang Wei , Jie Dong , Tony Li | ||
Last updated | 2018-12-20 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6232 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Stewart Bryant | ||
IESG note | David Ward (dward@juniper.net) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) F. Wei Request for Comments: 6232 Y. Qin Updates: 5301, 5304, 5310 Z. Li Category: Standards Track China Mobile ISSN: 2070-1721 T. Li Cisco Systems, Inc. J. Dong Huawei Technologies May 2011 Purge Originator Identification TLV for IS-IS Abstract 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6232. Wei, et al. Standards Track [Page 1] RFC 6232 Purge Originator Identification TLV May 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................2 2. Requirements Language ...........................................3 3. The Purge Originator Identification (POI) TLV ...................3 4. Using the Dynamic Hostname TLV in Purges ........................3 5. Security Considerations .........................................4 6. IANA Considerations .............................................4 7. Acknowledgments .................................................4 8. Normative References ............................................4 1. Introduction The IS-IS [ISO-10589] routing protocol has been widely used in large- scale IP networks because of its strong scalability and fast convergence. The IS-IS protocol floods purges throughout an area, regardless of which IS initiated the purge. If a network operator would like to investigate the cause of the purge, it is difficult to determine the origin of the purge. At present, the IS-IS protocol has no mechanism to locate the originator of a purge. To address this problem, this document defines a TLV to be added to purges to record the system ID of the IS generating the purge. Field experience has shown several circumstances where an IS can improperly generate a purge. These are all due to implementation deficiencies or implementations that predate [ISO-TC1] and generate a purge when they receive a corrupted Link State Protocol Data Unit (LSP). Wei, et al. Standards Track [Page 2] RFC 6232 Purge Originator Identification TLV May 2011 2. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. The Purge Originator Identification (POI) TLV This document defines a TLV to be included in purges. If an IS generates a purge, it SHOULD include this TLV in the purge with its own system ID. If an IS receives a purge that does not include this TLV, then it SHOULD add this TLV with both its own system ID and the system ID of the IS from which it received the purge. This allowsShow full document text