draft-ietf-idr-bgp-extended-messages-17.txt   draft-ietf-idr-bgp-extended-messages-18.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 17, 2017 D. Ward
Cisco Systems Cisco Systems
February 11, 2017 February 13, 2017
Extended Message support for BGP Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-17 draft-ietf-idr-bgp-extended-messages-18
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 1, line 46 skipping to change at page 1, line 46
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 August 15, 2017. This Internet-Draft will expire on August 17, 2017.
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 (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
skipping to change at page 3, line 24 skipping to change at page 3, line 24
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.
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 UPDATE 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.
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
to configuration, SHOULD NOT accept an extended message. A speaker to configuration, SHOULD NOT accept an extended message. A speaker
MAY implement a more liberal policy and accept extended messages even MAY implement a more liberal policy and accept extended messages even
from a peer that has not advertised the capability. from a peer that has not advertised the capability.
However, a BGP speaker that does not advertise the BGP Extended However, a BGP speaker that does not advertise the BGP Extended
Messages capability might also genuinely not support extended Messages capability might also genuinely not support extended
messages. Such a speaker would be expected to follow the error messages. Such a speaker would be expected to follow the error
handling procedures of [RFC4271], Section 6.1, and reset the session handling procedures of [RFC4271], Section 6.1, and reset the session
with a Bad Message Length NOTIFICATION if it receives an extended with a Bad Message Length NOTIFICATION if it receives an extended
message. A speaker that treats an improper extended message as a message. Similarly, any speaker that treats an improper extended
fatal error, as described in the preceding paragraph, MUST do message as a fatal error, MUST do likewise.
likewise.
The inconsistency between the local and remote BGP speakers MUST be The inconsistency between the local and remote BGP speakers MUST be
reported via syslog and/or SNMP. reported via syslog and/or SNMP.
6. Acknowledgements 6. Acknowledgements
The authors thank Enke Chen, Susan Hares, John Scudder, John Levine, The authors thank Enke Chen, Susan Hares, John Scudder, John Levine,
and Job Snijders for their input. and Job Snijders for their input.
7. IANA Considerations 7. IANA Considerations
The IANA is requested to register a new BGP Capability Code to be The IANA is requested to register a new BGP Capability Code to be
named BGP Extended Message Capability and referring to this document. named BGP Extended Message Capability and referring to this document.
Registry: BGP Capability Code Registry: BGP Capability Code
Value Description Document Value Description Document
----- ----------------------------------- ------------- ----- ----------------------------------- -------------
64 Graceful Restart Capability [RFC4724]
....
72 CP-ORF Capability [RFC7543]
...
TBD BGP-Extended Message [this draft] TBD BGP-Extended Message [this draft]
8. Security Considerations 8. 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. It does enable large BGPsec BGPSEC_PATHs, see issues. It does enable large BGPsec BGPSEC_PATHs, see
[I-D.ietf-sidr-bgpsec-protocol] [I-D.ietf-sidr-bgpsec-protocol]
9. References 9. References
 End of changes. 9 change blocks. 
15 lines changed or deleted 9 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/