< draft-xie-bier-ipv6-encapsulation-01.txt		draft-xie-bier-ipv6-encapsulation-02.txt >
	Network Working Group J. Xie		Network Working Group J. Xie
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track L. Geng		Intended status: Standards Track L. Geng
	Expires: December 21, 2019 China Mobile		Expires: January 2, 2020 China Mobile
	M. McBride		M. McBride
	Futurewei		Futurewei
			R. Asati
			Cisco
	S. Dhanaraj		S. Dhanaraj
	G. Yan		G. Yan
	Y. Xia		Y. Xia
	Huawei		Huawei
	June 19, 2019		July 1, 2019
	Encapsulation for BIER in Non-MPLS IPv6 Networks		Encapsulation for BIER in Non-MPLS IPv6 Networks
	draft-xie-bier-ipv6-encapsulation-01		draft-xie-bier-ipv6-encapsulation-02
	Abstract		Abstract
	This document proposes a BIER IPv6 (BIERv6) encapsulation for Non-		This document proposes a BIER IPv6 (BIERv6) encapsulation for Non-
	MPLS IPv6 Networks using the IPv6 Destination Option extension		MPLS IPv6 Networks using the IPv6 Destination Option extension
	header.		header.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 48 ¶
	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 December 21, 2019.		This Internet-Draft will expire on January 2, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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 2, line 27 ¶		skipping to change at page 2, line 27 ¶
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. BIER IPv6 Encapsulation . . . . . . . . . . . . . . . . . . . 3		3. BIER IPv6 Encapsulation . . . . . . . . . . . . . . . . . . . 3
	3.1. BIER Option in IPv6 Destination Options Header . . . . . 3		3.1. BIER Option in IPv6 Destination Options Header . . . . . 3
	3.2. Multicast and Unicast Destination Address . . . . . . . . 6		3.2. Multicast and Unicast Destination Address . . . . . . . . 6
	3.3. BIERv6 Packet Format . . . . . . . . . . . . . . . . . . 7		3.3. BIERv6 Packet Format . . . . . . . . . . . . . . . . . . 8
	4. BIERv6 Packet Processing . . . . . . . . . . . . . . . . . . 8		4. BIERv6 Packet Processing . . . . . . . . . . . . . . . . . . 9
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	6.1. BIER Option Type . . . . . . . . . . . . . . . . . . . . 10		6.1. BIER Option Type . . . . . . . . . . . . . . . . . . . . 11
	6.2. BIER Multicast Address . . . . . . . . . . . . . . . . . 11		6.2. BIER Multicast Address . . . . . . . . . . . . . . . . . 11
	6.3. End.BIER Function . . . . . . . . . . . . . . . . . . . . 11		6.3. End.BIER Function . . . . . . . . . . . . . . . . . . . . 12
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	8.1. Normative References . . . . . . . . . . . . . . . . . . 11		8.1. Normative References . . . . . . . . . . . . . . . . . . 12
	8.2. Informative References . . . . . . . . . . . . . . . . . 12		8.2. Informative References . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
	1. Introduction		1. Introduction
	Bit Index Explicit Replication (BIER) [RFC8279] is an architecture		Bit Index Explicit Replication (BIER) [RFC8279] is an architecture
	that provides optimal multicast forwarding without requiring		that provides optimal multicast forwarding without requiring
	intermediate routers to maintain any per-flow state by using a		intermediate routers to maintain any per-flow state by using a
	multicast-specific BIER header.		multicast-specific BIER header.
	[RFC8296] defines a common BIER Header format for MPLS and Non-MPLS		[RFC8296] defines a common BIER Header format for MPLS and Non-MPLS
	networks. It has defined two types of encapsulation methods using		networks. It has defined two types of encapsulation methods using
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	address and using this address as BFR prefix:		address and using this address as BFR prefix:
	# Config a BIER specific IPv6 address with 128-bit mask on loopback0.		# Config a BIER specific IPv6 address with 128-bit mask on loopback0.
	interface loopback0		interface loopback0
	ipv6 address 2019::AB37 128 End.BIER		ipv6 address 2019::AB37 128 End.BIER
	# Config the BIER-specific IPv6 address on loopback0 as BFR Prefix.		# Config the BIER-specific IPv6 address on loopback0 as BFR Prefix.
	bier sub-domain 6 ipv6-underlay		bier sub-domain 6 ipv6-underlay
	bfr-prefix interface loopback0		bfr-prefix interface loopback0
			The address used as "BIER specific" IPv6 address can be from inside
			the scope of an SRv6 Locator or outside the scope of the SRv6
			Locator(s) since it is a host prefix (128-bit prefix-length prefix).
			Each "BIER specific" address can be used in one or many sub-domains
			as BFR-prefix, such that it can be associated with one or many Multi-
			Topologies (MTs) or algorithms.
			More than one "BIER specific" address are also allowed as different
			BFR-prefix of more than one sub-domain, as described in section 2 of
			[RFC8279].
			The following is an example pseudo-code of the End.BIER function:
			1. IF NH = 60 AND HopLimit > 0 ;;Ref1
			2. IF (OptType1 = BIER) and (OptLength1 = HdrExtLen*8 + 4) ;;Ref2
			3. Lookup the BIER Header inside the BIER option TLV.
			4. Forward via the matched entry.
			5. ELSE
			6. Drop the packet.
			7. ELSE IF Last_NH = ICMPv6 ;;Ref3
			8. Send to CPU.
			9. ELSE
			10. Drop the packet.
			Ref1: Destination options header follows the IPv6 header directly and
			HopLimit is bigger than zero.
			Ref2: The first TLV is BIER type and is the only one in Destination
			options header.
			Ref3: An ICMPv6 packet using End.BIER as destination address.
	3.3. BIERv6 Packet Format		3.3. BIERv6 Packet Format
	As a multicast packet enters the BIER domain in a Non-MPLS IPv6		As a multicast packet enters the BIER domain in a Non-MPLS IPv6
	network, the multicast packet will be encapsulated with BIERv6		network, the multicast packet will be encapsulated with BIERv6
	Header.		Header.
	Typically a BIERv6 header would contain the Destination Options		Typically a BIERv6 header would contain the Destination Options
	Header as the only Extensions Header besides IPv6 Header. However,		Header as the only Extensions Header besides IPv6 Header. However,
	it is allowed and possible for other extension headers to appear		it is allowed and possible for other extension headers to appear
	along with the Destination Options Header as long as the requirements		along with the Destination Options Header as long as the requirements
	skipping to change at page 11, line 38 ¶		skipping to change at page 12, line 22 ¶
	| Value | Hex | Endpoint function | Reference |		| Value | Hex | Endpoint function | Reference |
	+-------+--------+--------------------------+------------+		+-------+--------+--------------------------+------------+
	| TBD | TBD | End.BIER | This draft |		| TBD | TBD | End.BIER | This draft |
	+-------+--------+--------------------------+------------+		+-------+--------+--------------------------+------------+
	Figure 3: End.BIER Function		Figure 3: End.BIER Function
	7. Acknowledgements		7. Acknowledgements
	The authors would like to thank Stig Venaas for his valuable		The authors would like to thank Stig Venaas for his valuable
	comments.		comments. Thanks IJsbrand Wijnands, Greg Shepherd, Tony Przygienda,
			Toerless Eckert, Jeffrey Zhang for the helpful comments to improve
			this document.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility		[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
	Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July		Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
	2011, <https://www.rfc-editor.org/info/rfc6275>.		2011, <https://www.rfc-editor.org/info/rfc6275>.
	[RFC7346] Droms, R., "IPv6 Multicast Address Scopes", RFC 7346,		[RFC7346] Droms, R., "IPv6 Multicast Address Scopes", RFC 7346,
	skipping to change at page 13, line 4 ¶		skipping to change at page 13, line 39 ¶
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	Authors' Addresses		Authors' Addresses
	Jingrong Xie		Jingrong Xie
	Huawei Technologies		Huawei Technologies
	Email: xiejingrong@huawei.com		Email: xiejingrong@huawei.com
	Liang Geng		Liang Geng
	China Mobile		China Mobile
	Beijing 10053		Beijing 10053
	Email: gengliang@chinamobile.com		Email: gengliang@chinamobile.com
	Mike McBride		Mike McBride
	Futurewei		Futurewei
	Email: mmcbride7@gmail.com		Email: mmcbride7@gmail.com
			Rajiv Asati
			Cisco
			Email: rajiva@cisco.com
	Senthil Dhanaraj		Senthil Dhanaraj
	Huawei		Huawei
	Email: senthil.dhanaraj@huawei.com		Email: senthil.dhanaraj@huawei.com
	Gang Yan		Gang Yan
	Huawei		Huawei
	Email: yangang@huawei.com		Email: yangang@huawei.com
End of changes. 11 change blocks.
	16 lines changed or deleted		58 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/