Data Fields for In-situ OAM
draft-ietf-ippm-ioam-data-10

Document Type Active Internet-Draft (ippm WG)
Last updated 2020-07-29 (latest revision 2020-07-13)
Replaces draft-ippm-ioam-data, draft-brockners-inband-oam-data
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Al Morton
Shepherd write-up Show (last changed 2020-05-30)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Duke
Send notices to Al Morton <acm@research.att.com>
ippm                                                   F. Brockners, Ed.
Internet-Draft                                          S. Bhandari, Ed.
Intended status: Standards Track                                   Cisco
Expires: January 14, 2021                                T. Mizrahi, Ed.
                                                                  Huawei
                                                           July 13, 2020

                      Data Fields for In-situ OAM
                      draft-ietf-ippm-ioam-data-10

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
   discusses the data fields and associated data types for in-situ OAM.
   In-situ OAM data fields can be encapsulated into a variety of
   protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension
   header), or IPv4.  In-situ OAM can be used to complement OAM
   mechanisms based on e.g.  ICMP or other types of probe packets.

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 January 14, 2021.

Copyright Notice

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

Brockners, et al.       Expires January 14, 2021                [Page 1]
Internet-Draft           In-situ OAM Data Fields               July 2020

   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.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Scope, Applicability, and Assumptions . . . . . . . . . . . .   5
   5.  IOAM Data-Fields, Types, Nodes  . . . . . . . . . . . . . . .   6
     5.1.  IOAM Data-Fields and Option-Types . . . . . . . . . . . .   6
     5.2.  IOAM-Domains and types of IOAM Nodes  . . . . . . . . . .   7
     5.3.  IOAM-Namespaces . . . . . . . . . . . . . . . . . . . . .   8
     5.4.  IOAM Trace Option-Types . . . . . . . . . . . . . . . . .  10
       5.4.1.  Pre-allocated and Incremental Trace Option-Types  . .  13
       5.4.2.  IOAM node data fields and associated formats  . . . .  17
         5.4.2.1.  Hop_Lim and node_id short format  . . . . . . . .  17
         5.4.2.2.  ingress_if_id and egress_if_id  . . . . . . . . .  18
         5.4.2.3.  timestamp seconds . . . . . . . . . . . . . . . .  18
         5.4.2.4.  timestamp subseconds  . . . . . . . . . . . . . .  18
         5.4.2.5.  transit delay . . . . . . . . . . . . . . . . . .  19
         5.4.2.6.  namespace specific data . . . . . . . . . . . . .  19
         5.4.2.7.  queue depth . . . . . . . . . . . . . . . . . . .  19
         5.4.2.8.  Checksum Complement . . . . . . . . . . . . . . .  20
         5.4.2.9.  Hop_Lim and node_id wide  . . . . . . . . . . . .  20
         5.4.2.10. ingress_if_id and egress_if_id wide . . . . . . .  21
         5.4.2.11. namespace specific data wide  . . . . . . . . . .  21
         5.4.2.12. buffer occupancy  . . . . . . . . . . . . . . . .  22
         5.4.2.13. Opaque State Snapshot . . . . . . . . . . . . . .  22
       5.4.3.  Examples of IOAM node data  . . . . . . . . . . . . .  23
     5.5.  IOAM Proof of Transit Option-Type . . . . . . . . . . . .  25
       5.5.1.  IOAM Proof of Transit Type 0  . . . . . . . . . . . .  27
     5.6.  IOAM Edge-to-Edge Option-Type . . . . . . . . . . . . . .  28
   6.  Timestamp Formats . . . . . . . . . . . . . . . . . . . . . .  30
     6.1.  PTP Truncated Timestamp Format  . . . . . . . . . . . . .  30
     6.2.  NTP 64-bit Timestamp Format . . . . . . . . . . . . . . .  31
     6.3.  POSIX-based Timestamp Format  . . . . . . . . . . . . . .  33
Show full document text