RFC 5357, "A Two-Way Active Measurement Protocol (TWAMP)", October 2008

Note: This RFC has been updated by RFC 5618, RFC 5938, RFC 6038, RFC 7717, RFC 7750, RFC 8545

Errata ID: 4429
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Steve Baillargeon
Date Reported: 2015-07-27
Held for Document Update by: Spencer Dawkins
Date Held: 2016-07-04

Section Appendix 1 says:

Section Appendix says: 
              controller                              responder
          +-----------------+                   +-------------------+
          |     Server      |<----------------->|                   |
          | Control-Client  |                   | Session-Reflector |
          | Session-Sender  |<--TWAMP-Test----->|                   |
          +-----------------+                   +-------------------+

It should say:

             controller                              responder
          +-----------------+                   +-------------------+
          |     Server      |                   |                   |
          | Control-Client  |                   | Session-Reflector |
          | Session-Sender  |<--TWAMP-Test----->|                   |
          +-----------------+                   +-------------------+

Notes:

The top arrow is not identified and misleading. It should be removed.

2015-07-29: RFC Editor changed the Type to Technical.

2016-07-04 Spencer chatted about this with Al Morton.

Al said -

> As I'm likely the last reachable author of TWAMP:
>
> In http://tools.ietf.org/html/rfc5357#section-1.2
> the Logical Model of TWAMP, the communications link
> between the Server and the Session-Reflector is indicated,
> but also undescribed. This communication is necessary for
> controlling state in the Session-Reflector, to start and
> stop sessions (which resets sequence renumbering in the
> Session-Reflector), for example.
>
> Also, section 1.2 says:
> "Unlabeled links in the figure are unspecified by
> this document and may be proprietary protocols."
>
> Like the Figure at the bottom of Page 4 in sec 1.2,
> the TWAMP-Light Figure is a re-formulation of the roles
> in the Logical Model, moving the Server alongside the
> Control-Client. The need for Server <-> Session-Reflector
> communications still exists for the case of TWAMP-Light
> operating *with* session state.

In previous discussions, Brian Trammell had suggested that unlabeled arrows should be marked "protocol unspecified" or "see section 1.2" here to clear up the confusion.

Spencer will leave this for the working group to consider if the document is updated.

Report New Errata