Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-13.txt

["Len Holgate" <[e-mail]>]

Nit picking, but...

 4.2.1 step 6 should probably say "value of 13".

 Why doesn't 5.1 use MUST and MUST NOT when talking about client to server
and server to client masking. Up until now I was under the impression that
the server COULD mask data if it really wanted to (hence the need for the
masking bit rather than simply assuming that client -> server == masked and
server -> client != masked. The text in 5.1 now seems to imply that the
server SHOULD NOT mask but it doesn't say so. I realise that client ->
server masking is required and is specified with MUST in another part of the
document but I think it should be made clear that a server CAN mask if it
really wants to so that we don't end up with client implementations that
don't expect to receive masked frames. One situation where I might wish to
mask a frame from server to client would be in a pong where there's no need
for me to unmask the data if I simply echo the ping directly back...

Apart from that I think this draft addresses all of the issues that I
considered important and I like the additional text that explains why the
spec is as it is.

The result is a much better document than I was expecting when I first
started to take an interest around the time that draft 8 came out. Well done
everyone.

Len
http://www.lenholgate.com
http://www.serverframework.com