idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-09.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 abstract seems to contain references ([RFC4271]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The abstract seems to indicate that this document updates RFC4271, but the header doesn't have an 'Updates:' line to match this. 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). -- The document date (January 10, 2015) is 3391 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) == Outdated reference: A later version (-08) exists of draft-ietf-sidr-bgpsec-overview-02 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Patel 3 Internet-Draft D. Ward 4 Intended status: Standards Track Cisco Systems 5 Expires: July 14, 2015 R. Bush 6 Internet Initiative Japan 7 January 10, 2015 9 Extended Message support for BGP 10 draft-ietf-idr-bgp-extended-messages-09 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 [RFC4271] by providing an extension to BGP to extend 18 its current message size from 4096 octets to 65535 octets. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to 24 be interpreted as described in RFC 2119 [RFC2119] only when they 25 appear in all upper case. They may also appear in lower or mixed 26 case as English words, without normative meaning. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on July 14, 2015. 45 Copyright Notice 47 Copyright (c) 2015 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. BGP Extended Message . . . . . . . . . . . . . . . . . . . . 2 64 3. Extended message Capability for BGP . . . . . . . . . . . . . 3 65 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 68 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 69 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 71 8.2. Informative References . . . . . . . . . . . . . . . . . 4 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 74 1. Introduction 76 The BGP specification [RFC4271] mandates a maximum BGP message size 77 of 4096 octets. As BGP is extended to support newer AFI/SAFIs and 78 newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is 79 a need to extend the maximum message size beyond 4096 octets. This 80 draft provides an extension to BGP to extend its current message size 81 limit from 4096 octets to 65535 octets. 83 2. BGP Extended Message 85 A BGP message over 4096 octets in length is a BGP Extended Message. 87 BGP Extended Messages have maximum message size of 65535 octets. The 88 smallest message that may be sent consists of a BGP header without a 89 data portion (19 octets). 91 Multi-octet fields MUST be in network byte order. 93 3. Extended message Capability for BGP 95 To advertise the BGP Extended Message Capability to a peer, a BGP 96 speaker uses BGP Capabilities Advertisement [RFC5492]. By 97 advertising the BGP Extended Message Capability to a peer, a BGP 98 speaker conveys that it is able to send, receive, and properly handle 99 BGP Extended Messages. 101 A peer which does not advertise this capability MUST NOT send BGP 102 Extended Messages, and BGP Extended Messages MUST NOT be sent to it. 104 The BGP Extended Message Capability is a new BGP Capability [RFC5492] 105 defined with Capability code TBD and Capability length 0. 107 4. Operation 109 A BGP speaker that is willing to send and receive BGP Extended 110 Messages from its peer should advertise the BGP Extended Message 111 Capability to its peer using BGP Capabilities Advertisement 112 [RFC5492]. A BGP speaker may send extended messages to its peer only 113 if it has received the Extended Message Capability from its peer. 115 An implementation that supports the BGP Extended Messages MUST be 116 prepared to receive an OPEN message that is larger than 4096 bytes. 118 Applications generating messages which might be encapsulated within 119 BGP messages MUST limit the size of their payload to take into 120 account the maximum message size and all encapsulation overheads on 121 the path the encapsulated data are expected to traverse. 123 5. Acknowledgements 125 The authors thank Enke Chen, John Scudder, John Levine, and Job 126 Snijders for their input. 128 6. IANA Considerations 130 The IANA is requested to register a new BGP Capability Code in the 131 upper range named BGP Extended Message Capability referring to this 132 document. 134 7. Security Considerations 136 This extension to BGP does not change BGP's underlying security 137 issues. 139 Many have said that BGP does not reveal sensitive data in the 140 presence of pervasive monitoring. While the topology information in 141 inter-provider BGP can be gained through other means, perhaps it does 142 not need to be made trivially easy. And BGP's use in VPN signaling 143 would seem to be sensitive. Perhaps this needs more thought. 145 8. References 147 8.1. Normative References 149 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 150 Requirement Levels", BCP 14, RFC 2119, March 1997. 152 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 153 Protocol 4 (BGP-4)", RFC 4271, January 2006. 155 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 156 with BGP-4", RFC 5492, February 2009. 158 8.2. Informative References 160 [I-D.ietf-sidr-bgpsec-overview] 161 Lepinski, M. and S. Turner, "An Overview of BGPSEC", 162 draft-ietf-sidr-bgpsec-overview-02 (work in progress), May 163 2012. 165 Authors' Addresses 167 Keyur Patel 168 Cisco Systems 169 170 W. Tasman Drive 170 San Jose, CA 95134 171 USA 173 Email: keyupate@cisco.com 175 Dave Ward 176 Cisco Systems 177 170 W. Tasman Drive 178 San Jose, CA 95134 179 USA 181 Email: dward@cisco.com 182 Randy Bush 183 Internet Initiative Japan 184 5147 Crystal Springs 185 Bainbridge Island, Washington 98110 186 US 188 Email: randy@psg.com