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

Document Type Active Internet-Draft (individual)
Last updated 2020-01-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                         January 2, 2020
Expires: July 5, 2020

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

Abstract

   Within a Segment Routing domain, segment routed measurement packets
   can be sent along pre-determined paths.  This enables new kinds of
   measurements.  Connectivity monitoring allows to supervise the state
   and performance 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 July 5, 2020.

Copyright Notice

   Copyright (c) 2020 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

Geib                      Expires July 5, 2020                  [Page 1]

Internet-Draft              Abbreviated Title               January 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

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

1.  Introduction

   Within a Segment Routing domain, 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
   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 exchanges hello messages
   between neighbors to keep alive routing and switfly adapt routing to
   topology changes.  Network Operators may be interested in monitoring
   connectivity and congestion of interfaces or sub-paths at a timescale
   of seconds, minutes or hours.  In both cases, the periodicity is
Show full document text