RFC 5357, "A Two-Way Active Measurement Protocol (TWAMP)", October 2008Source of RFC: ippm (tsv)
See Also: RFC 5357 w/ inline errata
Errata ID: 1590
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-11-05
Verifier Name: Lars Eggert
Date Verified: 2009-05-14
Section 4.2.1, pg.17 says:
<< second paragraph on page 17 >> Sequence Number is the sequence number of the test packet according | to its transmit order. It starts with zero and is incremented by one | for each subsequent packet. The Sequence Number generated by the Session-Reflector is independent from the sequence number of the arriving packets.
It should say:
Sequence Number is the sequence number of the test packet according | to its transmit order within the TWAMP test session. It starts with ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | zero and is incremented by one for each subsequent packet in the vvvvvvv ^^^^^^^^ | session. The Sequence Number generated by the Session-Reflector is independent from the sequence number of the arriving packets.
In the original text, it remains unclear whether this sequence number
is maintained per session, per Session-Sender, or per Session-Reflector.
Appendix I, in the 3rd text paragraph on page 23, seems to give
a hint that the Session-Reflector generated sequence numbers might
have been intended to be generated independently per *session*.
Since similar behavior is not present in OWAMP, it ugently needs to
be specified in RFC 5357 to further interoperable implementations.
The corrected text proposed aims at cure this deficiency via a change
with minimal footprint.