[ippm] TWAMP protocol

["Jeff W. Boote" <boote at internet2.edu>]

I have a couple of high-level questions/suggestions for this protocol.

(I'm sorry I have not looked at this until now - I realize this could be pretty 
late in the process and I understand these suggestions could get the same amount 
of attention I have given twamp up till now. ;) )

1) Why not use the extension mechanism built into OWAMP to indicate the 
additional/different functionality? (The 'Modes' word of the server greeting.)

Currently, there is no way for a twamp or owamp client to determine the 
difference between an owamp and twamp server until it actually requests a test. 
This is after the authentication phase. If this protocol is going to piggy-back 
on the same port number, I think it should be a more cooperative citizen.

The owamp protocol allowed for an extension mechanism, I think it should be used 
for this. I think it would also make the additional IANA registry unneeded. (An 
errata to the owamp spec would be good to include the additional mode bits used.)

2) I'm a bit concerned with the fact that the request-session does not indicate 
anything about the schedule at all. Minimally, as someone running a server, I 
would want a way to indicate how much traffic I was willing to accept. There 
does not seem to be any way for the server to decide how intensive of a test to 
allow. If nothing else, the schedule could be used to indicate a MAX rate that 
the client promises not to exceed. (Obviously, it could lie and attempt to use 
more. But, it would also be possible for the reflector to report the abuse and 
shut down that socket.)

jeff

_______________________________________________
ippm mailing list
ippm at ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm