A Connectivity Monitoring Metric for IPPM
draft-geib-ippm-connectivity-monitoring-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
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)
ippm                                                        R. Geib, Ed.
Internet-Draft                                          Deutsche Telekom
Intended status: Standards Track                          March 11, 2019
Expires: September 12, 2019

               A Connectivity Monitoring Metric for IPPM
               draft-geib-ippm-connectivity-monitoring-00

Abstract

   Segment Routed measurement packets can be sent along pre-determined
   paths.  This allows new kinds of measurements.  Connectivity
   monitoring allows to supervise the state of a connection or a
   (sub)path from one or a few central monitoring systems.  This
   document specifies a suitable type-P connectivity monitoring metric.

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 September 12, 2019.

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

Geib                   Expires September 12, 2019               [Page 1]

Internet-Draft              Abbreviated Title                 March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  A brief segment routing connectivity monitoring framework . .   3
   3.  Singleton Definition for Type-P-Path-Connectivity-and-
       Congestion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Metric Name . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Metric Parameters . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Metric Units  . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Defintion . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Discussion  . . . . . . . . . . . . . . . . . . . . . . .   7
     3.6.  Methodologies . . . . . . . . . . . . . . . . . . . . . .   7
     3.7.  Errors and Uncertainties  . . . . . . . . . . . . . . . .   9
     3.8.  Reporting the Metric  . . . . . . . . . . . . . . . . . .   9
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Segment Routing enables sending measurement packets along pre-
   determined segment routed paths [RFC8402].  A segment routed path may
   consist of pre-determined sub paths down to specific router-
   interfaces.  It may also consist of sub paths spanning multiple
   routers, given that all segments to address a desired path are
   available and known at the SR domain edge interface.

   A Path Monitoring System or PMS (see [RFC8403]) is a dedicated rather
   central Segment Routing domain monitoring device (as compared to a
   distributed monitoring approach based on router data and functions
   only).  Monitoring individual sub-paths or point-to-point connections
   is executed for different purposes.  IGP routing exchanges hello
   messages between neighbors to keep alive routing and switfly adapt to
   changes.  Network Operators may be interested in monitoring
   connectivity and lasting congestion of interfaces or sub-paths at a
   higher timescale,e.g., on the order of seconds.  This is still
   significantly faster than interface monitoring based on router
   information, which may be collected on a minute timescale to reduce
   the CPU load caused by monitoring.

Show full document text