< draft-ietf-bier-php-03.txt		draft-ietf-bier-php-04.txt >
	BIER Z. Zhang		BIER Z. Zhang
	Internet-Draft Juniper Networks		Internet-Draft Juniper Networks
	Intended status: Standards Track October 3, 2019		Intended status: Standards Track October 31, 2019
	Expires: April 5, 2020		Expires: May 3, 2020
	BIER Penultimate Hop Popping		BIER Penultimate Hop Popping
	draft-ietf-bier-php-03		draft-ietf-bier-php-04
	Abstract		Abstract
	Bit Index Explicit Replication (BIER) can be used as provider tunnel		Bit Index Explicit Replication (BIER) can be used as provider tunnel
	for Multicast Virtual Private Network (MVPN) [RFC6514], Global		for Multicast Virtual Private Network (MVPN) [RFC6514], Global
	Table Multicast [RFC7716] or Ethernet Virtual Private Network (EVPN)		Table Multicast [RFC7716] or Ethernet Virtual Private Network (EVPN)
	[RFC7432]. It is possible that not all routers in the provider		[RFC7432]. It is possible that not all routers in the provider
	network support BIER and there are various methods to handle BIER		network support BIER and there are various methods to handle BIER
	incapable transit routers. However those methods assume the MVPN/		incapable transit routers. However those methods assume the MVPN/
	EVPN Provider Edges (PEs) are BIER capable. This document specifies		EVPN Provider Edges (PEs) are BIER capable. This document specifies
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 April 5, 2020.		This Internet-Draft will expire on May 3, 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 3, line 24 ¶		skipping to change at page 3, line 24 ¶
	The transition of an existing MVPN/EVPN deployment with traditional		The transition of an existing MVPN/EVPN deployment with traditional
	provider tunnels to using BIER with some PEs not capable of receiving		provider tunnels to using BIER with some PEs not capable of receiving
	BIER packets can be incremental. All PEs are first upgraded to		BIER packets can be incremental. All PEs are first upgraded to
	support BIER at least in the control plane, with those not capable of		support BIER at least in the control plane, with those not capable of
	BIER forwarding requesting PHP. Then BIER capable ingress PEs		BIER forwarding requesting PHP. Then BIER capable ingress PEs
	independently and incrementally switch to BIER transport.		independently and incrementally switch to BIER transport.
	While the above text uses MVPN/EVPN as example, BIER PHP is		While the above text uses MVPN/EVPN as example, BIER PHP is
	applicable to any scenario where the multicast flow overlay edge		applicable to any scenario where the multicast flow overlay edge
	router does not support BIER, as long as the edge router does not		router does not support BIER, as long as the edge router does not
	need to know the transmitting BFIR.		need to know the transmitting BFIR or participate in BIER OAM
			procedures.
	This works well if a BIER incapable PE only needs to receive		This works well if a BIER incapable PE only needs to receive
	multicast traffic. If it needs to send multicast traffic as well,		multicast traffic. If it needs to send multicast traffic as well,
	then it must Ingress Replicate to a BIER capable helper PE, who will		then it must Ingress Replicate to a BIER capable helper PE, who will
	in turn relay the packet to other PEs. The helper PE is either a		in turn relay the packet to other PEs. The helper PE is either a
	Virtual Hub as specified in [RFC7024] for MVPN and [I-D.keyupate-		Virtual Hub as specified in [RFC7024] for MVPN and [I-D.keyupate-
	bess-evpn-virtual-hub] for EVPN, or an AR-Replicator as specified in		bess-evpn-virtual-hub] for EVPN, or an AR-Replicator as specified in
	[I-D.ietf-bess-evpn-optimized-ir] for EVPN.		[I-D.ietf-bess-evpn-optimized-ir] for EVPN.
	2. Specifications		2. Specifications
	The procedures in this section apply only if, by means outside the		The procedures in this section apply only if, by means outside the
	scope of this document, it is known that the payload after BIER		scope of this document, it is known that the payload after BIER
	header is one of the following:		header is one of the following:
	o MPLS packets with downstream-assigned label at top of stack (i.e.,		o MPLS packets with downstream-assigned label at top of stack (i.e.,
	the Proto field in the BIER header is 1). For example, a label		the Proto field in the BIER header is 1). For example, a label
	from a Domain-wide Common Block (DCB) is used as specified in [I-		from a Domain-wide Common Block (DCB) is used as specified in [I-
	D.ietf-bess-mvpn-evpn-aggregation-label].		D.ietf-bess-mvpn-evpn-aggregation-label].
	o Packets with VXLAN/NVGRE/GENEVE header [I-D.ietf-bier-evpn] (i.e.		o IPv4/IPv6 multicast packets for which Reverse Path Forwarding
	the Proto field in the BIER header specifies VXLAN/NVGRE/GENEVE		check is disabled.
	per IANA assignments to be done for [I-D.ietf-bier-evpn]).
	A BIER incapable router, if acting as a multicast flow overlay		A BIER incapable router, if acting as a multicast flow overlay
	router, MUST signal its BIER information as specified in [RFC8401] or		router, MUST signal its BIER information as specified in [RFC8401] or
	[RFC8444] or [I-D.ietf-bier-idr-extensions], with a PHP sub-sub-TLV		[RFC8444] or [I-D.ietf-bier-idr-extensions], with a PHP sub-sub-TLV
	included in the BIER sub-TLV attached to the BIER incapable router's		included in the BIER sub-TLV attached to the BIER incapable router's
	BIER prefix to request BIER PHP from other BFRs. The sub-sub-TLV's		BIER prefix to request BIER PHP from other BFRs. The sub-sub-TLV's
	type is TBD, and the length is 0.		type is TBD, and the length is 0.
	With MPLS encapsulation, the BIER incapable multicast flow overlay		With MPLS encapsulation, the BIER incapable multicast flow overlay
	router MAY omit the BIER MPLS Encapsulation sub-sub-TLV, or MUST set		router MAY omit the BIER MPLS Encapsulation sub-sub-TLV, or MUST set
	skipping to change at page 5, line 23 ¶		skipping to change at page 5, line 23 ¶
	Senthil Dhanaraj for his suggestion of requesting PHP if a BFER does		Senthil Dhanaraj for his suggestion of requesting PHP if a BFER does
	not support certain BSL.		not support certain BSL.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[I-D.ietf-bess-mvpn-evpn-aggregation-label]		[I-D.ietf-bess-mvpn-evpn-aggregation-label]
	Zhang, Z., Rosen, E., Lin, W., Li, Z., and I. Wijnands,		Zhang, Z., Rosen, E., Lin, W., Li, Z., and I. Wijnands,
	"MVPN/EVPN Tunnel Aggregation with Common Labels", draft-		"MVPN/EVPN Tunnel Aggregation with Common Labels", draft-
	ietf-bess-mvpn-evpn-aggregation-label-02 (work in		ietf-bess-mvpn-evpn-aggregation-label-03 (work in
	progress), December 2018.		progress), October 2019.
	[I-D.ietf-bier-evpn]		[I-D.ietf-bier-evpn]
	Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,		Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan,
	"EVPN BUM Using BIER", draft-ietf-bier-evpn-01 (work in		"EVPN BUM Using BIER", draft-ietf-bier-evpn-01 (work in
	progress), April 2018.		progress), April 2018.
	[I-D.ietf-bier-idr-extensions]		[I-D.ietf-bier-idr-extensions]
	Xu, X., Chen, M., Patel, K., Wijnands, I., and T.		Xu, X., Chen, M., Patel, K., Wijnands, I., and T.
	Przygienda, "BGP Extensions for BIER", draft-ietf-bier-		Przygienda, "BGP Extensions for BIER", draft-ietf-bier-
	idr-extensions-07 (work in progress), September 2019.		idr-extensions-07 (work in progress), September 2019.
End of changes. 6 change blocks.
	10 lines changed or deleted		10 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/