< draft-ietf-bier-use-cases-05.txt		draft-ietf-bier-use-cases-06.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: January 18, 2018 M. Chen		Expires: July 20, 2018 M. Chen
	X. Xu		X. Xu
	Huawei		Huawei
	A. Dolganow		A. Dolganow
	Nokia		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
	July 17, 2017		January 16, 2018
	BIER Use Cases		BIER Use Cases
	draft-ietf-bier-use-cases-05.txt		draft-ietf-bier-use-cases-06.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 5 ¶		skipping to change at page 2, line 5 ¶
	This document describes some of the use-cases for BIER.		This document describes some of the use-cases for BIER.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 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 January 18, 2018.		This Internet-Draft will expire on July 20, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2018 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		(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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	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 . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 14, line 21 ¶		skipping to change at page 14, line 21 ¶
	[I-D.ietf-bier-mvpn]		[I-D.ietf-bier-mvpn]
	Rosen, E., Sivakumar, M., Wijnands, I., Aldrin, S.,		Rosen, E., Sivakumar, M., Wijnands, I., Aldrin, S.,
	Dolganow, A., and T. Przygienda, "Multicast VPN Using		Dolganow, A., and T. Przygienda, "Multicast VPN Using
	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>.		<https://www.rfc-editor.org/info/rfc2119>.
	8.2. Informative References		8.2. Informative References
	[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,
	<http://www.rfc-editor.org/info/rfc4601>.		<https://www.rfc-editor.org/info/rfc4601>.
	[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for		[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
	IP", RFC 4607, DOI 10.17487/RFC4607, August 2006,		IP", RFC 4607, DOI 10.17487/RFC4607, August 2006,
	<http://www.rfc-editor.org/info/rfc4607>.		<https://www.rfc-editor.org/info/rfc4607>.
	[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer		[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer
	2 Virtual Private Networks (L2VPNs)", RFC 4664,		2 Virtual Private Networks (L2VPNs)", RFC 4664,
	DOI 10.17487/RFC4664, September 2006,		DOI 10.17487/RFC4664, September 2006,
	<http://www.rfc-editor.org/info/rfc4664>.		<https://www.rfc-editor.org/info/rfc4664>.
	[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,		[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
	"Bidirectional Protocol Independent Multicast (BIDIR-		"Bidirectional Protocol Independent Multicast (BIDIR-
	PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,		PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
	<http://www.rfc-editor.org/info/rfc5015>.		<https://www.rfc-editor.org/info/rfc5015>.
	[RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream		[RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream
	Label Assignment and Context-Specific Label Space",		Label Assignment and Context-Specific Label Space",
	RFC 5331, DOI 10.17487/RFC5331, August 2008,		RFC 5331, DOI 10.17487/RFC5331, August 2008,
	<http://www.rfc-editor.org/info/rfc5331>.		<https://www.rfc-editor.org/info/rfc5331>.
	[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/		[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
	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, <https://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>.		<https://www.rfc-editor.org/info/rfc7348>.
	[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,		[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
	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, <https://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
End of changes. 16 change blocks.
	16 lines changed or deleted		16 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/