W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2013

Re: [Bug 21877] API is unable to handle inbound streams prior to arrival of answer

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 2 May 2013 09:57:27 -0700
Message-ID: <CABkgnnV53k5g4UHKfqB8-E2JW4fgoOAAUJUyS=ZLpvkZS6bFCg@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 2 May 2013 00:18, Harald Alvestrand <harald@alvestrand.no> wrote:
> On 05/01/2013 04:13 PM, Martin Thomson wrote:
>>
>> No discussion?
>>
>> With an already-established DTLS-SRTP connection the crypto doesn't
>> block new inbound media.
>
>
> Ah - you're talking about subsequent additions of media after the first
> offer/answer, not the initial addition of media. I thought you were talking
> abou the initial media case.

Yes, I was.  In part.

I can imagine cases where a=fingerprint isn't needed ahead of time
(the callee fingerprint is in your contacts list).  Then you only need
to worry about ICE, and nothing says that you can't have the answerer
nominate and use peer-reflexive addresses.

Oh wait, we're using SDP offer/answer.  Sorry, the WebRTC API doesn't
permit those scenarios.
Received on Thursday, 2 May 2013 16:57:54 UTC

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