Found 1 record.
Status: Held for Document Update (1)
RFC 8186, "Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)", June 2017
Source of RFC: ippm (ops)
Errata ID: 8662
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Long Dao
Date Reported: 2025-12-01
Held for Document Update by: Mahesh Jethanandani
Date Held: 2025-12-08
Section 2.2 says:
o The Control-Client MUST set the PTPv2 Timestamp flag value to 1 in
the Modes field in the Set-Up-Response message if the Server
advertised that the Session-Reflector has the ability to use the
PTPv2 format for timestamps. Otherwise, the flag MUST be set to
0.
It should say:
o The Control-Client MUST set the PTPv2 Timestamp flag value to 1 in
the Modes field in the Set-Up-Response message if the Server
advertised that the Session-Reflector has the ability to use the
PTPv2 format for timestamps and the Session-Sender can also support
and wish to use this format. Otherwise, the flag MUST be set to 0.
Notes:
According to the original text, the Control-Client HAVE TO respond with a Timestamp flag of 1 in the Set-Up-Response message if it received that flag from the Server, regardless of whether the Session-Sender support the PTP format or not. This should not be the case, and the Control-Client should be allowed to reject using the PTP format (by setting its Timestamp flag to 0) if the Session-Sender doesn't support or doesn't wish to use it.