IETF Logo Mail Archive

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

Ralph Meijer <ralphm@ik.nu> Fri, 01 August 2014 15:12 UTC

Return-Path: <ralphm@ik.nu>
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 9ACB01B27CD for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 08:12: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, RP_MATCHES_RCVD=-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 f_MUswRuUBZU for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 08:12:37 -0700 (PDT)
Received: from mag.ik.nu (mag.ik.nu [83.98.201.61]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F6C1A04B7 for <xmpp@ietf.org>; Fri, 1 Aug 2014 08:12:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id 22BD41600E2; Fri, 1 Aug 2014 17:12:35 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mag.ik.nu
Received: from mag.ik.nu ([127.0.0.1]) by localhost (mag.ik.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mO795oeNjusg; Fri, 1 Aug 2014 17:12:33 +0200 (CEST)
Received: from [10.54.52.79] (unknown [89.205.224.12]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ralphm) by mag.ik.nu (Postfix) with ESMTPSA id C3E621600DE; Fri, 1 Aug 2014 17:12:32 +0200 (CEST)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
References: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
From: Ralph Meijer <ralphm@ik.nu>
Date: Fri, 01 Aug 2014 17:12:26 +0200
To: Alan Johnston <alan.b.johnston@gmail.com>, xmpp@ietf.org
Message-ID: <61e0e855-ed94-4e03-a1e7-018ceae47c97@email.android.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/zNBgKdCqr0RzNvVnCCtYvVuT7Oo
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 15:12:39 -0000

On August 1, 2014 4:50:47 PM CEST, Alan Johnston <alan.b.johnston@gmail.com> wrote:
> [..]
>   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.

Hi Alan,

Thanks for the heads-up.

Why the server address? In XMPP clients establishing media sessions, the communicating entity is fully addressable and its server might not be involves at all. Or, the server is itself providing for the STUN/TURN service, in which case the server address might not be so useful. In short, why not the (full) JID of the client for these cases?
-- 
ralphm

v2.23.0 | Report a Bug | By Email