draft-pignataro-opsawg-oam-whaaat-question-mark-02.txt		draft-pignataro-opsawg-oam-whaaat-question-mark-03.txt
	OPS Area Working Group C. Pignataro		OPS Area Working Group C. Pignataro
	Internet-Draft NC State University		Internet-Draft NC State University
	Updates: 6291 (if approved) A. Farrel		Updates: 6291 (if approved) A. Farrel
	Intended status: Best Current Practice Old Dog Consulting		Intended status: Best Current Practice Old Dog Consulting
	Expires: 23 July 2024 20 January 2024		Expires: 26 September 2024 25 March 2024
	Guidelines for Charactering "OAM"		Guidelines for Charactering "OAM"
	draft-pignataro-opsawg-oam-whaaat-question-mark-02		draft-pignataro-opsawg-oam-whaaat-question-mark-03
	Abstract		Abstract
	As the IETF continues to produce and standardize different		As the IETF continues to produce and standardize different
	Operations, Administration, and Maintenance (OAM) protocols and		Operations, Administration, and Maintenance (OAM) protocols and
	technologies, various qualifiers and modifiers are prepended to the		technologies, various qualifiers and modifiers are prepended to the
	OAM acronym. While, at first glance, the most used appear to be well		OAM acronym. While, at first glance, the most used appear to be well
	understood, the same qualifier may be interpreted differently in		understood, the same qualifier may be interpreted differently in
	different contexts. A case in point is the qualifiers "in-band" and		different contexts. A case in point is the qualifiers "in-band" and
	"out-of-band" which have their origins in the radio lexicon and which		"out-of-band" which have their origins in the radio lexicon and which
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 23 July 2024.		This Internet-Draft will expire on 26 September 2024.
	Copyright Notice		Copyright Notice
	Copyright (c) 2024 IETF Trust and the persons identified as the		Copyright (c) 2024 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 26 ¶
	described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Revised BSD License.		provided without warranty as described in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. In-Band and Out-of-Band OAM . . . . . . . . . . . . . . . . . 3		2. In-Band and Out-of-Band OAM . . . . . . . . . . . . . . . . . 3
	2.1. Historical Uses . . . . . . . . . . . . . . . . . . . . . 5		2.1. Historical Uses . . . . . . . . . . . . . . . . . . . . . 5
	3. Active, Passive, Hybrid, and Compound OAM . . . . . . . . . . 5		3. Active, Passive, Hybrid, and Compound OAM . . . . . . . . . . 5
	4. Extended OAM Acronyms . . . . . . . . . . . . . . . . . . . . 6		4. Extended OAM Acronyms . . . . . . . . . . . . . . . . . . . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 6		5. Node Processing OAM Packets . . . . . . . . . . . . . . . . . 6
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
	7.1. Normative References . . . . . . . . . . . . . . . . . . 7		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7.2. Informative References . . . . . . . . . . . . . . . . . 7		8.1. Normative References . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		8.2. Informative References . . . . . . . . . . . . . . . . . 8
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	It is not uncommon for historical and popular terms to have		It is not uncommon for historical and popular terms to have
	fundamental nuances in how they are interpreted or understood. This		fundamental nuances in how they are interpreted or understood. This
	was, for example, the case with the acronym for Operations,		was, for example, the case with the acronym for Operations,
	Administration, and Maintenance, "OAM", and [RFC6291] provided		Administration, and Maintenance, "OAM", and [RFC6291] provided
	guidelines for its use as well as definitions of its constituent		guidelines for its use as well as definitions of its constituent
	parts.		parts.
	skipping to change at page 5, line 37 ¶		skipping to change at page 5, line 42 ¶
	[RFC7799] provides clear definitions for active and passive		[RFC7799] provides clear definitions for active and passive
	performance assessment such that the construction of metrics and		performance assessment such that the construction of metrics and
	methods can be described as either "Active" or "Passive". Even		methods can be described as either "Active" or "Passive". Even
	though [RFC7799] does not include the specific terms "Active",		though [RFC7799] does not include the specific terms "Active",
	"Passive", or "Hybrid" as modifiers of "OAM", the following terms are		"Passive", or "Hybrid" as modifiers of "OAM", the following terms are
	used in many RFCs and are provided here for use in all future IETF		used in many RFCs and are provided here for use in all future IETF
	documents that refer to OAM.		documents that refer to OAM.
	Active OAM:		Active OAM:
	Depends on dedicated instrumentation OAM packets.		Depends on dedicated instrumented OAM packets.
	Passive OAM:		Passive OAM:
	Depends solely on the observation of one or more existing data		Depends solely on the observation of one or more existing data
	packet streams, and does not use dedicated OAM packets.		packet streams, and does not use dedicated OAM packets.
	Hybrid OAM:		Hybrid OAM:
	Uses instrumentation or modification of data packets themselves.		Uses instrumentation or modification of data packets themselves.
	[RFC9341] and [RFC9197] are examples labeled "Hybrid OAM" under		[RFC9341] and [RFC9197] are examples labeled "Hybrid OAM" under
	this definition.		this definition.
	skipping to change at page 6, line 35 ¶		skipping to change at page 6, line 41 ¶
	This document recommends avoiding the creation and use of extended		This document recommends avoiding the creation and use of extended
	acronyms for the qualifiers of "OAM". For example, the first "O" in		acronyms for the qualifiers of "OAM". For example, the first "O" in
	"OOAM" could mean out-of-band, overlay, or something else.		"OOAM" could mean out-of-band, overlay, or something else.
	[RFC9197] currently uses the acronym "IOAM" for In Situ Operations,		[RFC9197] currently uses the acronym "IOAM" for In Situ Operations,
	Administration, and Maintenance. While this document does not		Administration, and Maintenance. While this document does not
	obsolete that acronym, it still recommends that "In situ OAM" is used		obsolete that acronym, it still recommends that "In situ OAM" is used
	instead to avoid potential ambiguity.		instead to avoid potential ambiguity.
	5. Security Considerations		5. Node Processing OAM Packets
			There are multiple processing capabilities that nodes processing OAM
			packets can utilize. Some of those capabilities are explained in
			[RFC9197] for In situ OAM, and are further generalized in this
			document.
			Depending on the Type of OAM processing, nodes are chategorized as
			follows. Please note that this characterization exists within the
			context of a particular OAM protocol instance, and a given node can
			support multiple types:
			* Hybrid OAM instruments or modifies data packet themselves.
			Consequently:
			Encapsulating Node:
			Adds OAM information to data packets.
			Transit Node:
			Processes OAM information in data packets.
			Transparent Node:
			Does not process OAM information in data packets.
			Decapsulating Node:
			Removes OAM information to data packets.
			* Active OAM uses dedicated OAM packets, outside data packets.
			Consequently:
			Source Node:
			Creates and injects OAM packets into a flow.
			Sink Node:
			Processes and removes OAM packets from a flow.
			A node could be source and sink of Active OAM packets
			simultaneously.
			6. Security Considerations
	Security is improved when the terms used and their definitions are		Security is improved when the terms used and their definitions are
	unambiguous.		unambiguous.
	6. Acknowledgements		7. Acknowledgements
	The creation of this document was triggered when observing one of		The creation of this document was triggered when observing one of
	many on-mailing-list discussions of what these terms mean, and how to		many on-mailing-list discussions of what these terms mean, and how to
	abbreviate them. Participants on that mailing thread include,		abbreviate them. Participants on that mailing thread include,
	alphabetically: Adrian Farrel, Alexander Vainshtein, Florian Kauer,		alphabetically: Adrian Farrel, Alexander Vainshtein, Florian Kauer,
	Frank Brockners, Greg Mirsky, Italo Busi, Loa Andersson, Med		Frank Brockners, Greg Mirsky, Italo Busi, Loa Andersson, Med
	Boucadair, Michael Richardson, Quan Xiong, Stewart Bryant, Tom Petch,		Boucadair, Michael Richardson, Quan Xiong, Stewart Bryant, Tom Petch,
	Eduard Vasilenko, and Xiao Min.		Eduard Vasilenko, and Xiao Min.
	The authors wish to thank Hesham Elbakoury, Michael Richardson,		The authors wish to thank Hesham Elbakoury, Michael Richardson,
	Stewart Bryant, Greg Mirsky, Med Boucadair, and Loa Andersson for		Stewart Bryant, Greg Mirsky, Med Boucadair, Loa Andersson, Thomas
	their review and very useful comments.		Graf, and Alex Huang Feng for their thorough review and very useful
			comments that improved this document.
	7. References
	7.1. Normative References		8. References
			8.1. Normative References
	[RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu,		[RFC6291] Andersson, L., van Helvoort, H., Bonica, R., Romascanu,
	D., and S. Mansfield, "Guidelines for the Use of the "OAM"		D., and S. Mansfield, "Guidelines for the Use of the "OAM"
	Acronym in the IETF", BCP 161, RFC 6291,		Acronym in the IETF", BCP 161, RFC 6291,
	DOI 10.17487/RFC6291, June 2011,		DOI 10.17487/RFC6291, June 2011,
	<https://www.rfc-editor.org/info/rfc6291>.		<https://www.rfc-editor.org/info/rfc6291>.
	[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with		[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
	Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,		Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
	May 2016, <https://www.rfc-editor.org/info/rfc7799>.		May 2016, <https://www.rfc-editor.org/info/rfc7799>.
	7.2. Informative References		8.2. Informative References
	[I-D.ietf-detnet-oam-framework]		[I-D.ietf-detnet-oam-framework]
	Mirsky, G., Theoleyre, F., Papadopoulos, G. Z., Bernardos,		Mirsky, G., Theoleyre, F., Papadopoulos, G. Z., Bernardos,
	C. J., Varga, B., and J. Farkas, "Framework of Operations,		C. J., Varga, B., and J. Farkas, "Framework of Operations,
	Administration and Maintenance (OAM) for Deterministic		Administration and Maintenance (OAM) for Deterministic
	Networking (DetNet)", Work in Progress, Internet-Draft,		Networking (DetNet)", Work in Progress, Internet-Draft,
	draft-ietf-detnet-oam-framework-11, 8 January 2024,		draft-ietf-detnet-oam-framework-11, 8 January 2024,
	<https://datatracker.ietf.org/doc/html/draft-ietf-detnet-		<https://datatracker.ietf.org/doc/html/draft-ietf-detnet-
	oam-framework-11>.		oam-framework-11>.
	[I-D.ietf-raw-architecture]		[I-D.ietf-raw-architecture]
	Thubert, P., "Reliable and Available Wireless		Thubert, P., "Reliable and Available Wireless
	Architecture", Work in Progress, Internet-Draft, draft-		Architecture", Work in Progress, Internet-Draft, draft-
	ietf-raw-architecture-16, 20 October 2023,		ietf-raw-architecture-17, 4 March 2024,
	<https://datatracker.ietf.org/doc/html/draft-ietf-raw-		<https://datatracker.ietf.org/doc/html/draft-ietf-raw-
	architecture-16>.		architecture-17>.
	[I-D.kumar-ippm-ifa]		[I-D.kumar-ippm-ifa]
	Kumar, J., Anubolu, S., Lemon, J., Manur, R., Holbrook,		Kumar, J., Anubolu, S., Lemon, J., Manur, R., Holbrook,
	H., Ghanwani, A., Cai, D., Ou, H., Li, Y., and X. Wang,		H., Ghanwani, A., Cai, D., Ou, H., Li, Y., and X. Wang,
	"Inband Flow Analyzer", Work in Progress, Internet-Draft,		"Inband Flow Analyzer", Work in Progress, Internet-Draft,
	draft-kumar-ippm-ifa-07, 7 September 2023,		draft-kumar-ippm-ifa-07, 7 September 2023,
	<https://datatracker.ietf.org/doc/html/draft-kumar-ippm-		<https://datatracker.ietf.org/doc/html/draft-kumar-ippm-
	ifa-07>.		ifa-07>.
	[I-D.song-opsawg-ifit-framework]		[I-D.song-opsawg-ifit-framework]
End of changes. 12 change blocks.
	20 lines changed or deleted		60 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/