Re: [rtcweb] Requiring ICE for RTC calls

[Cameron Byrne <[e-mail]>]

On Sep 26, 2011 7:52 AM, "Roman Shpount" <[e-mail]> wrote:
>
> PSTN carriers today almost always run SBCs. At the same time I have not
seen an SBC from any major US carrier with firmware newer the 2 years old.
I've never seen an SBC in carrier deployment that currently supports ICE or
SRTP.
>
> Bottom line, no carriers currently support ICE or SRTP. If we create the
market requirements for them to support ICE and SRTP, it will take them 3-5
years to add such support. If we have anybody from SBC manufacturing
companies or carriers who can provide evidence to the opposite, I would love
to hear from them. In any case, it would be prudent to provide a way to use
current non-ICE, non-SRTP with RTC.
> _____________
> Roman Shpount
>

I am with a mobile carrier that does FMC and we have products that use SRTP
to an SBC today. I don't know about ICE, but I think your projection is
clearly not true.  If other carriers delay, I am glad to take their
business.

Cameron

>
>
> On Mon, Sep 26, 2011 at 10:45 AM, Cameron Byrne <[e-mail]>
wrote:
>>
>>
>> On Sep 26, 2011 7:30 AM, "Roman Shpount" <[e-mail]> wrote:
>> >
>> > I think requiring ICE in RTC is not only unfortunate, it will make it
impossible to connect to PSTN without media gateway. If we complete this
specification, and phone carriers decide that there is a business case for
them to support RTC clients directly, it will take them 3-5 years to
implement ICE in SBC. From what I've seen major carriers run SBC firmware
which is normally 2-3 years old. If we add time it takes to implement ICE in
SBC, plus time it will take PSTN provider to verify and test the feature, we
are easily looking into 5 year time frame.
>> >
>> > Since we need to have user confirmation to start a media call anyway,
and since this is not going to be any different from what SIP clients are
currently doing, it would make sense to allow a plain non-ICE, non-SRTP
call.
>> >
>> > Finally, ICE specification are desinged to interop with non-ICE end
points. We will need to change ICE to accomplish what you are doing.
>> >
>>
>> Maybe I misundersatnd you, but the PSTN carriers today and in the future
will always run an SBC because that is their security policy.
>>
>> Regarding firmware, they react to market needs and timing.
>>
>> Cb
>>
>> _____________
>> > Roman Shpount
>> >
>> >
>> > On Mon, Sep 26, 2011 at 1:23 AM, Randell Jesup <[e-mail]>
wrote:
>> >>
>> >> On 9/22/2011 4:37 PM, Cullen Jennings wrote:
>> >>>
>> >>> On Sep 22, 2011, at 2:04 PM, Christer Holmberg wrote:
>> >>>
>> >>>> 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.
>> >>
>> >>
>> >> I agree we can't solve the security issue with permission to send with
the
>> >> current threat model without ICE or some equivalent.
>> >>
>> >> There is another option that may help with some of the use cases (I've
mentioned
>> >> this before in the discussion on screensharing, among others).  For a
number
>> >> of the use cases security is an impassible problem with the current
threat model.
>> >> Those use cases generally involve replacing cases where an existing
desktop
>> >> install or plugin was used (webex, screensharing, vnc, SIP softclient,
Skype, etc).
>> >> Those cases all currently involve the user implicitly giving these
apps total
>> >> or close to code that could do pretty much anything on the user's
computer,
>> >> and are also often the "ongoing usage" authentication cases.
>> >>
>> >> The only mitigating safety of the external app/plugin model is that
they're typically
>> >> signed and go through the platforms software-install procedure,
cert-showing, UACs, etc.
>> >>
>> >> Currently people are trying to work out the HTML5 "installed" webapp
security model;
>> >> if that's far enough along we may be able to piggyback off that.   I'm
looking into it.
>> >>
>> >>
>> >> --
>> >> Randell Jesup
>> >> [e-mail]
>> >>
>> >> _______________________________________________
>> >> rtcweb mailing list
>> >> [e-mail]
>> >> https://www.ietf.org/mailman/listinfo/rtcweb
>> >
>> >
>> >
>> > _______________________________________________
>> > rtcweb mailing list
>> > [e-mail]
>> > https://www.ietf.org/mailman/listinfo/rtcweb
>> >
>
>