Re: Help on XMPP/Jabber Origin for STUN/TURN

Hi Philipp,

When XMPP or SIP is used for the signaling in WebRTC, the client is running
in JavaScript.  SIP or XMPP in the browser cannot configure or use
STUN/TURN except through the WebRTC APIs.  In this case, the browser origin
would be used, since the browser is running the STUN/TURN client.  Allowing
JavaScript to set the Origin would not be a good idea, and not really
useful either in this context.

- Alan -


On Fri, Aug 1, 2014 at 12:00 PM, Philipp Hancke <[email protected]>
wrote:

> The goal here is to make things simple on the client and have the client
>> just include something that it already knows in a known format.  This
>> why an HTTP origin and SIP registrar URI have been chosen.  We just need
>>
>
> What about XMPP (and SIP) clients in browser?
>
> Possibly XEP-0215 (http://xmpp.org/extensions/xep-0215.html) could be
> extended to let the XMPP server specify (or override) that as well. WebRTC
> clients don't have the chance to specify this however.
>
> _______________________________________________
> xmpp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/xmpp
>

_______________________________________________
xmpp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/xmpp