W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2014

Re: Proposal for RtpSender.rtcpTransport

From: Justin Uberti <juberti@google.com>
Date: Mon, 3 Nov 2014 16:38:07 -0800
Message-ID: <CAOJ7v-3CYwna5p=6WNv-BYBRQrx9KaM5REkYU3g-u0+mG_uA1A@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
For consistency with Peter's proposal on handling the DtlsTransport for
SCTP (i.e., also named |transport|).

On Mon, Nov 3, 2014 at 4:15 PM, Bernard Aboba <Bernard.Aboba@microsoft.com>
wrote:

> Transport is fine because we expect RTP/RTCP mux to be in use much of the
> time so the RTP and RTCP transport will be the same.
>
>
>
> > On Nov 3, 2014, at 3:10 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
> >
> >> On 3 November 2014 12:53, Peter Thatcher <pthatcher@google.com> wrote:
> >>  readonly attribute DtlsTransport transport;
> >>  readonly attribute DtlsTransport rtcpTransport; // === transport if
> muxing
> >
> >
> > That sounds OK.  I suppose that you have considered
> > s/transport/rtpTransport/ here and decided against it?
> >
>
>
Received on Tuesday, 4 November 2014 00:38:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:42 UTC