Network Monitoring Protocol (NMP)
draft-gu-network-monitoring-protocol-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-16
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                                                 S. Zhuang
Intended status: Standards Track                                   Z. Li
Expires: January 18, 2019                                          Huawei
                                                           July 17, 2018

                   Network Monitoring Protocol (NMP)
                draft-gu-network-monitoring-protocol-00

Abstract

   To evolve towards automated network OAM (Operations, administration
   and management), the monitoring of control plane protocols is a
   fundamental necessity.  In this document, a network monitoring
   protocol (NMP) is proposed to provision the running status
   information of control plane protocols, e.g., IGP (Interior Gateway
   Protocol) and other protocols.  By collecting the protocol monitoring
   data and reporting it to the NMP monitoring server in real-time, NMP
   can facilitate network troubleshooting.  In this document, NMP for
   IGP troubleshooting are illustrated to showcase the necessity of NMP.
   IS-IS is used as the demonstration protocol, and the case of OSPF
   (Open Shortest Path First) and other control protocols will be
   elaborated in the future versions.  The operations of NMP are
   described, and the NMP message types and message formats are defined
   in the document.

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."

Gu, et al.               Expires January 3, 2019                [Page 1]
Internet-Draft         Network Monitoring Protocol             July 2018

   This Internet-Draft will expire on January 3, 2019.

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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  IS-IS Adjacency Issues  . . . . . . . . . . . . . . . . .   5
     3.2.  Forwarding Path Disconnection . . . . . . . . . . . . . .   6
     3.3.  IS-IS LSP Synchronization Failure . . . . . . . . . . . .   6
   4.  NMP Message Format  . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Protocol Selection Options  . . . . . . . . . . . . . . .   7
     4.2.  Message Types . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Message Format  . . . . . . . . . . . . . . . . . . . . .   8
       4.3.1.  Common Header . . . . . . . . . . . . . . . . . . . .   8
       4.3.2.  Per Adjacency Header  . . . . . . . . . . . . . . . .   9
       4.3.3.  Initiation Message  . . . . . . . . . . . . . . . . .  10
       4.3.4.  Adjacency Status Change Notification  . . . . . . . .  11
       4.3.5.  Statistic Report Message  . . . . . . . . . . . . . .  12
       4.3.6.  IS-IS PDU Monitoring Message  . . . . . . . . . . . .  14
       4.3.7.  Termination Message . . . . . . . . . . . . . . . . .  14
   5.  IANA  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  15
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text