VPN Label Monitoring Using BMP
draft-gu-grow-bmp-vpn-label-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                              Y. Gu
Internet-Draft                                                    Huawei
Intended status: Standards Track                                 J. Chen
Expires: January 3, 2019                                         Tencent
                                                                   P. Mi
                                                               S. Zhuang
                                                                   Z. Li
                                                                  Huawei
                                                           July 02, 2018

                     VPN Label Monitoring Using BMP
                     draft-gu-grow-bmp-vpn-label-00

Abstract

   The BGP Monitoring Protocol (BMP) is designed to monitor BGP running
   status, such as BGP peer relationship establishment and termination
   and route updates.  This document provides a method of collecting the
   VPN label using BMP, as well as an implementation example.

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

Gu, et al.               Expires January 3, 2019                [Page 1]
Internet-Draft            VPN Label Monitoring                 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.  Extension of BMP Peer Up Message  . . . . . . . . . . . . . .   4
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Border Gateway Protocol (BGP) [RFC4271], as an inter-Autonomous
   (AS) routing protocol, is used to exchange network reachability
   information between BGP systems.  Later on, [RFC4760] extends BGP to
   carry not only the routing information for BGP, but also for multiple
   Network Layer protocols (e.g., IPv6, Multicast, etc.), known as the
   MP-BGP (Multiprotocol BGP).  The MP-BGP is currently widely deployed
   in case of MPLS L3VPN, to exchange VPN labels learned for the routes
   from the customer sites over the MPLS network.

   The BGP Monitoring Protocol (BMP) [RFC7854] has been proposed around
   2006 to monitor the BGP routing information, which includes the
   monitoring of BGP peer status, BGP route update, and BGP route
   statistics.  BMP is realized through setting up the TCP session
   between the monitored BGP device and the BMP monitoring station, and
   then periodic/event-triggerred messages are sent unidirectionaly from
   the monitored device to the BMP monitoring station.  Before BMP was
   introduced, such information could be only obtained through manual
   query, such as screen scraping.  The introduction of BMP greatly
   improves the BGP routing monitoring efficiency without interrupting
   or interfering the ongoing services.

Gu, et al.               Expires January 3, 2019                [Page 2]
Internet-Draft            VPN Label Monitoring                 July 2018

   Currently, BMP is mainly utilized to monitor the public BGP routes.
   There are also cases that the VPN (Virtual Private Network) route/
Show full document text