Re: [hybi] Ping/Pong body (was Re: TSV-Directorate review of draft-ietf-hybi-thewebsocketprotocol-07)

[Bruce Atherton <[e-mail]>]

I agree with you and Magnus that there will be lots of times you want 
the body of the Pong to be able to vary from the Ping. But perhaps a 
compromise could be reached. What if the body of the Pong must begin 
with the body of the Ping, but can have additional information after that?

On 12/05/2011 11:31 PM, Salvatore Loreto wrote:
> <as individual contributor>
>
> I agree with the fact that coordinating Ping and Pong body value 
> assigment,
> so that unsollicited Pong and reply Pong do not conflict each other,
> should be clearly specified in the spec instead of leave this duty to 
> the implementors or service designers.
>
>
> More I share the concern Magnus has on the text in Section 4.5.2;
> the text reduce significantly the possibility to develop future 
> extensions based on ping/pong.
> If people think that it is OK, I won't oppose, but I want to be sure 
> that people are well aware of this fact.
>
>     On 4/29/11 8:00 PM, Magnus Westerlund wrote:
>
>     28. Section 4.5.2:
>
>     The message
>         bodies (i.e. both the Extension data (if any) and the Application
>         data) of the Ping and Pong MUST be the same.
>
>     I find the fact that the extension body data needs to be the same to be
>     an issue. If one develops an extension that actually has to do with the
>     frames and their transport then not being able to change the data will
>     be an issue. As an example could be a Websocket RTT measurement
>     extension where you like to include in the PONG both the PING sending
>     time from the PING message and the amount of time between receving PING
>     and sending PONG. Thus requiring one to add additional data.
>