OAM Capabilities for IPv6
draft-bonica-6man-oam-03

Document Type Active Internet-Draft (individual)
Last updated 2019-03-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6man Working Group                                             R. Bonica
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                                   N. So
Expires: September 24, 2019                                        F. Xu
                                                            Reliance Jio
                                                                 G. Chen
                                                                   Baidu
                                                                  Y. Zhu
                                                                 G. Yang
                                                           China Telecom
                                                                 Y. Zhou
                                                               ByteDance
                                                          March 23, 2019

                       OAM Capabilities for IPv6
                        draft-bonica-6man-oam-03

Abstract

   This document defines new IPv6 Operations and Management (OAM)
   capabilities.  In order to support these new capabilities, this
   document defines an IPv6 OAM Option and an ICMPv6 OAM message.

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 https://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 September 24, 2019.

Copyright Notice

   Copyright (c) 2019 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

Bonica, et al.         Expires September 24, 2019               [Page 1]
Internet-Draft                  IPv6 OAM                      March 2019

   (https://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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  The OAM Option  . . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Processing  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  The ICMPv6 OAM Message  . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Problem Statement

   This document defines new IPv6 [RFC8200] Operations and Management
   (OAM) capabilities.  In order to support these new capabilities, this
   document defines an IPv6 OAM Option and an ICMPv6 [RFC4443] OAM
   message.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  The OAM Option

   IPv6 source nodes use the OAM option to invoke one or more OAM
   actions on downstream devices.  The OAM option can be included in any
   of the following:

   o  A Hop-by-hop header.

   o  A Destination Options header that precedes a Routing header.

   o  A Destination Options header that precedes an upper-layer header.

Bonica, et al.         Expires September 24, 2019               [Page 2]
Internet-Draft                  IPv6 OAM                      March 2019

   If a Hop-by-hop header includes an OAM option, OAM actions MAY be
   invoked on every node along the path to the destination, including
   the destination.  If a Destination Options header that precedes a
   Routing header includes an OAM option, OAM actions are invoked by the
   first node that appears in the IPv6 Destination Address field plus
Show full document text