Re: [rtcweb] Resolving RTP/SDES question in Paris

[Roman Shpount <[e-mail]>]

On Tue, Mar 20, 2012 at 9:48 AM, Iñaki Baz Castillo <[e-mail]> wrote:

> 2012/3/20 Roman Shpount <[e-mail]>:
> > Once again, I understand how this helps in case of HTTPS, but how would
> this
> > help in case of WebRTC? Media description is carried in some sort of
> > application defined protocol (can even be transmitted over an encrypted
> SCTP
> > data channel or encrypted in javaScript), so monitoring proxy cannot
> > reliably modify it. I understand how it can be allowed to fake the
> signature
> > on modified SDP by inserting a certificate in the browser, but how would
> the
> > proxy get to the SDP in the first place?
>
> That's up to the implementor, is not? This is: if a WebRTC provider
> wants to monitor the media by modifying the SDP it should design some
> system in which the SDP is carried by its systems (i.e. via HTTP(s) or
> WebSocket).
>
>
We got one group of people designing browsers, another group of people
designing monitoring proxies and the third group designing WebRTC
application. For the monitoring proxy to work it would need some sort of
network protocol to communicate with the browser (similar how HTTP proxy
needs a network protocol to work with the browser). I would expect what's
needed is some sort of network based protocol to send the SDP to a proxy,
get modified SDP back and pass it to JavaScript (or take the SDP from
JavaScript, through the proxy and to the media stack). I do not think this
is up to implementer, this is typically what the standards are for.
_____________
Roman Shpount