IETF Logo Mail Archive

Re: [xmpp] Help on XMPP/Jabber Origin for STUN/TURN

Dave Cridland <dave@cridland.net> Fri, 01 August 2014 16:23 UTC

Return-Path: <dave@cridland.net>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE25C1B27F9 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 09:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ML3k88zYak_1 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 09:23:01 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34A8C1B27F4 for <xmpp@ietf.org>; Fri, 1 Aug 2014 09:23:01 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id nu7so2788906obb.9 for <xmpp@ietf.org>; Fri, 01 Aug 2014 09:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=guOyh2sdeh/F1oXFnf9r0KwFtkNxnUVJorEsonpK35o=; b=ihpn+6GFmblOdd6TpDFt+H3fhl0Z2tWVS+EIV0/vc76e7NXB5dUUFXwvxgAzWKo1K7 jiX0EmEfVd2Sa98+Ysi9oP9/u4dw/cFtIhoIojw+Jasx4dq/DC0tu3eGMTCTCAhLYeJj tQ59XGm70nwLEULWjbMzJ0yQ+L+uscYBrEk1A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=guOyh2sdeh/F1oXFnf9r0KwFtkNxnUVJorEsonpK35o=; b=HFd+0I9vmkXKfl8RXfb9vwEEmQE+TSB2ZBHnY71fJsKKexASDzv7JbEwv9+QiiIPDD 7ys4H1wNhGp02DmDnlpmWw1yF0GUtRYdEwMQc4ua3VwZaJqJuyOapIhjV3JEpaVSMvBx vKO3Veq8FpmQjc/ayo8xmG1nPUwhppEnxJlbz9XR7EzvnygFulRP2WSuYO74Gm7MFNQq GxZSz+lesPXzAF3hyDISuucZknHTFN9Ehhj2mJX0pR1q7jbhKL/Pkn0RzxBCcUT9g8yU QcGRjX/V+fUowT+r7dZwJuXVzydlTwei0QtDnsINtdlk7L0BSVyOE4r/3KUyAMJttYsW X6ug==
X-Gm-Message-State: ALoCoQmfng5LQJsSiX/pCApEbT41aBMGuKHHoy3BotPnAO+fkUHAPnDes2oaHJBW0oUbB9MpI4nV
MIME-Version: 1.0
X-Received: by 10.60.146.198 with SMTP id te6mr9788395oeb.46.1406910180409; Fri, 01 Aug 2014 09:23:00 -0700 (PDT)
Received: by 10.60.134.145 with HTTP; Fri, 1 Aug 2014 09:23:00 -0700 (PDT)
In-Reply-To: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
References: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
Date: Fri, 01 Aug 2014 17:23:00 +0100
Message-ID: <CAKHUCzzLvW_p8MFwc42oVVZaafMgYp2mVZNszXfhaSHx=i5VZg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Alan Johnston <alan.b.johnston@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b5d30b688d97604ff93cd41"
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/fbjB1F9VyZCBe64Vxf-dGrdTb3c
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] Help on XMPP/Jabber Origin for STUN/TURN
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Aug 2014 16:23:05 -0000

You might want to flag this with the standards@xmpp.org list, and/or the
jingle@xmpp.org 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 <alan.b.johnston@gmail.com> 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
> xmpp@ietf.org
> https://www.ietf.org/mailman/listinfo/xmpp
>
>

v2.23.0 | Report a Bug | By Email