idnits 2.17.1 draft-shen-icmp-routing-inst-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 333. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 310. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 317. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 323. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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 (November 2006) is 6343 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: '8' is defined on line 272, but no explicit reference was found in the text == Outdated reference: A later version (-16) exists of draft-bonica-internet-icmp-12 == Outdated reference: A later version (-12) exists of draft-ietf-isis-wg-multi-topology-11 == Outdated reference: A later version (-09) exists of draft-ietf-ospf-mt-06 -- Possible downref: Non-RFC (?) normative reference: ref. '7' == Outdated reference: A later version (-13) exists of draft-ietf-idr-as4bytes-12 ** Obsolete normative reference: RFC 2338 (ref. '9') (Obsoleted by RFC 3768) -- Possible downref: Normative reference to a draft: ref. '11' Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet N. Shen 2 Internet-Draft E. Chen 3 Expires: May 2007 Cisco Systems 4 November 2006 6 ICMP Extensions for Routing Instances 7 draft-shen-icmp-routing-inst-00.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 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 This Internet-Draft will expire on March, 2007. 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This document specifies the extensions to ICMP that allows 41 routing instance information to be included inside the ICMP 42 packet. These extensions can be used to facilitate the 43 troubleshooting network problems within a routing domain or 44 across multiple routing domains. 46 1. Conventions Used In This Document 48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 50 document are to be interpreted as described in RFC2119 [10]. 52 2. Introduction 54 Internet Control Message Protocol (ICMP) [1] has been widely 55 used for troubleshooting purposes. This document utilizes the 56 ICMP multi-part message extension [2] to define a number of 57 important routing instance objects in ICMP messages. 59 When using traceroute diagnostic tool through multiple routing 60 domains, it is useful to have ICMP Time exceeded messages to 61 include the AS number [3] the router or virtual router 62 belongs to. 64 Within the same routing domain, if a network operates with multiple 65 topologies for IGP [4, 5], it is crucial in network troubleshooting 66 to know the multi-topology identifier the traceroute packet of 67 inbound interface is associated with. This information can be 68 included in the ICMP messages. 70 With the traditional Interior Gateway Protocol (IGP) diagnostics, 71 it is useful for the ICMP Time exceeded messages to report 72 OSPF area [6] the router belongs to or to report the IS-IS [7] 73 level the router or link belong to when the IGP being IS-IS. 74 The OSPF area and IS-IS level can also belong to a specific 75 routing instance the inbound interface is associated with for 76 the traceroute packets. 78 A router may support VRRP [9] over a LAN interface and it is 79 informative to know if the interface has redundancy protection and 80 it's configured virtual router identifier (VRID). 82 3. ICMP Multiple-part Message Extension 84 This document uses the ICMP extension [2]. The ICMP message 85 MUST include the IP header and leading payload octets of the 86 original datagram. An ICMP Extension Structure Header MUST 87 follow the octets from the original datagram and come before 88 any ICMP Extension Objects. 90 4. Routing Objects for ICMP 92 This section defines a number of ICMP routing instance objects that 93 can be optionally appended to the ICMP Time Exceeded and Destination 94 Unreachable messages. 96 4.1 Autonomous System Number Object 98 The router MAY include the AS number [3] when sending out the 99 ICMP messages. 101 Class-Num = 5 102 C-type = 1 103 Length = 8 105 Object payload: 107 0 1 2 3 108 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | AS Number | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 Figure 1: AS Number Object 115 4.2 Multi-Topology ID Object 117 The router MAY include the MT ID [4, 5] when sending out the 118 ICMP messages. 120 Class-Num = 5 121 C-type = 2 122 Length = 8 124 Object payload: 126 0 1 2 3 127 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | Reserved | MT ID | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 Figure 2: MT ID Object 134 The MT ID is a 12 bit number for IS-IS MT, and it is a 7 bit number 135 for OSPF. 137 4.3 OSPF Area ID Object 139 The router MAY include the Area ID for OSPF [6] when sending 140 out the ICMP messages. 142 Class-Num = 5 143 C-type = 3 144 Length = 8 146 Object payload: 148 0 1 2 3 149 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | Area ID | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 Figure 3: OSPF Area ID Object 156 4.4. IS-IS Level Object 158 The router MAY include the IS-IS level [7] when sending out the 159 ICMP messages. 161 Class-Num = 5 162 C-type = 4 163 Length = 8 165 Object payload: 167 0 1 2 3 168 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 | Instance ID | Reserved | Level | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 Figure 4: IS-IS Level Object 175 The Instance ID is a 16 bit number [11], default value is zero. 176 The Level is a 8 bit number, currently defined as following: 178 1 - IS-IS level-1 179 2 - IS-IS level-2 180 3 - IS-IS level-1-2 182 4.5 IGRP and EIGRP AS ID Object 184 The router MAY include the IGRP AS ID or EIGRP AS Number when sending 185 out the ICMP messages. 187 Class-Num = 5 188 C-type = 5 189 Length = 8 191 Object payload: 193 0 1 2 3 194 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | IGRP or EIGRP AS ID | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 Figure 5: IGRP or EIGRP AS ID Object 200 The IGRP/EIGRP AS ID is a 32 bit number. 202 4.6 Virtual Router Identifier Object 204 The router MAY include the virtual router identifier of VRRP [9] 205 when sending out the ICMP messages. 207 Class-Num = 5 208 C-type = 6 209 Length = 8 211 Object payload: 213 0 1 2 3 214 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | Reserved | VR ID | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 Figure 6: VRID Object 221 Virtual Router ID is an 8 bit number. 223 5. Security Considerations 225 These ICMP extensions can provide operators with additional routing 226 information during network troubleshooting. It may be desirable to 227 provide this information only to network operators. This may be 228 desirable in particular for the IGP routing related objects. The 229 implementation should allow the configuration of the policy control 230 over the operation of these objects. For example, an access list 231 can be attached to check the IP destination of the ICMP packets 232 with this extension belong to internal network management subnet. 234 6. IANA Considerations 236 IANA should should reserve from the ICMP Extension Object registry: 237 5 for the routing instance objects. IANA should also reserve 238 from the objects c-types as described in section 4 of this 239 document. 241 7. Acknowledgement 243 TBA. 245 8. References 247 8.1. Normative References 249 [1] Postel, J., "Internet Control Message Protocol", STD 5, 250 RFC 792, September 1981. 252 [2] Bonica, R., "Modifying ICMP to Support Multi-part Messages", 253 draft-bonica-internet-icmp-12 (work in progress), October 2006. 255 [3] Y. Rekhter., "A Border Gateway Protocol 4 (BGP-4)", 256 RFC 4271, January 2006. 258 [4] Przygienda, T., "M-ISIS: Multi Topology (MT) Routing in IS-IS", 259 draft-ietf-isis-wg-multi-topology-11 (work in progress), 260 April 2006. 262 [5] Psenak, P., "Multi-Topology (MT) Routing in OSPF", 263 draft-ietf-ospf-mt-06 (work in progress), February 2006. 265 [6] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 267 [7] ISO, "Intermediate system to Intermediate system routing 268 information exchange protocol for use in conjunction with the 269 Protocol for providing the Connectionless-mode Network Service 270 (ISO 8473)," ISO/IEC 10589:1992. 272 [8] Vohra, Q., "BGP Support for Four-octet AS Number Space", 273 draft-ietf-idr-as4bytes-12 (work in progress), 274 May 2006. 276 [9] Hinden, R., "Virtual Router Redundancy Protocol (VRRP)" 277 RFC 2338, April 2004. 279 [10] Bradner, S., "Key words for use in RFCs to Indicate 280 Requirement Levels", BCP 14, RFC 2119, March 1997. 282 [11] Previdi, S., "IS-IS Multi-instance Multi-topology", 283 draft-previdi-isis-mi-mt-01.txt (work in progress), June 2006. 285 Author's Addresses 287 Naiming Shen 288 Cisco Systems 289 225 West Tasman Drive 290 San Jose, CA 95134 291 USA 292 Email: naiming@cisco.com 294 Enke Chen 295 Cisco Systems 296 170 West Tasman Drive 297 San Jose, CA 95134 298 USA 299 Email: enkechen@cisco.com 301 Intellectual Property Statement 303 The IETF takes no position regarding the validity or scope of any 304 Intellectual Property Rights or other rights that might be claimed to 305 pertain to the implementation or use of the technology described in 306 this document or the extent to which any license under such rights 307 might or might not be available; nor does it represent that it has 308 made any independent effort to identify any such rights. Information 309 on the procedures with respect to rights in RFC documents can be 310 found in BCP 78 and BCP 79. 312 Copies of IPR disclosures made to the IETF Secretariat and any 313 assurances of licenses to be made available, or the result of an 314 attempt made to obtain a general license or permission for the use of 315 such proprietary rights by implementers or users of this 316 specification can be obtained from the IETF on-line IPR repository at 317 http://www.ietf.org/ipr. 319 The IETF invites any interested party to bring to its attention any 320 copyrights, patents or patent applications, or other proprietary 321 rights that may cover technology that may be required to implement 322 this standard. Please address the information to the IETF at 323 ietf-ipr@ietf.org. 325 Disclaimer of Validity 327 This document and the information contained herein are provided on an 328 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 329 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 330 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 331 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 332 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 333 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 335 Copyright Statement 337 Copyright (C) The Internet Society (2006). This document is subject 338 to the rights, licenses and restrictions contained in BCP 78, and 339 except as set forth therein, the authors retain all their rights. 341 Acknowledgment 343 Funding for the RFC Editor function is currently provided by the 344 Internet Society.