idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-03.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 : ---------------------------------------------------------------------------- No issues found here. 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 (July 3, 2012) is 4315 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: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group K. Patel 3 Internet-Draft D. Ward 4 Intended status: Standards Track Cisco Systems 5 Expires: January 02, 2013 R. Bush 6 Internet Initiative Japan 7 July 3, 2012 9 Extended Message support for BGP 10 draft-ietf-idr-bgp-extended-messages-03 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 draft provides an extension to BGP to extend its current message size 18 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 any 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 January 02, 2013. 45 Copyright Notice 47 Copyright (c) 2012 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 (http://trustee.ietf.org/ 52 license-info) in effect on the date of publication of this document. 53 Please review these documents carefully, as they describe your rights 54 and restrictions with respect to this document. Code Components 55 extracted from this document must include Simplified BSD License text 56 as described in Section 4.e of the Trust Legal Provisions and are 57 provided without warranty as described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Extended message Capability for BGP . . . . . . . . . . . . . 2 63 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 2 64 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 7.1. Normative References . . . . . . . . . . . . . . . . . . . 3 69 7.2. Informative References . . . . . . . . . . . . . . . . . . 3 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 3 72 1. Introduction 74 The BGP specification [RFC4271] mandates a maximum BGP message size 75 of 4096 octets. As BGP is extended to support newer AFI/SAFIs and 76 newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is 77 a need to extend the maximum message size beyond 4096 octets. This 78 draft provides an extension to BGP to extend its current message size 79 from 4096 octets to 65535 octets. 81 2. Extended message Capability for BGP 83 To advertise BGP Extended Message Capability to a peer, a BGP speaker 84 uses BGP Capabilities Advertisement [RFC5492]. By advertising the 85 BGP Extended Message Capability to a peer, a BGP speaker conveys that 86 it is able to send, receive, and properly handle BGP Extended 87 Messages. 89 A peer which does not advertise this capability MUST NOT send BGP 90 Extended Messages, and BGP Extended Messages MUST NOT be sent to it. 92 The BGP Extended Message Capability is a new BGP Capability [RFC5492] 93 defined with Capability code TBD and Capability length 0. 95 3. Operation 97 A BGP speaker that is willing to send and receive BGP Extended 98 Messages from its peer should advertise the BGP Extended Message 99 Capability to its peer using BGP Capabilities Advertisement 100 [RFC5492]. A BGP speaker may send extended messages to its peer only 101 if it has received the Extended Message Capability from its peer. 103 All BGP extended messages have maximum message size of 65535 octets. 104 The smallest message that may be sent consists of a BGP header 105 without a data portion (19 octets). All multi-octet fields are in 106 network byte order. 108 Applications generating messages which might be encapsulated within 109 BGP messages MUST limit the size of their payload to take into 110 account the maximum message size and all encapsulation overheads on 111 the path the encapsulated data are expected to traverse. 113 4. Acknowledgements 115 The authors thank John Scudder and John Levine for their input. 117 5. IANA Considerations 119 The IANA is requested to register a new BGP Capability Code in the 120 upper range named BGP Extended Message Capability referring to this 121 document. 123 6. Security Considerations 125 This extension to BGP does not change BGP's underlying security 126 issues. 128 7. References 130 7.1. Normative References 132 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 133 Requirement Levels", BCP 14, RFC 2119, March 1997. 135 [RFC4271] Rekhter, Y., Li, T. and S. Hares, "A Border Gateway 136 Protocol 4 (BGP-4)", RFC 4271, January 2006. 138 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 139 with BGP-4", RFC 5492, February 2009. 141 7.2. Informative References 143 [I-D.ietf-sidr-bgpsec-overview] 144 Lepinski, M. and S. Turner, "An Overview of BGPSEC", 145 Internet-Draft draft-ietf-sidr-bgpsec-overview-02, May 146 2012. 148 Authors' Addresses 149 Keyur Patel 150 Cisco Systems 151 170 W. Tasman Drive 152 San Jose, CA 95134 153 USA 155 Email: keyupate@cisco.com 157 Dave Ward 158 Cisco Systems 159 170 W. Tasman Drive 160 San Jose, CA 95134 161 USA 163 Email: dward@cisco.com 165 Randy Bush 166 Internet Initiative Japan 167 5147 Crystal Springs 168 Bainbridge Island, Washington 98110 169 US 171 Email: randy@psg.com