IETF Logo Mail Archive

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

Alan Johnston <alan.b.johnston@gmail.com> Fri, 01 August 2014 17:24 UTC

Return-Path: <alan.b.johnston@gmail.com>
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 E4EC01B2839 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 10:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 6ZAmm24xzroT for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 10:24:03 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63E161B2862 for <xmpp@ietf.org>; Fri, 1 Aug 2014 10:23:53 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u57so4594877wes.38 for <xmpp@ietf.org>; Fri, 01 Aug 2014 10:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4o3fE+8ibCtwFFrTfFZIj4yynnu5pB24rcZ6spaF96U=; b=GM2IO/RWKlYzAQiGyby7Hx5DWvJ5yU63EyQ680qRUh8Sz3IGZ8Hm9jxUaqkswa/Huf teXeTaHA5R8EdZlfbPlZAfiFMH+gY9MgCpxpuj/1+NRQedq4abtUu4RW7RoUIEo8bdr9 4o8O6rP5fUZH3XbNe3ZTzdebSQJq+6W/u3VIqg8bmJTLGCLDi4FZwLseycFOVz4wzfRC o94DGKcr94mG+x1pbx61H5VQtNy0CTqdQtexLkgFzjMHgaLU9OkMLv5ehE+33L5LBpFf 9XzHqs9Z9qaEpzfbO8BNatYDRsTy1DZn1hbjivK/+rQBBUBznS8X2e4GXTApM6K0ceKK ed2g==
MIME-Version: 1.0
X-Received: by 10.180.20.15 with SMTP id j15mr4528296wie.60.1406913831779; Fri, 01 Aug 2014 10:23:51 -0700 (PDT)
Received: by 10.216.108.135 with HTTP; Fri, 1 Aug 2014 10:23:51 -0700 (PDT)
In-Reply-To: <53DBC79F.3080704@goodadvice.pages.de>
References: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com> <CAKHUCzzLvW_p8MFwc42oVVZaafMgYp2mVZNszXfhaSHx=i5VZg@mail.gmail.com> <CAKhHsXFTEhcZuZMi6HgzLD7bjb6mCt_6GfRbBT9bGKYzW4ySUQ@mail.gmail.com> <53DBC79F.3080704@goodadvice.pages.de>
Date: Fri, 01 Aug 2014 12:23:51 -0500
Message-ID: <CAKhHsXECt9nvE4mTFCSfCferzjKHzgRLQgJRmff=L3Tm_cQO+Q@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: Philipp Hancke <fippo@goodadvice.pages.de>
Content-Type: multipart/alternative; boundary="bcaec53f39852c438404ff94a71b"
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/gOrJ1auiNiJgJhS41h36rBW_wKk
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 17:24:08 -0000

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 <fippo@goodadvice.pages.de>
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
> xmpp@ietf.org
> https://www.ietf.org/mailman/listinfo/xmpp
>

v2.23.0 | Report a Bug | By Email