[bmwg] Fw: New ID: Considerations for Interpreting Packet Loss Observed by Active Performance Measurements

[Libin Liu <[e-mail]>]

Dear All,

Following my previous email, I would like to share a more detailed set of slides introducing draft-liu-ippm-active-loss-considerations. The presentation provides more background on the motivation, the interpretation problem, and the overall framework discussed in the draft.

The slides are available in the GitHub repo: https://github.com/LibinLiu0189/draft-ippm-active-loss-considerations/blob/main/slides-ippm-active-loss-considerations-00.pdf

If the topic is of interest, I would appreciate any comments or feedback. I would also be happy to discuss the work, either in Vienna during IETF 126 or online.

Thank you very much.


Best,
Libin

________________________________
From: Libin Liu <liulb=[e-mail]>
Sent: Thursday, July 2, 2026 9:30 AM
To: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: [bmwg] New ID: Considerations for Interpreting Packet Loss Observed by Active Performance Measurements

Dear All,

I would like to draw your attention to a new draft that has recently been submitted: draft-liu-ippm-active-measurement-loss-considerations-00.

This document discusses considerations for interpreting packet loss observed by active performance measurements. While measurement protocols and metrics accurately report observable outcomes such as packet loss, missing responses, delay, and delay variation, these observations alone often do not reveal the underlying operational cause. Similar measurement results may arise from different conditions, including congestion, forwarding failures, routing changes, filtering policies, endpoint behavior, multipath forwarding, or validation-related packet discard.

The document proposes a common interpretation framework that distinguishes measured outcomes from inferred causes. It discusses how different operational conditions may affect the interpretation of packet loss, delay, and delay variation in active performance measurements, including one-way and two-way measurements, OWAMP, TWAMP, STAMP, and measurements over ECMP and link aggregation. The document also discusses how additional operational context may assist operators and measurement systems in reasoning about possible explanations for observed measurement results. The draft is available here: https://datatracker.ietf.org/doc/draft-liu-ippm-active-loss-considerations/. The GitHub repository for the draft is also available here for issues, comments, and pull requests: https://github.com/LibinLiu0189/draft-ippm-active-loss-considerations.

Comments, suggestions, and discussions would be greatly appreciated. I would also be interested to hear whether similar interpretation challenges have been encountered in operational deployments or existing measurement systems, and whether there are additional scenarios that should be considered in the document.

Thank you very much.


Best,
Libin

> -----Original Messages-----
> From: [e-mail]
> Send time:Wednesday, 01/07/2026 17:09:28
> To: "Libin Liu" <[e-mail]>
> Subject: New Version Notification for draft-liu-ippm-active-loss-considerations-00.txt
>
> A new version of Internet-Draft
> draft-liu-ippm-active-loss-considerations-00.txt has been successfully
> submitted by Libin Liu and posted to the
> IETF repository.
>
> Name:     draft-liu-ippm-active-loss-considerations
> Revision: 00
> Title:    Considerations for Interpreting Packet Loss Observed by Active Performance Measurements
> Date:     2026-07-01
> Group:    Individual Submission
> Pages:    30
> URL:      https://www.ietf.org/archive/id/draft-liu-ippm-active-loss-considerations-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-liu-ippm-active-loss-considerations/
> HTML:     https://www.ietf.org/archive/id/draft-liu-ippm-active-loss-considerations-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-liu-ippm-active-loss-considerations
>
>
> Abstract:
>
>    Active performance measurement protocols and metrics are commonly
>    used to measure packet loss, delay, delay variation, reachability,
>    and path behavior.  When an active measurement packet is not
>    received, a response is missing, or a measurement exchange times out,
>    the measurement result identifies the observable outcome but often
>    does not identify the underlying cause.
>
>    Loss observed by active performance measurements can be associated
>    with congestion, queue discard, link or forwarding failures, routing
>    changes, endpoint or reflector behavior, administrative filtering,
>    policing, multipath effects, or validation-related packet discard
>    such as Source Address Validation (SAV).  Different operational
>    conditions can produce similar measurement observations, but they may
>    have different meanings and require different troubleshooting
>    actions.
>
>    This document discusses considerations for interpreting packet loss
>    observed by active performance measurements.  It provides a common
>    set of considerations for separating measured outcomes from inferred
>    causes, describes operational conditions that can lead to observed
>    loss, discusses implications for one-way and two-way measurements,
>    delay and delay variation interpretation, OWAMP, TWAMP, STAMP, and
>    measurements over ECMP and link aggregation.  It also discusses how
>    some considerations may apply to hybrid and passive performance
>    measurements and identifies sources of operational context that can
>    help operators and measurement systems reason about possible
>    explanations.
>
>
>
> The IETF Secretariat
>
_______________________________________________
bmwg mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]