draft-ietf-idr-rtc-no-rt-04.txt		draft-ietf-idr-rtc-no-rt-05.txt
	IDR Working Group E. Rosen, Ed.		IDR Working Group E. Rosen, Ed.
	Internet-Draft Juniper Networks, Inc.		Internet-Draft Juniper Networks, Inc.
	Updates: 4684 (if approved) K. Patel		Updates: 4684 (if approved) K. Patel
	Intended status: Standards Track Cisco Systems, Inc.		Intended status: Standards Track Cisco Systems, Inc.
	Expires: May 16, 2016 J. Haas		Expires: November 10, 2016 J. Haas
	Juniper Networks, Inc.		Juniper Networks, Inc.
	R. Raszuk		R. Raszuk
	Bloomberg LP		Bloomberg LP
	November 13, 2015		May 9, 2016
	Route Target Constrained Distribution of Routes with no Route Targets		Route Target Constrained Distribution of Routes with no Route Targets
	draft-ietf-idr-rtc-no-rt-04.txt		draft-ietf-idr-rtc-no-rt-05.txt
	Abstract		Abstract
	There are a variety of BGP-enabled services in which the originator		There are a variety of BGP-enabled services in which the originator
	of a BGP route may attach one or more "Route Targets" to the route.		of a BGP route may attach one or more "Route Targets" to the route.
	By means of a procedure known as "RT Constrained Distribution" (RTC),		By means of a procedure known as "RT Constrained Distribution" (RTC),
	a given BGP speaker (call it "B") can announce the set of RTs in		a given BGP speaker (call it "B") can announce the set of RTs in
	which it has interest. The implication is that if a particular route		which it has interest. The implication is that if a particular route
	(call it "R") carries any RTs at all, BGP speaker B wants to receive		(call it "R") carries any RTs at all, BGP speaker B wants to receive
	route R if and only if B has announced interest in one of the RTs		route R if and only if B has announced interest in one of the RTs
	skipping to change at page 1, line 48 ¶		skipping to change at page 1, line 48 ¶
	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 May 16, 2016.		This Internet-Draft will expire on November 10, 2016.
	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 4, line 18 ¶		skipping to change at page 4, line 18 ¶
	routes that carry no RTs is problematic in at least three scenarios.		routes that carry no RTs is problematic in at least three scenarios.
	o [RFC6037] describes a deployed Multicast VPN (MVPN) solution. It		o [RFC6037] describes a deployed Multicast VPN (MVPN) solution. It
	defines a BGP SAFI known as "MDT-SAFI". Routes with this SAFI may		defines a BGP SAFI known as "MDT-SAFI". Routes with this SAFI may
	carry RTs, but are not required to do so. In order for the		carry RTs, but are not required to do so. In order for the
	procedures of [RFC6037] to work properly, if an MDT-SAFI route		procedures of [RFC6037] to work properly, if an MDT-SAFI route
	does not carry any RTs, the distribution of that route MUST NOT be		does not carry any RTs, the distribution of that route MUST NOT be
	constrained by RTC. However, if an MDT-SAFI route does carry one		constrained by RTC. However, if an MDT-SAFI route does carry one
	or more RTs, its distribution SHOULD be constrained by RTC.		or more RTs, its distribution SHOULD be constrained by RTC.
	o [GTM] specifies a way to provide "Global Table Multicast" (as		o [RFC7716] specifies a way to provide "Global Table Multicast" (as
	opposed to VPN multicast), using procedures that are very similar		opposed to VPN multicast), using procedures that are very similar
	to those described in [RFC6513] and [RFC6514] for MVPN. In		to those described in [RFC6513] and [RFC6514] for MVPN. In
	particular, it uses routes of the MCAST-VPN SAFI that is defined		particular, it uses routes of the MCAST-VPN SAFI that is defined
	in [RFC6514]. When used for MVPN, each MCAST-VPN route carries at		in [RFC6514]. When used for MVPN, each MCAST-VPN route carries at
	least one RT. However, when used for Global Table Multicast, it		least one RT. However, when used for Global Table Multicast, it
	is optional for certain MCAST-VPN routes to carry RTs. In order		is optional for certain MCAST-VPN routes to carry RTs. In order
	for the procedures of [GTM] to work properly, if an MCAST-VPN		for the procedures of [RFC7716] to work properly, if an MCAST-VPN
	route does not carry any RTs, the distribution of that route MUST		route does not carry any RTs, the distribution of that route MUST
	NOT be constrained by RTC.		NOT be constrained by RTC.
	o Typically, Route Targets have been carried only by routes that are		o Typically, Route Targets have been carried only by routes that are
	distributed as part of a VPN service (or the Global		distributed as part of a VPN service (or the Global
	Table Multicast service mentioned above). However, it may be		Table Multicast service mentioned above). However, it may be
	desirable to be able to place RTs on non-VPN routes (e.g., on		desirable to be able to place RTs on non-VPN routes (e.g., on
	unicast IPv4 or IPv6 routes) and then to use RTC to constrain the		unicast IPv4 or IPv6 routes) and then to use RTC to constrain the
	delivery of the non-VPN routes. For example, if a BGP speaker		delivery of the non-VPN routes. For example, if a BGP speaker
	desires to receive only a small set of IPv4 unicast routes, and		desires to receive only a small set of IPv4 unicast routes, and
	skipping to change at page 5, line 8 ¶		skipping to change at page 5, line 8 ¶
	document specifies a default behavior for the case where RTC is		document specifies a default behavior for the case where RTC is
	applied to a particular AFI/SAFI, and some (or all) routes of that		applied to a particular AFI/SAFI, and some (or all) routes of that
	address family do not carry any RTs.		address family do not carry any RTs.
	When RTC is applied, on a particular BGP session, to routes of the		When RTC is applied, on a particular BGP session, to routes of the
	MDT-SAFI address family (SAFI=66, [RFC6037]), the default behavior		MDT-SAFI address family (SAFI=66, [RFC6037]), the default behavior
	MUST be that routes that do not carry any RTs are distributed on that		MUST be that routes that do not carry any RTs are distributed on that
	session.		session.
	When RTC is applied, on a particular BGP session, to routes of the		When RTC is applied, on a particular BGP session, to routes of the
	MCAST-VPN address family (SAFI=5, [RFC6514], [GTM]), the default		MCAST-VPN address family (SAFI=5, [RFC6514], [RFC7716]), the default
	behavior MUST be that routes that do not carry any RTs are		behavior MUST be that routes that do not carry any RTs are
	distributed on that session.		distributed on that session.
	When RTC is applied, on a particular BGP session, to routes of other		When RTC is applied, on a particular BGP session, to routes of other
	address families, the default behavior MUST be that routes without		address families, the default behavior MUST be that routes without
	any RTs are not distributed on that session. This default "default		any RTs are not distributed on that session. This default "default
	behavior" applies to all AFI/SAFIs for which a different default		behavior" applies to all AFI/SAFIs for which a different default
	behavior has not been defined.		behavior has not been defined.
	A BGP speaker MAY be provisioned to apply a non-default behavior to a		A BGP speaker MAY be provisioned to apply a non-default behavior to a
	skipping to change at page 6, line 14 ¶		skipping to change at page 6, line 14 ¶
	[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,		[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
	R., Patel, K., and J. Guichard, "Constrained Route		R., Patel, K., and J. Guichard, "Constrained Route
	Distribution for Border Gateway Protocol/MultiProtocol		Distribution for Border Gateway Protocol/MultiProtocol
	Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual		Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
	Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,		Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
	November 2006, <http://www.rfc-editor.org/info/rfc4684>.		November 2006, <http://www.rfc-editor.org/info/rfc4684>.
	6.2. Informative References		6.2. Informative References
	[GTM] Zhang, J., Giulano, L., Rosen, E., Subramanian, K., and D.
	Pacella, "Global Table Multicast with BGP-MVPN
	Procedures", internet-draft draft-ietf-bess-mvpn-global-
	table-mcast-03, September 2015.
	[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>.
	[RFC6037] Rosen, E., Ed., Cai, Y., Ed., and IJ. Wijnands, "Cisco		[RFC6037] Rosen, E., Ed., Cai, Y., Ed., and IJ. Wijnands, "Cisco
	Systems' Solution for Multicast in BGP/MPLS IP VPNs",		Systems' Solution for Multicast in BGP/MPLS IP VPNs",
	RFC 6037, DOI 10.17487/RFC6037, October 2010,		RFC 6037, DOI 10.17487/RFC6037, October 2010,
	<http://www.rfc-editor.org/info/rfc6037>.		<http://www.rfc-editor.org/info/rfc6037>.
	[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, <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, DOI 10.17487/RFC6514, February 2012,		VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
	<http://www.rfc-editor.org/info/rfc6514>.		<http://www.rfc-editor.org/info/rfc6514>.
			[RFC7716] Zhang, J., Giuliano, L., Rosen, E., Ed., Subramanian, K.,
			and D. Pacella, "Global Table Multicast with BGP Multicast
			VPN (BGP-MVPN) Procedures", RFC 7716,
			DOI 10.17487/RFC7716, December 2015,
			<http://www.rfc-editor.org/info/rfc7716>.
	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
	Keyur Patel		Keyur Patel
End of changes. 10 change blocks.
	13 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/