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

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2012-01-10 (latest revision 2011-06-28)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IDR Working Group                                               K. Patel
Internet-Draft                                                   D. Ward
Intended status: Standards Track                           Cisco Systems
Expires: July 13, 2012                                           R. Bush
                                               Internet Initiative Japan
                                                        January 10, 2012

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

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
   draft provides 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" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 July 13, 2012.

Copyright Notice

   Copyright (c) 2012 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

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

   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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Extended message Capability for BGP . . . . . . . . . . . . . . 3
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 4

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

1.  Introduction

   The BGP specification [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
   from 4096 octets to 65535 octets.

2.  Extended message Capability for BGP

   To advertise BGP Extended Message Capability to a peer, a BGP speaker
   uses BGP Capabilities Advertisement [RFC5492].  By advertising the
   BGP Extended Message Capability to a peer, a BGP speaker conveys that
   it is able to send, receive, and properly handle BGP Extended
   Messages.

   A peer which does not advertise this capability MUST NOT send BGP
   Extended Messages, and BGP Extended Messages MUST NOT be sent to it.

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

3.  Operation

   A BGP speaker that is willing to send and receive BGP Extended
   Messages from its peer should advertise the BGP Extended Message
   Capability to its peer using BGP Capabilities Advertisement
   [RFC5492].  A BGP speaker may send extended messages to its peer only
   if it has received the Extended Message Capability from its peer.

   All BGP extended messages have maximum message size of 65535 octets.
Show full document text