draft-ietf-idr-bgp-extended-messages-08.txt   draft-ietf-idr-bgp-extended-messages-09.txt 
Network Working Group K. Patel Network 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: January 22, 2015 R. Bush Expires: July 14, 2015 R. Bush
Internet Initiative Japan Internet Initiative Japan
July 21, 2014 January 10, 2015
Extended Message support for BGP Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-08 draft-ietf-idr-bgp-extended-messages-09
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 January 22, 2015. This Internet-Draft will expire on July 14, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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 3, line 27 skipping to change at page 3, line 27
defined with Capability code TBD and Capability length 0. defined with Capability code TBD and Capability length 0.
4. 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.
An implementation that supports the BGP Extended Messages MUST be
prepared to receive an OPEN message that is larger than 4096 bytes.
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.
5. Acknowledgements 5. Acknowledgements
The authors thank John Scudder, John Levine, and Job Snijders for The authors thank Enke Chen, John Scudder, John Levine, and Job
their input. Snijders for their input.
6. 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.
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
 End of changes. 7 change blocks. 
7 lines changed or deleted 10 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/