draft-raza-mpls-oam-ipv6-rao-01.txt   draft-raza-mpls-oam-ipv6-rao-02.txt 
MPLS Working Group K. Raza MPLS Working Group K. Raza
Internet-Draft N. Akiya Internet-Draft N. Akiya
Intended status: Standards Track C. Pignataro Updates: 4379 (if approved) C. Pignataro
Expires: March 19, 2015 Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
September 15, 2014 Expires: April 3, 2015 September 30, 2014
IPv6 Router Alert Option for MPLS OAM IPv6 Router Alert Option for MPLS OAM
draft-raza-mpls-oam-ipv6-rao-01 draft-raza-mpls-oam-ipv6-rao-02
Abstract Abstract
RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the RFC4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the
Router Alert option must be set in the IP header of the MPLS Echo Router Alert option must be set in the IP header of the MPLS Echo
Request messages, and may conditionally be set in the IP header of Request messages, and may conditionally be set in the IP header of
the MPLS Echo Reply messages. While a generic "Router shall examine the MPLS Echo Reply messages. While a generic "Router shall examine
packet" Option Value is used for the IPv4 Router Alert Option (RAO), packet" Option Value is used for the IPv4 Router Alert Option (RAO),
there is no generic Router Alert Option Value defined for IPv6 that there is no generic Router Alert Option Value defined for IPv6 that
can be used. This document allocates a new generic IPv6 Router Alert can be used. This document allocates a new generic IPv6 Router Alert
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 19, 2015. This Internet-Draft will expire on April 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Specification of Requirements . . . . . . . . . . . . . . . . 3 2. Specification of Requirements . . . . . . . . . . . . . . . . 3
3. IPv6 Router Alert Option (RAO) Value for MPLS OAM . . . . . . 3 3. IPv6 Router Alert Option (RAO) Value for MPLS OAM . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. Updates to RFC 4379 . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 4 8.1. Normative References . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 8.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
A commonly deployed MPLS OAM tool is LSP Ping/Traceroute [RFC4379] A commonly deployed MPLS OAM tool is LSP Ping/Traceroute [RFC4379]
which is used to diagnose MPLS networks. The LSP Ping/Traceroute which is used to diagnose MPLS networks. The LSP Ping/Traceroute
specification [RFC4379] requires the use of Router Alert option in specification [RFC4379] requires the use of Router Alert option in
the IP header. For example, the section 4.3 of [RFC4379] states that the IP header. For example, the section 4.3 of [RFC4379] states that
IP Router Alert option MUST be set in the IP header of an MPLS Echo IP Router Alert option MUST be set in the IP header of an MPLS Echo
Request message. Similarly, the section 4.5 states that IP Router Request message. Similarly, the section 4.5 states that IP Router
Alert option MUST be set in the IP header of an MPLS Echo Reply Alert option MUST be set in the IP header of an MPLS Echo Reply
skipping to change at page 3, line 32 skipping to change at page 3, line 33
This document defines a new option value (TBD1) for the IPv6 Router This document defines a new option value (TBD1) for the IPv6 Router
Alert Option (RAO) to alert transit routers to examine the packet Alert Option (RAO) to alert transit routers to examine the packet
more closely for MPLS OAM purposes. This code point is used by any more closely for MPLS OAM purposes. This code point is used by any
MPLS OAM application that requires their packets to be examined by a MPLS OAM application that requires their packets to be examined by a
transit router. transit router.
In the scope of this document, this code point will be used by the In the scope of this document, this code point will be used by the
MPLS Echo Request and MPLS Echo Reply for its IPv6 messages as MPLS Echo Request and MPLS Echo Reply for its IPv6 messages as
required by [RFC4379]. required by [RFC4379].
4. IANA Considerations 4. Updates to RFC 4379
[RFC4379] specifies the use of the Router Alert Option in the IP
header. Sections 4.3 and 4.5 of [RFC4379] are updated as follows:
for every time in which the "Router Alert IP option" is used, the
following text is appended:
In case of an IPv4 header, the generic IPv4 Router Alert Option
value 0x0 [RFC2113] SHOULD be used. In case of an IPv6 header,
the IPv6 Router Alert Option value TBD1 allocated through this
document for MPLS OAM MUST be used.
5. IANA Considerations
This document defines a new code point (value TBD1) for IPv6 Router This document defines a new code point (value TBD1) for IPv6 Router
Alert option to alert transit routers to examine the packet the MPLS Alert option to alert transit routers to examine the packet the MPLS
OAM purpose. IANA is requested to assign a new code point under its OAM purpose. IANA is requested to assign a new code point under its
"IPv6 Router Alert Option Values" registry defined by [RFC5350] and "IPv6 Router Alert Option Values" registry defined by [RFC5350] and
maintained in [IANA-IPv6-RAO]. The new code point is as follows: maintained in [IANA-IPv6-RAO]. The new code point is as follows:
value Description Reference value Description Reference
----- ------------------------------- --------------- ----- ------------------------------- ---------------
TBD1 MPLS OAM [document.this] TBD1 MPLS OAM [document.this]
5. Security Considerations 6. Security Considerations
This document introduces no new security concerns in addition to what This document introduces no new security concerns in addition to what
have already been captured in [RFC4379] and [RFC6398]. have already been captured in [RFC4379] and [RFC6398].
6. Acknowledgments 7. Acknowledgments
The authors would like to thank George Swallow, Ole Troan, Bob The authors would like to thank George Swallow, Ole Troan, Bob
Hinden, Faisal Iqbal, and Mathew Janelle for their useful input. Hinden, Faisal Iqbal, Mathew Janelle, and Gregory Mirsky for their
useful input.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2711] Partridge, C. and A. Jackson, "IPv6 Router Alert Option", [RFC2711] Partridge, C. and A. Jackson, "IPv6 Router Alert Option",
RFC 2711, October 1999. RFC 2711, October 1999.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. February 2006.
[RFC5350] Manner, J. and A. McDonald, "IANA Considerations for the [RFC5350] Manner, J. and A. McDonald, "IANA Considerations for the
IPv4 and IPv6 Router Alert Options", RFC 5350, September IPv4 and IPv6 Router Alert Options", RFC 5350, September
2008. 2008.
[RFC6398] Le Faucheur, F., "IP Router Alert Considerations and [RFC6398] Le Faucheur, F., "IP Router Alert Considerations and
Usage", BCP 168, RFC 6398, October 2011. Usage", BCP 168, RFC 6398, October 2011.
7.2. Informative References 8.2. Informative References
[I-D.ietf-mpls-ldp-ipv6] [I-D.ietf-mpls-ldp-ipv6]
Asati, R., Manral, V., Papneja, R., and C. Pignataro, Asati, R., Manral, V., Papneja, R., and C. Pignataro,
"Updates to LDP for IPv6", draft-ietf-mpls-ldp-ipv6-13 "Updates to LDP for IPv6", draft-ietf-mpls-ldp-ipv6-13
(work in progress), July 2014. (work in progress), July 2014.
[IANA-IPv6-RAO] [IANA-IPv6-RAO]
IANA, "IPv6 Router Alert Option Values", IANA, "IPv6 Router Alert Option Values",
<http://www.iana.org/assignments/ipv6-routeralert-values/ <http://www.iana.org/assignments/ipv6-routeralert-values/
ipv6-routeralert-values.xhtml>. ipv6-routeralert-values.xhtml>.
 End of changes. 11 change blocks. 
19 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/