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

You might want to flag this with the [email protected] list, and/or the
[email protected] list.

My main comment is that since SIP and HTTP both use URIs here, you don't
want to use a jid, you want an XMPP URI. Whether this should be a URI to
the server, the account, or the client, really depends on what a STUN
server is meant to do with it.

My gut feeling is that you want just the server for most use-cases, but a
full jid might be more useful in others.

Also, my gut - which my wife says is growing, hence its ability to have
multiple opinions - says that you quite possibly want a bare domain in all
cases rather than a URI, since the realm-like use-cases are otherwise going
to imply that a STUN server know how to parse SIP, XMPP, and HTTP URIs, and
anything else that comes along later.

I've the vaguest notion that given the spread of use-cases, you possibly
want two attributes - an origin domain and an initiator URI.


On 1 August 2014 15:50, Alan Johnston <[email protected]> wrote:

> Hi,
>
> In the TRAM WG, we are working on an extension to STUN/TURN for a client
> to convey origin information to a server.
>
>      http://tools.ietf.org/html/draft-ietf-tram-stun-origin
>
> The driver for this effort is WebRTC, where the origin is the HTTP origin
> of the web site that is establishing the Peer Connection.  Other users of
> STUN and TURN can also provide origin information.  The draft currently has
> this text about SIP and XMPP:
>
>    For a SIP User Agent [RFC3261] using STUN and TURN, the ORIGIN
>    attribute is set to be the URI of the registrar server used by the
>    User Agent (i.e. the Request-URI of a REGISTER method).
>
>    For a Jabber client [RFC6120] using STUN and TURN, the ORIGIN
>    attribute is the Jabber ID (JID) [RFC6122] of the Jabber Server that
>    the client is using.
>
> We would greatly appreciate feedback from you on what this text should say
> about XMPP/Jabber in terms of a useful origin.
>
> - Alan -
>
> _______________________________________________
> xmpp mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/xmpp
>
>

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