--- 1/draft-ietf-idr-ext-opt-param-05.txt 2019-07-26 10:13:09.704355143 -0700 +++ 2/draft-ietf-idr-ext-opt-param-06.txt 2019-07-26 10:13:09.724355647 -0700 @@ -1,19 +1,19 @@ Internet Engineering Task Force E. Chen Internet-Draft Cisco Systems Updates: 4271 (if approved) J. Scudder Intended status: Standards Track Juniper Networks -Expires: December 30, 2016 June 28, 2016 +Expires: January 27, 2020 July 26, 2019 Extended Optional Parameters Length for BGP OPEN Message - draft-ietf-idr-ext-opt-param-05 + draft-ietf-idr-ext-opt-param-06 Abstract The Optional Parameters in the BGP OPEN message as defined in the base BGP specification are limited to 255 octets due to a one-octet length field. BGP Capabilities are carried in this field and may foreseeably exceed 255 octets in the future, leading to concern about this limitation. In this document we update RFC 4271 by extending the BGP OPEN length @@ -21,37 +21,37 @@ individual Optional Parameters is similarly extended. 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 December 30, 2016. + This Internet-Draft will expire on January 27, 2020. Copyright Notice - Copyright (c) 2016 IETF Trust and the persons identified as the + Copyright (c) 2019 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. 1. Introduction The Optional Parameters Length field in the BGP OPEN message is @@ -224,36 +224,36 @@ Mohapatra, Keyur Patel and Hannes Gredler for their valuable comments. 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, - . + . [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, - . + . 7.2. Informative References [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", RFC 4272, DOI 10.17487/RFC4272, January 2006, - . + . [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February - 2009, . + 2009, . Authors' Addresses Enke Chen Cisco Systems Email: enkechen@cisco.com John Scudder Juniper Networks