< draft-ietf-mboned-multicast-telemetry-01.txt		draft-ietf-mboned-multicast-telemetry-02.txt >
	MBONED H. Song		MBONED H. Song
	Internet-Draft M. McBride		Internet-Draft M. McBride
	Intended status: Standards Track Futurewei Technologies		Intended status: Standards Track Futurewei Technologies
	Expires: January 7, 2022 G. Mirsky		Expires: 8 July 2022 G. Mirsky
	ZTE Corp.		ZTE Corp.
	G. Mishra		G. Mishra
	Verizon Inc.		Verizon Inc.
	H. Asaeda		H. Asaeda
	NICT		NICT
	T. Zhou		T. Zhou
	Huawei		Huawei
	July 6, 2021		4 January 2022
	Multicast On-path Telemetry Solutions		Multicast On-path Telemetry Solutions
	draft-ietf-mboned-multicast-telemetry-01		draft-ietf-mboned-multicast-telemetry-02
	Abstract		Abstract
	This document discusses the requirement of on-path telemetry for		This document discusses the requirement of on-path telemetry for
	multicast traffic. The existing solutions are examined and their		multicast traffic. The existing solutions are examined and their
	issues are identified. Solution modifications are proposed to allow		issues are identified. Solution modifications are proposed to allow
	the original multicast tree to be correctly reconstructed without		the original multicast tree to be correctly reconstructed without
	unnecessary replication of telemetry information.		unnecessary replication of telemetry information.
	Requirements Language		Requirements Language
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	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 January 7, 2022.		This Internet-Draft will expire on 8 July 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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 Revised BSD License text as
	include Simplified BSD License text as described in Section 4.e of		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 Revised BSD License.
	described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Requirements for Multicast Traffic Telemetry . . . . . . . . 3		2. Requirements for Multicast Traffic Telemetry . . . . . . . . 3
	3. Issues of Existing Techniques . . . . . . . . . . . . . . . . 4		3. Issues of Existing Techniques . . . . . . . . . . . . . . . . 4
	4. Proposed Modifications to Existing Techniques . . . . . . . . 5		4. Proposed Modifications to Existing Techniques . . . . . . . . 5
	4.1. Per-hop postcard using IOAM DEX . . . . . . . . . . . . . 5		4.1. Per-hop postcard using IOAM DEX . . . . . . . . . . . . . 5
	4.2. Per-section postcard . . . . . . . . . . . . . . . . . . 7		4.2. Per-section postcard . . . . . . . . . . . . . . . . . . 7
	5. Considerations for Different Multicast Protocols . . . . . . 8		5. Considerations for Different Multicast Protocols . . . . . . 8
	5.1. Application in PIM . . . . . . . . . . . . . . . . . . . 8		5.1. Application in PIM . . . . . . . . . . . . . . . . . . . 8
	5.2. Application of MVPN X-PMSI Tunnel Encapsulation Attribute 9		5.2. Application of MVPN X-PMSI Tunnel Encapsulation
			Attribute . . . . . . . . . . . . . . . . . . . . . . . . 9
	5.3. Application in BIER . . . . . . . . . . . . . . . . . . . 9		5.3. Application in BIER . . . . . . . . . . . . . . . . . . . 9
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 10		6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10		8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	10.1. Normative References . . . . . . . . . . . . . . . . . . 10		10.1. Normative References . . . . . . . . . . . . . . . . . . 10
	10.2. Informative References . . . . . . . . . . . . . . . . . 12		10.2. Informative References . . . . . . . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
	skipping to change at page 3, line 48 ¶		skipping to change at page 3, line 48 ¶
	and P2MP (MLDP, RSVP-TE) the forwarding tree is established and		and P2MP (MLDP, RSVP-TE) the forwarding tree is established and
	maintained by the multicast routing protocol. With BIER, no state is		maintained by the multicast routing protocol. With BIER, no state is
	created in the network to establish a forwarding tree, instead, a		created in the network to establish a forwarding tree, instead, a
	bier header provides the necessary information for each packet to		bier header provides the necessary information for each packet to
	know the egress points. Multicast packets are only replicated at		know the egress points. Multicast packets are only replicated at
	each tree branch node for efficiency.		each tree branch node for efficiency.
	There are several requirements for multicast traffic telemetry, a few		There are several requirements for multicast traffic telemetry, a few
	of which are:		of which are:
	o Reconstruct and visualize the multicast tree through data plane		* Reconstruct and visualize the multicast tree through data plane
	monitoring.		monitoring.
	o Gather the multicast packet delay and jitter performance.		* Gather the multicast packet delay and jitter performance.
	o Find the multicast packet drop location and reason.		* Find the multicast packet drop location and reason.
	o Gather the VPN state and tunnel information in case of P2MP		* Gather the VPN state and tunnel information in case of P2MP
	multicast.		multicast.
	In order to meet these requirements, we need the ability to directly		In order to meet these requirements, we need the ability to directly
	monitor the multicast traffic and derive data from the multicast		monitor the multicast traffic and derive data from the multicast
	packets. The conventional OAM mechanisms, such as multicast ping and		packets. The conventional OAM mechanisms, such as multicast ping and
	trace, may not be sufficient to meet these requirements.		trace, may not be sufficient to meet these requirements.
	3. Issues of Existing Techniques		3. Issues of Existing Techniques
	On-path Telemetry techniques that directly retrieve data from		On-path Telemetry techniques that directly retrieve data from
	skipping to change at page 5, line 48 ¶		skipping to change at page 5, line 48 ¶
	: : +---:----->| C |--...		: : +---:----->| C |--...
	+-:-+ +-:-+ | : | |		+-:-+ +-:-+ | : | |
	| | | |----+ : +---+		| | | |----+ : +---+
	| A |------->| B | :		| A |------->| B | :
	| | | |--+ +-:-+		| | | |--+ +-:-+
	+---+ +---+ | | |		+---+ +---+ | | |
	+-->| D |--....		+-->| D |--....
	| |		| |
	+---+		+---+
	Figure 1: Per-hop Postcard		Figure 1: Per-hop Postcard
	Each branch fork node needs to generate the branch ID for each branch		Each branch fork node needs to generate the branch ID for each branch
	in its multicast tree instance and include it in the IOAM DEX option		in its multicast tree instance and include it in the IOAM DEX option
	header so the downstream node can learn it. The branch ID contains		header so the downstream node can learn it. The branch ID contains
	two parts: the branch fork node ID and a unique branch index.		two parts: the branch fork node ID and a unique branch index.
	Figure 2 shows that the branch ID is carried as an optional field		Figure 2 shows that the branch ID is carried as an optional field
	after the flow ID and sequence number optional fields in the IOAM DEX		after the flow ID and sequence number optional fields in the IOAM DEX
	option header. A bit "M" in the Flags field is reserved to indicate		option header. A bit "M" in the Flags field is reserved to indicate
	the presence of the branch index field. The "M" flag position will		the presence of the branch index field. The "M" flag position will
	skipping to change at page 6, line 31 ¶		skipping to change at page 6, line 31 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| IOAM-Trace-Type | Reserved |		| IOAM-Trace-Type | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Flow ID (optional) |		| Flow ID (optional) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sequence Number (Optional) |		| Sequence Number (Optional) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Encoded Branch ID (optional) |		| Encoded Branch ID (optional) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: Carry Branch Index in IOAM DEX option header		Figure 2: Carry Branch Index in IOAM DEX option header
	To avoid introducing a new type of data field to the IOAM DEX option		To avoid introducing a new type of data field to the IOAM DEX option
	header, we can encode the branch identifier using the existing node		header, we can encode the branch identifier using the existing node
	ID data field as defined in [I-D.ietf-ippm-ioam-data]. Currently,		ID data field as defined in [I-D.ietf-ippm-ioam-data]. Currently,
	the node ID field occupies three octets. A simple solution is to		the node ID field occupies three octets. A simple solution is to
	shorten the node ID field so a number of bits can be saved to encode		shorten the node ID field so a number of bits can be saved to encode
	the branch index, as shown in Figure 3.		the branch index, as shown in Figure 3.
	0 1 2 3		0 1 2 3
	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
	skipping to change at page 8, line 23 ¶		skipping to change at page 8, line 23 ¶
	: +-->| C |----->| D |-----...		: +-->| C |----->| D |-----...
	+---+ +---+ | | | | |--+		+---+ +---+ | | | | |--+
	| | {A} | |--+ +---+ +---+ |		| | {A} | |--+ +---+ +---+ |
	| A |---->| B | +--...		| A |---->| B | +--...
	| | | |--+ +---+ {D3}		| | | |--+ +---+ {D3}
	+---+ +---+ | | |{B2,E}		+---+ +---+ | | |{B2,E}
	+-->| E |--...		+-->| E |--...
	{B2} | |		{B2} | |
	+---+		+---+
	Figure 5: Per-section Postcard		Figure 5: Per-section Postcard
	There is no need to modify the IOAM trace mode header format. We		There is no need to modify the IOAM trace mode header format. We
	just need to configure the branch node to export the postcard and		just need to configure the branch node to export the postcard and
	refresh the IOAM header and data.		refresh the IOAM header and data.
	5. Considerations for Different Multicast Protocols		5. Considerations for Different Multicast Protocols
	MTRACEv2 [RFC8487] provides an active probing approach for the		MTRACEv2 [RFC8487] provides an active probing approach for the
	tracing of an IP multicast routing path. Mtrace can also provide		tracing of an IP multicast routing path. Mtrace can also provide
	information such as the packet rates and losses, as well as other		information such as the packet rates and losses, as well as other
	skipping to change at page 12, line 14 ¶		skipping to change at page 12, line 14 ¶
	[RFC8487] Asaeda, H., Meyer, K., and W. Lee, Ed., "Mtrace Version 2:		[RFC8487] Asaeda, H., Meyer, K., and W. Lee, Ed., "Mtrace Version 2:
	Traceroute Facility for IP Multicast", RFC 8487,		Traceroute Facility for IP Multicast", RFC 8487,
	DOI 10.17487/RFC8487, October 2018,		DOI 10.17487/RFC8487, October 2018,
	<https://www.rfc-editor.org/info/rfc8487>.		<https://www.rfc-editor.org/info/rfc8487>.
	10.2. Informative References		10.2. Informative References
	[I-D.herbert-ipv4-udpencap-eh]		[I-D.herbert-ipv4-udpencap-eh]
	Herbert, T., "IPv4 Extension Headers and UDP Encapsulated		Herbert, T., "IPv4 Extension Headers and UDP Encapsulated
	Extension Headers", draft-herbert-ipv4-udpencap-eh-01		Extension Headers", Work in Progress, Internet-Draft,
	(work in progress), March 2019.		draft-herbert-ipv4-udpencap-eh-01, 8 March 2019,
			<https://www.ietf.org/archive/id/draft-herbert-ipv4-
			udpencap-eh-01.txt>.
	[I-D.ietf-bier-oam-requirements]		[I-D.ietf-bier-oam-requirements]
	Mirsky, G., Kumar, N., Chen, M., and S. Pallagatti,		Mirsky, G., Kumar, N., Chen, M., and S. Pallagatti,
	"Operations, Administration and Maintenance (OAM)		"Operations, Administration and Maintenance (OAM)
	Requirements for Bit Index Explicit Replication (BIER)		Requirements for Bit Index Explicit Replication (BIER)
	Layer", draft-ietf-bier-oam-requirements-11 (work in		Layer", Work in Progress, Internet-Draft, draft-ietf-bier-
	progress), November 2020.		oam-requirements-11, 15 November 2020,
			<https://www.ietf.org/archive/id/draft-ietf-bier-oam-
			requirements-11.txt>.
	[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-12 (work in		for In-situ OAM", Work in Progress, Internet-Draft, draft-
	progress), February 2021.		ietf-ippm-ioam-data-17, 13 December 2021,
			<https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-
			data-17.txt>.
	[I-D.ietf-spring-sr-replication-segment]		[I-D.ietf-spring-sr-replication-segment]
	Voyer, D., Filsfils, C., Parekh, R., Bidgoli, H., and Z.		(editor), D. V., Filsfils, C., Parekh, R., Bidgoli, H.,
	Zhang, "SR Replication Segment for Multi-point Service		and Z. Zhang, "SR Replication Segment for Multi-point
	Delivery", draft-ietf-spring-sr-replication-segment-04		Service Delivery", Work in Progress, Internet-Draft,
	(work in progress), February 2021.		draft-ietf-spring-sr-replication-segment-06, 25 October
			2021, <https://www.ietf.org/archive/id/draft-ietf-spring-
			sr-replication-segment-06.txt>.
	[I-D.ioametal-ippm-6man-ioam-ipv6-deployment]		[I-D.ioametal-ippm-6man-ioam-ipv6-deployment]
	Bhandari, S., Brockners, F., Mizrahi, T., Kfir, A., Gafni,		Bhandari, S., Brockners, F., Mizrahi, T., Kfir, A., Gafni,
	B., Spiegel, M., Krishnan, S., and M. Smith, "Deployment		B., Spiegel, M., Krishnan, S., and M. Smith, "Deployment
	Considerations for In-situ OAM with IPv6 Options", draft-		Considerations for In-situ OAM with IPv6 Options", Work in
	ioametal-ippm-6man-ioam-ipv6-deployment-03 (work in		Progress, Internet-Draft, draft-ioametal-ippm-6man-ioam-
	progress), March 2020.		ipv6-deployment-03, 29 March 2020,
			<https://www.ietf.org/archive/id/draft-ioametal-ippm-6man-
			ioam-ipv6-deployment-03.txt>.
	[I-D.ioamteam-ippm-ioam-direct-export]		[I-D.ioamteam-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-ioamteam-ippm-ioam-direct-		OAM Direct Exporting", Work in Progress, Internet-Draft,
	export-00 (work in progress), October 2019.		draft-ioamteam-ippm-ioam-direct-export-00, 12 October
			2019, <https://www.ietf.org/archive/id/draft-ioamteam-
			ippm-ioam-direct-export-00.txt>.
	[I-D.mirsky-ippm-hybrid-two-step]		[I-D.mirsky-ippm-hybrid-two-step]
	Mirsky, G., Lingqiang, W., Zhui, G., and H. Song, "Hybrid		Mirsky, G., Lingqiang, W., Zhui, G., and H. Song, "Hybrid
	Two-Step Performance Measurement Method", draft-mirsky-		Two-Step Performance Measurement Method", Work in
	ippm-hybrid-two-step-09 (work in progress), March 2021.		Progress, Internet-Draft, draft-mirsky-ippm-hybrid-two-
			step-11, 8 July 2021, <https://www.ietf.org/archive/id/
			draft-mirsky-ippm-hybrid-two-step-11.txt>.
	[I-D.song-ippm-postcard-based-telemetry]		[I-D.song-ippm-postcard-based-telemetry]
	Song, H., Mirsky, G., Filsfils, C., Abdelsalam, A., Zhou,		Song, H., Mirsky, G., Filsfils, C., Abdelsalam, A., Zhou,
	T., Li, Z., Shin, J., and K. Lee, "Postcard-based On-Path		T., Li, Z., Shin, J., and K. Lee, "In-Situ OAM Marking-
	Flow Data Telemetry using Packet Marking", draft-song-		based Direct Export", Work in Progress, Internet-Draft,
	ippm-postcard-based-telemetry-09 (work in progress),		draft-song-ippm-postcard-based-telemetry-11, 15 November
	February 2021.		2021, <https://www.ietf.org/archive/id/draft-song-ippm-
			postcard-based-telemetry-11.txt>.
	[I-D.song-mpls-extension-header]		[I-D.song-mpls-extension-header]
	Song, H., Li, Z., Zhou, T., and L. Andersson, "MPLS		Song, H., Li, Z., Zhou, T., Andersson, L., and Z. Zhang,
	Extension Header", draft-song-mpls-extension-header-04		"MPLS Extension Header", Work in Progress, Internet-Draft,
	(work in progress), April 2021.		draft-song-mpls-extension-header-05, 10 July 2021,
			<https://www.ietf.org/archive/id/draft-song-mpls-
			extension-header-05.txt>.
	[I-D.xie-bier-ipv6-encapsulation]		[I-D.xie-bier-ipv6-encapsulation]
	Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,		Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S.,
	Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,		Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
	"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-		"Encapsulation for BIER in Non-MPLS IPv6 Networks", Work
	xie-bier-ipv6-encapsulation-10 (work in progress),		in Progress, Internet-Draft, draft-xie-bier-ipv6-
	February 2021.		encapsulation-10, 22 February 2021,
			<https://www.ietf.org/archive/id/draft-xie-bier-ipv6-
			encapsulation-10.txt>.
	Authors' Addresses		Authors' Addresses
	Haoyu Song		Haoyu Song
	Futurewei Technologies		Futurewei Technologies
	2330 Central Expressway		2330 Central Expressway
	Santa Clara		Santa Clara,
	USA		United States of America
	Email: hsong@futurewei.com		Email: hsong@futurewei.com
	Mike McBride		Mike McBride
	Futurewei Technologies		Futurewei Technologies
	2330 Central Expressway		2330 Central Expressway
	Santa Clara		Santa Clara,
	USA		United States of America
	Email: mmcbride@futurewei.com		Email: mmcbride@futurewei.com
	Greg Mirsky		Greg Mirsky
	ZTE Corp.		ZTE Corp.
	Email: gregimirsky@gmail.com		Email: gregimirsky@gmail.com
	Gyan Mishra		Gyan Mishra
	Verizon Inc.		Verizon Inc.
	Email: gyan.s.mishra@verizon.com		Email: gyan.s.mishra@verizon.com
	Hitoshi Asaeda		Hitoshi Asaeda
	National Institute of Information and Communications Technology		National Institute of Information and Communications Technology
	4-2-1 Nukui-Kitamachi		4-2-1 Nukui-Kitamachi, Tokyo
	Koganei, Tokyo 184-8795		184-8795
	Japan		Japan
	Email: asaeda@nict.go.jp		Email: asaeda@nict.go.jp
	Tianran Zhou		Tianran Zhou
	Huawei		Huawei
	Email: zhoutianran@huawei.com		Email: zhoutianran@huawei.com
End of changes. 29 change blocks.
	55 lines changed or deleted		74 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/