< draft-spiegel-ippm-ioam-rawexport-04.txt		draft-spiegel-ippm-ioam-rawexport-05.txt >
	ippm M. Spiegel		ippm M. Spiegel
	Internet-Draft Barefoot Networks, an Intel company		Internet-Draft Barefoot Networks, an Intel company
	Intended status: Informational F. Brockners		Intended status: Informational F. Brockners
	Expires: May 6, 2021 S. Bhandari		Expires: 13 January 2022 Cisco
			S. Bhandari
			Thoughtspot
	R. Sivakolundu		R. Sivakolundu
	Cisco		Cisco
	November 2, 2020		12 July 2021
	In-situ OAM raw data export with IPFIX		In-situ OAM raw data export with IPFIX
	draft-spiegel-ippm-ioam-rawexport-04		draft-spiegel-ippm-ioam-rawexport-05
	Abstract		Abstract
	In-situ Operations, Administration, and Maintenance (IOAM) records		In-situ Operations, Administration, and Maintenance (IOAM) records
	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 how In-situ Operations, Administration, and Maintenance		discusses how In-situ Operations, Administration, and Maintenance
	(IOAM) information can be exported in raw, i.e. uninterpreted, format		(IOAM) information can be exported in raw, i.e. uninterpreted, format
	from network devices to systems, such as monitoring or analytics		from network devices to systems, such as monitoring or analytics
	systems using IPFIX.		systems using IPFIX.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 41 ¶
	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 May 6, 2021.		This Internet-Draft will expire on 13 January 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 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/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		provided without warranty as described in the Simplified BSD License.
	described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 5		1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 4
	1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5		1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6		2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. IPFIX for IOAM raw data export . . . . . . . . . . . . . . . 6		3. IPFIX for IOAM raw data export . . . . . . . . . . . . . . . 6
	3.1. Key IPFIX information elements leveraged for IOAM raw		3.1. Key IPFIX information elements leveraged for IOAM raw data
	data export . . . . . . . . . . . . . . . . . . . . . . . 6		export . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.2. New IPFIX information elements leveraged for IOAM raw		3.2. New IPFIX information elements leveraged for IOAM raw data
	data export . . . . . . . . . . . . . . . . . . . . . . . 7		export . . . . . . . . . . . . . . . . . . . . . . . . . 7
	3.2.1. ioamReportFlags . . . . . . . . . . . . . . . . . . . 7		3.2.1. ioamReportFlags . . . . . . . . . . . . . . . . . . . 7
	3.2.2. ioamEncapsulationType . . . . . . . . . . . . . . . . 8		3.2.2. ioamEncapsulationType . . . . . . . . . . . . . . . . 8
	3.2.3. ioamPreallocatedTraceData . . . . . . . . . . . . . . 9		3.2.3. ioamPreallocatedTraceData . . . . . . . . . . . . . . 8
	3.2.4. ioamIncrementalTraceData . . . . . . . . . . . . . . 9		3.2.4. ioamIncrementalTraceData . . . . . . . . . . . . . . 9
	3.2.5. ioamE2EData . . . . . . . . . . . . . . . . . . . . . 10		3.2.5. ioamE2EData . . . . . . . . . . . . . . . . . . . . . 9
	3.2.6. ioamPOTData . . . . . . . . . . . . . . . . . . . . . 10		3.2.6. ioamPOTData . . . . . . . . . . . . . . . . . . . . . 10
	3.2.7. ioamDirectExportData . . . . . . . . . . . . . . . . 11		3.2.7. ioamDirectExportData . . . . . . . . . . . . . . . . 10
	3.2.8. ipHeaderPacketSectionWithPadding . . . . . . . . . . 11		3.2.8. ipHeaderPacketSectionWithPadding . . . . . . . . . . 11
	3.2.9. ethernetFrameSection . . . . . . . . . . . . . . . . 12		3.2.9. ethernetFrameSection . . . . . . . . . . . . . . . . 12
	4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 13		4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	4.1. Fixed Length IP Packet . . . . . . . . . . . . . . . . . 13		4.1. Fixed Length IP Packet . . . . . . . . . . . . . . . . . 13
	4.2. Variable Length IP Packet (length < 255) . . . . . . . . 14		4.2. Variable Length IP Packet (length < 255) . . . . . . . . 13
	4.3. Variable Length IP Packet (length > 255) . . . . . . . . 15		4.3. Variable Length IP Packet (length > 255) . . . . . . . . 14
	4.4. Variable Length ETHERNET Packet (length < 255) . . . . . 16		4.4. Variable Length ETHERNET Packet (length < 255) . . . . . 15
	4.5. Variable Length IP Packet with Fixed Length IOAM		4.5. Variable Length IP Packet with Fixed Length IOAM
	Incremental Trace Data . . . . . . . . . . . . . . . . . 17		Incremental Trace Data . . . . . . . . . . . . . . . . . 16
	4.6. Variable Length IP Packet with Variable Length IOAM		4.6. Variable Length IP Packet with Variable Length IOAM
	Incremental Trace Data . . . . . . . . . . . . . . . . . 18		Incremental Trace Data . . . . . . . . . . . . . . . . . 17
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
	6. Manageability Considerations . . . . . . . . . . . . . . . . 20		6. Manageability Considerations . . . . . . . . . . . . . . . . 19
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 20		7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 20		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
	9.1. Normative References . . . . . . . . . . . . . . . . . . 20		9.1. Normative References . . . . . . . . . . . . . . . . . . 19
	9.2. Informative References . . . . . . . . . . . . . . . . . 21		9.2. Informative References . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
	1. Introduction		1. Introduction
	In-situ Operations, Administration, and Maintenance (IOAM) records		In-situ Operations, Administration, and Maintenance (IOAM) records
	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. IOAM data fields		traverses a path between two points in the network. IOAM data fields
	are defined in [I-D.ietf-ippm-ioam-data]. This document discusses		are defined in [I-D.ietf-ippm-ioam-data]. This document discusses
	how In-situ Operations, Administration, and Maintenance (IOAM)		how In-situ Operations, Administration, and Maintenance (IOAM)
	information can be exported in raw format, i.e. uninterpreted format,		information can be exported in raw format, i.e. uninterpreted format,
	from network devices to systems, such as monitoring or analytics		from network devices to systems, such as monitoring or analytics
	skipping to change at page 5, line 9 ¶		skipping to change at page 4, line 51 ¶
	Raw export of IOAM data is typically generated by network devices at		Raw export of IOAM data is typically generated by network devices at
	the edges of the network. Deployment and use-case dependent, such as		the edges of the network. Deployment and use-case dependent, such as
	in case of direct export [I-D.ietf-ippm-ioam-direct-export] or in		in case of direct export [I-D.ietf-ippm-ioam-direct-export] or in
	cases where the operator is interested in dropped packets, raw export		cases where the operator is interested in dropped packets, raw export
	of IOAM data may be generated by IOAM transit nodes.		of IOAM data may be generated by IOAM transit nodes.
	1.1. Requirements		1.1. Requirements
	Requirements for raw export of IOAM data:		Requirements for raw export of IOAM data:
	o Export all IOAM information contained in a packet.		* Export all IOAM information contained in a packet.
	o Export a specific IOAM data type - Incremental Trace type,		* Export a specific IOAM data type - Incremental Trace type,
	Preallocated Trace type, Proof of Transit type, Edge to Edge type,		Preallocated Trace type, Proof of Transit type, Edge to Edge type,
	Direct Export type.		Direct Export type.
	o Export IOAM trace data associated with a packet, even if that data		* Export IOAM trace data associated with a packet, even if that data
	was never included in a transmitted or received packet in the		was never included in a transmitted or received packet in the
	network, for example in case of direct export.		network, for example in case of direct export.
	o Support coalescing of the IOAM data from multiple packets into a		* Support coalescing of the IOAM data from multiple packets into a
	single raw export packet.		single raw export packet.
	o Support export of additional parts of the packet, other than the		* Support export of additional parts of the packet, other than the
	IOAM data as part of the raw export. This could be parts of the		IOAM data as part of the raw export. This could be parts of the
	packet header and/or parts of the packet payload. This additional		packet header and/or parts of the packet payload. This additional
	information provides context to the IOAM data (e.g. to be used for		information provides context to the IOAM data (e.g. to be used for
	flow identification) and is to enable the IOAM data processing		flow identification) and is to enable the IOAM data processing
	system to perform further analysis on the received data.		system to perform further analysis on the received data.
	o Report the reason why IOAM data was exported. The "reason for		* Report the reason why IOAM data was exported. The "reason for
	export" is to complement the IOAM data retrieved from the packet.		export" is to complement the IOAM data retrieved from the packet.
	For example, if a packet was dropped by a node due to congestion,		For example, if a packet was dropped by a node due to congestion,
	it could be helpful to export the IOAM data of this dropped packet		it could be helpful to export the IOAM data of this dropped packet
	along with an indication that the packet that the IOAM data		along with an indication that the packet that the IOAM data
	belongs to was dropped due to congestion.		belongs to was dropped due to congestion.
	1.2. Scope		1.2. Scope
	This document discusses raw export of IOAM data using IPFIX.		This document discusses raw export of IOAM data using IPFIX.
	The following is considered out of scope for this document:		The following is considered out of scope for this document:
	o Protocols other than IPFIX for raw export of IOAM data.		* Protocols other than IPFIX for raw export of IOAM data.
	o Interpretation or aggregation of IOAM data prior to exporting.		* Interpretation or aggregation of IOAM data prior to exporting.
	o Configuration of network devices so that they can determine when		* Configuration of network devices so that they can determine when
	to generate IOAM reports, and what information to include in those		to generate IOAM reports, and what information to include in those
	reports.		reports.
	o Events that trigger generation of IOAM reports.		* Events that trigger generation of IOAM reports.
	o Selection of particular destinations within distributed telemetry		* Selection of particular destinations within distributed telemetry
	monitoring systems, to which IOAM reports will be sent.		monitoring systems, to which IOAM reports will be sent.
	o Export format for flow statistics or processed/interpreted/		* Export format for flow statistics or processed/interpreted/
	aggregated IOAM data.		aggregated IOAM data.
	2. Conventions		2. Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	Abbreviations used in this document:		Abbreviations used in this document:
	skipping to change at page 7, line 4 ¶		skipping to change at page 6, line 46 ¶
	3.1. Key IPFIX information elements leveraged for IOAM raw data export		3.1. Key IPFIX information elements leveraged for IOAM raw data export
	The existing IPFIX Information Elements that are required for IOAM		The existing IPFIX Information Elements that are required for IOAM
	raw data export are listed here. Their details are available in		raw data export are listed here. Their details are available in
	IANA's IPFIX registry [IANA-IPFIX].		IANA's IPFIX registry [IANA-IPFIX].
	The existing IPFIX Information Elements used to carry the sections of		The existing IPFIX Information Elements used to carry the sections of
	the packets including IOAM data within it are as follows:		the packets including IOAM data within it are as follows:
	313 - ipHeaderPacketSection		313 - ipHeaderPacketSection
	315 - dataLinkFrameSection		315 - dataLinkFrameSection
	The following Information Elements will be used to provide context to		The following Information Elements will be used to provide context to
	the ipHeaderPacketSection and dataLinkFrameSection as described in		the ipHeaderPacketSection and dataLinkFrameSection as described in
	[IANA-IPFIX]:		[IANA-IPFIX]:
	408 - dataLinkFrameType		408 - dataLinkFrameType
	409 - sectionOffset		409 - sectionOffset
	410 - sectionExportedOctets		410 - sectionExportedOctets
	The following Information Element will be used to provide forwarding		The following Information Element will be used to provide forwarding
	status of the flow and any attached reasons.		status of the flow and any attached reasons.
	89 - forwardingStatus		89 - forwardingStatus
	3.2. New IPFIX information elements leveraged for IOAM raw data export		3.2. New IPFIX information elements leveraged for IOAM raw data export
	IOAM data raw export using IPFIX requires a set of new information		IOAM data raw export using IPFIX requires a set of new information
	elements which are described in this section.		elements which are described in this section.
	3.2.1. ioamReportFlags		3.2.1. ioamReportFlags
	Description:		Description:
	skipping to change at page 20, line 4 ¶		skipping to change at page 18, line 51 ¶
	TBD2 ioamEncapsulationType		TBD2 ioamEncapsulationType
	TBD3 ioamPreallocatedTraceData		TBD3 ioamPreallocatedTraceData
	TBD4 ioamIncrementalTraceData		TBD4 ioamIncrementalTraceData
	TBD5 ioamE2EData		TBD5 ioamE2EData
	TBD6 ioamPOTData		TBD6 ioamPOTData
	TBD7 ioamDirectExportData
			TBD7 ioamDirectExportData
	TBD8 ipHeaderPacketSectionWithPadding		TBD8 ipHeaderPacketSectionWithPadding
	TBD9 ethernetFrameSection		TBD9 ethernetFrameSection
	See Section 3.2 for further details.		See Section 3.2 for further details.
	IANA is requested to create subregistries for ioamReportFlags defined		IANA is requested to create subregistries for ioamReportFlags defined
	in Section 3.2.1 and ioamEncapsulationType defined in Section 3.2.2.		in Section 3.2.1 and ioamEncapsulationType defined in Section 3.2.2.
	6. Manageability Considerations		6. Manageability Considerations
	skipping to change at page 20, line 37 ¶		skipping to change at page 19, line 35 ¶
	The authors would like to thank Barak Gafni, Tal Mizrahi, John Lemon,		The authors would like to thank Barak Gafni, Tal Mizrahi, John Lemon,
	and Aviv Kfir for their thoughts and comments on raw IOAM data		and Aviv Kfir for their thoughts and comments on raw IOAM data
	export.		export.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[I-D.ietf-ippm-ioam-data]		[I-D.ietf-ippm-ioam-data]
	Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields		Brockners, F., Bhandari, S., and T. Mizrahi, "Data Fields
	for In-situ OAM", draft-ietf-ippm-ioam-data-10 (work in		for In-situ OAM", Work in Progress, Internet-Draft, draft-
	progress), July 2020.		ietf-ippm-ioam-data-14, 24 June 2021,
			<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
			data-14.txt>.
	[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>.
	[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet		[RFC5476] Claise, B., Ed., Johnson, A., and J. Quittek, "Packet
	Sampling (PSAMP) Protocol Specifications", RFC 5476,		Sampling (PSAMP) Protocol Specifications", RFC 5476,
	DOI 10.17487/RFC5476, March 2009,		DOI 10.17487/RFC5476, March 2009,
	<https://www.rfc-editor.org/info/rfc5476>.		<https://www.rfc-editor.org/info/rfc5476>.
	skipping to change at page 21, line 15 ¶		skipping to change at page 20, line 15 ¶
	[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,		[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
	"Specification of the IP Flow Information Export (IPFIX)		"Specification of the IP Flow Information Export (IPFIX)
	Protocol for the Exchange of Flow Information", STD 77,		Protocol for the Exchange of Flow Information", STD 77,
	RFC 7011, DOI 10.17487/RFC7011, September 2013,		RFC 7011, DOI 10.17487/RFC7011, September 2013,
	<https://www.rfc-editor.org/info/rfc7011>.		<https://www.rfc-editor.org/info/rfc7011>.
	9.2. Informative References		9.2. Informative References
	[I-D.brockners-ippm-ioam-geneve]		[I-D.brockners-ippm-ioam-geneve]
	Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,		Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,
	Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Lapukhov,		Nainar, N., Gredler, H., Leddy, J., Youell, S., Mizrahi,
	P., Gafni, B., Kfir, A., and M. Spiegel, "Geneve		T., Lapukhov, P., Gafni, B., Kfir, A., and M. Spiegel,
	encapsulation for In-situ OAM Data", draft-brockners-ippm-		"Geneve encapsulation for In-situ OAM Data", Work in
	ioam-geneve-04 (work in progress), May 2020.		Progress, Internet-Draft, draft-brockners-ippm-ioam-
			geneve-05, 19 November 2020, <https://www.ietf.org/
			internet-drafts/draft-brockners-ippm-ioam-geneve-05.txt>.
	[I-D.brockners-ippm-ioam-vxlan-gpe]		[I-D.brockners-ippm-ioam-vxlan-gpe]
	Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,		Brockners, F., Bhandari, S., Govindan, V., Pignataro, C.,
	Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Kfir, A.,		Gredler, H., Leddy, J., Youell, S., Mizrahi, T., Kfir, A.,
	Gafni, B., Lapukhov, P., and M. Spiegel, "VXLAN-GPE		Gafni, B., Lapukhov, P., and M. Spiegel, "VXLAN-GPE
	Encapsulation for In-situ OAM Data", draft-brockners-ippm-		Encapsulation for In-situ OAM Data", Work in Progress,
	ioam-vxlan-gpe-03 (work in progress), November 2019.		Internet-Draft, draft-brockners-ippm-ioam-vxlan-gpe-03, 4
			November 2019, <http://www.ietf.org/internet-drafts/draft-
			brockners-ippm-ioam-vxlan-gpe-03.txt>.
	[I-D.ietf-ippm-ioam-direct-export]		[I-D.ietf-ippm-ioam-direct-export]
	Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,		Song, H., Gafni, B., Zhou, T., Li, Z., Brockners, F.,
	Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ		Bhandari, S., Sivakolundu, R., and T. Mizrahi, "In-situ
	OAM Direct Exporting", draft-ietf-ippm-ioam-direct-		OAM Direct Exporting", Work in Progress, Internet-Draft,
	export-02 (work in progress), November 2020.		draft-ietf-ippm-ioam-direct-export-05, 12 July 2021,
			<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
			direct-export-05.txt>.
	[I-D.ietf-ippm-ioam-ipv6-options]		[I-D.ietf-ippm-ioam-ipv6-options]
	Bhandari, S., Brockners, F., Pignataro, C., Gredler, H.,		Bhandari, S., Brockners, F., Pignataro, C., Gredler, H.,
	Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B.,		Leddy, J., Youell, S., Mizrahi, T., Kfir, A., Gafni, B.,
	Lapukhov, P., Spiegel, M., Krishnan, S., Asati, R., and M.		Lapukhov, P., Spiegel, M., Krishnan, S., Asati, R., and M.
	Smith, "In-situ OAM IPv6 Options", draft-ietf-ippm-ioam-		Smith, "In-situ OAM IPv6 Options", Work in Progress,
	ipv6-options-04 (work in progress), November 2020.		Internet-Draft, draft-ietf-ippm-ioam-ipv6-options-05, 21
			February 2021, <https://www.ietf.org/archive/id/draft-
			ietf-ippm-ioam-ipv6-options-05.txt>.
	[I-D.ietf-sfc-ioam-nsh]		[I-D.ietf-sfc-ioam-nsh]
	Brockners, F. and S. Bhandari, "Network Service Header		Brockners, F. and S. Bhandari, "Network Service Header
	(NSH) Encapsulation for In-situ OAM (IOAM) Data", draft-		(NSH) Encapsulation for In-situ OAM (IOAM) Data", Work in
	ietf-sfc-ioam-nsh-04 (work in progress), June 2020.		Progress, Internet-Draft, draft-ietf-sfc-ioam-nsh-05, 12
			December 2020, <https://www.ietf.org/internet-drafts/
			draft-ietf-sfc-ioam-nsh-05.txt>.
	[I-D.weis-ippm-ioam-eth]		[I-D.weis-ippm-ioam-eth]
	Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan,		Weis, B., Brockners, F., Hill, C., Bhandari, S., Govindan,
	V., Pignataro, C., Gredler, H., Leddy, J., Youell, S.,		V., Pignataro, C., Gredler, H., Leddy, J., Youell, S.,
	Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., and M.		Mizrahi, T., Kfir, A., Gafni, B., Lapukhov, P., and M.
	Spiegel, "EtherType Protocol Identification of In-situ OAM		Spiegel, "EtherType Protocol Identification of In-situ OAM
	Data", draft-weis-ippm-ioam-eth-04 (work in progress), May		Data", Work in Progress, Internet-Draft, draft-weis-ippm-
	2020.		ioam-eth-04, 13 May 2020, <http://www.ietf.org/internet-
			drafts/draft-weis-ippm-ioam-eth-04.txt>.
	[IANA-IPFIX]		[IANA-IPFIX]
	"IP Flow Information Export (IPFIX) Entities",		"IP Flow Information Export (IPFIX) Entities",
	<https://www.iana.org/assignments/ipfix/ipfix.xhtml>.		<https://www.iana.org/assignments/ipfix/ipfix.xhtml>.
	[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804,		[RFC2804] IAB and IESG, "IETF Policy on Wiretapping", RFC 2804,
	DOI 10.17487/RFC2804, May 2000,		DOI 10.17487/RFC2804, May 2000,
	<https://www.rfc-editor.org/info/rfc2804>.		<https://www.rfc-editor.org/info/rfc2804>.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	skipping to change at page 22, line 28 ¶		skipping to change at page 21, line 44 ¶
	[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G.		[RFC5477] Dietz, T., Claise, B., Aitken, P., Dressler, F., and G.
	Carle, "Information Model for Packet Sampling Exports",		Carle, "Information Model for Packet Sampling Exports",
	RFC 5477, DOI 10.17487/RFC5477, March 2009,		RFC 5477, DOI 10.17487/RFC5477, March 2009,
	<https://www.rfc-editor.org/info/rfc5477>.		<https://www.rfc-editor.org/info/rfc5477>.
	Authors' Addresses		Authors' Addresses
	Mickey Spiegel		Mickey Spiegel
	Barefoot Networks, an Intel company		Barefoot Networks, an Intel company
	4750 Patrick Henry Drive		4750 Patrick Henry Drive
	Santa Clara, CA 95054		Santa Clara, CA, 95054
	US		United States of America
	Email: mickey.spiegel@intel.com		Email: mickey.spiegel@intel.com
	Frank Brockners		Frank Brockners
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Hansaallee 249, 3rd Floor		Hansaallee 249, 3rd Floor
	DUESSELDORF, NORDRHEIN-WESTFALEN 40549		40549 DUESSELDORF, NORDRHEIN-WESTFALEN
	Germany		Germany
	Email: fbrockne@cisco.com		Email: fbrockne@cisco.com
	Shwetha Bhandari		Shwetha Bhandari (editor)
	Cisco Systems, Inc.		Thoughtspot
	Cessna Business Park, Sarjapura Marathalli Outer Ring Road		3rd Floor, Indiqube Orion, 24th Main Rd, Garden Layout, HSR Layout
	Bangalore, KARNATAKA 560 087		Bangalore, KARNATAKA 560 102
	India		India
	Email: shwethab@cisco.com		Email: shwetha.bhandari@thoughtspot.com
	Ramesh Sivakolundu		Ramesh Sivakolundu
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Dr.		170 West Tasman Dr.
	SAN JOSE, CA 95134		SAN JOSE, CA 95134,
	U.S.A.		United States of America
	Email: sramesh@cisco.com		Email: sramesh@cisco.com
End of changes. 42 change blocks.
	74 lines changed or deleted		90 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/