< draft-mizrahi-ippm-ioam-profile-01.txt		draft-mizrahi-ippm-ioam-profile-02.txt >
	Network Working Group T. Mizrahi		Network Working Group T. Mizrahi
	Internet-Draft Huawei Network.IO Innovation Lab		Internet-Draft Huawei Smart Platforms iLab
	Intended status: Informational F. Brockners		Intended status: Informational F. Brockners
	Expires: March 14, 2020 S. Bhandari		Expires: August 9, 2020 S. Bhandari
	R. Sivakolundu		R. Sivakolundu
	C. Pignataro		C. Pignataro
	Cisco		Cisco
	A. Kfir		A. Kfir
	B. Gafni		B. Gafni
	Mellanox Technologies, Inc.		Mellanox Technologies, Inc.
	M. Spiegel		M. Spiegel
	Barefoot Networks		Barefoot Networks
	T. Zhou		T. Zhou
	Huawei		Huawei
	J. Lemon		J. Lemon
	Broadcom		Broadcom
	September 11, 2019		February 6, 2020
	In Situ OAM Profiles		In Situ OAM Profiles
	draft-mizrahi-ippm-ioam-profile-01		draft-mizrahi-ippm-ioam-profile-02
	Abstract		Abstract
	In Situ Operations, Administration and Maintenance (IOAM) is used for		In Situ Operations, Administration and Maintenance (IOAM) is used for
	monitoring network performance and for detecting traffic bottlenecks		monitoring network performance and for detecting traffic bottlenecks
	and anomalies. This is achieved by incorporating IOAM data into in-		and anomalies. This is achieved by incorporating IOAM data into in-
	flight data packets. This document introduces the concept of use		flight data packets. This document introduces the concept of use
	case-driven IOAM profiles. An IOAM profile defines a use case or a		case-driven IOAM profiles. An IOAM profile defines a use case or a
	set of use cases for IOAM, and an associated set of rules that		set of use cases for IOAM, and an associated set of rules that
	restrict the scope and features of the IOAM specification, thereby		restrict the scope and features of the IOAM specification, thereby
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	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 March 14, 2020.		This Internet-Draft will expire on August 9, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2020 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		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 36 ¶		skipping to change at page 2, line 36 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Specifying an IOAM Profile . . . . . . . . . . . . . . . . . 3		2. Specifying an IOAM Profile . . . . . . . . . . . . . . . . . 3
	2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 4		2.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 4
	2.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 4		2.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 4
	2.4. IOAM Option Header Field Values . . . . . . . . . . . . . 4		2.4. IOAM Option Header Field Values . . . . . . . . . . . . . 4
	2.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 4		2.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 4
	2.6. Timestamp Format . . . . . . . . . . . . . . . . . . . . 4		2.6. Timestamp Format . . . . . . . . . . . . . . . . . . . . 5
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 5		4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	5. Normative References . . . . . . . . . . . . . . . . . . . . 5		5. Normative References . . . . . . . . . . . . . . . . . . . . 5
	Appendix A. An IOAM Profile Example . . . . . . . . . . . . . . 5		Appendix A. An IOAM Profile Example . . . . . . . . . . . . . . 6
	A.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 5		A.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
	A.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 6		A.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 6
	A.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 6		A.3. IOAM Options . . . . . . . . . . . . . . . . . . . . . . 6
	A.4. IOAM Option Header Field Values . . . . . . . . . . . . . 6		A.4. IOAM Option Header Field Values . . . . . . . . . . . . . 6
	A.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 6		A.5. Opaque State Snapshot . . . . . . . . . . . . . . . . . . 6
	A.6. Profile Coexistence . . . . . . . . . . . . . . . . . . . 6		A.6. Profile Coexistence . . . . . . . . . . . . . . . . . . . 6
	A.7. Validity . . . . . . . . . . . . . . . . . . . . . . . . 6		A.7. Validity . . . . . . . . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
	1. Introduction		1. Introduction
	IOAM [I-D.ietf-ippm-ioam-data] is used for monitoring traffic in the		IOAM [I-D.ietf-ippm-ioam-data] is used for monitoring traffic in the
	network by incorporating IOAM data fields into in-flight data		network by incorporating IOAM data fields into in-flight data
	packets.		packets.
	This document introduces the concept of use case driven IOAM		This document introduces the concept of use case driven IOAM
	profiles. The motivation for defining profiles is to limit the scope		profiles. The motivation for defining profiles is to limit the scope
	skipping to change at page 3, line 43 ¶		skipping to change at page 3, line 43 ¶
	A profile defines a set of rules that limit the scope or		A profile defines a set of rules that limit the scope or
	functionality of IOAM. By default, any detail in IOAM that is not		functionality of IOAM. By default, any detail in IOAM that is not
	specifically addressed or limited by the profile is as defined in		specifically addressed or limited by the profile is as defined in
	IOAM [I-D.ietf-ippm-ioam-data]. The rest of this section presents a		IOAM [I-D.ietf-ippm-ioam-data]. The rest of this section presents a
	set of topics that may be addressed in a profile specification. A		set of topics that may be addressed in a profile specification. A
	profile may include some or all of these topics, and optionally other		profile may include some or all of these topics, and optionally other
	topics.		topics.
	A profile may in part be defined using a specific assignment to the		A profile may in part be defined using a specific assignment to the
	IOAM YANG model [I-D.zhou-ippm-ioam-yang]. It should be noted that		IOAM YANG model. The IOAM YANG model [I-D.zhou-ippm-ioam-yang]
	while the YANG model assists in the definition of a profile, it does		defines a set of IOAM-related attributes, such as which IOAM option
	not replace the profile definition. Specifically, a profile		types are enabled, and which data fields are used. For example, an
	definition includes the use case(s) for using the profile, and		IOAM profile that only uses the icremental trace option may be
	possibly some properties that cannot be defined by an assignment to		defined as such by an assignment to the respective attributes that
	the YANG model, such as the semantics of the Opaque State Snapshot		are defined in the YANG model. It should be noted that while the
	field.		YANG model assists in the definition of a profile, it does not
			replace the profile definition. Specifically, a profile definition
			includes the use case(s) for using the profile, and possibly some
			properties that cannot be defined by an assignment to the YANG model,
			such as the semantics of the Opaque State Snapshot field.
	2.2. Use Cases		2.2. Use Cases
	An IOAM profile should define the use case(s) for using the profile.		An IOAM profile should define the use case(s) for using the profile.
	The use case may describe deployment scenarios or specific		The use case may describe deployment scenarios or specific
	applications that make use of IOAM data. The use case should		applications that make use of IOAM data. The use case should
	typically define the required functionality from IOAM. For example,		typically define the required functionality from IOAM. For example,
	an IOAM profile may be defined such that it requires transit delay		an IOAM profile may be defined such that it requires transit delay
	monitoring, but does not require path tracing. These requirements		monitoring, but does not require path tracing. These requirements
	then affect which IOAM data fields are used in the profile.		then affect which IOAM data fields are used in the profile.
	skipping to change at page 5, line 31 ¶		skipping to change at page 5, line 36 ¶
	Moreover, in some cases a profile may limit the set of features of		Moreover, in some cases a profile may limit the set of features of
	IOAM in a way that reduces the set of potential threats compared to a		IOAM in a way that reduces the set of potential threats compared to a
	full implementation of IOAM. In fact, a particular IOAM profile can		full implementation of IOAM. In fact, a particular IOAM profile can
	optimize a particular security posture or requirement.		optimize a particular security posture or requirement.
	5. Normative References		5. Normative References
	[I-D.ietf-ippm-ioam-data]		[I-D.ietf-ippm-ioam-data]
	Brockners, F., Bhandari, S., Pignataro, C., Gredler, H.,		Brockners, F., Bhandari, S., Pignataro, C., Gredler, H.,
	Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov,		Leddy, J., Youell, S., Mizrahi, T., Mozes, D., Lapukhov,
	P., Chang, R., daniel.bernier@bell.ca, d., and J. Lemon,		P., remy@barefootnetworks.com, r., daniel.bernier@bell.ca,
	"Data Fields for In-situ OAM", draft-ietf-ippm-ioam-		d., and J. Lemon, "Data Fields for In-situ OAM", draft-
	data-07 (work in progress), September 2019.		ietf-ippm-ioam-data-08 (work in progress), October 2019.
	[I-D.zhou-ippm-ioam-yang]		[I-D.zhou-ippm-ioam-yang]
	Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A		Zhou, T., Guichard, J., Brockners, F., and S. Raghavan, "A
	YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam-		YANG Data Model for In-Situ OAM", draft-zhou-ippm-ioam-
	yang-04 (work in progress), June 2019.		yang-05 (work in progress), January 2020.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	Appendix A. An IOAM Profile Example		Appendix A. An IOAM Profile Example
	A.1. Overview		A.1. Overview
	skipping to change at page 7, line 8 ¶		skipping to change at page 7, line 17 ¶
	An IOAM transit/decapsulating node that receives a packet with IOAM		An IOAM transit/decapsulating node that receives a packet with IOAM
	options that do not comply to the current profile should forward/		options that do not comply to the current profile should forward/
	decapsulate the packet without IOAM processing, if it is able to do		decapsulate the packet without IOAM processing, if it is able to do
	so. If a decapsulating node is not able to decapsulate an IOAM		so. If a decapsulating node is not able to decapsulate an IOAM
	option that is not compliant to the current profile, the packet is		option that is not compliant to the current profile, the packet is
	discarded.		discarded.
	Authors' Addresses		Authors' Addresses
	Tal Mizrahi		Tal Mizrahi
	Huawei Network.IO Innovation Lab		Huawei Smart Platforms iLab
			8-2 Matam
			Haifa 3190501
	Israel		Israel
	Email: tal.mizrahi.phd@gmail.com		Email: tal.mizrahi.phd@gmail.com
	Frank Brockners		Frank Brockners
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Hansaallee 249, 3rd Floor		Hansaallee 249, 3rd Floor
	DUESSELDORF, NORDRHEIN-WESTFALEN 40549		DUESSELDORF, NORDRHEIN-WESTFALEN 40549
	Germany		Germany
	skipping to change at page 8, line 35 ¶		skipping to change at page 9, line 4 ¶
	Email: mspiegel@barefootnetworks.com		Email: mspiegel@barefootnetworks.com
	Tianran Zhou		Tianran Zhou
	Huawei		Huawei
	156 Beiqing Rd.		156 Beiqing Rd.
	Beijing 100095		Beijing 100095
	China		China
	Email: zhoutianran@huawei.com		Email: zhoutianran@huawei.com
			Jennifer Lemon
	John Lemon
	Broadcom		Broadcom
	270 Innovation Drive		270 Innovation Drive
	San Jose, CA 95134		San Jose, CA 95134
	US		US
	Email: john.lemon@broadcom.com		Email: jennifer.lemon@broadcom.com
End of changes. 15 change blocks.
	24 lines changed or deleted		29 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/