Data Fields for In-situ OAM
draft-ietf-ippm-ioam-data-06
ippm F. Brockners
Internet-Draft S. Bhandari
Intended status: Standards Track C. Pignataro
Expires: January 5, 2020 Cisco
H. Gredler
RtBrick Inc.
J. Leddy
S. Youell
JPMC
T. Mizrahi
Huawei Network.IO Innovation Lab
D. Mozes
P. Lapukhov
Facebook
R. Chang
Barefoot Networks
D. Bernier
Bell Canada
J. Lemon
Broadcom
July 04, 2019
Data Fields for In-situ OAM
draft-ietf-ippm-ioam-data-06
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 embedded into a variety of transports
such as NSH, Segment Routing, Geneve, native 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/.
Brockners, et al. Expires January 5, 2020 [Page 1]
Internet-Draft In-situ OAM Data Fields July 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 January 5, 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. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Scope, Applicability, and Assumptions . . . . . . . . . . . . 4
4. IOAM Data Types and Formats . . . . . . . . . . . . . . . . . 5
4.1. IOAM Namespaces . . . . . . . . . . . . . . . . . . . . . 7
4.2. IOAM Tracing Options . . . . . . . . . . . . . . . . . . 9
4.2.1. Pre-allocated and Incremental Trace Options . . . . . 11
4.2.2. IOAM node data fields and associated formats . . . . 15
4.2.3. Examples of IOAM node data . . . . . . . . . . . . . 21
4.3. IOAM Proof of Transit Option . . . . . . . . . . . . . . 22
4.3.1. IOAM Proof of Transit Type 0 . . . . . . . . . . . . 24
4.4. IOAM Edge-to-Edge Option . . . . . . . . . . . . . . . . 25
5. Timestamp Formats . . . . . . . . . . . . . . . . . . . . . . 27
5.1. PTP Truncated Timestamp Format . . . . . . . . . . . . . 27
5.2. NTP 64-bit Timestamp Format . . . . . . . . . . . . . . . 28
5.3. POSIX-based Timestamp Format . . . . . . . . . . . . . . 29
6. IOAM Data Export . . . . . . . . . . . . . . . . . . . . . . 31
Show full document text