Re: [hybi] Changing meaning of 1007 status code ("frame" => "message")

As suggested in the other thread:
"
  1007 indicates that an endpoint is terminating the connection
  because it has received a text message that was not valid UTF-8 [RFC3629].
"
Text frames are the only UTF-8 things that are currently specified, and future UTF-8 things should have their own error codes.

On Sep 6, 2011, at 11:37 AM, Iñaki Baz Castillo wrote:

> As said in other mail I suggest changing the meaning of 1007 status code from:
> 
>      1007 indicates that an endpoint is terminating the connection
>      because it has received data that was supposed to be UTF-8 (such
>      as in a text frame) that was in fact not valid UTF-8 [RFC3629].
> 
> to:
> 
>      1007 indicates that an endpoint is terminating the connection
>      because it has received a message that was supposed to be UTF-8
>      that was in fact not valid UTF-8 [RFC3629].
> 
> 
> WS message format/encoding/content MUST be validated when receiving
> all the frames belonging to such message, as message inspection/usage
> belongs to the WS application, rather than the WS "transport" layer
> (framing stuf).
> 
> Of couse, a WS endpoint COULD validate each text frame by inspecting
> whether it contains valid UTF-8 bytes (completed or splitted bytes).
> That's could be an optimization out of the scope of the protocol
> specification (as many others).
> 
> I insist: this specification SHOULD define logic layers, basically:
> 
> * WS transport layer: framing stuff and control frames.
> * WS application layer: sends and receives *full* WS messages (binary or text).
> 
> - The WS transport layer receives control frames and send control
> frames to the other endpoint.
> - The WS transport layer gives received *messages* to the WS
> application layer (it doesn't matter giving the full buffered message
> or using straming).
> - The WS application layer sends *messages* to the WS transport layer.
> The transport layer decides whether to split, or not, the message into
> N frames.
> - The WS application layer notifies the WS transport layer to close
> the connection with status 1007 upon receipt of an invalid UTF-8 text
> message.
> - The WS application layer notifies the WS transport layer to close
> the connection due to other causes (normal termination and so).
> - The WS transport layer notifies the WS application layer when the
> connection has been closed (locally or remotely) and the exact cause.
> 
> How the WS transport layer and the WS application layer sends messages
> or notifies events to each other is out of the scope of this
> specification (of course).
> 
> 
> Validation of a WS message should be done by the WS application layer,
> so 1007 code should refer to "message" rather than "frame".
> 
> IMHO this is obvious, and it's also obvious that defining logic layers
> when creating a protocol specification is *good* for the implementor.
> If not, we end with these kinds of anarchic discussions (see other
> threads) which have difficult answer due to the protocol specification
> ambiguity.
> 
> Please consider it. Any protocol in Internet is designed with logical
> layers, all but WebSocket.
> 
> Regards.
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi