< draft-ietf-bier-mvpn-01.txt		draft-ietf-bier-mvpn-02.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 7, 2016 IJ. Wijnands		Expires: June 30, 2016 Cisco Systems, Inc.
	Cisco Systems, Inc.
	S. Aldrin		S. Aldrin
	Google, Inc.		Google, Inc.
	A. Dolganow		A. Dolganow
	Alcatel-Lucent		Alcatel-Lucent
	T. Przygienda		T. Przygienda
	Ericsson		Ericsson
	July 6, 2015		December 28, 2015
	Multicast VPN Using BIER		Multicast VPN Using BIER
	draft-ietf-bier-mvpn-01		draft-ietf-bier-mvpn-02
	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 48 ¶		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 7, 2016.		This Internet-Draft will expire on June 30, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 32 ¶		skipping to change at page 2, line 32 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Use of the PMSI Tunnel Attribute . . . . . . . . . . . . . . 4		2. Use of the PMSI Tunnel Attribute . . . . . . . . . . . . . . 4
	3. Explicit Tracking . . . . . . . . . . . . . . . . . . . . . . 6		3. Explicit Tracking . . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Using the LIR Flag . . . . . . . . . . . . . . . . . . . 7		3.1. Using the LIR Flag . . . . . . . . . . . . . . . . . . . 7
	3.2. Using the LIR-pF Flag . . . . . . . . . . . . . . . . . . 7		3.2. Using the LIR-pF Flag . . . . . . . . . . . . . . . . . . 7
	4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.1. Encapsulation and Transmission . . . . . . . . . . . . . 8		4.1. Encapsulation and Transmission . . . . . . . . . . . . . 8
	4.2. Disposition . . . . . . . . . . . . . . . . . . . . . . . 9		4.2. Disposition . . . . . . . . . . . . . . . . . . . . . . . 9
	4.2.1. At a BFER that is an Egress PE . . . . . . . . . . . 9		4.2.1. At a BFER that is an Egress PE . . . . . . . . . . . 9
	4.2.2. At a BFER that is a P-tunnel Segmentation Boundary . 9		4.2.2. At a BFER that is a P-tunnel Segmentation Boundary . 9
	5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		5. Contributor Addresses . . . . . . . . . . . . . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 10		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	8.1. Normative References . . . . . . . . . . . . . . . . . . 10		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	8.2. Informative References . . . . . . . . . . . . . . . . . 11		9.1. Normative References . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		9.2. Informative References . . . . . . . . . . . . . . . . . 11
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
	1. Introduction		1. Introduction
	[RFC6513] and [RFC6514] specify the protocols and procedures that a		[RFC6513] and [RFC6514] specify the protocols and procedures that a
	Service Provider (SP) can use to provide Multicast Virtual Private		Service Provider (SP) can use to provide Multicast Virtual Private
	Network (MVPN) service to its customers. Multicast tunnels are		Network (MVPN) service to its customers. Multicast tunnels are
	created through an SP's backbone network; these are known as		created through an SP's backbone network; these are known as
	"P-tunnels". The P-tunnels are used for carrying multicast traffic		"P-tunnels". The P-tunnels are used for carrying multicast traffic
	across the backbone. The MVPN specifications allow the use of		across the backbone. The MVPN specifications allow the use of
	several different kinds of P-tunnel technology.		several different kinds of P-tunnel technology.
	skipping to change at page 10, line 7 ¶		skipping to change at page 10, line 7 ¶
	its next P-tunnel segment. The choice of the next P-tunnel segment		its next P-tunnel segment. The choice of the next P-tunnel segment
	for the packet depends upon the C-flow to which the packet belongs.		for the packet depends upon the C-flow to which the packet belongs.
	Since the BFIR assigns a distinct upstream-assigned MPLS label for		Since the BFIR assigns a distinct upstream-assigned MPLS label for
	each C-flow, the BFER can select the proper "next P-tunnel segment"		each C-flow, the BFER can select the proper "next P-tunnel segment"
	for a given packet simply by looking up the upstream-assigned label		for a given packet simply by looking up the upstream-assigned label
	that immediately follows the BIER header. (If the BFIR had not		that immediately follows the BIER header. (If the BFIR had not
	assigned a distinct label to each C-flow, the BFER would need to		assigned a distinct label to each C-flow, the BFER would need to
	maintain all the state from the Multicast Flow Overlay in order to		maintain all the state from the Multicast Flow Overlay in order to
	select the next P-tunnel segment.)		select the next P-tunnel segment.)
	5. Acknowledgments		5. Contributor Addresses
			Below is a list of other contributing authors in alphabetical order:
			IJsbrand Wijnands
			Cisco Systems, Inc.
			De Kleetlaan 6a
			Diegem 1831
			Belgium
			Email: ice@cisco.com
			6. Acknowledgments
	The authors wish to thank Jeffrey Zhang for his ideas and		The authors wish to thank Jeffrey Zhang for his ideas and
	contributions to this work.		contributions to this work.
	6. IANA Considerations		7. IANA Considerations
	IANA is requested to assign a value for "BIER" from the "P-Multicast		IANA is requested to assign a value for "BIER" from the "P-Multicast
	Service Interface Tunnel (PMSI Tunnel) Tunnel Types" registry. The		Service Interface Tunnel (PMSI Tunnel) Tunnel Types" registry. The
	reference should be this document.		reference should be this document.
	7. Security Considerations		8. Security Considerations
	The security considerations of [BIER_ARCH], [BIER_ENCAPS], [RFC6513]		The security considerations of [BIER_ARCH], [BIER_ENCAPS], [RFC6513]
	and [RFC6514] are applicable.		and [RFC6514] are applicable.
	8. References		9. References
	8.1. Normative References		9.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-
	00, April 2015.		02, July 2015.
	[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-00.txt, April 2015.		bier-mpls-encapsulation-02.txt, August 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, March 1997.		Requirement Levels", BCP 14, RFC 2119,
			DOI 10.17487/RFC2119, March 1997,
			<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, February 2006.		Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
			2006, <http://www.rfc-editor.org/info/rfc4364>.
	[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", RFC		Label Assignment and Context-Specific Label Space",
	5331, August 2008.		RFC 5331, DOI 10.17487/RFC5331, August 2008,
			<http://www.rfc-editor.org/info/rfc5331>.
	[RFC6513] Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP		[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
	VPNs", RFC 6513, February 2012.		BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
			2012, <http://www.rfc-editor.org/info/rfc6513>.
	[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP		[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
	Encodings and Procedures for Multicast in MPLS/BGP IP		Encodings and Procedures for Multicast in MPLS/BGP IP
	VPNs", RFC 6514, February 2012.		VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
			<http://www.rfc-editor.org/info/rfc6514>.
	[RFC6625] Rosen, E., Rekhter, Y., Hendrickx, W., and R. Qiu,		[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
	"Wildcards in Multicast VPN Auto-Discovery Routes", RFC		Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
	6625, May 2012.		RFC 6625, DOI 10.17487/RFC6625, May 2012,
			<http://www.rfc-editor.org/info/rfc6625>.
	8.2. Informative References		9.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,
	March 2015.		August 2015.
	[EXTRANET]		[EXTRANET]
	Rekhter, Y., Rosen, E., Aggarwal, R., Cai, Y., and T.		Rekhter, Y., Rosen, E., Aggarwal, R., Cai, Y., and T.
	Morin, "Extranet Multicast in BGP/IP MPLS VPNs", internet-		Morin, "Extranet Multicast in BGP/IP MPLS VPNs", internet-
	draft draft-ietf-bess-mvpn-extranet-02, May 2015.		draft draft-ietf-bess-mvpn-extranet-05, December 2015.
	[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, May 2015.		(LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015,
			<http://www.rfc-editor.org/info/rfc7524>.
	Authors' Addresses		Authors' Addresses
	Eric C. Rosen (editor)		Eric C. Rosen (editor)
	Juniper Networks, Inc.		Juniper Networks, Inc.
	10 Technology Park Drive		10 Technology Park Drive
	Westford, Massachusetts 01886		Westford, Massachusetts 01886
	United States		United States
	Email: erosen@juniper.net		Email: erosen@juniper.net
	Mahesh Sivakumar		Mahesh Sivakumar
	Cisco Systems, Inc.		Cisco Systems, Inc.
	510 McCarthy Blvd		510 McCarthy Blvd
	Milpitas, California 95035		Milpitas, California 95035
	United States		United States
	Email: masivaku@cisco.com		Email: masivaku@cisco.com
	IJsbrand Wijnands
	Cisco Systems, Inc.
	De Kleetlaan 6a
	Diegem 1831
	Belgium
	Email: ice@cisco.com
	Sam K Aldrin		Sam K Aldrin
	Google, Inc.		Google, Inc.
	1600 Amphitheatre Parkway		1600 Amphitheatre Parkway
	Mountain View, California		Mountain View, California
	United States		United States
	Email: aldrin.ietf@gmail.com		Email: aldrin.ietf@gmail.com
	Andrew Dolganow		Andrew Dolganow
End of changes. 23 change blocks.
	41 lines changed or deleted		54 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/