< draft-ietf-bess-evpn-bum-procedure-updates-00.txt		draft-ietf-bess-evpn-bum-procedure-updates-01.txt >
	BESS Z. Zhang		BESS Z. Zhang
	Internet-Draft W. Lin		Internet-Draft W. Lin
	Updates: 7432 (if approved) Juniper Networks		Updates: 7432 (if approved) Juniper Networks
	Intended status: Standards Track J. Rabadan		Intended status: Standards Track J. Rabadan
	Expires: April 21, 2017 Nokia		Expires: June 17, 2017 Nokia
	K. Patel		K. Patel
	Cisco Systems		Cisco Systems
	October 18, 2016		December 14, 2016
	Updates on EVPN BUM Procedures		Updates on EVPN BUM Procedures
	draft-ietf-bess-evpn-bum-procedure-updates-00		draft-ietf-bess-evpn-bum-procedure-updates-01
	Abstract		Abstract
	This document specifies procedure updates for broadcast, unknown		This document specifies procedure updates for broadcast, unknown
	unicast, and multicast (BUM) traffic in Ethernet VPNs (EVPN),		unicast, and multicast (BUM) traffic in Ethernet VPNs (EVPN),
	including selective multicast, and provider tunnel segmentation.		including selective multicast, and provider tunnel segmentation.
	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 42 ¶		skipping to change at page 1, line 42 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 21, 2017.		This Internet-Draft will expire on June 17, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 35 ¶		skipping to change at page 2, line 35 ¶
	5. Inter-AS Segmentation . . . . . . . . . . . . . . . . . . . . 7		5. Inter-AS Segmentation . . . . . . . . . . . . . . . . . . . . 7
	5.1. Changes to Section 7.2.2 of RFC 7117 . . . . . . . . . . 7		5.1. Changes to Section 7.2.2 of RFC 7117 . . . . . . . . . . 7
	5.2. I-PMSI Leaf Tracking . . . . . . . . . . . . . . . . . . 8		5.2. I-PMSI Leaf Tracking . . . . . . . . . . . . . . . . . . 8
	5.3. Backward Compatibility . . . . . . . . . . . . . . . . . 9		5.3. Backward Compatibility . . . . . . . . . . . . . . . . . 9
	6. Inter-Region Segmentation . . . . . . . . . . . . . . . . . . 10		6. Inter-Region Segmentation . . . . . . . . . . . . . . . . . . 10
	6.1. Area vs. Region . . . . . . . . . . . . . . . . . . . . . 10		6.1. Area vs. Region . . . . . . . . . . . . . . . . . . . . . 10
	6.2. Per-region Aggregation . . . . . . . . . . . . . . . . . 12		6.2. Per-region Aggregation . . . . . . . . . . . . . . . . . 12
	6.3. Use of S-NH-EC . . . . . . . . . . . . . . . . . . . . . 13		6.3. Use of S-NH-EC . . . . . . . . . . . . . . . . . . . . . 13
	6.4. Ingress PE's I-PMSI Leaf Tracking . . . . . . . . . . . . 13		6.4. Ingress PE's I-PMSI Leaf Tracking . . . . . . . . . . . . 13
	7. Multi-homing Support . . . . . . . . . . . . . . . . . . . . 13		7. Multi-homing Support . . . . . . . . . . . . . . . . . . . . 13
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 14		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14		9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14		10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14		11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
	11.1. Normative References . . . . . . . . . . . . . . . . . . 14		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
	11.2. Informative References . . . . . . . . . . . . . . . . . 15		12.1. Normative References . . . . . . . . . . . . . . . . . . 15
			12.2. Informative References . . . . . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Terminology		1. Terminology
	To be added		To be added
	2. Introduction		2. Introduction
	RFC 7432 specifies procedures to handle broadcast, unknown unicast,		RFC 7432 specifies procedures to handle broadcast, unknown unicast,
	and multicast (BUM) traffic in Section 11, 12 and 16, using Inclusive		and multicast (BUM) traffic in Section 11, 12 and 16, using Inclusive
	skipping to change at page 5, line 29 ¶		skipping to change at page 5, line 29 ¶
	So far five types have been defined:		So far five types have been defined:
	+ 1 - Ethernet Auto-Discovery (A-D) route		+ 1 - Ethernet Auto-Discovery (A-D) route
	+ 2 - MAC/IP Advertisement route		+ 2 - MAC/IP Advertisement route
	+ 3 - Inclusive Multicast Ethernet Tag route		+ 3 - Inclusive Multicast Ethernet Tag route
	+ 4 - Ethernet Segment route		+ 4 - Ethernet Segment route
	+ 5 - IP Prefix Route		+ 5 - IP Prefix Route
	This document defines three additional route types:		This document defines three additional route types:
	+ 6 - Per-Region I-PMSI A-D route		+ 9 - Per-Region I-PMSI A-D route
	+ 7 - S-PMSI A-D route		+ 10 - S-PMSI A-D route
	+ 8 - Leaf A-D route		+ 11 - Leaf A-D route
	The "Route Type specific" field of the type 6 and type 7 EVPN NLRIs		The "Route Type specific" field of the type 6 and type 7 EVPN NLRIs
	starts with a type 1 RD, whose Administrative sub-field MUST match		starts with a type 1 RD, whose Administrative sub-field MUST match
	that of the RD in all the EVPN routes from the same advertising		that of the RD in all the EVPN routes from the same advertising
	router for a given EVI, except the Leaf A-D route (Section 3.3).		router for a given EVI, except the Leaf A-D route (Section 3.3).
	3.1. Per-Region I-PMSI A-D route		3.1. Per-Region I-PMSI A-D route
	The Per-region I-PMSI A-D route has the following format. Its usage		The Per-region I-PMSI A-D route has the following format. Its usage
	is discussed in Section 6.2.		is discussed in Section 6.2.
	skipping to change at page 13, line 45 ¶		skipping to change at page 13, line 45 ¶
	not set the LIR flag in its originated I-PMSI A-D routes, and		not set the LIR flag in its originated I-PMSI A-D routes, and
	determines the leaves based on the BGP next hops in its received		determines the leaves based on the BGP next hops in its received
	I-PMSI A-D routes, as specified in Section 5.2.		I-PMSI A-D routes, as specified in Section 5.2.
	The same backward compatibility issue exists, and the same solution		The same backward compatibility issue exists, and the same solution
	as in the inter-as case applies, as specified in Section 5.3.		as in the inter-as case applies, as specified in Section 5.3.
	7. Multi-homing Support		7. Multi-homing Support
	If multi-homing does not span across different ASes or regions,		If multi-homing does not span across different ASes or regions,
	existing procedures work with segmentation. If an ES is multi-homed		existing procedures work with segmentation, and a segmentation point
			will remove the ESI label from the packets. If an ES is multi-homed
	to PEs in different ASes or regions, additional procedures are needed		to PEs in different ASes or regions, additional procedures are needed
	to work with segmentation. The procedures are well understood but		to work with segmentation. The procedures are well understood but
	omitted here until the requirement becomes clear.		omitted here until the requirement becomes clear.
	8. Security Considerations		8. IANA Considerations
			This document requests IANA to assign the following new EVPN route
			types:
			o 9 - Per-Region I-PMSI A-D route
			o 10 - S-PMSI A-D route
			o 11 - Leaf A-D route
			9. Security Considerations
	This document does not seem to introduce new security risks, though		This document does not seem to introduce new security risks, though
	this may be revised after further review and scrutiny.		this may be revised after further review and scrutiny.
	9. Acknowledgements		10. Acknowledgements
	The authors thank Eric Rosen, John Drake, and Ron Bonica for their		The authors thank Eric Rosen, John Drake, and Ron Bonica for their
	comments and suggestions.		comments and suggestions.
	10. Contributors		11. Contributors
	The following also contributed to this document through their earlier		The following also contributed to this document through their earlier
	work in EVPN selective multicast.		work in EVPN selective multicast.
	Junlin Zhang		Junlin Zhang
	Huawei Technologies		Huawei Technologies
	Huawei Bld., No.156 Beiqing Rd.		Huawei Bld., No.156 Beiqing Rd.
	Beijing 100095		Beijing 100095
	China		China
	Email: jackey.zhang@huawei.com		Email: jackey.zhang@huawei.com
	Zhenbin Li		Zhenbin Li
	Huawei Technologies		Huawei Technologies
	Huawei Bld., No.156 Beiqing Rd.		Huawei Bld., No.156 Beiqing Rd.
	Beijing 100095		Beijing 100095
	China		China
	Email: lizhenbin@huawei.com		Email: lizhenbin@huawei.com
	11. References		12. References
			12.1. Normative References
	11.1. Normative References
	[I-D.ietf-bess-ir]		[I-D.ietf-bess-ir]
	Rosen, E., Subramanian, K., and J. Zhang, "Ingress		Rosen, E., Subramanian, K., and J. Zhang, "Ingress
	Replication Tunnels in Multicast VPN", draft-ietf-bess-		Replication Tunnels in Multicast VPN", draft-ietf-bess-
	ir-00 (work in progress), January 2015.		ir-00 (work in progress), January 2015.
	[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,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	skipping to change at page 15, line 21 ¶		skipping to change at page 15, line 32 ¶
	Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based		Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
	Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February		Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
	2015, <http://www.rfc-editor.org/info/rfc7432>.		2015, <http://www.rfc-editor.org/info/rfc7432>.
	[RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T.,		[RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T.,
	Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area		Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area
	Point-to-Multipoint (P2MP) Segmented Label Switched Paths		Point-to-Multipoint (P2MP) Segmented Label Switched Paths
	(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,		(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,
	<http://www.rfc-editor.org/info/rfc7524>.		<http://www.rfc-editor.org/info/rfc7524>.
	11.2. Informative References		12.2. Informative References
	[I-D.ietf-bess-dci-evpn-overlay]		[I-D.ietf-bess-dci-evpn-overlay]
	Rabadan, J., Sathappan, S., Henderickx, W., Palislamovic,		Rabadan, J., Sathappan, S., Henderickx, W., Palislamovic,
	S., Balus, F., Sajassi, A., and D. Cai, "Interconnect		S., Balus, F., Sajassi, A., and D. Cai, "Interconnect
	Solution for EVPN Overlay networks", draft-ietf-bess-dci-		Solution for EVPN Overlay networks", draft-ietf-bess-dci-
	evpn-overlay-00 (work in progress), January 2015.		evpn-overlay-00 (work in progress), January 2015.
	[I-D.ietf-bess-evpn-overlay]		[I-D.ietf-bess-evpn-overlay]
	Sajassi, A., Drake, J., Bitar, N., Isaac, A., Uttaro, J.,		Sajassi, A., Drake, J., Bitar, N., Isaac, A., Uttaro, J.,
	and W. Henderickx, "A Network Virtualization Overlay		and W. Henderickx, "A Network Virtualization Overlay
End of changes. 12 change blocks.
	21 lines changed or deleted		33 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/