draft-ietf-idr-bgp-ipv6-rt-constrain-05.txt		draft-ietf-idr-bgp-ipv6-rt-constrain-06.txt
	Network Working Group K. Patel		Network Working Group K. Patel
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track R. Raszuk		Intended status: Standards Track R. Raszuk
	Expires: December 12, 2014 NTT MCL Inc.		Expires: June 25, 2015 Mirantis Inc.
	M. Djernaes		M. Djernaes
	Juniper Networks		Juniper Networks
	J. Dong		J. Dong
	M. Chen		M. Chen
	Huawei Technologies		Huawei Technologies
	June 10, 2014		December 22, 2014
	IPv6 Extensions for Route Target Distribution		IPv6 Extensions for Route Target Distribution
	draft-ietf-idr-bgp-ipv6-rt-constrain-05		draft-ietf-idr-bgp-ipv6-rt-constrain-06
	Abstract		Abstract
	The current route target distribution specification described in		The current route target distribution specification as described in
	RFC4684 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		The IPv6 specific Route Target extended community is defined in [RFC
	[RFC5701] as length of 20 bytes. Since the current specification		5701] as length of 20 bytes. Since the current specification only
	only supports prefixes of maximum length of 12 bytes, the lack of an		supports prefixes of maximum length of 12 bytes, the lack of an IPv6
	IPv6 specific Route Target reachability information may be a problem		specific Route Target reachability information may be a problem when
	when an operator wants to use this application in a pure IPv6		an operator wants to use this application in a pure IPv6 environment.
	environment. This document defines an extension that allows BGP to		This document defines an extension that allows BGP to exchange longer
	exchange longer length IPv6 Route Target prefixes.		length IPv6 Route Target prefixes.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	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
	skipping to change at page 2, line 4		skipping to change at page 2, line 4
	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 December 12, 2014.		This Internet-Draft will expire on June 25, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 5, line 16		skipping to change at page 5, line 16
	Keyur Patel		Keyur Patel
	Cisco Systems		Cisco Systems
	170 W. Tasman Drive		170 W. Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	USA		USA
	Email: keyupate@cisco.com		Email: keyupate@cisco.com
	Robert Raszuk		Robert Raszuk
	NTT MCL Inc.		Mirantis Inc.
	101 S Ellsworth Avenue Suite 350		615 National Ave. #100
	San Mateo, CA 94401		Mt View, CA 94043
	USA		USA
	Email: robert@raszuk.net		Email: robert@raszuk.net
	Martin Djernaes		Martin Djernaes
	Juniper Networks		Juniper Networks
	1194 N. Mathilda Avenue		1194 N. Mathilda Avenue
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	USA		USA
End of changes. 6 change blocks.
	16 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/