draft-ietf-idr-bgp-extended-messages-06.txt		draft-ietf-idr-bgp-extended-messages-07.txt
	IDR Working Group K. Patel		IDR Working Group K. Patel
	Internet-Draft D. Ward		Internet-Draft D. Ward
	Intended status: Standards Track Cisco Systems		Intended status: Standards Track Cisco Systems
	Expires: February 04, 2014 R. Bush		Expires: July 31, 2014 R. Bush
	Internet Initiative Japan		Internet Initiative Japan
	August 03, 2013		January 27, 2014
	Extended Message support for BGP		Extended Message support for BGP
	draft-ietf-idr-bgp-extended-messages-06		draft-ietf-idr-bgp-extended-messages-07
	Abstract		Abstract
	The BGP specification mandates a maximum BGP message size of 4096		The BGP specification mandates a maximum BGP message size of 4096
	octets. As BGP is extended to support newer AFI/SAFIs, there is a		octets. As BGP is extended to support newer AFI/SAFIs, there is a
	need to extend the maximum message size beyond 4096 octets. This		need to extend the maximum message size beyond 4096 octets. This
	document updates [RFC4271] by providing an extension to BGP to extend		document updates [RFC4271] by providing an extension to BGP to extend
	its current message size from 4096 octets to 65535 octets.		its current message size from 4096 octets to 65535 octets.
	Requirements Language		Requirements Language
	skipping to change at page 1, line 44		skipping to change at page 1, line 44
	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 February 04, 2014.		This Internet-Draft will expire on July 31, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 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
	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 5		skipping to change at page 3, line 48
	The IANA is requested to register a new BGP Capability Code in the		The IANA is requested to register a new BGP Capability Code in the
	upper range named BGP Extended Message Capability referring to this		upper range named BGP Extended Message Capability referring to this
	document.		document.
	7. Security Considerations		7. Security Considerations
	This extension to BGP does not change BGP's underlying security		This extension to BGP does not change BGP's underlying security
	issues.		issues.
			Many have said that BGP does not reveal sensitive data in the
			presence of pervasive monitoring. While the topology information in
			inter-provider BGP can be gained through other means, perhaps it does
			not need to be made trivially easy. And BGP's use in VPN signaling
			would seem to be sensitive. Perhaps this needs more thought.
	8. References		8. References
	8.1. Normative References		8.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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway		[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
End of changes. 6 change blocks.
	5 lines changed or deleted		11 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/