IETF Logo Mail Archive

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

Philipp Hancke <fippo@goodadvice.pages.de> Fri, 01 August 2014 17:00 UTC

Return-Path: <fippo@goodadvice.pages.de>
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 0C2721B27A3 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 10:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WzusrWGxEWmZ for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 10:00:30 -0700 (PDT)
Received: from lo.psyced.org (lost.IN.psyced.org [188.40.42.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 256D81A0051 for <xmpp@ietf.org>; Fri, 1 Aug 2014 10:00:29 -0700 (PDT)
Received: from [192.168.178.45] (p5DCFCBB1.dip0.t-ipconnect.de [93.207.203.177]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id s71H0Z1j011189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <xmpp@ietf.org>; Fri, 1 Aug 2014 19:00:37 +0200
Message-ID: <53DBC79F.3080704@goodadvice.pages.de>
Date: Fri, 01 Aug 2014 19:00:15 +0200
From: Philipp Hancke <fippo@goodadvice.pages.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: xmpp@ietf.org
References: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com> <CAKHUCzzLvW_p8MFwc42oVVZaafMgYp2mVZNszXfhaSHx=i5VZg@mail.gmail.com> <CAKhHsXFTEhcZuZMi6HgzLD7bjb6mCt_6GfRbBT9bGKYzW4ySUQ@mail.gmail.com>
In-Reply-To: <CAKhHsXFTEhcZuZMi6HgzLD7bjb6mCt_6GfRbBT9bGKYzW4ySUQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/OEYC6uLEr0H4ZFBbUlJ_ue_itPQ
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:00:39 -0000

> 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.

v2.23.0 | Report a Bug | By Email