Deployment Considerations for In-situ OAM with IPv6 Options
draft-ioametal-ippm-6man-ioam-ipv6-deployment-01

Document Type Active Internet-Draft (individual)
Last updated 2019-03-28
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)
ippm,6man                                                    S. Bhandari
Internet-Draft                                              F. Brockners
Intended status: Standards Track                                   Cisco
Expires: September 29, 2019                                   T. Mizrahi
                                        Huawei Network.IO Innovation Lab
                                                                 A. Kfir
                                                                B. Gafni
                                             Mellanox Technologies, Inc.
                                                              M. Spiegel
                                                       Barefoot Networks
                                                             S. Krishnan
                                                                  Kaloom
                                                                M. Smith
                                                          March 28, 2019

      Deployment Considerations for In-situ OAM with IPv6 Options
            draft-ioametal-ippm-6man-ioam-ipv6-deployment-01

Abstract

   In-situ Operations, Administration, and Maintenance (IOAM) records
   operational and telemetry information in the packet while the packet
   traverses a path between two points in the network.  This document
   outlines how IOAM can be enabled in an IPv6 network.

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 September 29, 2019.

Copyright Notice

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

Bhandari, et al.       Expires September 29, 2019               [Page 1]
Internet-Draft       In-situ OAM IPv6 encapsulation           March 2019

   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.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Considerations for IOAM deployment in IPv6 networks . . . . .   3
   4.  IOAM domains bounded by hosts . . . . . . . . . . . . . . . .   4
   5.  IOAM domains bounded by network devices . . . . . . . . . . .   4
     5.1.  Deployment options  . . . . . . . . . . . . . . . . . . .   5
       5.1.1.  IPv6-in-IPv6 encapsulation  . . . . . . . . . . . . .   5
       5.1.2.  IP-in-IPv6 encapsulation with ULA . . . . . . . . . .   5
       5.1.3.  x-in-IPv6 Encapsulation that is used Independently  .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   In-situ Operations, Administration, and Maintenance (IOAM) records
   operational and telemetry information in the packet while the packet
   traverses a path between two points in the network.
   [I-D.ioametal-ippm-6man-ioam-ipv6-options] defines how IOAM data
   fields are encapsulated in the IPv6 [RFC8200].  This document
   discusses deployment options for networks which leverage IOAM data
   fields encapsulated in the IPv6 protocol.

   Deployment considerations differ, whether the IOAM domain starts and
   ends on hosts or whether the IOAM encapsulating and decapsulating
   nodes are network devices that forward traffic, such as routers.
Show full document text