Network Monitoring Protocol (NMP)
draft-gu-network-mornitoring-protol-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                                                 S. Zhuang
Intended status: Standards Track                                   Z. Li
Expires: January 3, 2019                                          Huawei
                                                           July 02, 2018

                   Network Monitoring Protocol (NMP)
                 draft-gu-network-mornitoring-protol-00

Abstract

   To enable automated network OAM (Operations, administration and
   management), the availability of network protocol running status
   information is a fundamental step.  In this document, a network
   monitoring protocol (NMP) is proposed to provision the information
   related to running status of IGP (Interior Gateway Protocol) and
   other control protocols.  It can facilitate the network
   troubleshooting of control protocols in a network domain.  Typical
   network issues are illustrated as the usecases of NMP for ISIS to
   showcase the necessity of NMP.  Then the operations and the message
   formats of NMP for ISIS are defined.  In this document ISIS is used
   as the illustration protocol, and the case of OSPF and other control
   protocols will be included in the future version.

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         Network Monitoring Protocol             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
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  ISIS Adjacency Issues . . . . . . . . . . . . . . . . . .   4
     3.2.  Forwarding Path Disconnection . . . . . . . . . . . . . .   5
     3.3.  ISIS LSP Synchronization Failure  . . . . . . . . . . . .   5
   4.  Extensions of NMP for ISIS  . . . . . . . . . . . . . . . . .   6
     4.1.  Message Types . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Message Format  . . . . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Common Header . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Per Peer Header . . . . . . . . . . . . . . . . . . .   7
       4.2.3.  Initiation Message  . . . . . . . . . . . . . . . . .   8
       4.2.4.  Peer Status Change Notification . . . . . . . . . . .   9
       4.2.5.  Statistic Report Message  . . . . . . . . . . . . . .  10
       4.2.6.  ISIS PDU Monitoring Message . . . . . . . . . . . . .  12
       4.2.7.  Termination Message . . . . . . . . . . . . . . . . .  12
   5.  IANA  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

1.1.  Motivation

   The requirement for better network OAM approaches has been greatly
   driven by the network evolvement.  Network OAM provides visibility to
   the network health conditions, and is beneficial for faster network
Show full document text