< draft-ietf-bier-idr-extensions-00.txt		draft-ietf-bier-idr-extensions-01.txt >
	Network Working Group X. Xu		Network Working Group X. Xu, Ed.
	Internet-Draft M. Chen		Internet-Draft M. Chen
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: March 26, 2016 K. Patel		Expires: January 1, 2017 K. Patel
	I. Wijnands		I. Wijnands
	Cisco		Cisco
	A. Przygienda		A. Przygienda
	Ericsson		Juniper
	September 23, 2015		June 30, 2016
	BGP Extensions for BIER		BGP Extensions for BIER
	draft-ietf-bier-idr-extensions-00		draft-ietf-bier-idr-extensions-01
	Abstract		Abstract
	Bit Index Explicit Replication (BIER) is a new multicast forwarding		Bit Index Explicit Replication (BIER) is a new multicast forwarding
	architecture which doesn't require an explicit tree-building protocol		architecture which doesn't require an explicit tree-building protocol
	and doesn't require intermediate routers to maintain any multicast		and doesn't require intermediate routers to maintain any multicast
	state. BIER is applicable in a multi-tenant data center network		state. BIER is applicable in a multi-tenant data center network
	environment for efficient delivery of Broadcast, Unknown-unicast and		environment for efficient delivery of Broadcast, Unknown-unicast and
	Multicast (BUM) traffic while eliminating the need for maintaining a		Multicast (BUM) traffic while eliminating the need for maintaining a
	huge amount of multicast state in the underlay. This document		huge amount of multicast state in the underlay. This document
	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 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 March 26, 2016.		This Internet-Draft will expire on January 1, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 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
	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
	skipping to change at page 6, line 21 ¶		skipping to change at page 6, line 21 ¶
	This document introduces no new security considerations beyond those		This document introduces no new security considerations beyond those
	already specified in [RFC4271].		already specified in [RFC4271].
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[I-D.ietf-bier-architecture]		[I-D.ietf-bier-architecture]
	Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and		Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
	S. Aldrin, "Multicast using Bit Index Explicit		S. Aldrin, "Multicast using Bit Index Explicit
	Replication", draft-ietf-bier-architecture-02 (work in		Replication", draft-ietf-bier-architecture-03 (work in
	progress), July 2015.		progress), January 2016.
	[I-D.ietf-bier-mpls-encapsulation]		[I-D.ietf-bier-mpls-encapsulation]
	Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and		Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and
	S. Aldrin, "Encapsulation for Bit Index Explicit		S. Aldrin, "Encapsulation for Bit Index Explicit
	Replication in MPLS Networks", draft-ietf-bier-mpls-		Replication in MPLS Networks", draft-ietf-bier-mpls-
	encapsulation-02 (work in progress), August 2015.		encapsulation-04 (work in progress), April 2016.
	[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>.
	[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A		[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
	Border Gateway Protocol 4 (BGP-4)", RFC 4271,		Border Gateway Protocol 4 (BGP-4)", RFC 4271,
	DOI 10.17487/RFC4271, January 2006,		DOI 10.17487/RFC4271, January 2006,
	<http://www.rfc-editor.org/info/rfc4271>.		<http://www.rfc-editor.org/info/rfc4271>.
	10.2. Informative References		10.2. Informative References
	[I-D.ietf-bier-use-cases]		[I-D.ietf-bier-use-cases]
	Kumar, N., Asati, R., Chen, M., Xu, X., Dolganow, A.,		Kumar, N., Asati, R., Chen, M., Xu, X., Dolganow, A.,
	Przygienda, T., arkadiy.gulko@thomsonreuters.com, a.,		Przygienda, T., arkadiy.gulko@thomsonreuters.com, a.,
	Robinson, D., and V. Arya, "BIER Use Cases", draft-ietf-		Robinson, D., Arya, V., and C. Bestler, "BIER Use Cases",
	bier-use-cases-01 (work in progress), August 2015.		draft-ietf-bier-use-cases-02 (work in progress), January
			2016.
	[I-D.ietf-rtgwg-bgp-routing-large-dc]		[I-D.ietf-rtgwg-bgp-routing-large-dc]
	Lapukhov, P., Premji, A., and J. Mitchell, "Use of BGP for		Lapukhov, P., Premji, A., and J. Mitchell, "Use of BGP for
	routing in large-scale data centers", draft-ietf-rtgwg-		routing in large-scale data centers", draft-ietf-rtgwg-
	bgp-routing-large-dc-07 (work in progress), August 2015.		bgp-routing-large-dc-11 (work in progress), June 2016.
	Authors' Addresses		Authors' Addresses
	Xiaohu Xu		Xiaohu Xu (editor)
	Huawei		Huawei
	Email: xuxiaohu@huawei.com		Email: xuxiaohu@huawei.com
	Mach Chen		Mach Chen
	Huawei		Huawei
	Email: mach.chen@huawei.com		Email: mach.chen@huawei.com
	Keyur Patel		Keyur Patel
	Cisco		Cisco
	Email: keyupate@cisco.com		Email: keyupate@cisco.com
	IJsbrand Wijnands		IJsbrand Wijnands
	Cisco		Cisco
	Email: ice@cisco.com		Email: ice@cisco.com
	Antoni Przygienda		Antoni Przygienda
	Ericsson		Juniper
	Email: antoni.przygienda@ericsson.com		Email: prz@juniper.net
End of changes. 13 change blocks.
	15 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/