--- 1/draft-ietf-idr-bgp-extended-messages-22.txt 2017-10-30 16:17:26.680640891 -0700 +++ 2/draft-ietf-idr-bgp-extended-messages-23.txt 2017-10-30 16:17:26.708641561 -0700 @@ -1,21 +1,21 @@ Network Working Group R. Bush Internet-Draft Internet Initiative Japan Updates: 4271 (if approved) K. Patel Intended status: Standards Track Arrcus, Inc. -Expires: February 16, 2018 D. Ward +Expires: May 1, 2018 D. Ward Cisco Systems - August 15, 2017 + October 28, 2017 Extended Message support for BGP - draft-ietf-idr-bgp-extended-messages-22 + draft-ietf-idr-bgp-extended-messages-23 Abstract The BGP specification mandates a maximum BGP message size of 4096 octets. As BGP is extended to support newer AFI/SAFIs and other features, there is a need to extend the maximum message size beyond 4096 octets. This document updates the BGP specification RFC4271 by providing an extension to BGP to extend its current maximum message size from 4096 octets to 65535 octets for all except the OPEN message. @@ -29,37 +29,37 @@ words, without normative meaning. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- - Drafts is at http://datatracker.ietf.org/drafts/current/. + Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on February 16, 2018. + This Internet-Draft will expire on May 1, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents - (http://trustee.ietf.org/license-info) in effect on the date of + (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 @@ -184,20 +184,24 @@ This extension to BGP does not change BGP's underlying security issues; see [RFC4272]. Section 5 allowed a receiver to accept an Extended Message even though they had not advertised the capability. This slippery slope will surely lead to sloppy implementations sending Extended Messages when the receiver is not prepared to deal with them, e.g. to peer groups. At best, this will result in errors; at worst, buffer overflows. + Due to increased (over [RFC4272]) memory requirements for buffering, + there may be increased exposure to resource exhaustion, intentional + or unintentional. + 9. Acknowledgments The authors thank Alvaro Retana, Enke Chen, Susan Hares, John Scudder, John Levine, and Job Snijders for their input; and Oliver Borchert and Kyehwan Lee for their implementations and testing. 10. References 10.1. Normative References