Re: [rtcweb] Meaning of SHOULD support/use interleaving

[Michael Tuexen <[e-mail]>]

On 27 Oct 2014, at 19:41, Christer Holmberg <[e-mail]> wrote:

> Hi,
> 
>>>>> Within the CLUE WG, we had a discussion regarding the following statement in section 6.1 of draft-ietf-rtcweb-data-channel-12.txt:
>>>>> 
>>>>> "The support for message interleaving as defined in
>>>>>                [I-D.ietf-tsvwg-sctp-ndata] SHOULD be used."
>>>>> 
>>>>> First, it is a little unclear what "the support SHOULD be used" means.
>>>> My understanding is that SCTP implementations supporting the extension will use it.
>>>> This is negotiated during the setup of the SCTP association.
>>> If it's done on SCTP level, why do we need to talk about it in the data channel draft? 
>>> 
>>> Is there a reason why it is important to use it for data channels? If so, does it apply to data channels in general? 
>> 
>> NDATA was added in order to avoid head-of-line blocking on the transport (if I understand this correctly, until 
>> this was added, sending a huge message would block the delivery of small messages on all channels until the huge message was fully delivered).
>> 
>> Unlike Michael, I see no reason to make this a SHOULD; I think it should be a MUST, and the older 
>> implementations in browsers should just be called out as non-conformant.
>> 
>> That said, I think that data channels ought to interoperate successfully with implementations that don't support the 
>> extension - but data channel implementations in WebRTC endpoints should be under a "MUST implement, MUST offer" ruleset.
> 
> First, keep in mind that I am NOT talking about WebRTC endpoints (which is one reason we shouldn't call it webrtc data channel to begin with, but that's another story...), but ANY type of endpoint that wants to use a data channel. 
> 
> Second, I am not talking about MUST support, but MUST use/offer.
> 
> Assume I have a CLUE endpoint, which will use a data channel ONLY to transport CLUE messages. CLUE messages aren't that hugeto begin with, and there will be no blocking of small messages on other channels - as there are no other channels.
> 
> So, why does the CLUE endpoint need to offer interleaving?
As far as I know we don't have different flavours of data channels. At least right now.

Best regards
Michael
> 
> Regards,
> 
> Christer
> 
> 
>> Whether messages are interleaved or not depends on the stream scheduler. This is a sender side only decision. The receiver has to deal with it.
>> It is not a MUST, since there are implementations now in use which don't support the extension.
>> 
>> Best regards
>> Michael
>>> 
>>> Second, does it mean that any data channel protocol (e.g CLUE) SHOULD use interleaving, even if the characteristics of the protocol wouldn't require it?
>>> 
>>> Regards,
>>> 
>>> Christer
>>> _______________________________________________
>>> rtcweb mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>> _______________________________________________
>> rtcweb mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> --
> Surveillance is pervasive. Go Dark.
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>