idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-01.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 28, 2011) is 4678 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-00 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 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 30, 2011 Juniper Networks 6 R. Bush 7 Internet Initiative Japan 8 June 28, 2011 10 Extended Message support for BGP 11 draft-ietf-idr-bgp-extended-messages-01 13 Abstract 15 The BGP specification mandates a maximum BGP message size of 4096 16 octets. As BGP is extended to support newer AFI/SAFIs, there is a 17 need to extend the maximum message size beyond 4096 octets. This 18 draft provides an extension to BGP to extend its current message size 19 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 30, 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 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 draft-ietf-sidr-bgpsec-overview-00 (work in progress), 146 June 2011. 148 Authors' Addresses 150 Keyur Patel 151 Cisco Systems 152 170 W. Tasman Drive 153 San Jose, CA 95134 154 USA 156 Email: keyupate@cisco.com 157 Dave Ward 158 Juniper Networks 159 1194 N. Mathilda Ave 160 Sunnyvale, CA 94089 161 USA 163 Email: dward@juniper.net 165 Randy Bush 166 Internet Initiative Japan 167 5147 Crystal Springs 168 Bainbridge Island, Washington 98110 169 US 171 Phone: +1 206 780 0431 x1 172 Email: randy@psg.com