idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-00.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 date (June 6, 2011) is 4707 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) ** Obsolete normative reference: RFC 3392 (Obsoleted by RFC 5492) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Patel 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track D. Ward 5 Expires: December 8, 2011 Juniper Networks 6 R. Bush 7 Internet Initiative Japan 8 June 6, 2011 10 Extended Message support for BGP 11 draft-ietf-idr-bgp-extended-messages-00 13 Abstract 15 The current BGP specification mandates a maximum BGP message size of 16 4096 octets. As BGP is extended to support newer AFI/SAFIs, there is 17 a need to extend the maximum message size beyond 4096 octets. This 18 draft provides an extension for BGP to extend its current message 19 size for BGP messages from 4096 octets to 65535 octets. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in RFC 2119 [RFC2119]. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on December 8, 2011. 44 Copyright Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Extended message Capability for BGP . . . . . . . . . . . . . . 3 63 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 65 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 69 7.2. Informative References . . . . . . . . . . . . . . . . . . 4 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 72 1. Introduction 74 The current BGP specification [RFC4271] mandates a maximum BGP 75 message size of 4096 octets. As BGP is extended to support newer 76 AFI/SAFIs and newer capabilities (e.g., 77 [I-D.lepinski-bgpsec-overview], there is a need to extend the maximum 78 message size beyond 4096 octets. This draft provides an extension 79 for BGP to extend its current message size for BGP messages from 4096 80 octets to 65535 octets. 82 2. Extended message Capability for BGP 84 To advertise BGP Extended Message Capability to a peer, a BGP speaker 85 uses BGP Capabilities Advertisement [RFC3392]. By advertising the 86 BGP Extended Message Capability to a peer, a BGP speaker conveys that 87 either peer MAY send, and both peers MUST be able to receive and 88 properly handle, BGP Extended Messages. 90 The BGP Extended Message Capability is a new BGP Capability [RFC3392] 91 defined with Capability code TBD and Capability length 0. 93 3. Operation 95 A BGP speaker that is willing to send and receive BGP Extended 96 Messages from its peer should advertise the BGP Extended Message 97 Capability to its peer using BGP Capabilities Advertisement 98 [RFC3392]. A BGP speaker may send extended messages to its peer only 99 if it has received the Extended Message Capability from its peer. 101 All BGP extended messages have maximum message size of 65535 octets. 102 The smallest message that may be sent consists of a BGP header 103 without a data portion (19 octets). All multi-octet fields are in 104 network byte order. 106 Applications generating messages which might be encapsulated within 107 BGP messages MUST limit the size of their payload to take into 108 account the maximum message size and all encapsulation overheads on 109 the path the encapsulated data are expected to traverse. 111 4. Acknowledgements 113 The authors thank John Scudder for his input. 115 5. IANA Considerations 117 This document defines the Extended Message Capability for BGP. The 118 new Capability code needs to be assigned by IANA. 120 6. Security Considerations 122 This extension to BGP does not change BGP's underlying security 123 issues. 125 7. References 127 7.1. Normative References 129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 130 Requirement Levels", BCP 14, RFC 2119, March 1997. 132 [RFC3392] Chandra, R. and J. Scudder, "Capabilities Advertisement 133 with BGP-4", RFC 3392, November 2002. 135 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 136 Protocol 4 (BGP-4)", RFC 4271, January 2006. 138 7.2. Informative References 140 [I-D.lepinski-bgpsec-overview] 141 Lepinski, M. and S. Turner, "An Overview of BGPSEC", 142 draft-lepinski-bgpsec-overview-00 (work in progress), 143 March 2011. 145 Authors' Addresses 147 Keyur Patel 148 Cisco Systems 149 170 W. Tasman Drive 150 San Jose, CA 95134 151 USA 153 Email: keyupate@cisco.com 154 Dave Ward 155 Juniper Networks 156 1194 N. Mathilda Ave 157 Sunnyvale, CA 94089 158 USA 160 Email: dward@juniper.net 162 Randy Bush 163 Internet Initiative Japan 164 5147 Crystal Springs 165 Bainbridge Island, Washington 98110 166 US 168 Phone: +1 206 780 0431 x1 169 Email: randy@psg.com