RFC 9197

Data Fields for In Situ Operations, Administration, and Maintenance (IOAM), May 2022

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML icon for inline errata
Status:
PROPOSED STANDARD
Authors:
F. Brockners, Ed.
S. Bhandari, Ed.
T. Mizrahi, Ed.
Stream:
IETF
Source:
ippm (tsv)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC9197

Discuss this RFC: Send questions or comments to ippm@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9197


Abstract

In situ Operations, Administration, and Maintenance (IOAM) collects 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 IOAM. IOAM-Data-Fields can be encapsulated into a variety of protocols, such as Network Service Header (NSH), Segment Routing, Generic Network Virtualization Encapsulation (Geneve), or IPv6. IOAM can be used to complement OAM mechanisms based on, e.g., ICMP or other types of probe packets.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search