draft-ietf-idr-rtc-no-rt-10.txt		draft-ietf-idr-rtc-no-rt-11.txt
	IDR Working Group E. Rosen, Ed.		IDR Working Group E. Rosen
	Internet-Draft Juniper Networks, Inc.		Internet-Draft Unaffiliated
	Updates: 4684 (if approved) K. Patel		Updates: 4684 (if approved) K. Patel
	Intended status: Standards Track Arccus		Intended status: Standards Track Arccus
	Expires: April 18, 2019 J. Haas		Expires: October 10, 2019 J. Haas, Ed.
	Juniper Networks, Inc.		Juniper Networks, Inc.
	R. Raszuk		R. Raszuk
	Bloomberg LP		Bloomberg LP
	October 15, 2018		April 8, 2019
	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-10.txt		draft-ietf-idr-rtc-no-rt-11.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 41 ¶		skipping to change at page 1, line 41 ¶
	effect of the RTC mechanism on routes that do not have any RTs.		effect of the RTC mechanism on routes that do not have any RTs.
	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 https://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 April 18, 2019.		This Internet-Draft will expire on October 10, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2019 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
	(https://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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	skipping to change at page 5, line 43 ¶		skipping to change at page 5, line 43 ¶
	applications using them to operate properly. Allowing the		applications using them to operate properly. Allowing the
	distribution of such routes does not create any new security		distribution of such routes does not create any new security
	considerations beyond those of the applications that use the routes.		considerations beyond those of the applications that use the routes.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[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, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc2119>.		editor.org/info/rfc2119>.
	[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended		[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
	Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,		Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
	February 2006, <https://www.rfc-editor.org/info/rfc4360>.		February 2006, <https://www.rfc-editor.org/info/rfc4360>.
	[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,
	skipping to change at page 6, line 35 ¶		skipping to change at page 6, line 35 ¶
	2012, <https://www.rfc-editor.org/info/rfc6513>.		2012, <https://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,
	<https://www.rfc-editor.org/info/rfc6514>.		<https://www.rfc-editor.org/info/rfc6514>.
	[RFC7716] Zhang, J., Giuliano, L., Rosen, E., Ed., Subramanian, K.,		[RFC7716] Zhang, J., Giuliano, L., Rosen, E., Ed., Subramanian, K.,
	and D. Pacella, "Global Table Multicast with BGP Multicast		and D. Pacella, "Global Table Multicast with BGP Multicast
	VPN (BGP-MVPN) Procedures", RFC 7716,		VPN (BGP-MVPN) Procedures", RFC 7716,
	DOI 10.17487/RFC7716, December 2015,		DOI 10.17487/RFC7716, December 2015, <https://www.rfc-
	<https://www.rfc-editor.org/info/rfc7716>.		editor.org/info/rfc7716>.
	Authors' Addresses		Authors' Addresses
	Eric C. Rosen (editor)		Eric C. Rosen
	Juniper Networks, Inc.		Unaffiliated
	10 Technology Park Drive
	Westford, Massachusetts 01886
	United States
	Email: erosen@juniper.net		Email: erosen52@gmail.com
	Keyur Patel		Keyur Patel
	Arccus		Arccus
	Email: keyur@arccus.com		Email: keyur@arccus.com
	Jeffrey Haas		Jeffrey Haas (editor)
	Juniper Networks, Inc.		Juniper Networks, Inc.
	1194 N. Mathilda Ave.		1133 Innovation Way
	Sunnyvale, California 94089		Sunnyvale, California 94089
	United States		United States
	Email: jhaas@juniper.net		Email: jhaas@juniper.net
	Robert Raszuk		Robert Raszuk
	Bloomberg LP		Bloomberg LP
	731 Lexington Ave		731 Lexington Ave
	New York City, NY 10022		New York City, NY 10022
	United States		United States
End of changes. 14 change blocks.
	21 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/