W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2015

Re: PR for adding RtpSender.transport, RtpReceiver.transport, RTCDtlsTransport, RTCIceTransport, etc

From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 22 Jun 2015 15:22:45 -0700
Message-ID: <CABcZeBNbPp1CcsvDdTj7+N9EaYR4VXK-=ernWYoECdinKrvuWQ@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Jun 22, 2015 at 3:19 PM, Bernard Aboba <Bernard.Aboba@microsoft.com>

>  On Jun 22, 2015, at 6:16 PM, Peter Thatcher <pthatcher@google.com> wrote:
>   ​
> I'm fine with changing it to "getSelectedCandidatePair"
> ​ (what we had at TPAC 2014)​
> .  Does anyone else have an opinion before I change it?
>  I think we need to be very clear about what it means. If the pair has
> been checked successfully and media is being sent, but the "use candidate"
> flag was not set, is it considered "selected"?


"11.1.1.  Procedures for Full Implementations

   Agents always send media using a candidate pair, called the selected
   candidate pair.  An agent will send media to the remote candidate in
   the selected pair (setting the destination address and port of the
   packet equal to that remote candidate), and will send it from the
   local candidate of the selected pair. "

Received on Monday, 22 June 2015 22:23:52 UTC

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