In Situ OAM Profiles
draft-mizrahi-ippm-ioam-profile-01

Document Type Active Internet-Draft (individual)
Last updated 2019-09-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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)
Network Working Group                                         T. Mizrahi
Internet-Draft                          Huawei Network.IO Innovation Lab
Intended status: Informational                              F. Brockners
Expires: March 14, 2020                                      S. Bhandari
                                                          R. Sivakolundu
                                                            C. Pignataro
                                                                   Cisco
                                                                 A. Kfir
                                                                B. Gafni
                                             Mellanox Technologies, Inc.
                                                              M. Spiegel
                                                       Barefoot Networks
                                                                 T. Zhou
                                                                  Huawei
                                                                J. Lemon
                                                                Broadcom
                                                      September 11, 2019

                          In Situ OAM Profiles
                   draft-mizrahi-ippm-ioam-profile-01

Abstract

   In Situ Operations, Administration and Maintenance (IOAM) is used for
   monitoring network performance and for detecting traffic bottlenecks
   and anomalies.  This is achieved by incorporating IOAM data into in-
   flight data packets.  This document introduces the concept of use
   case-driven IOAM profiles.  An IOAM profile defines a use case or a
   set of use cases for IOAM, and an associated set of rules that
   restrict the scope and features of the IOAM specification, thereby
   limiting it to a subset of the full functionality.  The motivation
   for defining profiles is to limit the scope of IOAM features,
   allowing simpler implementation, verification, and interoperability
   testing in the context of specific use cases that do not require the
   full functionality of IOAM.

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/.

Mizrahi, et al.          Expires March 14, 2020                 [Page 1]
Internet-Draft                IOAM Profiles               September 2019

   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 14, 2020.

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
   (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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Specifying an IOAM Profile  . . . . . . . . . . . . . . . . .   3
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  IOAM Options  . . . . . . . . . . . . . . . . . . . . . .   4
     2.4.  IOAM Option Header Field Values . . . . . . . . . . . . .   4
     2.5.  Opaque State Snapshot . . . . . . . . . . . . . . . . . .   4
     2.6.  Timestamp Format  . . . . . . . . . . . . . . . . . . . .   4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  An IOAM Profile Example  . . . . . . . . . . . . . .   5
     A.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   5
     A.2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   6
     A.3.  IOAM Options  . . . . . . . . . . . . . . . . . . . . . .   6
     A.4.  IOAM Option Header Field Values . . . . . . . . . . . . .   6
     A.5.  Opaque State Snapshot . . . . . . . . . . . . . . . . . .   6
     A.6.  Profile Coexistence . . . . . . . . . . . . . . . . . . .   6
Show full document text