idnits 2.17.1 draft-raza-mpls-oam-ipv6-rao-01.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 15, 2014) is 3508 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 (==), 1 comment (--). 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 Intended status: Standards Track C. Pignataro 5 Expires: March 19, 2015 Cisco Systems, Inc. 6 September 15, 2014 8 IPv6 Router Alert Option for MPLS OAM 9 draft-raza-mpls-oam-ipv6-rao-01 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 March 19, 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 67 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 70 7.2. Informative References . . . . . . . . . . . . . . . . . 4 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 73 1. Introduction 75 A commonly deployed MPLS OAM tool is LSP Ping/Traceroute [RFC4379] 76 which is used to diagnose MPLS networks. The LSP Ping/Traceroute 77 specification [RFC4379] requires the use of Router Alert option in 78 the IP header. For example, the section 4.3 of [RFC4379] states that 79 IP Router Alert option MUST be set in the IP header of an MPLS Echo 80 Request message. Similarly, the section 4.5 states that IP Router 81 Alert option MUST be set in the IP header of an MPLS Echo Reply 82 message if the Reply Mode in the echo request is set to "Reply via an 83 IPv4/IPv6 UDP packet with Router Alert". 85 [RFC2113] defines a generic Option Value 0x0 for IPv4 Router Alert 86 Option (RAO) that is used by LSP Ping and LSP Traceroute for MPLS 87 IPv4. However, currently there is no generic IPV6 Router Alert code 88 point defined that can be used by LSP Ping and LSP Traceroute for 89 MPLS IPv6. Specifically, [RFC2711] defined the router alert for a 90 general IPv6 purpose but required the Value field in the router alert 91 option to indicate a specific reason for using the router alert 92 option. Because there is no defined value for MPLS LSP Ping/ 93 Traceroute use or for general use, it is not possible for MPLS OAM 94 tools to use the IPv6 Router Alert mechanism. 96 As vendors are starting to implement MPLS on IPv6 control plane 97 (e.g., [I-D.ietf-mpls-ldp-ipv6]), there is a need to define and 98 allocate such a code point for IPv6 in order to comply with 99 [RFC4379]. This document defines a new IPv6 Router Alert Option 100 Value that can be used by MPLS OAM tools, including the MPLS Echo 101 Request and MPLS Echo Reply messages for MPLS IPv6. 103 2. Specification of Requirements 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in [RFC2119]. 109 3. IPv6 Router Alert Option (RAO) Value for MPLS OAM 111 This document defines a new option value (TBD1) for the IPv6 Router 112 Alert Option (RAO) to alert transit routers to examine the packet 113 more closely for MPLS OAM purposes. This code point is used by any 114 MPLS OAM application that requires their packets to be examined by a 115 transit router. 117 In the scope of this document, this code point will be used by the 118 MPLS Echo Request and MPLS Echo Reply for its IPv6 messages as 119 required by [RFC4379]. 121 4. IANA Considerations 123 This document defines a new code point (value TBD1) for IPv6 Router 124 Alert option to alert transit routers to examine the packet the MPLS 125 OAM purpose. IANA is requested to assign a new code point under its 126 "IPv6 Router Alert Option Values" registry defined by [RFC5350] and 127 maintained in [IANA-IPv6-RAO]. The new code point is as follows: 129 value Description Reference 130 ----- ------------------------------- --------------- 131 TBD1 MPLS OAM [document.this] 133 5. Security Considerations 135 This document introduces no new security concerns in addition to what 136 have already been captured in [RFC4379] and [RFC6398]. 138 6. Acknowledgments 140 The authors would like to thank George Swallow, Ole Troan, Bob 141 Hinden, Faisal Iqbal, and Mathew Janelle for their useful input. 143 7. References 145 7.1. Normative References 147 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 148 Requirement Levels", BCP 14, RFC 2119, March 1997. 150 [RFC2711] Partridge, C. and A. Jackson, "IPv6 Router Alert Option", 151 RFC 2711, October 1999. 153 [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol 154 Label Switched (MPLS) Data Plane Failures", RFC 4379, 155 February 2006. 157 [RFC5350] Manner, J. and A. McDonald, "IANA Considerations for the 158 IPv4 and IPv6 Router Alert Options", RFC 5350, September 159 2008. 161 [RFC6398] Le Faucheur, F., "IP Router Alert Considerations and 162 Usage", BCP 168, RFC 6398, October 2011. 164 7.2. Informative References 166 [I-D.ietf-mpls-ldp-ipv6] 167 Asati, R., Manral, V., Papneja, R., and C. Pignataro, 168 "Updates to LDP for IPv6", draft-ietf-mpls-ldp-ipv6-13 169 (work in progress), July 2014. 171 [IANA-IPv6-RAO] 172 IANA, "IPv6 Router Alert Option Values", 173 . 176 [RFC2113] Katz, D., "IP Router Alert Option", RFC 2113, February 177 1997. 179 Authors' Addresses 180 Kamran Raza 181 Cisco Systems, Inc. 182 2000 Innovation Drive 183 Kanata, ON K2K-3E8 184 CA 186 Email: skraza@cisco.com 188 Nobo Akiya 189 Cisco Systems, Inc. 190 2000 Innovation Drive 191 Kanata, ON K2K-3E8 192 CA 194 Email: nobo@cisco.com 196 Carlos Pignataro 197 Cisco Systems, Inc. 198 7200-12 Kit Creek Road 199 Research Triangle Park, NC 27709 200 USA 202 Email: cpignata@cisco.com