[ippm] [Editorial Errata Reported] RFC8972 (8592)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 04 October 2025 00:41 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 847E46D28491; Fri, 3 Oct 2025 17:41:09 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 58796C000065; Fri, 3 Oct 2025 17:41:09 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20251004004109.58796C000065@rfcpa.rfc-editor.org>
Date: Fri, 03 Oct 2025 17:41:09 -0700
Message-ID-Hash: PHFHVYP2RMNBAAP2S5WSJMBSPFYTSIVI
X-Message-ID-Hash: PHFHVYP2RMNBAAP2S5WSJMBSPFYTSIVI
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: hawkins@obs.cr, hnydell@accedian.com, footer.foote@nokia.com, ippm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [ippm] [Editorial Errata Reported] RFC8972 (8592)
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/_sK9708NnI79IRif4AFN8LmmkZs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>
The following errata report has been submitted for RFC8972, "Simple Two-Way Active Measurement Protocol Optional Extensions". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8592 -------------------------------------- Type: Editorial Reported by: William Hawkins <hawkins@obs.cr> Section: 4.7 Original Text ------------- A Session-Reflector might be able to put only an "SW Local" (see Table 9) timestamp in the Follow-Up Timestamp field. Corrected Text -------------- A Session-Reflector might be able to put only an "SW Local" (see Table 9) timestamp in the Timestamp field of the reflected STAMP packet (Figure 2). Notes ----- Sorry for the back-to-back submissions -- I had these queued up and had delayed submission. In an earlier version of the RFC, the sentence quoted in the Original Text read "A Session-Reflector might be able to put in the Timestamp field only a "SW Local" (see Table 6) timestamp." (see, inter alia, https://datatracker.ietf.org/doc/html/draft-ietf-ippm-stamp-option-tlv-02#section-4.7) I have confirmed with one of the draft's original authors that a simple copy editing error was the cause of this tiny mistake. The sentence at the beginning of section 4.7 is meant to refer to the Timestamp field in the STAMP packet transmitted by the Session Reflector. The earlier draft of this RFC specified that what is currently named the Follow-Up Timestamp field should be named the Timestamp field. The name collision resulted in an overzealous search/replace hiccup. I hope that having the record reflect the correct field name will save future developers from having to scratch their head like I did. As usual, I sincerely appreciate the technical accuracy of the authors of the STAMP-related RFCs. As an implementer, the writing and specificity make it easy to build compliant software. I hope that this errata report is helpful for future implementers. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC8972 (draft-ietf-ippm-stamp-option-tlv-10) -------------------------------------- Title : Simple Two-Way Active Measurement Protocol Optional Extensions Publication Date : January 2021 Author(s) : G. Mirsky, X. Min, H. Nydell, R. Foote, A. Masputra, E. Ruffini Category : PROPOSED STANDARD Source : IP Performance Measurement Stream : IETF Verifying Party : IESG
- [ippm] [Editorial Errata Reported] RFC8972 (8592) RFC Errata System
- [ippm] Re: [Editorial Errata Reported] RFC8972 (8… mohamed.boucadair
- [ippm] Re: [Editorial Errata Reported] RFC8972 (8… Will Hawkins