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

[Christer Holmberg <[e-mail]>]

Hi,

>>> I am not suggesting different flavors - I am suggesting to make the usage of
>>> interleaving optional. Other SCTP features are also optional (including reliability, ordering etc).
>>>
>>> Where are these things optional? According to
>>> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section
>>> -6.1 an implementation MUST implement PR-SCTP and the support of the
>>> FORWARD-TSN chunk will be negotiated similar to the NDATA chunk. I don't see a difference, especially not if we move to MUST support NDATA.
>>
>> For example, section 6.1 says:
>>
>>      "The partial reliability extension defined in [RFC3758] MUST be supported."
>>
>> However, in CLUE we say that a CLUE entity MUST NOT *use* the extension, as all CLUE messages are required to be sent reliably.
>
> That is OK. However, support for PR-SCTP MUST be there and it will be negotiated. You just never send a message with partial reliability. At least this is my understanding...

So, can the same be done for interleaving? I.e. the support MUST be there, but e.g. CLUE entities can choose not to use it?

Note that my issue is not about support, it's about usage :)

What resource is being conserved by not just requiring it?

I don’t know. The task is to figure out whether there are technical reasons to mandate usage of certain SCTP features for CLUE.

Regards,

Christer