Subject: Re: [ippm] Comments for draft-ietf-ippm-twamp-reflect-octets-05

From: Al Morton <[email-masked]>
Date: Mon, 31 May 2010 09:51:07 -0400

...and I just did.

I got rid of the "Client octets" and simply
mentioned a possibility for other Packet Padding.

Al

At 12:23 PM 4/26/2010, Al Morton wrote:
>Thanks Steve, these are good comments, and
>we'll resolve them as you suggest in the next draft.
>Al
>
>
>At 12:21 PM 4/26/2010, [email-masked] wrote:
>>Content-type: multipart/alternative;
>>  boundary="Boundary_(ID_NEJL3a72RdguL2k8r4BKBg)"
>>Content-language: en
>>
>>Hi Al
>>Here are some comments on the latest draft.
>>
>>- It will be best to explicitly indicate that both the control and 
>>test protocols can reflect octets in an independent manner even if 
>>it is indirectly stated in the introduction.
>>
>>- The definition for the "Server octets" field shall indicate where 
>>those bits should appear in the Packet Padding (to be reflected) field.
>>
>>- The spec should state that a zero value in the "Server octets" 
>>field means the Server does not desire these octets to be reflected.
>>
>>- The spec should state that a non-zero value in the "Server 
>>octets" field means the Server desires these octets to be 
>>reflected. The actual position of these octets in the padding 
>>octets of the test packets shall be clarified.
>>
>>- A defintion for Client octets field should be provided and 
>>indicates that is the equal to Octets to be reflected field (from 
>>Request-TW-Session).
>>
>>- The spec should indicate when the Client octets field shall 
>>appear in the Packet Padding (to be reflected) field. Based on the 
>>example provided, it looks like the usage of this field is optional 
>>and/or implementation-specific when reflecting octets in test 
>>packets. If so, please indicate it.
>>
>>Thank you
>>
>>Regards
>>Steve Baillargeon
>>_______________________________________________
>>ippm mailing list
>>[email-masked]
>>https://www.ietf.org/mailman/listinfo/ippm
>
>_______________________________________________
>ippm mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/ippm