Re: [rtcweb] SIP Glare - Re: Minimal SDP negotiation mechanism

[Cullen Jennings <[e-mail]>]

On Sep 22, 2011, at 2:04 PM, Christer Holmberg wrote:

> 
> Hi Cullen, 
> 
>>>> Magnus' analysis worries me a bit, because it seems to assume 
>>>> specific functionality in the gateway (tracking of state and ability 
>>>> to generate SIP messages depending on state).
>>>> It seems reasonably simple to build a gateway, but we quickly get to 
>>>> the point where we have to write standards for the gateway function 
>>>> .... which could lead us down rather deep ratholes.
>>> 
>>> Are we assuming that a media gateway will be required for RTP/media 
>>> communication between a WebRTC client (web browser) and a SIP node?
>>> If such decision is taken IMHO it's sad.
>> 
>> My take is that most people want to make sure that a translator between SIP and web stuff would only need to look at signalling - it would not touch the media. I'm working on the asumption that is what any solution will look like. 
>> So, no media GW. 
> 
> If so, what is your assumption then regarding ICE? That the SIP nodes will support ICE, or that the browser will be allowed to communicate with the SIP nodes without enabling ICE?

I see no way of solving the security problems without having ICE or something more or less like it. Therefore, I'm working on the assumption that it will only work if the SIP side supports ICE, or is front ended by a SBC with media GW that does ICE. In the short term, there will be some devices that don't do ICE but SIP devices are increasingly having ICE added. Particularly SIP devices that are internet facing because the need for NAT traversal. 

I find requiring ICE to be a very unfortunate assumption to have to make - obviously it reduces the number of legacy voip devices WebRTC devices can talk to without an SBC but I don't see any way around this limitation. Allowing web browsers inside the firewall to send packets to an arbitrary address that is inside the firewall with no validation that address speaks RTP is not acceptable.