Extended Message support for BGP
draft-ietf-idr-bgp-extended-messages-34

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2019-07-30
Replaces draft-ymbk-bgp-extended-messages
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2019-07-08)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to jgs@juniper.net, jie.dong@huawei.com, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
Network Working Group                                            R. Bush
Internet-Draft                                              IIJ & Arrcus
Updates: 4271 (if approved)                                     K. Patel
Intended status: Standards Track                            Arrcus, Inc.
Expires: January 31, 2020                                        D. Ward
                                                           Cisco Systems
                                                           July 30, 2019

                    Extended Message support for BGP
                draft-ietf-idr-bgp-extended-messages-34

Abstract

   The BGP specification mandates a maximum BGP message size of 4,096
   octets.  As BGP is extended to support newer AFI/SAFIs and other
   features, there is a need to extend the maximum message size beyond
   4,096 octets.  This document updates the BGP specification RFC4271 by
   extending the maximum message size from 4,096 octets to 65,535 octets
   for all except the OPEN and KEEPALIVE messages.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 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 January 31, 2020.

Bush, et al.            Expires January 31, 2020                [Page 1]
Internet-Draft      Extended Message support for BGP           July 2019

Copyright Notice

   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
   (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
   2.  BGP Extended Message  . . . . . . . . . . . . . . . . . . . .   2
   3.  Extended Message Capability for BGP . . . . . . . . . . . . .   3
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Changes to RFC4271  . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The BGP specification [RFC4271] mandates a maximum BGP message size
   of 4,096 octets.  As BGP is extended to support newer AFI/SAFIs and
   newer capabilities (e.g., BGPsec [RFC8205] and BGP-LS [RFC7752]),
   there is a need to extend the maximum message size beyond 4,096
   octets.  This draft provides an extension to BGP to extend its
   message size limit from 4,096 octets to 65,535 octets for all except
   the OPEN and KEEPALIVE messages.

2.  BGP Extended Message

   A BGP message over 4,096 octets in length is a BGP Extended Message.

   BGP Extended Messages have a maximum message size of 65,535 octets.
   The smallest message that may be sent consists of a BGP KEEPALIVE
   which consists of 19 octets.

Bush, et al.            Expires January 31, 2020                [Page 2]
Internet-Draft      Extended Message support for BGP           July 2019

3.  Extended Message Capability for BGP

   The BGP Extended Message Capability is a new BGP Capability [RFC5492]
   defined with Capability code 6 and Capability length 0.

   To advertise the BGP Extended Message Capability to a peer, a BGP
Show full document text