Performance Measurement Using STAMP for Segment Routing Networks
draft-gandhi-spring-stamp-srpm-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-23
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)
SPRING Working Group                                      R. Gandhi, Ed.
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: September 24, 2020                                     D. Voyer
                                                             Bell Canada
                                                                 M. Chen
                                                                  Huawei
                                                             B. Janssens
                                                                    Colt
                                                          March 23, 2020

    Performance Measurement Using STAMP for Segment Routing Networks
                   draft-gandhi-spring-stamp-srpm-00

Abstract

   Segment Routing (SR) leverages the source routing paradigm.  SR is
   applicable to both Multiprotocol Label Switching (SR-MPLS) and IPv6
   (SRv6) data planes.  This document specifies procedure for sending
   and processing probe query and response messages for Performance
   Measurement (PM) in Segment Routing networks.  The procedure uses the
   mechanisms defined in RFC 8762 (Simple Two-Way Active Measurement
   Protocol (STAMP)) for Delay Measurement, and uses the mechanisms
   defined in this document for Loss Measurement.  The procedure
   specified is applicable to SR-MPLS and SRv6 data planes and is used
   for both Links and end-to-end SR Policies.

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 24, 2020.

Gandhi, et al.         Expires September 24, 2020               [Page 1]
Internet-Draft          STAMP for Segment Routing             March 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   4
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Reference Topology  . . . . . . . . . . . . . . . . . . .   5
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Example Provisioning Model  . . . . . . . . . . . . . . .   6
   4.  Probe Messages  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Probe Query Message . . . . . . . . . . . . . . . . . . .   7
       4.1.1.  Delay Measurement Query Message . . . . . . . . . . .   7
       4.1.2.  Loss Measurement Query Message  . . . . . . . . . . .   8
       4.1.3.  Probe Query for Links . . . . . . . . . . . . . . . .   9
       4.1.4.  Probe Query for End-to-end Measurement for SR Policy    9
       4.1.5.  Control Code Field for STAMP Messages . . . . . . . .  10
       4.1.6.  Loss Measurement Query Message Formats for STAMP  . .  12
     4.2.  Probe Response Message  . . . . . . . . . . . . . . . . .  14
       4.2.1.  One-way Measurement Mode  . . . . . . . . . . . . . .  15
       4.2.2.  Two-way Measurement Mode  . . . . . . . . . . . . . .  15
       4.2.3.  Loopback Measurement Mode . . . . . . . . . . . . . .  17
       4.2.4.  Loss Measurement Response Message Formats for STAMP .  17
     4.3.  Node Address TLV for STAMP Message  . . . . . . . . . . .  19
     4.4.  Return Path TLV for STAMP Message . . . . . . . . . . . .  19
   5.  Performance Measurement for P2MP SR Policies  . . . . . . . .  21
   6.  ECMP Support for SR Policies  . . . . . . . . . . . . . . . .  22
   7.  Additional Message Processing Rules . . . . . . . . . . . . .  22
     7.1.  TTL and Hop Limit . . . . . . . . . . . . . . . . . . . .  22
Show full document text