Skip to main content

Segment Routing Header encapsulation for In-situ OAM Data
draft-ali-spring-ioam-srv6-06

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Zafar Ali , Rakesh Gandhi , Clarence Filsfils , Frank Brockners , Nagendra Kumar Nainar , Carlos Pignataro , Cheng Li , Mach Chen , Gaurav Dawra
Last updated 2023-01-11 (Latest revision 2022-07-10)
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

OAM and PM information from the SR endpoints can be piggybacked in the data packet. The OAM and PM information piggybacking in the data packets is also known as In-situ OAM (IOAM). IOAM records operational and telemetry information in the data packet while the packet traverses a path between two points in the network. This document defines how IOAM data fields are transported as part of the Segment Routing with IPv6 data plane (SRv6) header.

Authors

Zafar Ali
Rakesh Gandhi
Clarence Filsfils
Frank Brockners
Nagendra Kumar Nainar
Carlos Pignataro
Cheng Li
Mach Chen
Gaurav Dawra

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)