Help on XMPP/Jabber Origin for STUN/TURN

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