RFC Errata
Found 7 records.
Status: Verified (5)
RFC 6038, "Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features", October 2010
Source of RFC: ippm (tsv)
Errata ID: 4260
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Huck Zhao
Date Reported: 2015-02-04
Verifier Name: Spencer Dawkins
Date Verified: 2016-07-04
Section 5.2.1 says:
... When the Reflect Octets mode is selected, the Session-Sender SHALL use the following TWAMP-Test Packet Format in Unauthenticated mode: It should be Session-Reflector that SHALL use the following format.
It should say:
... When the Reflect Octets mode is selected, the Session-Reflector SHALL use the following TWAMP-Test Packet Format in Unauthenticated mode:
Notes:
I confirmed this with Al Morton via e-mail.
Errata ID: 5549
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Prabhjot Singh Sethi
Date Reported: 2018-11-07
Verifier Name: Mirja Kühlewind
Date Verified: 2020-03-04
Section 5.1.5 says:
In this combined mode, the Packet Padding to be reflected follows the 27 MBZ octets. In Authenticated or Encrypted modes, the Packet Padding to be reflected follows the 56 MBZ octets.
It should say:
In this combined mode, the Packet Padding to be reflected follows the 27 MBZ octets. In Authenticated or Encrypted modes, the Packet Padding to be reflected follows the 64 MBZ octets.
Notes:
To achieve symmetrical size in authenticated and encrypted mode length of mbz field needs to be 64 octects instead of 56 octects.
Errata ID: 6408
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.1.3 says:
When using the truncation process in TWAMP alone, see Section 4.2.1
of [RFC5357], the Session-Sender MUST append sufficient Packet
Padding octets to allow the same IP packet payload lengths to be used
in each direction of transmission (this is usually desirable). To
compensate for the Session-Reflector's larger test packet format, the
Session-Sender MUST append at least 27 octets of padding in
Unauthenticated mode, and at least 56 octets in Authenticated and
Encrypted modes. The sizes of TWAMP-Test protocol packets and the
resulting truncated padding to achieve equal packet sizes in both
directions are shown in the table below:
Morton & Ciavattone Standards Track [Page 11]
RFC 6038 Reflect Octets & Symmetric Size October 2010
+-------------------+----------------------+---------------------+
| Octets in: | Unauthenticated Mode | Auth/Encrypted Mode |
+-------------------+----------------------+---------------------+
| Reflector Header | 41 | 104 |
| Sender Header | 14 | 48 |
| Truncated Padding | 27 | 56 |
+-------------------+----------------------+---------------------+
TWAMP-Test Padding Truncation
When using the Reflect Octets mode simultaneously with the truncation
process that TWAMP recommends in Section 4.2.1 of [RFC5357], the
Session-Sender MUST append at least 27 octets of padding plus the
Length of the padding to reflect octets when operating in
Unauthenticated mode. The Session-Sender MUST append at least 56
octets of padding plus the Length of the padding to reflect octets
when operating in Authenticated and Encrypted modes.
It should say:
When using the truncation process in TWAMP alone, see Section 4.2.1
of [RFC5357], the Session-Sender MUST append sufficient Packet
Padding octets to allow the same IP packet payload lengths to be used
in each direction of transmission (this is usually desirable). To
compensate for the Session-Reflector's larger test packet format, the
Session-Sender MUST append at least 27 octets of padding in
Unauthenticated mode, and at least 64 octets in Authenticated and
Encrypted modes. The sizes of TWAMP-Test protocol packets and the
resulting truncated padding to achieve equal packet sizes in both
directions are shown in the table below:
Morton & Ciavattone Standards Track [Page 11]
RFC 6038 Reflect Octets & Symmetric Size October 2010
+-------------------+----------------------+---------------------+
| Octets in: | Unauthenticated Mode | Auth/Encrypted Mode |
+-------------------+----------------------+---------------------+
| Reflector Header | 41 | 112 |
| Sender Header | 14 | 48 |
| Truncated Padding | 27 | 64 |
+-------------------+----------------------+---------------------+
TWAMP-Test Padding Truncation
When using the Reflect Octets mode simultaneously with the truncation
process that TWAMP recommends in Section 4.2.1 of [RFC5357], the
Session-Sender MUST append at least 27 octets of padding plus the
Length of the padding to reflect octets when operating in
Unauthenticated mode. The Session-Sender MUST append at least 64
octets of padding plus the Length of the padding to reflect octets
when operating in Authenticated and Encrypted modes.
Notes:
Incorrect header sizes (104 instead of 112) and the required padding size (56 instead of 64) for modes with authentication and encryption.
Errata ID: 6409
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 4.2 says:
The Padding Length SHOULD be >= 56 octets when specifying a test session using the Authenticated or Encrypted TWAMP-Test modes to allow for the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357]. The Padding Length SHALL be > the Length of padding to reflect when specifying a test session using the OPTIONAL Reflect Octets mode. In Unauthenticated TWAMP-Test mode, the Padding Length SHALL be >= 27 + Length of padding to reflect octets when specifying a test session using both the OPTIONAL Reflect Octets mode and the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357]. In Authenticated or Encrypted TWAMP-Test modes, the Padding Length SHALL be >= 56 + Length of padding to reflect octets when specifying a test session using both the OPTIONAL Reflect Octets mode and the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357].
It should say:
The Padding Length SHOULD be >= 64 octets when specifying a test session using the Authenticated or Encrypted TWAMP-Test modes to allow for the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357]. The Padding Length SHALL be > the Length of padding to reflect when specifying a test session using the OPTIONAL Reflect Octets mode. In Unauthenticated TWAMP-Test mode, the Padding Length SHALL be >= 27 + Length of padding to reflect octets when specifying a test session using both the OPTIONAL Reflect Octets mode and the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357]. In Authenticated or Encrypted TWAMP-Test modes, the Padding Length SHALL be >= 64 + Length of padding to reflect octets when specifying a test session using both the OPTIONAL Reflect Octets mode and the truncation process that TWAMP recommends, see Section 4.2.1 of [RFC5357].
Notes:
Invalid required padding size (56 instead of 64) for modes with authentication and encryption.
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.
Status: Held for Document Update (2)
RFC 6038, "Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features", October 2010
Source of RFC: ippm (tsv)
Errata ID: 4258
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Huck Zhao
Date Reported: 2015-02-04
Held for Document Update by: Spencer Dawkins
Date Held: 2016-01-13
Section 4.3 says:
Last bullet on Page 8: Section 4.1.2 defines...
It should say:
Section 5.1.2 defines...
Notes:
(There's actually not a section 4.1.2 in this RFC)
Errata ID: 4259
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Huck Zhao
Date Reported: 2015-02-04
Held for Document Update by: Spencer Dawkins
Date Held: 2016-01-13
Section 5.2 says:
o Symmetrical Size mode: The Session-Reflector MUST operate using
the Session_Reflector Packet Format defined in Section 5.1.4,
where the Padding Octets are separated from the information
fields.
Section 5.1.4 defines Session_Sender Packet Format.
It should say:
o Symmetrical Size mode: The Session-Reflector MUST operate using
the Session_Sender Packet Format defined in Section 5.1.4,
where the Padding Octets are separated from the information
fields.
Notes:
This is just dropping a sentence that repeats what was just said previously.