draft-ietf-idr-bgp-extended-messages-04.txt		draft-ietf-idr-bgp-extended-messages-05.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: June 27, 2013 R. Bush		Expires: June 27, 2013 R. Bush
	Internet Initiative Japan		Internet Initiative Japan
	December 24, 2012		December 24, 2012
	Extended Message support for BGP		Extended Message support for BGP
	draft-ietf-idr-bgp-extended-messages-04		draft-ietf-idr-bgp-extended-messages-05
	Abstract		Abstract
	The BGP specificatanyion 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
	draft provides an extension to BGP to extend its current message size		document updates [RFC4271] by providing an extension to BGP to extend
	from 4096 octets to 65535 octets.		its current message size from 4096 octets to 65535 octets.
	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" are to		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
	be interpreted as described in RFC 2119 [RFC2119] only when they		be interpreted as described in RFC 2119 [RFC2119] only when they
	appear in all upper case. They may also appear in lower or mixed		appear in all upper case. They may also appear in lower or mixed
	case as English words, without normative meaning.		case as English words, without normative meaning.
	Status of this Memo		Status of this Memo
	skipping to change at page 2, line 18		skipping to change at page 2, line 18
	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 . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Extended message Capability for BGP . . . . . . . . . . . . . . 3		2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . . 3
	3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Extended message Capability for BGP . . . . . . . . . . . . . . 3
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3		4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
	6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4		7. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 4		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	7.2. Informative References . . . . . . . . . . . . . . . . . . 4		8.1. Normative References . . . . . . . . . . . . . . . . . . . 4
			8.2. Informative References . . . . . . . . . . . . . . . . . . 4
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
	1. Introduction		1. Introduction
	The BGP specification [RFC4271] mandates a maximum BGP message size		The BGP specification [RFC4271] mandates a maximum BGP message size
	of 4096 octets. As BGP is extended to support newer AFI/SAFIs and		of 4096 octets. As BGP is extended to support newer AFI/SAFIs and
	newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is		newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is
	a need to extend the maximum message size beyond 4096 octets. This		a need to extend the maximum message size beyond 4096 octets. This
	draft provides an extension to BGP to extend its current message size		draft provides an extension to BGP to extend its current message size
	from 4096 octets to 65535 octets.		limit from 4096 octets to 65535 octets.
	2. Extended message Capability for BGP		2. BGP Extended Message
	To advertise BGP Extended Message Capability to a peer, a BGP speaker		A BGP message over 4095 octets in length is a Extended Message.
	uses BGP Capabilities Advertisement [RFC5492]. By advertising the
	BGP Extended Message Capability to a peer, a BGP speaker conveys that		BGP extended messages have maximum message size of 65535 octets. The
	it is able to send, receive, and properly handle BGP Extended		smallest message that may be sent consists of a BGP header without a
	Messages.		data portion (19 octets).
			Multi-octet fields MUST be in network byte order.
			3. Extended message Capability for BGP
			To advertise the BGP Extended Message Capability to a peer, a BGP
			speaker uses BGP Capabilities Advertisement [RFC5492]. By
			advertising the BGP Extended Message Capability to a peer, a BGP
			speaker conveys that it is able to send, receive, and properly handle
			BGP Extended Messages.
	A peer which does not advertise this capability MUST NOT send BGP		A peer which does not advertise this capability MUST NOT send BGP
	Extended Messages, and BGP Extended Messages MUST NOT be sent to it.		Extended Messages, and BGP Extended Messages MUST NOT be sent to it.
	The BGP Extended Message Capability is a new BGP Capability [RFC5492]		The BGP Extended Message Capability is a new BGP Capability [RFC5492]
	defined with Capability code TBD and Capability length 0.		defined with Capability code TBD and Capability length 0.
	3. Operation		4. Operation
	A BGP speaker that is willing to send and receive BGP Extended		A BGP speaker that is willing to send and receive BGP Extended
	Messages from its peer should advertise the BGP Extended Message		Messages from its peer should advertise the BGP Extended Message
	Capability to its peer using BGP Capabilities Advertisement		Capability to its peer using BGP Capabilities Advertisement
	[RFC5492]. A BGP speaker may send extended messages to its peer only		[RFC5492]. A BGP speaker may send extended messages to its peer only
	if it has received the Extended Message Capability from its peer.		if it has received the Extended Message Capability from its peer.
	All BGP extended messages have maximum message size of 65535 octets.
	The smallest message that may be sent consists of a BGP header
	without a data portion (19 octets). All multi-octet fields are in
	network byte order.
	Applications generating messages which might be encapsulated within		Applications generating messages which might be encapsulated within
	BGP messages MUST limit the size of their payload to take into		BGP messages MUST limit the size of their payload to take into
	account the maximum message size and all encapsulation overheads on		account the maximum message size and all encapsulation overheads on
	the path the encapsulated data are expected to traverse.		the path the encapsulated data are expected to traverse.
	4. Acknowledgements		5. Acknowledgements
	The authors thank John Scudder and John Levine for their input.		The authors thank John Scudder, John Levine, and Job Snijders for
			their input.
	5. IANA Considerations		6. IANA Considerations
	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.
	6. 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.
	7. References		8. References
	7.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.
	[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement		[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
	with BGP-4", RFC 5492, February 2009.		with BGP-4", RFC 5492, February 2009.
	7.2. Informative References		8.2. Informative References
	[I-D.ietf-sidr-bgpsec-overview]		[I-D.ietf-sidr-bgpsec-overview]
	Lepinski, M. and S. Turner, "An Overview of BGPSEC",		Lepinski, M. and S. Turner, "An Overview of BGPSEC",
	draft-ietf-sidr-bgpsec-overview-02 (work in progress),		draft-ietf-sidr-bgpsec-overview-02 (work in progress),
	May 2012.		May 2012.
	Authors' Addresses		Authors' Addresses
	Keyur Patel		Keyur Patel
	Cisco Systems		Cisco Systems
End of changes. 16 change blocks.
	32 lines changed or deleted		39 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/