[ippm] [Technical Errata Reported] RFC8762 (8518)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 22 July 2025 21:18 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 0AED748D734B; Tue, 22 Jul 2025 14:18:00 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id CAE641D5687; Tue, 22 Jul 2025 14:17:59 -0700 (PDT)
To: gregimirsky@gmail.com, guo.jun2@zte.com.cn, hnydell@accedian.com, footer.foote@nokia.com, ippm-ads@ietf.org, marcus.ihlar@ericsson.com, thomas.graf@swisscom.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250722211759.CAE641D5687@rfcpa.rfc-editor.org>
Date: Tue, 22 Jul 2025 14:17:59 -0700
Message-ID-Hash: KJN7B5BXQFGQ6WELMP2M27ADOLGPOA2Z
X-Message-ID-Hash: KJN7B5BXQFGQ6WELMP2M27ADOLGPOA2Z
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: hawkinsw@obs.cr, ippm@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [ippm] [Technical Errata Reported] RFC8762 (8518)
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/QhoDmae-983IKn_HFF1XCADWP0s>
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 RFC8762, "Simple Two-Way Active Measurement Protocol". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8518 -------------------------------------- Type: Technical Reported by: Will Hawkins <hawkinsw@obs.cr> Section: 4.3.1-4.5 Original Text ------------- The Session-Sender TTL field is one octet long, and its value is the copy of the TTL field in IPv4 (or Hop Limit in IPv6) from the received STAMP-Test packet. Corrected Text -------------- The Session-Sender TTL field is one octet long, and its value is the copy of the TTL field in IPv4 (or Hop Limit in IPv6) from the received STAMP-Test packet. If an implementation cannot fetch the actual TTL value from the TTL field (or Hop Limit) in the IP header of the received STAMP-Test packet, it MUST set the Session- Sender TTL value as 255. Notes ----- The RFC contains no language describing the value that the reflector should include in the Session Sender TTL field of a reflected STAMP packet if the TTL value cannot be read from the IP header of the test packet. The language seems to presume that fetching the TTL is always possible. Having a description for the behavior of an implementation when that is not the case would help the life of the implementer. As an added benefit of defining the behavior in the "error case", there would be an increase in the compatibility between STAMP and TWAMP Light. TWAMP Light, as a result of its reliance on TWAMP, specifies the behavior of an implementation that cannot fetch the TTL value from a test packet (and is the source of the suggested language given above). 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. -------------------------------------- RFC8762 (draft-ietf-ippm-stamp-10) -------------------------------------- Title : Simple Two-Way Active Measurement Protocol Publication Date : March 2020 Author(s) : G. Mirsky, G. Jun, H. Nydell, R. Foote Category : PROPOSED STANDARD Source : IP Performance Measurement Stream : IETF Verifying Party : IESG
- [ippm] [Technical Errata Reported] RFC8762 (8518) RFC Errata System
- [ippm] Re: [Technical Errata Reported] RFC8762 (8… Will Hawkins
- [ippm] Re: [Technical Errata Reported] RFC8762 (8… mohamed.boucadair
- [ippm] Re: [Technical Errata Reported] RFC8762 (8… Will Hawkins
- [ippm] Re: [Technical Errata Reported] RFC8762 (8… mohamed.boucadair
- [ippm] Re: [Technical Errata Reported] RFC8762 (8… Will Hawkins