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

["Makaraju, Maridi Raju (Raju)" <[e-mail]>]

> > +1 to make N-DATA optional.
> >
> > Data channel provides a robust generic peer to peer communication channel.
> So, one can see that data channel may be used under non-webrtc contexts
> (like as in CLUE) as a general transport or as a replacement of native to
> SCTP to traverse firewalls. IMHO, majority of these use cases:
> > a. May just involve a single data channel (with possible multiplexing on
> top of it)
> > b. And may not use the DCEP either (both ends could assume same data
> channel stream id, this is similar to SCTP PPIDs).
> > We already made DCEP(b) as optional.
> >
> > If an app is using just a single data channel then there is no real
> benefit in using N-DATA. Then why not make it optional? Also, as already
> pointed out, making it optional won't break interop as it is still
> negotiated during SCTP setup time anyway.
> >
> > I would like to point out that there will be some webrtc applications
> which might just use one webrtc data channel for simplicity (and may use
> some multiplexing of different types of msgs/objects on top of it) or one is
> just sufficient as the app does not send/recv huge chunks of data. So, N-
> DATA isn't needed for such webrtc clients either. Then why add burden to
> such webrtc implementations!?
> Are you implementing this? I would say that adding N-DATA to an SCTP
> implementation with support
> for Stream Reconfiguration and PR-SCTP does not increase the complexity
> substantially...

<Raju>
I don't think the question is really about if NDATA adds complexity or not.
NDATA is a new capability to be added to SCTP stacks; and adding it takes
resources to develop, test, deliver, deploy/update.

As I just responded to Harald's post, we need to look at it from
data channel use in non-webrtc contexts and also data channel use
for non-browser webrtc clients. Just focusing on webrtc+browser alone
is not fair as not all the webrtc or non-webrtc data channel implementations
can keep up with the same pace as browsers do; also they don't have
resources like browser companies do!!

</Raju>

BR
Raju