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

Gabriel Montenegro wrote:
> The real issue here is that MUST is the right keyword if something is required for interoperability. A SHOULD means you are recommended to do a certain thing, but you may depart from that recommendation if you know better or have a good reason. MAY is for optional stuff. 
>
> My take on it is that the basic framing is absolutely a MUST. Optional stuff like multiplexing or compression are MAYs (when and if we get to them). Fragmentation support sounds like a SHOULD.
>   

Fragmentation is a MUST, based on past experience with non-browser 
clients and HTTP.

Since a non-browser client might only send small queries, but receive 
large data, a lazy implementation with would skip fragmenting support 
entirely (because they never need to send fragments) if it's SHOULD, 
because it's slightly easier for them to force the server to buffer all 
data, which defeats the whole point of fragmenting. Since the receiving 
code for fragmentation is actually small, allowing that kind of laziness 
is harmful.

There's no requirement that anyone send fragments, of course, but they 
MUST be able to receive fragmented data, or server writers will go insane.

-- Scott
>   
>> -----Original Message-----
>> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
>> Julian Reschke
>> Sent: Thursday, September 02, 2010 5:05 AM
>> To: James Graham
>> Cc: hybi@ietf.org
>> Subject: Re: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt
>>
>> On 02.09.2010 13:47, James Graham wrote:
>>     
>>> On 09/02/2010 12:45 AM, Internet-Drafts@ietf.org wrote:
>>>
>>>       
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-hybi-thewebsocketproto
>>>> col-01.txt
>>>>
>>>>         
>>> A few initial comments:
>>>
>>> The framing sections seem to have a lot of SHOULDs. This is worrying
>>> as SHOULD-level conditions can't really be tested (it is not an error
>>> to violate them) and can be a source of interoperability problems. I
>>> would
>>>       
>>  > ...
>>
>> Nothing stops you from testing them; you just need to either state that you
>> reported SHOULD failures as violations, or need to report different compliance
>> levels.
>>
>> Best regards, Julian
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>     
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>
>
>   