W3C home > Mailing lists > Public > public-orca@w3.org > February 2014

Re: Proposal for SctpTransport (and big picture diagram)

From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 3 Feb 2014 11:12:25 -0800
Message-ID: <CAJrXDUGzZp4_J+bR5q+haTWeEF9PopZgvbZ98T1R=E8vEOsWiw@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-orca@w3.org" <public-orca@w3.org>
On Sat, Feb 1, 2014 at 7:38 PM, Bernard Aboba
<Bernard.Aboba@microsoft.com> wrote:
> Peter --
>
> The Big Picture diagram is great.
>
> A question about RTCDataChannelParameters.
>
> Now that we have allowed a Data Channel to be connected to
> a transport, I am wondering whether some parameters in
> RTCDataChannelParameters shouldn't be parameters of the transport
> instead.
>
> For example, in WebRTC 1.0 DataChannelInit, protocol refers to the
> sub-protocol, but that might or might not make sense depending on
> the transport.
>
> Does it make sense to have RTCSctpParameters?

Is it possible to have different data channels with different
protocols/sub-protocols in the same SctpTransport?  If so, then it
needs to be a per-data-channel setting, not a per-transport setting.
And my understanding is that you can have different
protocols/sub-protocols in the same transport.

>
> -------------------------------------------------------------------
> A missing piece of the current ORTC API is SCTP data channels.  I
> think this part of WebRTC 1.0 is pretty good, we this exception of its
> dependence on SDP and PeerConnection.  I propose we add a
> createDataChannel method and a ondatachannel event similar to the one
> on WebRTC 1.0's PeerConnection.  But instead of adding it to directly
> to DtlsTransport, we create an SctpTransport which wraps a
> DtlsTransport, like so:
>
>
> [Constructor(RTCDtlsTransport)]
> interface RTCSctpTransport {
>  attribute RTCDtlsTransport transport;
>
>  static RTCSctpCapabilities getCapabilities();
>
>  void start(RTCSctpCapabilities remoteCaps);
>  void stop();
>
>  DataChannel createDataChannel(RTCDataChannelParameters);
>  EventHandler<DataChannel> ondatachannel;
> }
>
> dictionary RTCSctpCapabilities {
>  int maxMessageSize;
> }
>
> // Same as WebRTC 1.0 DataChannelInit
> dictionary RTCDataChannelParameters {
>  boolean outOfOrderAllowed;
>  unsigned short maxRetransmitTime;
>  unsigned short maxRetransmitNum;
>  DOMString protocol;
>  boolean preset;
>  unsigned short stream;
> }
>
Received on Monday, 3 February 2014 19:13:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:39:24 UTC