< draft-ietf-bier-ipv6-requirements-05.txt		draft-ietf-bier-ipv6-requirements-06.txt >
	Network Working Group M. McBride		Network Working Group M. McBride
	Internet-Draft Futurewei		Internet-Draft Futurewei
	Intended status: Standards Track J. Xie		Intended status: Standards Track J. Xie
	Expires: January 11, 2021 S. Dhanaraj		Expires: January 29, 2021 S. Dhanaraj
	Huawei		Huawei
	R. Asati		R. Asati
	Cisco		Cisco
	Y. Zhu		Y. Zhu
	China Telecom		China Telecom
	G. Mishra		G. Mishra
	Verizon Inc.		Verizon Inc.
	July 10, 2020		July 28, 2020
	BIER IPv6 Requirements		BIER IPv6 Requirements
	draft-ietf-bier-ipv6-requirements-05		draft-ietf-bier-ipv6-requirements-06
	Abstract		Abstract
	The BIER WG charter includes work on developing "a mechanism to use		The BIER WG charter includes work on developing "a mechanism to use
	BIER natively in IPv6". There have been several proposed solutions		BIER natively in IPv6". There have been several proposed solutions
	in this area. But there hasn't been a document which describes the		in this area. But there hasn't been a document which describes the
	problem and lists the requirements. The goal of this document is to		problem and lists the requirements. The goal of this document is to
	describe the BIER IPv6 requirements, summarize the encapsulation		describe the BIER IPv6 requirements, summarize the encapsulation
	modes of the proposed solutions, guide the working group in		modes of the proposed solutions, guide the working group in
	understanding the benefits and drawbacks of the various solutions,		understanding the benefits and drawbacks of the various solutions,
	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 January 11, 2021.		This Internet-Draft will expire on January 29, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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
	skipping to change at page 3, line 48 ¶		skipping to change at page 3, line 48 ¶
	o BUM: Broadcast, Unknown Unicast, Multicast. Term used to describe		o BUM: Broadcast, Unknown Unicast, Multicast. Term used to describe
	the three types of Ethernet modes that will be forwarded to		the three types of Ethernet modes that will be forwarded to
	multiple destinations		multiple destinations
	2. Problem Statement		2. Problem Statement
	The problem is the ability of the network to transport BUM packets,		The problem is the ability of the network to transport BUM packets,
	with BIER headers, in an IPv6 environment. In many IPv6 network		with BIER headers, in an IPv6 environment. In many IPv6 network
	deployments, non-MPLS encapsulation is used for unicast as the data-		deployments, non-MPLS encapsulation is used for unicast as the data-
	plane and it is likewise expected to have BIER IPv6 deployments which		plane. It is likewise expected to have BIER IPv6 deployments which
	depend on these same unicast technologies.		depend on these same unicast technologies to traverse through non-BFR
			routers.
	One such case involves supporting a non-BFR router in a network as		One such case involves supporting a non-BFR router in a network as
	described in section 6.9 of RFC8279. In the context of this		described in section 6.9 of RFC8279. In the context of this
	document, an IPv6 based unicast tunnel is needed to support such		document, an IPv6 based unicast tunnel is needed to support such
	deployment where a non-BFR exists. Another case is to support inter-		deployment where a non-BFR exists. Another case is to support inter-
	AS multicast deployment as illustrated in		AS multicast deployment as illustrated in
	[I-D.geng-bier-ipv6-inter-domain]. In such deployment, there are		[I-D.geng-bier-ipv6-inter-domain]. In such deployment, there are
	non-BFR routers, or even an entire non-BIER network, that needs the		non-BFR routers, or even an entire non-BIER network, that needs the
	ability to traverse from one BFR to another.		ability to traverse from one BFR to another.
	[I-D.ietf-bier-use-cases] shows it is possible there are other cases		[I-D.ietf-bier-use-cases] shows it is possible there are other cases
	skipping to change at page 7, line 5 ¶		skipping to change at page 6, line 51 ¶
	<-----> BIER(P2MP) tunnel		<-----> BIER(P2MP) tunnel
	In this model, BIER works as part of the IPv6 data plane. BFIR and		In this model, BIER works as part of the IPv6 data plane. BFIR and
	BFERs work as IPv6 (P2MP) tunnel endpoints, and BFRs work as IPv6		BFERs work as IPv6 (P2MP) tunnel endpoints, and BFRs work as IPv6
	segment endpoints. On each BFR, the segment endpoint behaviour of		segment endpoints. On each BFR, the segment endpoint behaviour of
	IPv6 data plane is executed, and there is no decapsulation of		IPv6 data plane is executed, and there is no decapsulation of
	receiving IPv6 tunnel and encapsulation of new IPv6 tunnel for		receiving IPv6 tunnel and encapsulation of new IPv6 tunnel for
	sending.		sending.
	In this mode, BIER is integrated into the IPv6 data plane. The IPv6		In this mode, the BIER header is integrated into the IPv6 extension
	source address is the BIER packet source-origin identifier, and is		header and processing of the BIER header (e.g., the BitString) is
	unchanged through the BIER domain from BFIR to BFERs.		implemented as part of the IPv6 extension header processing. The
			IPv6 source address is the BIER packet source-origin identifier, and
			is unchanged through the BIER domain from BFIR to BFERs.
	This model is similar to many examples emerging in the IETF community		This model is similar to many examples emerging in the IETF community
	which soley use the IPv6 data plane. SRv6 introduced in [RFC8754]		which soley use the IPv6 data plane. SRv6 introduced in [RFC8754]
	and [I-D.ietf-spring-srv6-network-programming] is an example. The		and [I-D.ietf-spring-srv6-network-programming] is an example. The
	benefits of such approach includes reducing the number of		benefits of such approach includes reducing the number of
	encapsulation layers, capability of deployment with non-capable		encapsulation layers, capability of deployment with non-capable
	routers in a network, extending the technology in a wider inter-AS		routers in a network, extending the technology in a wider inter-AS
	scope using IP reachability, and capability of integrating the		scope using IP reachability, and capability of integrating the
	functions of the IPv6 data plane.		functions of the IPv6 data plane.
	skipping to change at page 11, line 7 ¶		skipping to change at page 11, line 7 ¶
	draft-ietf-spring-srv6-network-programming-16 (work in		draft-ietf-spring-srv6-network-programming-16 (work in
	progress), June 2020.		progress), June 2020.
	[I-D.pfister-bier-over-ipv6]		[I-D.pfister-bier-over-ipv6]
	Pfister, P. and I. Wijnands, "An IPv6 based BIER		Pfister, P. and I. Wijnands, "An IPv6 based BIER
	Encapsulation and Encoding", draft-pfister-bier-over-		Encapsulation and Encoding", draft-pfister-bier-over-
	ipv6-01 (work in progress), October 2016.		ipv6-01 (work in progress), October 2016.
	[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., and X. Geng, "Encapsulation		Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng,
	for BIER in Non-MPLS IPv6 Networks", draft-xie-bier-		"Encapsulation for BIER in Non-MPLS IPv6 Networks", draft-
	ipv6-encapsulation-07 (work in progress), June 2020.		xie-bier-ipv6-encapsulation-08 (work in progress), July
			2020.
	[I-D.xu-bier-encapsulation]		[I-D.xu-bier-encapsulation]
	Xu, X., somasundaram.s@alcatel-lucent.com, s., Jacquenet,		Xu, X., somasundaram.s@alcatel-lucent.com, s., Jacquenet,
	C., Raszuk, R., and Z. Zhang, "A Transport-Independent Bit		C., Raszuk, R., and Z. Zhang, "A Transport-Independent Bit
	Index Explicit Replication (BIER) Encapsulation Header",		Index Explicit Replication (BIER) Encapsulation Header",
	draft-xu-bier-encapsulation-06 (work in progress),		draft-xu-bier-encapsulation-06 (work in progress),
	September 2016.		September 2016.
	[I-D.zhang-bier-bierin6]		[I-D.zhang-bier-bierin6]
	Zhang, Z., Przygienda, T., Wijnands, I., Bidgoli, H., and		Zhang, Z., Przygienda, T., Wijnands, I., Bidgoli, H., and
	M. McBride, "BIER in IPv6 (BIERin6)", draft-zhang-bier-		M. McBride, "BIER in IPv6 (BIERin6)", draft-zhang-bier-
	bierin6-04 (work in progress), January 2020.		bierin6-06 (work in progress), July 2020.
	[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,		[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
	RFC 1112, DOI 10.17487/RFC1112, August 1989,		RFC 1112, DOI 10.17487/RFC1112, August 1989,
	<https://www.rfc-editor.org/info/rfc1112>.		<https://www.rfc-editor.org/info/rfc1112>.
	[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>.
End of changes. 8 change blocks.
	13 lines changed or deleted		17 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/