idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC4271, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). (Using the creation date from RFC4271, updated by this document, for RFC5378 checks: 2006-01-13) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 22, 2016) is 2865 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC4724' is mentioned on line 160, but not defined == Missing Reference: 'RFC7543' is mentioned on line 162, but not defined == Outdated reference: A later version (-08) exists of draft-ietf-sidr-bgpsec-overview-02 == Outdated reference: A later version (-23) exists of draft-ietf-sidr-bgpsec-protocol-07 Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Bush 3 Internet-Draft Internet Initiative Japan 4 Updates: 4271 (if approved) K. Patel 5 Intended status: Standards Track D. Ward 6 Expires: December 24, 2016 Cisco Systems 7 June 22, 2016 9 Extended Message support for BGP 10 draft-ietf-idr-bgp-extended-messages-13 12 Abstract 14 The BGP specification mandates a maximum BGP message size of 4096 15 octets. As BGP is extended to support newer AFI/SAFIs, there is a 16 need to extend the maximum message size beyond 4096 octets. This 17 document updates the BGP specification by providing an extension to 18 BGP to extend its current message size from 4096 octets to 65535 19 octets. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to 25 be interpreted as described in RFC 2119 [RFC2119] only when they 26 appear in all upper case. They may also appear in lower or mixed 27 case as English words, without normative meaning. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on December 24, 2016. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . 2 65 3. Extended message Capability for BGP . . . . . . . . . . . . . 3 66 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 3 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 70 8. Security Considerations . . . . . . . . . . . . . . . . . . . 4 71 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 9.1. Normative References . . . . . . . . . . . . . . . . . . 4 73 9.2. Informative References . . . . . . . . . . . . . . . . . 4 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 76 1. Introduction 78 The BGP specification RFC4271 [RFC4271] mandates a maximum BGP 79 message size of 4096 octets. As BGP is extended to support newer 80 AFI/SAFIs and newer capabilities (e.g., 81 [I-D.ietf-sidr-bgpsec-overview]), there is a need to extend the 82 maximum message size beyond 4096 octets. This draft provides an 83 extension to BGP to extend its current message size limit from 4096 84 octets to 65535 octets. 86 2. BGP Extended Message 88 A BGP message over 4096 octets in length is a BGP Extended Message. 90 BGP Extended Messages have maximum message size of 65535 octets. The 91 smallest message that may be sent consists of a BGP header without a 92 data portion (19 octets). 94 Multi-octet fields MUST be in network byte order. 96 3. Extended message Capability for BGP 98 To advertise the BGP Extended Message Capability to a peer, a BGP 99 speaker uses BGP Capabilities Advertisement [RFC5492]. By 100 advertising the BGP Extended Message Capability to a peer, a BGP 101 speaker conveys that it is able to send, receive, and properly handle 102 BGP Extended Messages. 104 A peer which does not advertise this capability MUST NOT send BGP 105 Extended Messages, and BGP Extended Messages MUST NOT be sent to it. 107 The BGP Extended Message Capability is a new BGP Capability [RFC5492] 108 defined with Capability code TBD and Capability length 0. 110 4. Operation 112 A BGP speaker that is willing to send and receive BGP Extended 113 Messages from its peer should advertise the BGP Extended Message 114 Capability to its peer using BGP Capabilities Advertisement 115 [RFC5492]. A BGP speaker may send extended messages to its peer only 116 if it has received the Extended Message Capability from its peer. 118 An implementation that supports the BGP Extended Messages MUST be 119 prepared to receive an OPEN message that is larger than 4096 bytes. 121 Applications generating messages which might be encapsulated within 122 BGP messages MUST limit the size of their payload to take into 123 account the maximum message size and all encapsulation overheads on 124 the path the encapsulated data are expected to traverse. 126 5. Error Handling 128 A BGP speaker that has the ability to use extended messages but has 129 not advertised the BGP Extended Messages capability, presumably due 130 to configuration, SHOULD NOT accept an extended message. A speaker 131 MAY implement a more liberal policy and accept extended messages even 132 from a peer that has not advertised the capability. 134 However, a BGP speaker that does not advertise the BGP Extended 135 Messages capability might also genuinely not support extended 136 messages. Such a speaker would be expected to follow the error 137 handling procedures of [RFC4271], Section 6.1, and reset the session 138 with a Bad Message Length NOTIFICATION if it receives an extended 139 message. A speaker that treats an improper extended message as a 140 fatal error, as described in the preceding paragraph, MUST do 141 likewise. 143 The inconsistency between the local and remote BGP speakers MUST be 144 reported via syslog and/or SNMP. 146 6. Acknowledgements 148 The authors thank Enke Chen, Susan Hares, John Scudder, John Levine, 149 and Job Snijders for their input. 151 7. IANA Considerations 153 The IANA is requested to register a new BGP Capability Code to be 154 named BGP Extended Message Capability and referring to this document. 156 Registry: BGP Capability Code 158 Value Description Document 159 ----- ----------------------------------- ------------- 160 64 Graceful Restart Capability [RFC4724] 161 .... 162 72 CP-ORF Capability [RFC7543] 163 ... 164 TBD BGP-Extended Message [this draft] 166 8. Security Considerations 168 This extension to BGP does not change BGP's underlying security 169 issues. It does enable large BGPsec BGPSEC_PATHs, see 170 [I-D.ietf-sidr-bgpsec-protocol] 172 9. References 174 9.1. Normative References 176 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 177 Requirement Levels", BCP 14, RFC 2119, March 1997. 179 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 180 Protocol 4 (BGP-4)", RFC 4271, January 2006. 182 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 183 with BGP-4", RFC 5492, February 2009. 185 9.2. Informative References 187 [I-D.ietf-sidr-bgpsec-overview] 188 Lepinski, M. and S. Turner, "An Overview of BGPSEC", 189 draft-ietf-sidr-bgpsec-overview-02 (work in progress), May 190 2012. 192 [I-D.ietf-sidr-bgpsec-protocol] 193 Lepinski, M., "BGPSEC Protocol Specification", draft-ietf- 194 sidr-bgpsec-protocol-07 (work in progress), February 2013. 196 Authors' Addresses 198 Randy Bush 199 Internet Initiative Japan 200 5147 Crystal Springs 201 Bainbridge Island, Washington 98110 202 US 204 Email: randy@psg.com 206 Keyur Patel 207 Cisco Systems 208 170 W. Tasman Drive 209 San Jose, CA 95134 210 USA 212 Email: keyupate@cisco.com 214 Dave Ward 215 Cisco Systems 216 170 W. Tasman Drive 217 San Jose, CA 95134 218 USA 220 Email: dward@cisco.com