Storing BMP messages in MRT Format
draft-petrie-grow-mrt-bmp-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
Global Routing Operations                                      C. Petrie
Internet-Draft                                                       NTT
Intended status: Standards Track                        November 1, 2019
Expires: May 4, 2020

                   Storing BMP messages in MRT Format
                      draft-petrie-grow-mrt-bmp-00

Abstract

   This document extends the Multi-threaded Routing Toolkit (MRT) export
   format to support the storage of BMP messages.

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 May 4, 2020.

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.

Petrie                     Expires May 4, 2020                  [Page 1]
Internet-Draft                 BMP in MRT                  November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  BMP Type  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     5.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   The MRT record format [RFC6396] was developed to provide researchers
   and engineers a means to encapsulate, export, and archive routing
   protocol transactions and routing information base snapshots.

   BMP [RFC7854] was developed to monitor BGP sessions, and also
   includes messages containing routing protocol transactions and
   Routing Information Base contents and changes.  BMP [RFC7854] does
   not define a mechanism for exporting and archiving BMP messages.  MRT
   can be a suitable format for this.

   This document contains an optional extension to the MRT format
   [RFC6396] and defines additional MRT types to permit storage of BMP
   messages.

2.  BMP Type

   This document defines the following new MRT Types:

   o  BMP

   o  BMP_ET

   These MRT types support the BMP protocol.  They are used to encode
   the exchange of BMP messages.  The _ET variant is for use with the
   Extended Timestamp MRT Header.

Petrie                     Expires May 4, 2020                  [Page 2]
Internet-Draft                 BMP in MRT                  November 2019

   The format of the MRT Message field for the BMP types is as follows:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        Address Family           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Remote IP Address (variable)                |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Local IP Address (variable)                 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                  BMP Message Contents (variable)
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                                 Figure 1

   The Address Family indicates what types of addresses are in the
   subsequent address fields.  At present, the following AFI Types are
   supported:

      1 - AFI_IPv4

      2 - AFI_IPv6

   The Address Family value only applies to the IP addresses contained
   in the MRT header.  The BMP type is otherwise transparent to the
   contents of the actual message that may contain any valid AFI/SAFI
Show full document text