BMP Compression
draft-msri-grow-bmp-compression-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-15
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)
Network Working Group                                      M. Srivastava
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                              P. Lucente
Expires: April 17, 2020                                              NTT
                                                        October 15, 2019

                            BMP Compression
                   draft-msri-grow-bmp-compression-00

Abstract

   This document provides specification for an optional compressed BMP
   Feed from a router to BMP station.

Requirements Language

   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 RFC 2119 [RFC2119] RFC 8174 [RFC8174] when, and only when, they
   appear in all capitals, as shown here.

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 April 17, 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

Srivastava & Lucente     Expires April 17, 2020                 [Page 1]
Internet-Draft               BMP compression                October 2019

   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.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Starting Compressor Capability  . . . . . . . . . . . . .   3
     2.2.  Compression Information TLV . . . . . . . . . . . . . . .   3
     2.3.  Compressed BMP Messages . . . . . . . . . . . . . . . . .   4
     2.4.  Compressor Overflow . . . . . . . . . . . . . . . . . . .   4
     2.5.  Error Handling  . . . . . . . . . . . . . . . . . . . . .   4
     2.6.  Processing of Compressed Route Monitoring messages  . . .   5
   3.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  BMP Compression Information TLV . . . . . . . . . . . . .   5
     4.2.  BMP Compression Route Monitoring message type . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The BGP Monitoring Protocol (BMP) allows monitoring of Rib-in RFC7854
   [RFC7854], Loc-Rib,BGP local-rib [I-D.ietf-grow-bmp-local-rib] and
   Rib-in and Rib-Out monitoring allows pre-policy and post-policy view
   of the prefix.  Thus, for a scaled setup, with all these kinds of
   monitoring enabled, BMP will get a lot of back pressure in the
   protocol as it needs to dump a huge data for its monitored peers,
   through a single socket towards BMP station.  BGP update PDU which is
   part of the BMP Route-monitoring (RM) message is also increasing.  It
   is no more limited to 4K as noted in draft-ietf-idr-bgp-extended-
   messages-21.  Essentially, BMP is heading towards becoming I/O bound
   monitoring protocol.  This document proposes compression of BMP feed
   towards BMP station.  Compression will ease the pressure on TCP
   socket between a router and BMP station.  Such a scheme would be
   useful if a route can spare some extra CPU for BMP operation.

   As it must be obvious, this scheme will require compressor mechanism
   at the BMP speaking router and a decompressor on the BMP station.
   The compression mechanism used at the BMP speaking is an
   implementation specific detail and is beyond the scope of this
   specification.

Srivastava & Lucente     Expires April 17, 2020                 [Page 2]
Internet-Draft               BMP compression                October 2019
Show full document text