Re: [rtcweb] Signalling, SDP, and the way we think about interconnecting RTCWEB applications

[Iñaki Baz Castillo <[e-mail]>]

2011/10/14  <[e-mail]>:
> The interconnection trapezoid we inherited from SIP has become a sort of Gordian knot. If we could avoid RTCWEB server from having to speak to each other at all, we could avoid re-inventing SDP syntax and/or semantics, at least to some degree.

Hi, maybe I miss something, but this is WWW world and here there is no
server-to-external-server interoperability, never.

The SIP trapezoid exists and works, but IMHO there will never be a
"RTCweb trapezoid". Or do we expect that a user visiting facebook.com
should be able to establish a media session with other user visiting
linkedin.com? I don't think that will occur. There are not "federated
chats" in the web, why should we specify "federated media sessions"?

IMHO this is out of the scope of RTCweb, and in case of introducing it
in the specifications, it would become an overkill (standarizing
signaling between different WWW domains? that's not feasible in this
world).

So I agree with your draft. Instead of "federating" (a concept that
does not exist in WWW jungle) using OAuth or something similar is the
key (so a linkedin.com visitor would establish a HTTP/WebSocket
connection with Facebook.com servers in order to establish a media
session with other user visiting Facebook).

Regards.



-- 
Iñaki Baz Castillo
<[e-mail]>