Version Capability for BGP
draft-abraitis-bgp-version-capability-05

Document Type Active Internet-Draft (individual)
Last updated 2020-08-03 (latest revision 2020-03-24)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream ISE state In ISE Review
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
Network Working Group                                        D. Abraitis
Internet-Draft                                                 Hostinger
Intended status: Informational                            March 24, 2020
Expires: September 25, 2020

                       Version Capability for BGP
                draft-abraitis-bgp-version-capability-05

Abstract

   In this document, we introduce a new BGP capability that allows the
   advertisement of a BGP speaker's version.

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 September 25, 2020.

Copyright Notice

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

Abraitis               Expires September 25, 2020               [Page 1]
Internet-Draft         Version Capability for BGP             March 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   2
   3.  Version Capability  . . . . . . . . . . . . . . . . . . . . .   2
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In modern data center designs, we tend to have conventional hosts
   participating in the routing process.  And the fleet of hosts has
   different versions of routing daemon.  This means that
   troubleshooting is a crucial part to quickly identify the root cause.
   This document introduces the new BGP capability to advertise the
   version of the routing daemon.

2.  Specification of Requirements

   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.

3.  Version Capability

   The Version Capability is a new BGP capability [RFC5492].  The
   implementation is specific to the vendor.  The version is
   unstructured and can be defined in any format the vendor decides.

   The length of the version SHOULD be limited to 64 bytes.  This is the
   limit to allow other capabilities as much space as they require.  The
   version MUST NOT be empty.

   This capability is OPTIONAL.  The vendor MUST implement a capability
   switch to enable or disable it.

   In case you reached 255 bytes of capabilities, you can disable this
   capability.  The capability is designed more to non-production
   environments where you need more visibility for troubleshooting
   purposes.  It's RECOMMENDED to turn it only inside a single
   Autonomous System domain or Autonomous System Confederations.

Abraitis               Expires September 25, 2020               [Page 2]
Internet-Draft         Version Capability for BGP             March 2020

   Such protocols like LLDP, CDP can provide the same information as
   well, but in containerized environments, it's very hard and NOT
   RECOMMENDED run background processes.  To minimize operational costs
   it would help having all the necessary information in place.

                   +--------------------------------+
                   |    Version Length (1 octet)    |
                   +--------------------------------+
                   |      Version (variable)        |
Show full document text