idnits 2.17.1 draft-li-reg-purge-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC3563, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3563, updated by this document, for RFC5378 checks: 2002-10-24) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 13, 2010) is 5005 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IS-IS Working Group T. Li 3 Internet-Draft Cisco Systems, Inc. 4 Updates: 3563 (if approved) August 13, 2010 5 Intended status: Informational 6 Expires: February 14, 2011 8 IS-IS Registry Extension for Purges 9 draft-li-reg-purge-00 11 Abstract 13 IANA maintains the IS-IS TLV Codepoint Registry. This registry 14 documents which TLVs can appear in different types of IS-IS PDUs, but 15 does not document which TLVs can be found in zero Remaining Lifetime 16 LSP (a.k.a., purges). This document extends the existing registry to 17 record the set of TLVs that are permissible in purges. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on February 14, 2011. 36 Copyright Notice 38 Copyright (c) 2010 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 56 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 3 57 5. Informative References . . . . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 1. Introduction 62 The IS-IS [ISO 10589] routing protocol maintains a link state 63 database of the topology of its routing domain by flooding a set of 64 Link State Protocol Data Units (LSPs). When the protocol no longer 65 needs the information stored in an LSP, it uses the purge mechanism 66 to cause the Intermediate Systems (ISes) in its domain to discard the 67 information contained in the LSP. The process for generating purges 68 can be found in Section 7.3.16.4 of [ISO 10589]. This process 69 retains only the LSP header, discarding any TLVs that had been 70 carried within the LSP. 72 Subsequent enhancements to IS-IS, such as [RFC5304], amend the 73 process of generating a purge and allow the inclusion of certain TLVs 74 in purges. 76 This document extends the current IS-IS TLV Codepoint Registry, 77 defined in [RFC3563], to record the set of TLVs that can be found in 78 purges. This will serve as an aid to subsequent documents, which can 79 then refer to the registry as the definitive list of the TLVs allowed 80 in purges. This will also act as an aid to implementors, providing 81 them with an easily accessible compendium of allowable TLVs. 83 2. IANA Considerations 85 This document requests that IANA modify the IS-IS 'TLV Codepoints 86 Registry' by adding a column in the registry for 'Purge'. A 'y' in 87 this column indicates that the TLV for this row can be found in a 88 purge. A 'n' in this column indicates that the TLV for this row 89 cannot be found in a purge. 91 The 'Purge' column should initially contain a 'y' for TLV type 10 92 (Authentication). All other entries in this column should have an 93 'n'. 95 3. Security Considerations 97 This document introduces no new security issues. 99 4. Acknowledgments 101 The author would like to thank Les Ginsberg for provoking this 102 effort. 104 5. Informative References 106 [ISO 10589] 107 ISO, "Intermediate system to Intermediate system routeing 108 information exchange protocol for use in conjunction with 109 the Protocol for providing the Connectionless-mode Network 110 Service (ISO 8473)", ISO/IEC 10589:2002. 112 [RFC3563] Zinin, A., "Cooperative Agreement Between the ISOC/IETF 113 and ISO/IEC Joint Technical Committee 1/Sub Committee 6 114 (JTC1/SC6) on IS-IS Routing Protocol Development", 115 RFC 3563, July 2003. 117 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 118 Authentication", RFC 5304, October 2008. 120 Author's Address 122 Tony Li 123 Cisco Systems, Inc. 124 170 W. Tasman Dr. 125 San Jose, CA 95134 126 USA 128 Email: tony.li@tony.li