< draft-ietf-idr-bgp-extended-messages-35.txt   draft-ietf-idr-bgp-extended-messages-36.txt >
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft IIJ & Arrcus Internet-Draft Arrcus & IIJ
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 1, 2020 D. Ward Expires: February 17, 2020 D. Ward
Cisco Systems Cisco Systems
July 31, 2019 August 16, 2019
Extended Message support for BGP Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-35 draft-ietf-idr-bgp-extended-messages-36
Abstract Abstract
The BGP specification mandates a maximum BGP message size of 4,096 The BGP specification mandates a maximum BGP message size of 4,096
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
4,096 octets. This document updates the BGP specification RFC4271 by 4,096 octets. This document updates the BGP specification RFC4271 by
extending the maximum message size from 4,096 octets to 65,535 octets extending the maximum message size from 4,096 octets to 65,535 octets
for all except the OPEN and KEEPALIVE messages. for all except the OPEN and KEEPALIVE messages.
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 https://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 1, 2020. This Internet-Draft will expire on February 17, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . 2 2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . 2
3. Extended Message Capability for BGP . . . . . . . . . . . . . 3 3. Extended Message Capability for BGP . . . . . . . . . . . . . 3
4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4 5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 4
6. Changes to RFC4271 . . . . . . . . . . . . . . . . . . . . . 5 6. Changes to RFC4271 . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 6 10.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
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 4,096 octets. As BGP is extended to support newer AFI/SAFIs and of 4,096 octets. As BGP is extended to support newer AFI/SAFIs and
newer capabilities (e.g., BGPsec [RFC8205] and BGP-LS [RFC7752]), newer capabilities (e.g., BGPsec [RFC8205] and BGP-LS [RFC7752]),
there is a need to extend the maximum message size beyond 4,096 there is a need to extend the maximum message size beyond 4,096
octets. This draft provides an extension to BGP to extend its octets. This draft provides an extension to BGP to extend its
message size limit from 4,096 octets to 65,535 octets for all except message size limit from 4,096 octets to 65,535 octets for all except
skipping to change at page 4, line 49 skipping to change at page 4, line 49
MUST NOT implement a more liberal policy accepting BGP Extended MUST NOT implement a more liberal policy accepting BGP Extended
Messages. Messages.
A BGP speaker that does not advertise the BGP Extended Messages A BGP speaker that does not advertise the BGP Extended Messages
capability might also genuinely not support Extended Messages. Such capability might also genuinely not support Extended Messages. Such
a speaker will follow the error handling procedures of [RFC4271] if a speaker will follow the error handling procedures of [RFC4271] if
it receives an Extended Message. Similarly, any speaker that treats it receives an Extended Message. Similarly, any speaker that treats
an improper Extended Message as a fatal error, MUST follow the error an improper Extended Message as a fatal error, MUST follow the error
handling procedures of [RFC4271]. handling procedures of [RFC4271].
The UPDATE Message Error Handling, as specified in Section 6.3 of
[RFC4271], is unchanged. However, if a NOTIFICATION is to be sent to
a BGP speaker that has not advertised the BGP Extended Message
Capability, the size of the message MUST NOT exceed 4,096 octets.
It is RECOMMENDED that BGP protocol developers and implementers are It is RECOMMENDED that BGP protocol developers and implementers are
conservative in their application and use of Extended Messages. conservative in their application and use of Extended Messages.
Future protocol specifications MUST describe how to handle peers Future protocol specifications MUST describe how to handle peers
which can only accommodate 4,096 octet messages. which can only accommodate 4,096 octet messages.
6. Changes to RFC4271 6. Changes to RFC4271
[RFC4271] states "The value of the Length field MUST always be at [RFC4271] states "The value of the Length field MUST always be at
least 19 and no greater than 4,096." This document changes the least 19 and no greater than 4,096." This document changes the
latter number to 65,535 for all except the OPEN and KEEPALIVE latter number to 65,535 for all except the OPEN and KEEPALIVE
messages. messages.
skipping to change at page 7, line 18 skipping to change at page 7, line 24
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<http://www.rfc-editor.org/info/rfc7752>. <http://www.rfc-editor.org/info/rfc7752>.
[RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol
Specification", RFC 8205, DOI 10.17487/RFC8205, September Specification", RFC 8205, DOI 10.17487/RFC8205, September
2017, <https://www.rfc-editor.org/info/rfc8205>. 2017, <https://www.rfc-editor.org/info/rfc8205>.
Authors' Addresses Authors' Addresses
Randy Bush Randy Bush
IIJ & Arrcus Arrcus & IIJ
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, Washington 98110 Bainbridge Island, Washington 98110
US US
Email: randy@psg.com Email: randy@psg.com
Keyur Patel Keyur Patel
Arrcus, Inc. Arrcus, Inc.
Email: keyur@arrcus.com Email: keyur@arrcus.com
 End of changes. 9 change blocks. 
8 lines changed or deleted 12 lines changed or added

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