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

Document Type Active Internet-Draft (idr WG)
Last updated 2015-07-24
Replaces draft-ymbk-bgp-extended-messages
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state In WG Last Call
Revised I-D Needed - Issue raised by WG
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2015-07-18)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to "Susan Hares" <shares@ndzh.com.>
Network Working Group                                           K. Patel
Internet-Draft                                                   D. Ward
Updates: 4271 (if approved)                                Cisco Systems
Intended status: Standards Track                                 R. Bush
Expires: January 25, 2016                      Internet Initiative Japan
                                                           July 24, 2015

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

Abstract

   The BGP specification mandates a maximum BGP message size of 4096
   octets.  As BGP is extended to support newer AFI/SAFIs, there is a
   need to extend the maximum message size beyond 4096 octets.  This
   document updates the BGP specification in RFC4271 by providing an
   extension to BGP to extend its current message size from 4096 octets
   to 65535 octets.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English 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/.

   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 25, 2016.

Patel, et al.           Expires January 25, 2016                [Page 1]
Internet-Draft      Extended Message support for BGP           July 2015

Copyright Notice

   Copyright (c) 2015 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
   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  . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The BGP specification RFC4271 [RFC4271] mandates a maximum BGP
   message size of 4096 octets.  As BGP is extended to support newer
   AFI/SAFIs and newer capabilities (e.g.,
   [I-D.ietf-sidr-bgpsec-overview]), there is a need to extend the
   maximum message size beyond 4096 octets.  This draft provides an
   extension to BGP to extend its current message size limit from 4096
   octets to 65535 octets.

2.  BGP Extended Message

   A BGP message over 4096 octets in length is a BGP Extended Message.

   BGP Extended Messages have maximum message size of 65535 octets.  The
   smallest message that may be sent consists of a BGP header without a
   data portion (19 octets).

Patel, et al.           Expires January 25, 2016                [Page 2]
Internet-Draft      Extended Message support for BGP           July 2015

   Multi-octet fields MUST be in network byte order.
Show full document text