idnits 2.17.1 draft-ietf-idr-bgp-extended-messages-02.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 (January 10, 2012) is 4483 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-01 Summary: 0 errors (**), 0 flaws (~~), 2 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: July 13, 2012 R. Bush 6 Internet Initiative Japan 7 January 10, 2012 9 Extended Message support for BGP 10 draft-ietf-idr-bgp-extended-messages-02 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" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on July 13, 2012. 43 Copyright Notice 45 Copyright (c) 2012 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Extended message Capability for BGP . . . . . . . . . . . . . . 3 62 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 66 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 68 7.2. Informative References . . . . . . . . . . . . . . . . . . 4 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 71 1. Introduction 73 The BGP specification [RFC4271] mandates a maximum BGP message size 74 of 4096 octets. As BGP is extended to support newer AFI/SAFIs and 75 newer capabilities (e.g., [I-D.ietf-sidr-bgpsec-overview]), there is 76 a need to extend the maximum message size beyond 4096 octets. This 77 draft provides an extension to BGP to extend its current message size 78 from 4096 octets to 65535 octets. 80 2. Extended message Capability for BGP 82 To advertise BGP Extended Message Capability to a peer, a BGP speaker 83 uses BGP Capabilities Advertisement [RFC5492]. By advertising the 84 BGP Extended Message Capability to a peer, a BGP speaker conveys that 85 it is able to send, receive, and properly handle BGP Extended 86 Messages. 88 A peer which does not advertise this capability MUST NOT send BGP 89 Extended Messages, and BGP Extended Messages MUST NOT be sent to it. 91 The BGP Extended Message Capability is a new BGP Capability [RFC5492] 92 defined with Capability code TBD and Capability length 0. 94 3. Operation 96 A BGP speaker that is willing to send and receive BGP Extended 97 Messages from its peer should advertise the BGP Extended Message 98 Capability to its peer using BGP Capabilities Advertisement 99 [RFC5492]. A BGP speaker may send extended messages to its peer only 100 if it has received the Extended Message Capability from its peer. 102 All BGP extended messages have maximum message size of 65535 octets. 103 The smallest message that may be sent consists of a BGP header 104 without a data portion (19 octets). All multi-octet fields are in 105 network byte order. 107 Applications generating messages which might be encapsulated within 108 BGP messages MUST limit the size of their payload to take into 109 account the maximum message size and all encapsulation overheads on 110 the path the encapsulated data are expected to traverse. 112 4. Acknowledgements 114 The authors thank John Scudder and John Levine for their input. 116 5. IANA Considerations 118 The IANA is requested to register a new BGP Capability Code in the 119 upper range named BGP Extended Message Capability referring to this 120 document. 122 6. Security Considerations 124 This extension to BGP does not change BGP's underlying security 125 issues. 127 7. References 129 7.1. Normative References 131 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 132 Requirement Levels", BCP 14, RFC 2119, March 1997. 134 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 135 Protocol 4 (BGP-4)", RFC 4271, January 2006. 137 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 138 with BGP-4", RFC 5492, February 2009. 140 7.2. Informative References 142 [I-D.ietf-sidr-bgpsec-overview] 143 Lepinski, M. and S. Turner, "An Overview of BGPSEC", 144 draft-ietf-sidr-bgpsec-overview-01 (work in progress), 145 October 2011. 147 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 156 Dave Ward 157 Cisco Systems 158 170 W. Tasman Drive 159 San Jose, CA 95134 160 USA 162 Email: dward@cisco.com 164 Randy Bush 165 Internet Initiative Japan 166 5147 Crystal Springs 167 Bainbridge Island, Washington 98110 168 US 170 Phone: +1 206 780 0431 x1 171 Email: randy@psg.com