draft-ietf-idr-bgp-extended-messages-16.txt   draft-ietf-idr-bgp-extended-messages-17.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: August 15, 2017 D. Ward Expires: August 15, 2017 D. Ward
Cisco Systems Cisco Systems
February 11, 2017 February 11, 2017
Extended Message support for BGP Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-16 draft-ietf-idr-bgp-extended-messages-17
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 the BGP specification RFC 4271 by providing an document updates the BGP specification RFC 4271 by providing an
extension to BGP to extend its current message size from 4096 octets extension to BGP to extend its current message size from 4096 octets
to 65535 octets. to 65535 octets.
skipping to change at page 3, line 30 skipping to change at page 3, line 30
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 An implementation that supports the BGP Extended Messages MUST be
prepared to receive an OPEN message that is larger than 4096 bytes. prepared to receive an UPDATE 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. Error Handling 5. Error Handling
A BGP speaker that has the ability to use extended messages but has A BGP speaker that has the ability to use extended messages but has
not advertised the BGP Extended Messages capability, presumably due not advertised the BGP Extended Messages capability, presumably due
 End of changes. 2 change blocks. 
2 lines changed or deleted 2 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/