[ippm] Internet-Draft draft-li-ippm-ioam-packet-triggered-reporting-00.txt is now

["[e-mail]" <[e-mail]>]

Hi all,
 
We submitted a new document to discuss a packet-triggered statistics reporting  extension for In-situ Operations, Administration, and Maintenance (IOAM).

The draft may be found here: https://datatracker.ietf.org/doc/draft-li-ippm-ioam-packet-triggered-reporting/

The draft  defines an extension mechanism for "In-situ OAM" (IOAM) called "packet-triggered statistical reporting." 

Its core objective is to address the challenge of how to more reliably and promptly trigger and report statistical information (such as packet and byte counts) for each measurement interval in periodic packet loss measurement. 

The draft standardizes a 2-bit "Cycle ID" field, which enables the receiving node (the decapsulating node) to automatically detect the sequential change in the Cycle ID value within packets (0 → 1 → 2 → 3 → 0...) and thereby trigger the reporting of statistics for the previous measurement cycle. 

This approach serves as an alternative or supplement to traditional timer-based reporting methods. 

The mechanism also defines rules for generating "Keepalive" packets to ensure that during measurement intervals with no user data traffic, at least one packet carrying the Cycle ID reaches the receiver, thereby maintaining measurement continuity. 

Its significance lies in providing a more precise, traffic-agnostic, and globally clock-synchronization-independent OAM measurement triggering solution for high-performance networks (such as data centers and telecom core networks), effectively enhancing the automation and timeliness of network performance monitoring and fault localization.

This is an initial version for discussion on the mailing list.  

We will update it based on the discussion progress! 

Welcome more contribution and collaboration!

Thanks!



[e-mail]