< draft-ietf-bier-mvpn-04.txt		draft-ietf-bier-mvpn-05.txt >
	Internet Engineering Task Force E. Rosen, Ed.		Internet Engineering Task Force E. Rosen, Ed.
	Internet-Draft Juniper Networks, Inc.		Internet-Draft Juniper Networks, Inc.
	Intended status: Standards Track M. Sivakumar		Intended status: Standards Track M. Sivakumar
	Expires: January 19, 2017 Cisco Systems, Inc.		Expires: July 14, 2017 Cisco Systems, Inc.
	S. Aldrin		S. Aldrin
	Google, Inc.		Google, Inc.
	A. Dolganow		A. Dolganow
	Nokia		Nokia
	T. Przygienda		T. Przygienda
	Juniper Networks, Inc.		Juniper Networks, Inc.
	July 18, 2016		January 10, 2017
	Multicast VPN Using BIER		Multicast VPN Using BIER
	draft-ietf-bier-mvpn-04		draft-ietf-bier-mvpn-05
	Abstract		Abstract
	The Multicast Virtual Private Network (MVPN) specifications require		The Multicast Virtual Private Network (MVPN) specifications require
	the use of multicast tunnels ("P-tunnels") that traverse a Service		the use of multicast tunnels ("P-tunnels") that traverse a Service
	Provider's backbone network. The P-tunnels are used for carrying		Provider's backbone network. The P-tunnels are used for carrying
	multicast traffic across the backbone. A variety of P-tunnel types		multicast traffic across the backbone. A variety of P-tunnel types
	are supported. Bit Index Explicit Replication (BIER) is a new		are supported. Bit Index Explicit Replication (BIER) is a new
	architecture that provides optimal multicast forwarding through a		architecture that provides optimal multicast forwarding through a
	"multicast domain", without requiring intermediate routers to		"multicast domain", without requiring intermediate routers to
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 January 19, 2017.		This Internet-Draft will expire on July 14, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 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
	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 11, line 18 ¶		skipping to change at page 11, line 18 ¶
	and [RFC6514] are applicable.		and [RFC6514] are applicable.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[BIER_ARCH]		[BIER_ARCH]
	Wijnands, IJ., Rosen, E., Dolganow, A., Przygienda, T.,		Wijnands, IJ., Rosen, E., Dolganow, A., Przygienda, T.,
	and S. Aldrin, "Multicast using Bit Index Explicit		and S. Aldrin, "Multicast using Bit Index Explicit
	Replication", internet-draft draft-ietf-bier-architecture-		Replication", internet-draft draft-ietf-bier-architecture-
	03, January 2016.		05, October 2016.
	[BIER_ENCAPS]		[BIER_ENCAPS]
	Wijnands, IJ., Rosen, E., Dolganow, A., Tantsura, J., and		Wijnands, IJ., 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", internet-draft draft-ietf-		Replication in MPLS Networks", internet-draft draft-ietf-
	bier-mpls-encapsulation-04.txt, April 2016.		bier-mpls-encapsulation-06.txt, December 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>.
	[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private		[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
	Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February		Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
	2006, <http://www.rfc-editor.org/info/rfc4364>.		2006, <http://www.rfc-editor.org/info/rfc4364>.
	skipping to change at page 12, line 10 ¶		skipping to change at page 12, line 10 ¶
	[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.		[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
	Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",		Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
	RFC 6625, DOI 10.17487/RFC6625, May 2012,		RFC 6625, DOI 10.17487/RFC6625, May 2012,
	<http://www.rfc-editor.org/info/rfc6625>.		<http://www.rfc-editor.org/info/rfc6625>.
	8.2. Informative References		8.2. Informative References
	[EXPLICIT_TRACKING]		[EXPLICIT_TRACKING]
	Dolganow, A., Kotalwar, J., Rosen, E., and Z. Zhang,		Dolganow, A., Kotalwar, J., Rosen, E., and Z. Zhang,
	"Explicit Tracking with Wild Card Routes in Multicast		"Explicit Tracking with Wild Card Routes in Multicast
	VPN", internet-draft draft-ietf-bess-mvpn-expl-track-00,		VPN", internet-draft draft-ietf-bess-mvpn-expl-track-01,
	June 2016.		December 2016.
	[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>.
	[RFC7900] Rekhter, Y., Ed., Rosen, E., Ed., Aggarwal, R., Cai, Y.,		[RFC7900] Rekhter, Y., Ed., Rosen, E., Ed., Aggarwal, R., Cai, Y.,
	and T. Morin, "Extranet Multicast in BGP/IP MPLS VPNs",		and T. Morin, "Extranet Multicast in BGP/IP MPLS VPNs",
	RFC 7900, DOI 10.17487/RFC7900, June 2016,		RFC 7900, DOI 10.17487/RFC7900, June 2016,
End of changes. 8 change blocks.
	9 lines changed or deleted		9 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/