draft-ietf-idr-bgp-ipv6-rt-constrain-10.txt		draft-ietf-idr-bgp-ipv6-rt-constrain-11.txt
	Network Working Group K. Patel		Network Working Group K. Patel
	Internet-Draft Arrcus, Inc.		Internet-Draft Arrcus, Inc.
	Intended status: Standards Track R. Raszuk		Intended status: Standards Track R. Raszuk
	Expires: July 3, 2017 Bloomberg LP		Expires: August 16, 2018 Bloomberg LP
	M. Djernaes		M. Djernaes
	Juniper Networks		Juniper Networks
	J. Dong		J. Dong
	M. Chen		M. Chen
	Huawei Technologies		Huawei Technologies
	December 30, 2016		February 12, 2018
	IPv6 Extensions for Route Target Distribution		IPv6 Extensions for Route Target Distribution
	draft-ietf-idr-bgp-ipv6-rt-constrain-10		draft-ietf-idr-bgp-ipv6-rt-constrain-11
	Abstract		Abstract
	The current route target distribution specification as described in		The current route target distribution specification as described in
	[RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes.		[RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes.
	The IPv6 specific Route Target extended community is defined in [RFC		The IPv6 specific Route Target extended community is defined in [RFC
	5701] as length of 20 bytes. Since the current specification only		5701] as length of 20 bytes. Since the current specification only
	supports prefixes of maximum length of 12 bytes, the lack of an IPv6		supports prefixes of maximum length of 12 bytes, the lack of an IPv6
	specific Route Target reachability information may be a problem when		specific Route Target reachability information may be a problem when
	an operator wants to use this application in a pure IPv6 environment.		an operator wants to use this application in a pure IPv6 environment.
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 July 3, 2017.		This Internet-Draft will expire on August 16, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2018 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		(https://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 4, line 27 ¶		skipping to change at page 4, line 27 ¶
	The authors would like to thank Pedro Marques, John Scudder, Alton Lo		The authors would like to thank Pedro Marques, John Scudder, Alton Lo
	and Zhenqiang Li for discussions and review.		and Zhenqiang Li for discussions and review.
	7. References		7. References
	7.1. Normative References		7.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,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://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>.		<https://www.rfc-editor.org/info/rfc4271>.
	[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, <http://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,
	November 2006, <http://www.rfc-editor.org/info/rfc4684>.		November 2006, <https://www.rfc-editor.org/info/rfc4684>.
	[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement		[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
	with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February		with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
	2009, <http://www.rfc-editor.org/info/rfc5492>.		2009, <https://www.rfc-editor.org/info/rfc5492>.
	[RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community		[RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community
	Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009,		Attribute", RFC 5701, DOI 10.17487/RFC5701, November 2009,
	<http://www.rfc-editor.org/info/rfc5701>.		<https://www.rfc-editor.org/info/rfc5701>.
	7.2. Informative References		7.2. Informative References
	[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,		[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
	"Multiprotocol Extensions for BGP-4", RFC 4760,		"Multiprotocol Extensions for BGP-4", RFC 4760,
	DOI 10.17487/RFC4760, January 2007,		DOI 10.17487/RFC4760, January 2007,
	<http://www.rfc-editor.org/info/rfc4760>.		<https://www.rfc-editor.org/info/rfc4760>.
	Authors' Addresses		Authors' Addresses
	Keyur Patel		Keyur Patel
	Arrcus, Inc.		Arrcus, Inc.
	USA		USA
	Email: keyur@arrcus.com		Email: keyur@arrcus.com
	Robert Raszuk		Robert Raszuk
End of changes. 14 change blocks.
	14 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/