draft-ietf-idr-bgp-extended-messages-22.txt		draft-ietf-idr-bgp-extended-messages-23.txt
	Network Working Group R. Bush		Network Working Group R. Bush
	Internet-Draft Internet Initiative Japan		Internet-Draft Internet Initiative Japan
	Updates: 4271 (if approved) K. Patel		Updates: 4271 (if approved) K. Patel
	Intended status: Standards Track Arrcus, Inc.		Intended status: Standards Track Arrcus, Inc.
	Expires: February 16, 2018 D. Ward		Expires: May 1, 2018 D. Ward
	Cisco Systems		Cisco Systems
	August 15, 2017		October 28, 2017
	Extended Message support for BGP		Extended Message support for BGP
	draft-ietf-idr-bgp-extended-messages-22		draft-ietf-idr-bgp-extended-messages-23
	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 and other		octets. As BGP is extended to support newer AFI/SAFIs and other
	features, there is a need to extend the maximum message size beyond		features, there is a need to extend the maximum message size beyond
	4096 octets. This document updates the BGP specification RFC4271 by		4096 octets. This document updates the BGP specification RFC4271 by
	providing an extension to BGP to extend its current maximum message		providing an extension to BGP to extend its current maximum message
	size from 4096 octets to 65535 octets for all except the OPEN		size from 4096 octets to 65535 octets for all except the OPEN
	message.		message.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	words, without normative meaning.		words, without normative meaning.
	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 February 16, 2018.		This Internet-Draft will expire on May 1, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 5, line 5 ¶		skipping to change at page 5, line 5 ¶
	This extension to BGP does not change BGP's underlying security		This extension to BGP does not change BGP's underlying security
	issues; see [RFC4272].		issues; see [RFC4272].
	Section 5 allowed a receiver to accept an Extended Message even		Section 5 allowed a receiver to accept an Extended Message even
	though they had not advertised the capability. This slippery slope		though they had not advertised the capability. This slippery slope
	will surely lead to sloppy implementations sending Extended Messages		will surely lead to sloppy implementations sending Extended Messages
	when the receiver is not prepared to deal with them, e.g. to peer		when the receiver is not prepared to deal with them, e.g. to peer
	groups. At best, this will result in errors; at worst, buffer		groups. At best, this will result in errors; at worst, buffer
	overflows.		overflows.
			Due to increased (over [RFC4272]) memory requirements for buffering,
			there may be increased exposure to resource exhaustion, intentional
			or unintentional.
	9. Acknowledgments		9. Acknowledgments
	The authors thank Alvaro Retana, Enke Chen, Susan Hares, John		The authors thank Alvaro Retana, Enke Chen, Susan Hares, John
	Scudder, John Levine, and Job Snijders for their input; and Oliver		Scudder, John Levine, and Job Snijders for their input; and Oliver
	Borchert and Kyehwan Lee for their implementations and testing.		Borchert and Kyehwan Lee for their implementations and testing.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
End of changes. 7 change blocks.
	6 lines changed or deleted		10 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/