RFC Errata
RFC 6038, "Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features", October 2010
Source of RFC: ippm (ops)See Also: RFC 6038 w/ inline errata
Errata ID: 6410
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2021-01-25
Verifier Name: Martin Duke
Date Verified: 2021-01-26
Section 5.2.1 says:
Section 4.2.1 of [RFC5357] recommends a padding truncation process for use in TWAMP. When using that process in conjunction with the Reflect Octets mode, the Session-Reflector MUST reflect the designated octets from the Session-Sender's test packet in the Packet Padding (from Session-Sender) field, and MAY re-use additional Packet Padding from the Session-Sender. The Session-Reflector MUST truncate the padding such that the highest number octets are discarded, and the test packet length equals the Session-Sender's packet length. When using the recommended truncation process, the Session-Reflector MUST truncate exactly 27 octets of padding in Unauthenticated mode, and exactly 56 octets in Authenticated and Encrypted modes.
It should say:
Section 4.2.1 of [RFC5357] recommends a padding truncation process for use in TWAMP. When using that process in conjunction with the Reflect Octets mode, the Session-Reflector MUST reflect the designated octets from the Session-Sender's test packet in the Packet Padding (from Session-Sender) field, and MAY re-use additional Packet Padding from the Session-Sender. The Session-Reflector MUST truncate the padding such that the highest number octets are discarded, and the test packet length equals the Session-Sender's packet length. When using the recommended truncation process, the Session-Reflector MUST truncate exactly 27 octets of padding in Unauthenticated mode, and exactly 64 octets in Authenticated and Encrypted modes.
Notes:
Invalid required padding size (56 instead of 64) for modes with authentication and encryption.