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

Peter Saint-Andre <stpeter@stpeter.im> Fri, 01 August 2014 15:45 UTC

Return-Path: <stpeter@stpeter.im>
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 F32051B2791 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 08:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 jF2TWueS8h7y for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 08:45:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 151871A007A for <xmpp@ietf.org>; Fri, 1 Aug 2014 08:45:23 -0700 (PDT)
Received: from [10.152.18.180] (unknown [166.147.82.143]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5722A4108C; Fri, 1 Aug 2014 09:45:22 -0600 (MDT)
References: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAKhHsXEN2ZfSzbj3ZP3X=qA7UObOX1CYiuY+zM_xSWiqALSGQQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-5FB8442B-4DA6-4324-8864-810E93E90191"
Content-Transfer-Encoding: 7bit
Message-Id: <B5ADEBD1-5417-453B-BF68-5173CB8ECD2E@stpeter.im>
X-Mailer: iPhone Mail (11D257)
From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Fri, 01 Aug 2014 09:45:20 -0600
To: Alan Johnston <alan.b.johnston@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/psprwv9KH6yxUtHNLNLaCP1Uz9o
Cc: "xmpp@ietf.org" <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 15:45:25 -0000

Hi Alan, did you receive the email message I sent you on this topic some weeks ago? ;-)

Sent from mobile, might be terse 

> On Aug 1, 2014, at 8:50 AM, 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