Return-Path: 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 969241B2841 for ; Fri, 1 Aug 2014 10:25:10 -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 kINKDf5NlWL3 for ; Fri, 1 Aug 2014 10:25:08 -0700 (PDT) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 344AF1B2839 for ; Fri, 1 Aug 2014 10:25:08 -0700 (PDT) Received: by mail-we0-f176.google.com with SMTP id q58so4623248wes.7 for ; Fri, 01 Aug 2014 10:25:06 -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=3woKbSUNqeDsIbN1RjHufWlb+fahMOS7aox5175uCAo=; b=rYeRaQRdIva6c0nNayaUHdjv0Z+BrzJPfbaNrgjJZ4a5Tw3OHP+vtxRdBQp9TL7s8E +z/ostk355IkD1+pK1ZNRU7m/Jy1cAnn35D20eOrqNMOXxnx5+/rflzXHKR7DzrGZcoS k/WQ1GbpkRAR+8LNnwXQ/lKrzANnf2hnnoF7cJLWkbaa81JFaP1tUAbQUWgOwtmeV3l8 O4vwEaoJJ3NF5/IPiZN7/s2UKabwT7yljgr+u/Vh5Jrq55atfo8Aw2h2X5/FER/j+guW cfv0Sf2LAWK8wx1R/kABhBADGHmOOSa3ps+qeqmEc2/VbBf3he7aigpZGcC2p0TJ2Atp GV3w== MIME-Version: 1.0 X-Received: by 10.194.202.231 with SMTP id kl7mr9766339wjc.134.1406913906843; Fri, 01 Aug 2014 10:25:06 -0700 (PDT) Received: by 10.216.108.135 with HTTP; Fri, 1 Aug 2014 10:25:06 -0700 (PDT) In-Reply-To: <53DBC50B.8050906@stpeter.im> References: <53DBC50B.8050906@stpeter.im> Date: Fri, 1 Aug 2014 12:25:06 -0500 Message-ID: From: Alan Johnston To: Peter Saint-Andre Content-Type: multipart/alternative; boundary=047d7bae4836a5aa8e04ff94abd7 Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/ROMVG38_hc1M8fPIQRwLsGxn3P0 Cc: XMPP Working Group 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2014 17:25:10 -0000 --047d7bae4836a5aa8e04ff94abd7 Content-Type: text/plain; charset=UTF-8 Peter, Thanks for resending this. I like the suggested text and think it would work well. - Alan - On Fri, Aug 1, 2014 at 11:49 AM, Peter Saint-Andre wrote: > Hi Alan, > > Here's what I had sent to you and your co-authors in July 1st... > > ### > > First, I think it's better to say "XMPP", not "Jabber". > > This might be ambiguous: > > 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. > > If user's JID is foo@example.com but the "Jabber server" (resolved via > SRV) is xmpp.hosting.example.net, we'd use "example.com". > > The next paragraph indicates that the ORIGIN is supposed to be a URL: > > Other contexts can define a usage of the ORIGIN attribute to use an > appropriate URI or URL. > > In that case, we'd specify an XMPP URI (RFC 5122). > > Thus I might suggest: > > For an XMPP client [RFC6120] using STUN and TURN, the ORIGIN > attribute is an XMPP URI [RFC5122] representing the domainpart > of the client's Jabber ID (JID) [RFC6122]; for example, if the > client's JID is "juliet@im.example.com/balcony" then the ORIGIN > attribute would be "xmpp:im.example.com". > > Peter > > ### > > On 8/1/14, 9:45 AM, Peter Saint-Andre wrote: > >> 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 > > 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 >>> >> >> >> _______________________________________________ >> xmpp mailing list >> xmpp@ietf.org >> https://www.ietf.org/mailman/listinfo/xmpp >> >> > --047d7bae4836a5aa8e04ff94abd7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Peter,

Thanks for resending this. I lik= e the suggested text and think it would work well.

- Alan -


On Fri, Aug 1, 2014 at 11:49 AM, Peter Saint-Andre <= stpeter@stpeter.im<= /a>> wrote:
Hi Alan,

Here's what I had sent to you and your co-authors in July 1st...

###

First, I think it's better to say "XMPP", not "Jabber&qu= ot;.

This might be ambiguous:

=C2=A0 =C2=A0For a Jabber client [RFC6120] using STUN and TURN, the ORIGIN<= br> =C2=A0 =C2=A0attribute is the Jabber ID (JID) [RFC6122] of the Jabber Serve= r that
=C2=A0 =C2=A0the client is using.

If user's JID is f= oo@example.com but the "Jabber server" (resolved via SRV) is = xmpp.hosting.= example.net, we'd use "example.com".

The next paragraph indicates that the ORIGIN is supposed to be a URL:

=C2=A0 =C2=A0Other contexts can define a usage of the ORIGIN attribute to u= se an
=C2=A0 =C2=A0appropriate URI or URL.

In that case, we'd specify an XMPP URI (RFC 5122).

Thus I might suggest:

=C2=A0 =C2=A0For an XMPP client [RFC6120] using STUN and TURN, the ORIGIN =C2=A0 =C2=A0attribute is an XMPP URI [RFC5122] representing the domainpart=
=C2=A0 =C2=A0of the client's Jabber ID (JID) [RFC6122]; for example, if= the
=C2=A0 =C2=A0client's JID is "juliet@im.example.com/balcony&quo= t; then the ORIGIN
=C2=A0 =C2=A0attribute would be "xmpp:im.example.com".

Peter

###

On 8/1/14, 9:45 AM, Peter Saint-Andre wrote:
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
<mailto:a= lan.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.
=C2=A0Other users of STUN and TURN can also provide origin information.
=C2=A0The draft currently has this text about SIP and XMPP:

=C2=A0 =C2=A0For a SIP User Agent [RFC3261] using STUN and TURN, the ORIGIN=
=C2=A0 =C2=A0attribute is set to be the URI of the registrar server used by= the
=C2=A0 =C2=A0User Agent (i.e. the Request-URI of a REGISTER method).

=C2=A0 =C2=A0For a Jabber client [RFC6120] using STUN and TURN, the ORIGIN<= br> =C2=A0 =C2=A0attribute is the Jabber ID (JID) [RFC6122] of the Jabber Serve= r that
=C2=A0 =C2=A0the 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 <ma= ilto:xmpp@ietf.org&g= t;
ht= tps://www.ietf.org/mailman/listinfo/xmpp


_______________________________________________
xmpp mailing list
xmpp@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/xmpp



--047d7bae4836a5aa8e04ff94abd7--