Diff: draft-ietf-bier-use-cases-04.txt - draft-ietf-bier-use-cases-05.txt

	< draft-ietf-bier-use-cases-04.txt	draft-ietf-bier-use-cases-05.txt >

	Network Working Group N. Kumar	Network Working Group N. Kumar
	Internet-Draft R. Asati	Internet-Draft R. Asati
	Intended status: Informational Cisco	Intended status: Informational Cisco

	Expires: July 12, 2017 M. Chen	Expires: January 18, 2018 M. Chen
	X. Xu	X. Xu
	Huawei	Huawei
	A. Dolganow	A. Dolganow

	Alcatel-Lucent	Nokia
	T. Przygienda	T. Przygienda
	Ericsson	Ericsson
	A. Gulko	A. Gulko
	Thomson Reuters	Thomson Reuters
	D. Robinson	D. Robinson
	id3as-company Ltd	id3as-company Ltd
	V. Arya	V. Arya
	DirecTV Inc	DirecTV Inc
	C. Bestler	C. Bestler
	Nexenta	Nexenta

	January 8, 2017	July 17, 2017

	BIER Use Cases	BIER Use Cases

	draft-ietf-bier-use-cases-04 .txt	draft-ietf-bier-use-cases-05.txt

	Abstract	Abstract

	Bit Index Explicit Replication (BIER) is an architecture that	Bit Index Explicit Replication (BIER) is an architecture that
	provides optimal multicast forwarding through a "BIER domain" without	provides optimal multicast forwarding through a "BIER domain" without
	requiring intermediate routers to maintain any multicast related per-	requiring intermediate routers to maintain any multicast related per-
	flow state. BIER also does not require any explicit tree-building	flow state. BIER also does not require any explicit tree-building
	protocol for its operation. A multicast data packet enters a BIER	protocol for its operation. A multicast data packet enters a BIER
	domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the	domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
	BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).	BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).

	skipping to change at page 2, line 12 ¶	skipping to change at page 2, line 12 ¶
	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 July 12, 2017.	This Internet-Draft will expire on January 18, 2018.

	Copyright Notice	Copyright Notice

	Copyright (c) 2017 IETF Trust and the persons identified as the	Copyright (c) 2017 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 4, line 41 ¶	skipping to change at page 4, line 41 ¶
	procedures as defined in [RFC5331]. Also see [I-D.ietf-bier-mvpn]	procedures as defined in [RFC5331]. Also see [I-D.ietf-bier-mvpn]
	for more information.	for more information.

	With BIER only a few MVPN profiles will remain relevant, simplifying	With BIER only a few MVPN profiles will remain relevant, simplifying
	the operational cost and making it easier to be interoperable among	the operational cost and making it easier to be interoperable among
	different vendors.	different vendors.

	3.2. BUM in EVPN	3.2. BUM in EVPN

	The current widespread adoption of L2VPN services [RFC4664],	The current widespread adoption of L2VPN services [RFC4664],

	especially the upcoming EVPN solution [I-D.ietf-l2vpn-evpn] which	especially the upcoming EVPN solution [RFC7432] which transgresses
	transgresses many limitations of VPLS, introduces the need for an	many limitations of VPLS, introduces the need for an efficient
	efficient mechanism to replicate broadcast, unknown and multicast	mechanism to replicate broadcast, unknown and multicast (BUM) traffic
	(BUM) traffic towards the PEs that participate in the same EVPN	towards the PEs that participate in the same EVPN instances (EVIs).
	instances (EVIs). As simplest deployable mechanism, ingress	As simplest deployable mechanism, ingress replication is used but
	replication is used but poses accordingly a high burden on the	poses accordingly a high burden on the ingress node as well as
	ingress node as well as saturating the underlying links with many	saturating the underlying links with many copies of the same frame
	copies of the same frame headed to different PEs. Fortunately	headed to different PEs. Fortunately enough, EVPN signals internally
	enough, EVPN signals internally P-Multicast Service Interface (PMSI)	P-Multicast Service Interface (PMSI) [RFC6513] attribute to establish
	[RFC6513] attribute to establish transport for BUM frames and with	transport for BUM frames and with that allows to deploy a plethora of
	that allows to deploy a plethora of multicast replication services	multicast replication services that the underlying network layer can
	that the underlying network layer can provide. It is therefore	provide. It is therefore relatively simple to deploy BIER P-Tunnels
	relatively simple to deploy BIER P-Tunnels for EVPN and with that	for EVPN and with that distribute BUM traffic without building of
	distribute BUM traffic without building of P-router state in the core	P-router state in the core required by PIM, mLDP or comparable
	required by PIM, mLDP or comparable solutions.	solutions.

	Specifically, the same I-PMSI attribute suggested for mVPN can be	Specifically, the same I-PMSI attribute suggested for mVPN can be
	used easily in EVPN and given EVPN can multiplex and disassociate BUM	used easily in EVPN and given EVPN can multiplex and disassociate BUM
	frames on p2mp and mp2mp trees using upstream assigned labels, BIER	frames on p2mp and mp2mp trees using upstream assigned labels, BIER
	P-Tunnel will support BUM flooding for any number of EVIs over a	P-Tunnel will support BUM flooding for any number of EVIs over a
	single sub-domain for maximum scalability but allow at the other	single sub-domain for maximum scalability but allow at the other
	extreme of the spectrum to use a single BIER sub-domain per EVI if	extreme of the spectrum to use a single BIER sub-domain per EVI if
	such a deployment is necessary.	such a deployment is necessary.

	Multiplexing EVIs onto the same PMSI forces the PMSI to span more	Multiplexing EVIs onto the same PMSI forces the PMSI to span more

	skipping to change at page 14, line 25 ¶	skipping to change at page 14, line 25 ¶
	BIER", draft-ietf-bier-mvpn-01 (work in progress), July	BIER", draft-ietf-bier-mvpn-01 (work in progress), July
	2015.	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>.

	8.2. Informative References	8.2. Informative References


	[I-D.ietf-l2vpn-evpn]
	Sajassi, A., Aggarwal, R., Bitar, N., Isaac, A., and J.
	Uttaro, "BGP MPLS Based Ethernet VPN", draft-ietf-l2vpn-
	evpn-11 (work in progress), October 2014.

	[I-D.ietf-spring-segment-routing]	[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,	Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
	and r. rjs@rob.sh, "Segment Routing Architecture", draft-	and r. rjs@rob.sh, "Segment Routing Architecture", draft-
	ietf-spring-segment-routing-04 (work in progress), July	ietf-spring-segment-routing-04 (work in progress), July
	2015.	2015.

	[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,	[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
	"Protocol Independent Multicast - Sparse Mode (PIM-SM):	"Protocol Independent Multicast - Sparse Mode (PIM-SM):
	Protocol Specification (Revised)", RFC 4601,	Protocol Specification (Revised)", RFC 4601,
	DOI 10.17487/RFC4601, August 2006,	DOI 10.17487/RFC4601, August 2006,

	skipping to change at page 15, line 26 ¶	skipping to change at page 15, line 21 ¶
	BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February	BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
	2012, <http://www.rfc-editor.org/info/rfc6513>.	2012, <http://www.rfc-editor.org/info/rfc6513>.

	[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,	[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
	L., Sridhar, T., Bursell, M., and C. Wright, "Virtual	L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
	eXtensible Local Area Network (VXLAN): A Framework for	eXtensible Local Area Network (VXLAN): A Framework for
	Overlaying Virtualized Layer 2 Networks over Layer 3	Overlaying Virtualized Layer 2 Networks over Layer 3
	Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,	Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
	<http://www.rfc-editor.org/info/rfc7348>.	<http://www.rfc-editor.org/info/rfc7348>.


		[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
		Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
		Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
		2015, <http://www.rfc-editor.org/info/rfc7432>.

	Authors' Addresses	Authors' Addresses

	Nagendra Kumar	Nagendra Kumar
	Cisco	Cisco
	7200 Kit Creek Road	7200 Kit Creek Road
	Research Triangle Park, NC 27709	Research Triangle Park, NC 27709
	US	US

	Email: naikumar@cisco.com	Email: naikumar@cisco.com


	skipping to change at page 16, line 10 ¶	skipping to change at page 16, line 10 ¶
	Mach(Guoyi) Chen	Mach(Guoyi) Chen
	Huawei	Huawei

	Email: mach.chen@huawei.com	Email: mach.chen@huawei.com
	Xiaohu Xu	Xiaohu Xu
	Huawei	Huawei

	Email: xuxiaohu@huawei.com	Email: xuxiaohu@huawei.com

	Andrew Dolganow	Andrew Dolganow

	Alcatel-Lucent	Nokia
	600 March Road	750D Chai Chee Rd
	Ottawa, ON K2K2E6	06-06 Viva Business Park 469004
	Canada	Singapore


	Email: andrew.dolganow@alcatel-lucent.com	Email: andrew.dolganow@nokia.com

	Tony Przygienda	Tony Przygienda
	Ericsson	Ericsson
	300 Holger Way	300 Holger Way
	San Jose, CA 95134	San Jose, CA 95134
	USA	USA

	Email: antoni.przygienda@ericsson.com	Email: antoni.przygienda@ericsson.com

	Arkadiy Gulko	Arkadiy Gulko

End of changes. 10 change blocks.
	30 lines changed or deleted	30 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/