< draft-ietf-bier-bierin6-01.txt		draft-ietf-bier-bierin6-02.txt >
	BIER Z. Zhang		BIER Z. Zhang
	Internet-Draft ZTE Corporation		Internet-Draft ZTE Corporation
	Intended status: Standards Track Z. Zhang, Ed.		Intended status: Standards Track Z. Zhang, Ed.
	Expires: 11 June 2022 Juniper Networks		Expires: 10 July 2022 Juniper Networks
	I. Wijnands		I. Wijnands
	Individual		Individual
	M. Mishra		M. Mishra
	Cisco Systems		Cisco Systems
	H. Bidgoli		H. Bidgoli
	Nokia		Nokia
	G. Mishra		G. Mishra
	Verizon		Verizon
	8 December 2021		6 January 2022
	Supporting BIER in IPv6 Networks (BIERin6)		Supporting BIER in IPv6 Networks (BIERin6)
	draft-ietf-bier-bierin6-01		draft-ietf-bier-bierin6-02
	Abstract		Abstract
	BIER is a new architecture for the forwarding of multicast data		BIER is a new architecture for the forwarding of multicast data
	packets without requiring per-flow state inside the network. This		packets without requiring per-flow state inside the network. This
	document describes how the existing BIER encapsulation specified in		document describes how the existing BIER encapsulation specified in
	RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6.		RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6.
	Specifically, like in an IPv4 network, BIER can work over L2 links		Specifically, like in an IPv4 network, BIER can work over L2 links
	directly or over tunnels. In case of IPv6 tunneling, a new IP "Next		directly or over tunnels. In case of IPv6 tunneling, a new IP "Next
	Header" type is to be assigned for BIER.		Header" type is to be assigned for BIER.
	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 11 June 2022.		This Internet-Draft will expire on 10 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 (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
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Revised BSD License text as		extracted from this document must include Revised BSD License text as
	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.
	skipping to change at page 2, line 43 ¶		skipping to change at page 2, line 43 ¶
	2.1. IPv6 Options Considerations . . . . . . . . . . . . . . . 6		2.1. IPv6 Options Considerations . . . . . . . . . . . . . . . 6
	3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 6		3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. IPv6 Encapsulation Advertisement . . . . . . . . . . . . . . 6		4. IPv6 Encapsulation Advertisement . . . . . . . . . . . . . . 6
	4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 6		4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 6
	4.2. Inter-area prefix redistribution . . . . . . . . . . . . 7		4.2. Inter-area prefix redistribution . . . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 7		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 8
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	8.1. Normative References . . . . . . . . . . . . . . . . . . 8		8.1. Normative References . . . . . . . . . . . . . . . . . . 8
	8.2. Informative References . . . . . . . . . . . . . . . . . 8		8.2. Informative References . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	BIER [RFC8279] is a new architecture for the forwarding of multicast		BIER [RFC8279] is a new architecture for the forwarding of multicast
	data packets. It provides optimal forwarding through a "multicast		data packets. It provides optimal forwarding through a "multicast
	domain" and it does not precondition construction of a multicast		domain" and it does not precondition construction of a multicast
	distribution tree, nor does it require intermediate nodes to maintain		distribution tree, nor does it require intermediate nodes to maintain
	any per-flow state.		any per-flow state.
	skipping to change at page 4, line 20 ¶		skipping to change at page 4, line 20 ¶
	mandatory requirements.		mandatory requirements.
	For the two optional requirements for fragmentation and Encapsulating		For the two optional requirements for fragmentation and Encapsulating
	Security Payload (ESP), they can be satisfied by one of two ways:		Security Payload (ESP), they can be satisfied by one of two ways:
	* IPv6 based fragmentation/ESP: a BFIR encapsulates the payload in		* IPv6 based fragmentation/ESP: a BFIR encapsulates the payload in
	IPv6 with fragmentation and/or ESP header, and then the IPv6		IPv6 with fragmentation and/or ESP header, and then the IPv6
	packets are treated as BIER payload.		packets are treated as BIER payload.
	* Generic Fragmentation/ESP		* Generic Fragmentation/ESP
	[I-D.zzhang-tsvwg-generic-transport-functions]: a BFIR does		[I-D.zzhang-intarea-generic-delivery-functions]: a BFIR does
	generic fragmentation and/or ESP (without using IPv6		generic fragmentation and/or ESP (without using IPv6
	encapsulation) and the resulting packets are treated as BIER		encapsulation) and the resulting packets are treated as BIER
	payload.		payload.
	Either way, the fragmentation/ESP is handled by a layer outside of		Either way, the fragmentation/ESP is handled by a layer outside of
	BIER and then the resulting packets are treated as BIER payload.		BIER and then the resulting packets are treated as BIER payload.
	BIERin6 does support SRv6 based overlay services (e.g. MVPN/EVPN).		BIERin6 does support SRv6 based overlay services (e.g. MVPN/EVPN).
	One of the following methods can be used (relevant overlay signaling		One of the following methods can be used (relevant overlay signaling
	will be specified separately):		will be specified separately):
	skipping to change at page 4, line 43 ¶		skipping to change at page 4, line 43 ¶
	with an IPv6 header (with optional fragmentation and ESP extension		with an IPv6 header (with optional fragmentation and ESP extension
	headers). The destination address is a multicast locator plus the		headers). The destination address is a multicast locator plus the
	Fucn/Arg portion that identifies the service. That IPv6 packet is		Fucn/Arg portion that identifies the service. That IPv6 packet is
	then treated as BIER payload. An egress PE (which is a BFER) uses		then treated as BIER payload. An egress PE (which is a BFER) uses
	the standard SRv6 procedures to forward the IPv6 packet that is		the standard SRv6 procedures to forward the IPv6 packet that is
	exposed after the BIER header is decapsulated.		exposed after the BIER header is decapsulated.
	* Alternatively, since only the destination IPv6 address in the		* Alternatively, since only the destination IPv6 address in the
	above-mentioned IPv6 header is used for service delimiting		above-mentioned IPv6 header is used for service delimiting
	purpose, a new value can be assigned for the Proto field in the		purpose, a new value can be assigned for the Proto field in the
	BIER header to indicate that an IPv6 address (instead of an entire		BIER header to indicate that an SRv6 Service SID [I-D.ietf-bess-
	IPv6 header) is added between the BIER header and original		srv6-services] (instead of an entire IPv6 header) is added between
	payload.		the BIER header and original payload. The service SID serves the
			same purpose as a service-indicating MPLS label does. For
			example, an End.DT2/4/6 service SID could be used to route the
			original payload in a corresponding VRF.
	BIERin6 being a solution based on [RFC8279] [RFC8296], ECMP is		BIERin6 being a solution based on [RFC8279] [RFC8296], ECMP is
	inherently supported by BFRs using the the 20-bit entropy field in		inherently supported by BFRs using the the 20-bit entropy field in
	the BIER header for the load balancing hash. When a BIER packet is		the BIER header for the load balancing hash. When a BIER packet is
	transported over an IPv6 tunnel, the entropy value is copied into the		transported over an IPv6 tunnel, the entropy value is copied into the
	20-bit IPv6 Flow Label (instead of using local 5-tuple input key to a		20-bit IPv6 Flow Label (instead of using local 5-tuple input key to a
	hash function to locally generate the stateless 20-bit flow label) so		hash function to locally generate the stateless 20-bit flow label) so
	that routers along the tunnel can do ECMP based on Flow Labels. For		that routers along the tunnel can do ECMP based on Flow Labels. For
	a router along the tunnel doing deep packet inspection for ECMP		a router along the tunnel doing deep packet inspection for ECMP
	purpose, if it understands BIER header it can go past the BIER header		purpose, if it understands BIER header it can go past the BIER header
	skipping to change at page 7, line 41 ¶		skipping to change at page 7, line 41 ¶
	options" in the "ICMP code value" registry.		options" in the "ICMP code value" registry.
	IANA is requested to assign a new "BIER IPv6 transportation Sub-sub-		IANA is requested to assign a new "BIER IPv6 transportation Sub-sub-
	TLV" type in the "OSPFv3 BIER Ethernet Encapsulation sub-TLV"		TLV" type in the "OSPFv3 BIER Ethernet Encapsulation sub-TLV"
	Registry.		Registry.
	IANA is requested to set up a new "BIER IPv6 transportation Sub-sub-		IANA is requested to set up a new "BIER IPv6 transportation Sub-sub-
	sub-TLV" type in the "IS-IS BIER Ethernet Encapsulation sub-sub-TLV"		sub-TLV" type in the "IS-IS BIER Ethernet Encapsulation sub-sub-TLV"
	Registry.		Registry.
	IANA is requested to allocate a new value "IPv6 Address" from "BIER		IANA is requested to allocate a new value "SRv6 Service" from "BIER
	Next Protocol Identifiers" registry to indicate that an IPv6 address		Next Protocol Identifiers" registry to indicate that BIER payload
	is inserted between the BIER header and BIER payload.		starts with an SRv6 Service SID.
	6. Security Considerations		6. Security Considerations
	General IPv6 and BIER security considerations apply.		General IPv6 and BIER security considerations apply.
	7. Acknowledgement		7. Acknowledgement
	The authors would like to thank Tony Przygienda, Nagendra Kumar for		The authors would like to thank Tony Przygienda, Nagendra Kumar for
	their review and valuable comments.		their review and valuable comments.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
			[I-D.ietf-bess-srv6-services]
			Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R.,
			Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based
			Overlay Services", Work in Progress, Internet-Draft,
			draft-ietf-bess-srv6-services-08, 10 November 2021,
			<https://www.ietf.org/archive/id/draft-ietf-bess-srv6-
			services-08.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>.
	[RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme,		[RFC6437] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme,
	"IPv6 Flow Label Specification", RFC 6437,		"IPv6 Flow Label Specification", RFC 6437,
	DOI 10.17487/RFC6437, November 2011,		DOI 10.17487/RFC6437, November 2011,
	<https://www.rfc-editor.org/info/rfc6437>.		<https://www.rfc-editor.org/info/rfc6437>.
	skipping to change at page 10, line 32 ¶		skipping to change at page 10, line 39 ¶
	[I-D.ietf-bier-pmmm-oam]		[I-D.ietf-bier-pmmm-oam]
	Mirsky, G., Zheng, L., Chen, M., and G. Fioccola,		Mirsky, G., Zheng, L., Chen, M., and G. Fioccola,
	"Performance Measurement (PM) with Marking Method in Bit		"Performance Measurement (PM) with Marking Method in Bit
	Index Explicit Replication (BIER) Layer", Work in		Index Explicit Replication (BIER) Layer", Work in
	Progress, Internet-Draft, draft-ietf-bier-pmmm-oam-11, 4		Progress, Internet-Draft, draft-ietf-bier-pmmm-oam-11, 4
	October 2021, <https://www.ietf.org/archive/id/draft-ietf-		October 2021, <https://www.ietf.org/archive/id/draft-ietf-
	bier-pmmm-oam-11.txt>.		bier-pmmm-oam-11.txt>.
	[I-D.ietf-bier-prefix-redistribute]		[I-D.ietf-bier-prefix-redistribute]
	Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., and Y. Liu,		Zhang, Z., Wu, B., Zhang, Z., Wijnands, I., Liu, Y., and
	"BIER Prefix Redistribute", Work in Progress, Internet-		H. Bidgoli, "BIER Prefix Redistribute", Work in Progress,
	Draft, draft-ietf-bier-prefix-redistribute-00, 4 August		Internet-Draft, draft-ietf-bier-prefix-redistribute-01, 23
	2020, <https://www.ietf.org/archive/id/draft-ietf-bier-		December 2021, <https://www.ietf.org/archive/id/draft-
	prefix-redistribute-00.txt>.		ietf-bier-prefix-redistribute-01.txt>.
	[I-D.xzlnp-bier-ioam]		[I-D.xzlnp-bier-ioam]
	Min, X., Zhang, Z., Liu, Y., Nainar, N. K., and C.		Min, X., Zhang, Z., Liu, Y., Nainar, N. K., and C.
	Pignataro, "Bit Index Explicit Replication (BIER)		Pignataro, "Bit Index Explicit Replication (BIER)
	Encapsulation for In-situ OAM (IOAM) Data", Work in		Encapsulation for In-situ OAM (IOAM) Data", Work in
	Progress, Internet-Draft, draft-xzlnp-bier-ioam-02, 11		Progress, Internet-Draft, draft-xzlnp-bier-ioam-02, 11
	July 2021, <https://www.ietf.org/archive/id/draft-xzlnp-		July 2021, <https://www.ietf.org/archive/id/draft-xzlnp-
	bier-ioam-02.txt>.		bier-ioam-02.txt>.
	[I-D.zhang-bier-babel-extensions]		[I-D.zhang-bier-babel-extensions]
	Zhang, Z. and T. Przygienda, "BIER in BABEL", Work in		Zhang, Z. and T. Przygienda, "BIER in BABEL", Work in
	Progress, Internet-Draft, draft-zhang-bier-babel-		Progress, Internet-Draft, draft-zhang-bier-babel-
	extensions-06, 7 November 2021,		extensions-06, 7 November 2021,
	<https://www.ietf.org/archive/id/draft-zhang-bier-babel-		<https://www.ietf.org/archive/id/draft-zhang-bier-babel-
	extensions-06.txt>.		extensions-06.txt>.
	[I-D.zzhang-tsvwg-generic-transport-functions]		[I-D.zzhang-intarea-generic-delivery-functions]
	Zhang, Z., Bonica, R., and K. Kompella, "Generic Transport		Zhang, Z., Bonica, R., Kompella, K., and G. Mirsky,
	Functions", Work in Progress, Internet-Draft, draft-		"Generic Delivery Functions", Work in Progress, Internet-
	zzhang-tsvwg-generic-transport-functions-00, 1 November		Draft, draft-zzhang-intarea-generic-delivery-functions-02,
	2020, <https://www.ietf.org/archive/id/draft-zzhang-tsvwg-		25 August 2021, <https://www.ietf.org/archive/id/draft-
	generic-transport-functions-00.txt>.		zzhang-intarea-generic-delivery-functions-02.txt>.
	[RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J.		[RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J.
	Weil, "IPv6 Home Networking Architecture Principles",		Weil, "IPv6 Home Networking Architecture Principles",
	RFC 7368, DOI 10.17487/RFC7368, October 2014,		RFC 7368, DOI 10.17487/RFC7368, October 2014,
	<https://www.rfc-editor.org/info/rfc7368>.		<https://www.rfc-editor.org/info/rfc7368>.
	Authors' Addresses		Authors' Addresses
	Zheng(Sandy) Zhang		Zheng(Sandy) Zhang
	ZTE Corporation		ZTE Corporation
End of changes. 12 change blocks.
	24 lines changed or deleted		35 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/