idnits 2.17.1 draft-ietf-isis-wg-tlv-codepoints-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 3) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (July 2001) is 8293 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'Cal90a' is defined on line 112, but no explicit reference was found in the text == Unused Reference: 'Cal90b' is defined on line 116, but no explicit reference was found in the text == Unused Reference: 'ISO90' is defined on line 121, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'Cal90a' -- Possible downref: Non-RFC (?) normative reference: ref. 'Cal90b' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO90' Summary: 5 errors (**), 0 flaws (~~), 7 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force T.Przygienda 4 INTERNET DRAFT 5 Redback 7 July 2001 8 Reserved TLV Codepoints in ISIS 9 11 Status of This Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. Internet-Drafts are 15 working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months 22 and may be updated, replaced, or obsoleted by other documents at 23 any time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Copyright Notice Copyright (C) The Internet Society (2000). All 33 Rights Reserved. 35 Abstract 37 This draft describes implementation codepoints within 38 IS-IS [ISO90 , Cal90a , Cal90b ] used today by several ISPs for 39 routing within their clouds. IS-IS is an interior gateway routing 40 protocol developed originally by OSI and used with IP extensions as 41 IGP. This draft summarizes all TLV codepoints that are being used by 43 the protocol and its pending extensions. 45 Przygienda Expires Jan 2002 47 Internet Draft TLV Codepoints 48 July 2001 50 1. TLV Codepoints reserved 51 ___________________________________________________________ 52 Name Value IIH LSP SNP Status 54 ___________________________________________________________ 56 Area Addresses 1 y y n RFC 57 IIS Neighbors 2 n y n RFC 58 ES Neighbors 3 n y n RFC 59 Part. DIS 4 n y n RFC 60 Prefix Neighbors 5 n y n RFC 61 IIS Neighbors 6 y n n RFC 62 Padding 8 y n n RFC 63 LSP Entries 9 n n y RFC 64 Authentication 10 y y y IETF-draft 65 Opt. Checksum 12 y n y IETF-draft 66 LSPBufferSize 14 y? y n SIF-draft 67 TE IIS Neigh. 22 n y n IETF-draft 68 MT-ISN 222 n y n IETF-draft 69 IP Int. Reach 128 n y n RFC 70 Prot. Supported 129 y y n RFC 71 M-Topologies 229 y y n IETF-draft 72 IP Ext. Address 130 n y n RFC 73 IDRPI 131 n y y RFC 74 IP Intf. Address 132 y y n RFC 75 IPv6 Intf. Addr. 232 y y n IETF-draft 76 illegal 133 n n n ? 77 Router ID 134 n y n IETF-draft 78 TE IP. Reach 135 n y n IETF-draft 79 MT IP. Reach 235 n y n IETF-draft 80 IPv6 IP. Reach 236 n y n IETF-draft 81 Dynamic Name 137 n y n RFC 82 3-Way hellos 240 y n n RFC 84 2. Assignment Procedures 86 This document is provided to avoid possible future conflicts in 87 assignment of TLV numbers. It does not constitute or represent any 88 standard or authority assigning TLV numbers. TLV assignment happens 90 on a shared, informational basis between the ISO, SIF and the IETF 91 working groups. The core ISIS protocol is being specified in the 92 ISO standards body, IP extensions to it however are products of the 93 ISIS working group in IETF. Since ISO does not provide a numbering 94 authority and IANA is only responsible for IP related coding points, 96 Przygienda Expires Jan 2002 98 Internet Draft TLV Codepoints 99 July 2001 101 no plausible central authority to assign TLV numbers exists as of 102 today. 104 3. Acknowledgments 106 4. Security Consideration 108 ISIS security applies to the work presented. No specific security 109 issues are being introduced. 110 References 112 [Cal90a] R. Callon. OSI ISIS Intradomain Routing Protocol. 113 INTERNET-RFC, Internet Engineering Task Force, February 114 1990. 116 [Cal90b] R. Callon. Use of OSI ISIS for Routing in TCP/IP and Dual 118 Environments. INTERNET-RFC, Internet Engineering Task 119 Force, December 1990. 121 [ISO90] ISO. Information Technology - Telecommunications and 122 Information Exchange between Systems - Intermediate System 124 to Intermediate System Routing Exchange Protocol for 125 Use in Conjunction with the Protocol for Providing the 126 Connectionless-Mode Network Service. ISO, 1990. 128 5. Authors' Addresses 130 Tony Przygienda 131 Redback Networks 132 350 Holger Way 133 San Jose, CA, 95134-1362 134 prz@redback.com 136 6. Full Copyright Statement 138 Copyright (C) The Internet Society (1997). All Rights Reserved. 140 This document and translations of it may be copied and furnished to 141 others, and derivative works that comment on or otherwise explain it 143 or assist in its implementation may be prepared, copied, published 144 and distributed, in whole or in part, without restriction of any 145 kind, provided that the above copyright notice and this paragraph 146 are included on all such copies and derivative works. However, 147 Przygienda Expires Jan 2002 149 Internet Draft TLV Codepoints 150 July 2001 152 this document itself may not be modified in any way, such as by 153 removing the copyright notice or references to the Internet Society 154 or other Internet organizations, except as needed for the purpose 155 of developing Internet standards in which case the procedures 156 for copyrights defined in the Internet Standards process must be 157 followed, or as required to translate it into languages other than 158 English. 160 The limited permissions granted above are perpetual and will not be 161 revoked by the Internet Society or its successors or assigns. 163 This document and the information contained herein is provided on an 165 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 166 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 167 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 168 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 169 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 170 Przygienda Expires Jan 2002