Hi All,

This draft comprehensively details procedures for leveraging the STAMP to 
measure performance in Segment Routing networks (SR-MPLS/SRv6). Especially, the 
new extension of STAMP to support new modes (one-way, loopback, and 
timestamp-and-forward) significantly enhances scalability and practicality for 
operational deployments. Below are some suggestions for further discussion. 


It will be better to add descriptions of Business Edition (BE) scenarios, 
covering both the SR-MPLS and SRv6 planes, to ensure the document encompasses 
all SR situations.


The document hints at the capability negotiation mechanisms for the newly 
defined MNA.TSF and End.TSF in sections 7.1.2 and 7.2.2, but without specifics. 
Detailed elaboration is suggested.


It39s advised to outline clock synchronization requirements separately for 
one-way and two-way measurements, as well as for packet-loss measurement. This 
would better inform real network deployments.


Best Regards,


Liyan






From: internet-drafts
Date: 2025-05-09 21:52
To: i-d-annou...@ietf.org
CC: spring
Subject: [spring] I-D Action: draft-ietf-spring-stamp-srpm-18.txt


Internet-Draft draft-ietf-spring-stamp-srpm-18.txt is now available. It is a
work item of the Source Packet Routing in Networking (SPRING) WG of the IETF.
 
   Title:   Performance Measurement Using Simple Two-Way Active Measurement 
Protocol (STAMP) for Segment Routing Networks
   Authors: Rakesh Gandhi
            Clarence Filsfils
            Bart Janssens
            Mach(Guoyi) Chen
            Richard Foote
   Name:    draft-ietf-spring-stamp-srpm-18.txt
   Pages:   53
   Dates:   2025-05-09
 
Abstract:
 
   Segment Routing (SR) leverages the source routing paradigm and
   applies to both Multiprotocol Label Switching (SR-MPLS) and IPv6
   (SRv6) data planes.  This document describes procedures for
   Performance Measurement in SR networks using the Simple Two-Way
   Active Measurement Protocol (STAMP) defined in RFC 8762, along with
   its optional extensions defined in RFC 8972 and further augmented in
   RFC 9503.  The described procedure is used for links and SR paths
   (including SR Policies and SR IGP Flexible Algorithm paths), as well
   as Layer-3 and Layer-2 services in SR networks, and is applicable to
   both SR-MPLS and SRv6 data planes.
 
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-stamp-srpm/
 
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-spring-stamp-srpm-18.html
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-stamp-srpm-18
 
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
 
 
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org

 

_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org

Reply via email to