rfc9197v3.txt		rfc9197.txt
	Internet Engineering Task Force (IETF) F. Brockners, Ed.		Internet Engineering Task Force (IETF) F. Brockners, Ed.
	Request for Comments: 9197 Cisco		Request for Comments: 9197 Cisco
	Category: Standards Track S. Bhandari, Ed.		Category: Standards Track S. Bhandari, Ed.
	ISSN: 2070-1721 Thoughtspot		ISSN: 2070-1721 Thoughtspot
	T. Mizrahi, Ed.		T. Mizrahi, Ed.
	Huawei		Huawei
	April 2022		May 2022
	Data Fields for In Situ Operations, Administration, and Maintenance		Data Fields for In Situ Operations, Administration, and Maintenance
	(IOAM)		(IOAM)
	Abstract		Abstract
	In situ Operations, Administration, and Maintenance (IOAM) collects		In situ Operations, Administration, and Maintenance (IOAM) collects
	operational and telemetry information in the packet while the packet		operational and telemetry information in the packet while the packet
	traverses a path between two points in the network. This document		traverses a path between two points in the network. This document
	discusses the data fields and associated data types for IOAM. IOAM-		discusses the data fields and associated data types for IOAM. IOAM-
	skipping to change at line 803 ¶		skipping to change at line 803 ¶
	depth". With this approach, nodes can supply the information in		depth". With this approach, nodes can supply the information in
	their original format and are not required to perform unit or format		their original format and are not required to perform unit or format
	conversions. Systems that further process IOAM information, e.g.,		conversions. Systems that further process IOAM information, e.g.,
	like a network management system, are assumed to also handle unit		like a network management system, are assumed to also handle unit
	conversions as part of their IOAM-Data-Fields processing. The		conversions as part of their IOAM-Data-Fields processing. The
	combination of a particular data field and the Namespace-ID provides		combination of a particular data field and the Namespace-ID provides
	for the context to interpret the provided data appropriately.		for the context to interpret the provided data appropriately.
	4.4.2.1. Hop_Lim and node_id Short		4.4.2.1. Hop_Lim and node_id Short
	The "Hop_Lim and node_id short format" field is a 4-octet field that		The "Hop_Lim and node_id short" field is a 4-octet field that is
	is defined as follows:		defined as follows:
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Hop_Lim | node_id |		| Hop_Lim | node_id |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Hop_Lim:		Hop_Lim:
	1-octet unsigned integer. It is set to the Hop Limit value in the		1-octet unsigned integer. It is set to the Hop Limit value in the
	packet at egress from the node that records this data. Hop Limit		packet at egress from the node that records this data. Hop Limit
	information is used to identify the location of the node in the		information is used to identify the location of the node in the
End of changes. 2 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/