[ippm] Re: Call for adoption: draft-gandhi-ippm-stamp-ber-07 (Ends 2026-10-12)

["Wen, Bin" <[e-mail]>]

Dear WG,

I have reviewed this draft and support the workgroup adoption.

Regards,

Bin


From: Thomas Graf via Datatracker <[e-mail]>
Date: Monday, September 28, 2026 at 4:44 AM
To: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: [ippm] Call for adoption: draft-gandhi-ippm-stamp-ber-07 (Ends 2026-10-12)

This message starts a ippm WG Call for Adoption of:
draft-gandhi-ippm-stamp-ber-07

This Working Group Call for Adoption ends on 2026-10-12

Abstract:
   The Simple Two-Way Active Measurement Protocol (STAMP), as defined in
   RFC 8762, along with its optional extensions specified in RFC 8972,
   can be utilized for active measurement.  Networks may experience
   transmission bit errors due to various factors, including poor fiber
   quality.  Even with efficient CRC and FEC mechanisms, some bit errors
   may escape detection and correction, referred to as residual bit
   errors.  This document further augments the STAMP extensions
   specified in RFC 8972 to enable the measurement of the residual bit
   error rate within the "Extra Padding" TLV of STAMP test packets.

Slides from IETF 126 IPPM/BMWG session:
   https://datatracker.ietf.org/meeting/126/materials/slides-126-ippm-simple-two-way-active-measurement-protocol-stamp-extensions-for-residual-bit-error-rate-measurement-draft-gandhi-ippm-stamp-ber<https://urldefense.com/v3/__https://datatracker.ietf.org/meeting/126/materials/slides-126-ippm-simple-two-way-active-measurement-protocol-stamp-extensions-for-residual-bit-error-rate-measurement-draft-gandhi-ippm-stamp-ber__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujspdDDQg$>

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the ippm WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujPTQZn8A$>
[2] https://datatracker.ietf.org/doc/bcp79/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujGJF0k-c$>
[3] https://datatracker.ietf.org/doc/rfc6701/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujceNbdic$>

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-gandhi-ippm-stamp-ber/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-gandhi-ippm-stamp-ber/__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujqCsthwQ$>

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-gandhi-ippm-stamp-ber-07<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-gandhi-ippm-stamp-ber-07__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9PujyBraDbA$>

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-gandhi-ippm-stamp-ber-07<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-gandhi-ippm-stamp-ber-07__;!!CQl3mcHX2A!CmcMWAEqufTLjDMuOUENR2AHkq7ZkxCi1eKBBxfsyXiwnDqhI_2Q-4lmu8Xo4DO40GVC9Pujw6XE228$>
_______________________________________________
ippm mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]