idnits 2.17.1 draft-raza-mpls-oam-ipv6-rao-02.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 RFC4379, but the abstract doesn't seem to directly say this. It does mention RFC4379 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4379, updated by this document, for RFC5378 checks: 2002-03-27) -- 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 (September 30, 2014) is 3496 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) ** Obsolete normative reference: RFC 4379 (Obsoleted by RFC 8029) == Outdated reference: A later version (-17) exists of draft-ietf-mpls-ldp-ipv6-13 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group K. Raza 3 Internet-Draft N. Akiya 4 Updates: 4379 (if approved) C. Pignataro 5 Intended status: Standards Track Cisco Systems, Inc. 6 Expires: April 3, 2015 September 30, 2014 8 IPv6 Router Alert Option for MPLS OAM 9 draft-raza-mpls-oam-ipv6-rao-02 11 Abstract 13 RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the 14 Router Alert option must be set in the IP header of the MPLS Echo 15 Request messages, and may conditionally be set in the IP header of 16 the MPLS Echo Reply messages. While a generic "Router shall examine 17 packet" Option Value is used for the IPv4 Router Alert Option (RAO), 18 there is no generic Router Alert Option Value defined for IPv6 that 19 can be used. This document allocates a new generic IPv6 Router Alert 20 Option Value that can be used by MPLS OAM tools, including the MPLS 21 Echo Request and MPLS Echo Reply messages for MPLS IPv6. 23 The initial motivation to request an IPv6 Router Alert Option (RAO) 24 code point for MPLS OAM comes from MPLS LSP Ping/Traceroute. 25 However, this codepoint is applicable to all MPLS OAM and not limited 26 to MPLS LSP Ping/Traceroute. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on April 3, 2015. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Specification of Requirements . . . . . . . . . . . . . . . . 3 64 3. IPv6 Router Alert Option (RAO) Value for MPLS OAM . . . . . . 3 65 4. Updates to RFC 4379 . . . . . . . . . . . . . . . . . . . . . 3 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 68 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 69 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 71 8.2. Informative References . . . . . . . . . . . . . . . . . 4 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 74 1. Introduction 76 A commonly deployed MPLS OAM tool is LSP Ping/Traceroute [RFC4379] 77 which is used to diagnose MPLS networks. The LSP Ping/Traceroute 78 specification [RFC4379] requires the use of Router Alert option in 79 the IP header. For example, the section 4.3 of [RFC4379] states that 80 IP Router Alert option MUST be set in the IP header of an MPLS Echo 81 Request message. Similarly, the section 4.5 states that IP Router 82 Alert option MUST be set in the IP header of an MPLS Echo Reply 83 message if the Reply Mode in the echo request is set to "Reply via an 84 IPv4/IPv6 UDP packet with Router Alert". 86 [RFC2113] defines a generic Option Value 0x0 for IPv4 Router Alert 87 Option (RAO) that is used by LSP Ping and LSP Traceroute for MPLS 88 IPv4. However, currently there is no generic IPV6 Router Alert code 89 point defined that can be used by LSP Ping and LSP Traceroute for 90 MPLS IPv6. Specifically, [RFC2711] defined the router alert for a 91 general IPv6 purpose but required the Value field in the router alert 92 option to indicate a specific reason for using the router alert 93 option. Because there is no defined value for MPLS LSP Ping/ 94 Traceroute use or for general use, it is not possible for MPLS OAM 95 tools to use the IPv6 Router Alert mechanism. 97 As vendors are starting to implement MPLS on IPv6 control plane 98 (e.g., [I-D.ietf-mpls-ldp-ipv6]), there is a need to define and 99 allocate such a code point for IPv6 in order to comply with 100 [RFC4379]. This document defines a new IPv6 Router Alert Option 101 Value that can be used by MPLS OAM tools, including the MPLS Echo 102 Request and MPLS Echo Reply messages for MPLS IPv6. 104 2. Specification of Requirements 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in [RFC2119]. 110 3. IPv6 Router Alert Option (RAO) Value for MPLS OAM 112 This document defines a new option value (TBD1) for the IPv6 Router 113 Alert Option (RAO) to alert transit routers to examine the packet 114 more closely for MPLS OAM purposes. This code point is used by any 115 MPLS OAM application that requires their packets to be examined by a 116 transit router. 118 In the scope of this document, this code point will be used by the 119 MPLS Echo Request and MPLS Echo Reply for its IPv6 messages as 120 required by [RFC4379]. 122 4. Updates to RFC 4379 124 [RFC4379] specifies the use of the Router Alert Option in the IP 125 header. Sections 4.3 and 4.5 of [RFC4379] are updated as follows: 126 for every time in which the "Router Alert IP option" is used, the 127 following text is appended: 129 In case of an IPv4 header, the generic IPv4 Router Alert Option 130 value 0x0 [RFC2113] SHOULD be used. In case of an IPv6 header, 131 the IPv6 Router Alert Option value TBD1 allocated through this 132 document for MPLS OAM MUST be used. 134 5. IANA Considerations 136 This document defines a new code point (value TBD1) for IPv6 Router 137 Alert option to alert transit routers to examine the packet the MPLS 138 OAM purpose. IANA is requested to assign a new code point under its 139 "IPv6 Router Alert Option Values" registry defined by [RFC5350] and 140 maintained in [IANA-IPv6-RAO]. The new code point is as follows: 142 value Description Reference 143 ----- ------------------------------- --------------- 144 TBD1 MPLS OAM [document.this] 146 6. Security Considerations 148 This document introduces no new security concerns in addition to what 149 have already been captured in [RFC4379] and [RFC6398]. 151 7. Acknowledgments 153 The authors would like to thank George Swallow, Ole Troan, Bob 154 Hinden, Faisal Iqbal, Mathew Janelle, and Gregory Mirsky for their 155 useful input. 157 8. References 159 8.1. Normative References 161 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 162 Requirement Levels", BCP 14, RFC 2119, March 1997. 164 [RFC2711] Partridge, C. and A. Jackson, "IPv6 Router Alert Option", 165 RFC 2711, October 1999. 167 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 168 Label Switched (MPLS) Data Plane Failures", RFC 4379, 169 February 2006. 171 [RFC5350] Manner, J. and A. McDonald, "IANA Considerations for the 172 IPv4 and IPv6 Router Alert Options", RFC 5350, September 173 2008. 175 [RFC6398] Le Faucheur, F., "IP Router Alert Considerations and 176 Usage", BCP 168, RFC 6398, October 2011. 178 8.2. Informative References 180 [I-D.ietf-mpls-ldp-ipv6] 181 Asati, R., Manral, V., Papneja, R., and C. Pignataro, 182 "Updates to LDP for IPv6", draft-ietf-mpls-ldp-ipv6-13 183 (work in progress), July 2014. 185 [IANA-IPv6-RAO] 186 IANA, "IPv6 Router Alert Option Values", 187 . 190 [RFC2113] Katz, D., "IP Router Alert Option", RFC 2113, February 191 1997. 193 Authors' Addresses 195 Kamran Raza 196 Cisco Systems, Inc. 197 2000 Innovation Drive 198 Kanata, ON K2K-3E8 199 CA 201 Email: skraza@cisco.com 203 Nobo Akiya 204 Cisco Systems, Inc. 205 2000 Innovation Drive 206 Kanata, ON K2K-3E8 207 CA 209 Email: nobo@cisco.com 211 Carlos Pignataro 212 Cisco Systems, Inc. 213 7200-12 Kit Creek Road 214 Research Triangle Park, NC 27709 215 USA 217 Email: cpignata@cisco.com