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

Re: [ACTION-43] (sdp related objects and global namespace) - way forward

From: Randell Jesup <randell-ietf@jesup.org>
Date: Tue, 19 Jun 2012 15:53:28 -0400
Message-ID: <4FE0D8B8.8000508@jesup.org>
To: public-webrtc@w3.org
On 6/19/2012 10:13 AM, Stefan Hakansson LK wrote:
> On 06/19/2012 03:42 PM, Justin Uberti wrote:
>>
>>
>> On Tue, Jun 19, 2012 at 4:03 AM, Dominique Hazael-Massieux <dom@w3.org
>> <mailto:dom@w3.org>> wrote:
>>
>>     Le vendredi 15 juin 2012 à 12:07 -0400, Justin Uberti a écrit :
>>
>>      > I still don't understand why think that developers who are
>> unwilling
>>      > to understand these concepts or use a library that takes care
>> of them
>>      > will be able to deploy a TURN server or handle the other necessary
>>      > aspects of running a reliable communications service.
>>
>>     I think assuming that PeerConnection will only be used by developers
>>     that want to run a reliable communication service is a mistake; as I
>>     have said before, the availability of a P2P data channel is likely
>> to be
>>     as big if not much bigger in usage than video/audio chat.
>>
>>
>> I agree regarding the potential for the data channel, but said channel
>> requires the same infrastructure (i.e. TURN) as voice/video.
>
> In an experimental phase STUN could be sufficient, and then there seem
> to exist publicly available servers (source
> http://www.voip-info.org/wiki/view/STUN). Of course TURN (with some
> fallback - http?) would have to be deployed before being able to launch
> something that is reliable in uncontrolled network topologies.

Small or casual developers may simply live without TURN; I agree for a 
solid implementation it will be required, OR the user will need to add 
port-mappings, OR routers may become WebRTC/ICE/etc-aware and provide 
the needed port mappings on demand (as some do today with SIP ALGs).

Also, that's a property of the DTLS/ICE transport channel; the 
DataChannel protocol and DOM API might be used in the future over other 
transports without this issue.

That all said, this is a minor issue and I'm fine with doing whatever is 
easy today if it doesn't close doors for us in future uses.

Let's get it out the door... :-)
-- 
Randell Jesup
randell-ietf@jesup.org
Received on Tuesday, 19 June 2012 19:54:28 UTC

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