BMP Extensible Route-Monitoring Messages
draft-hsmit-bmp-extensible-routemon-msgs-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-18
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
GROW Working Group                                          H. Smit, Ed.
Internet-Draft                                                     Nokia
Intended status: Standards Track                           July 18, 2018
Expires: January 19, 2019

                BMP Extensible Route-Monitoring Messages
              draft-hsmit-bmp-extensible-routemon-msgs-00

Abstract

   The BGP Monitoring Protocol (BMP) is defined in RFC7854.  Most of the
   types of messages in BMP are extensible via the mechanism of TLVs.
   However, the most important type of message, the route-monitoring
   message, has a fixed format.

   This document proposes a relatively small change to the format of BMP
   route-monitoring messages.  The new format of route-monitoring
   messages is no longer fixed-format, but tlv-encoded.  This document
   also proposes to split the route-monitoring message-type into 3 new
   message-types.  For Adj-RIB-In, Adj-RIB-Out and Loc-RIB.

   This document proposes two types of TLVs to be used in this new
   format.  A TLV to report the BGP update message itself.  And a flags-
   field TLV, to report state of the reported routes.

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 [1].

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 19, 2019.

Smit                    Expires January 19, 2019                [Page 1]
Internet-Draft  BMP Extensible Route-Monitoring Messages       July 2018

Copyright Notice

   Copyright (c) 2018 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.  Limitations of the current route-monitoring message format  .   3
   3.  Proposed changes  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  New Message-types . . . . . . . . . . . . . . . . . . . . . .   5
   5.  TLV-encoding  . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  BGP Update Message TLV  . . . . . . . . . . . . . . . . . . .   6
   7.  Flags-field TLV . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Two flags per piece of state  . . . . . . . . . . . . . .   6
     7.2.  Proposed flags in the flag-field TLV  . . . . . . . . . .   7
     7.3.  Reporting state in the flags-field TLV that is already
           known . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Example of layout of a tlv-encoded BMP route-monitoring
       message . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   11. Contributor Addresses . . . . . . . . . . . . . . . . . . . .   9
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     13.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The BGP Monitoring Protocol (BMP) is defined in RFC 7854 [2].  One of
   the message-types is the Route-Monitoring message.  The route-
   monitoring message consists of:

   o  generic bmp header

   o  per-peer bmp header

Smit                    Expires January 19, 2019                [Page 2]
Internet-Draft  BMP Extensible Route-Monitoring Messages       July 2018

   o  a full BGP update message

   This means that route-monitoring messages have a fixed format.  This
   brings some limitations to the BMP protocol regarding extensibility.
Show full document text