IPv6 Router Alert Option for MPLS OAM
draft-raza-mpls-oam-ipv6-rao-01

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2014-09-17
Replaced by draft-ietf-mpls-oam-ipv6-rao, rfc7506
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state Candidate for WG Adoption
Document shepherd Loa Andersson
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                               K. Raza
Internet-Draft                                                  N. Akiya
Intended status: Standards Track                            C. Pignataro
Expires: March 19, 2015                              Cisco Systems, Inc.
                                                      September 15, 2014

                 IPv6 Router Alert Option for MPLS OAM
                    draft-raza-mpls-oam-ipv6-rao-01

Abstract

   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
   Request messages, and may conditionally be set in the IP header of
   the MPLS Echo Reply messages.  While a generic "Router shall examine
   packet" Option Value is used for the IPv4 Router Alert Option (RAO),
   there is no generic Router Alert Option Value defined for IPv6 that
   can be used.  This document allocates a new generic IPv6 Router Alert
   Option Value that can be used by MPLS OAM tools, including the MPLS
   Echo Request and MPLS Echo Reply messages for MPLS IPv6.

   The initial motivation to request an IPv6 Router Alert Option (RAO)
   code point for MPLS OAM comes from MPLS LSP Ping/Traceroute.
   However, this codepoint is applicable to all MPLS OAM and not limited
   to MPLS LSP Ping/Traceroute.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 19, 2015.

Raza, et al.             Expires March 19, 2015                 [Page 1]
Internet-Draft         MPLS OAM IPv6 Router Alert         September 2014

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   3
   3.  IPv6 Router Alert Option (RAO) Value for MPLS OAM . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   A commonly deployed MPLS OAM tool is LSP Ping/Traceroute [RFC4379]
   which is used to diagnose MPLS networks.  The LSP Ping/Traceroute
   specification [RFC4379] requires the use of Router Alert option in
   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
   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
   message if the Reply Mode in the echo request is set to "Reply via an
   IPv4/IPv6 UDP packet with Router Alert".

   [RFC2113] defines a generic Option Value 0x0 for IPv4 Router Alert
   Option (RAO) that is used by LSP Ping and LSP Traceroute for MPLS
   IPv4.  However, currently there is no generic IPV6 Router Alert code
   point defined that can be used by LSP Ping and LSP Traceroute for
   MPLS IPv6.  Specifically, [RFC2711] defined the router alert for a
   general IPv6 purpose but required the Value field in the router alert
   option to indicate a specific reason for using the router alert
   option.  Because there is no defined value for MPLS LSP Ping/

Raza, et al.             Expires March 19, 2015                 [Page 2]
Internet-Draft         MPLS OAM IPv6 Router Alert         September 2014
Show full document text