Real-Time Monitoring Link/Protocol Neighbor State
draft-xu-rtgwg-monitoring-neighbor-state-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                              F. Xu
Internet-Draft                                                   Tencent
Intended status: Standards Track                               S. Zhuang
Expires: April 25, 2019                                            Y. Gu
                                                                  Huawei
                                                        October 22, 2018

           Real-Time Monitoring Link/Protocol Neighbor State
              draft-xu-rtgwg-monitoring-neighbor-state-00

Abstract

   Various protocols are deployed in today's networks, such as BGP /
   ISIS / OSPF etc.  Link neighbor state changes and protocol neighbor
   state changes are the most important network events that need to be
   processed with the highest priority.  In particular, the SDN
   controller needs to quickly sense the link neighbor & protocol
   neighbor state change information in the network.  Thus, the various
   policies applied by the SDN controller to the network can quickly
   match the current state of the network.  This document discusses some
   possible scenarios and the relevant requirements.

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 April 25, 2019.

Xu, et al.               Expires April 25, 2019                 [Page 1]
Internet-Draft          Monitoring Neighbor State           October 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.  Requirements and Options  . . . . . . . . . . . . . . . . . .   3
   3.  Neighbor State Information Format . . . . . . . . . . . . . .   4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Various protocols are deployed in today's networks, such as BGP /
   ISIS / OSPF / LDP / BFD etc.  When managing a network, one of the
   most important things to monitor is changes to the various protocols'
   neighbor states.  Many times a protocol neighbor state change is
   indicative of a problem on the network, and it is an important basis
   for the SND controller to deploy the traffic steering policies.
   There are several ways to monitor these state changes, e.g. we can
   use command-line interface (CLI) to get them from the devices, but
   typically it's done with either SNMP based polling and/or SNMP traps.
   For BGP, we can use BMP (BGP Monitoring Protocol) [RFC7854] to
   collect BGP neighbor state change information.

   Link neighbor state changes and protocol neighbor state changes are
   the most important network events that need to be processed with the
   highest priority.  In particular, the SDN controller needs to quickly
   sense the link neighbor & protocol neighbor state change information
   in the network.  Thus, the various policies applied by the SDN
   controller to the network can quickly match the current state of the
   network.

Xu, et al.               Expires April 25, 2019                 [Page 2]
Internet-Draft          Monitoring Neighbor State           October 2018
Show full document text