Re: [Stox] Extended WGLC for draft-ietf-stox-groupchat-04

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 28 May 2014 12:52 UTC

Return-Path: <saul@ag-projects.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220481A037D for <stox@ietfa.amsl.com>; Wed, 28 May 2014 05:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level:
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3] autolearn=no
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 1M84dpux0ddf for <stox@ietfa.amsl.com>; Wed, 28 May 2014 05:52:04 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) by ietfa.amsl.com (Postfix) with ESMTP id F2BC61A0151 for <stox@ietf.org>; Wed, 28 May 2014 05:52:03 -0700 (PDT)
Received: from imac.saghul.lan (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id D862314AC001; Wed, 28 May 2014 14:51:59 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
In-Reply-To: <5384A67A.6050302@stpeter.im>
Date: Wed, 28 May 2014 14:51:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <35FABB91-8C3A-41A7-BD95-4C6FAD148BD5@ag-projects.com>
References: <CALm9TZ_--rtZyWu3k4WjNd1Oo=ZuYUuwyhySRQkD7aEPi5cJdQ@mail.gmail.com> <5363FD13.5020106@alum.mit.edu> <5384A67A.6050302@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/539py5H3_7Ga3AQpYcoVEz_9et8
Cc: stox@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Stox] Extended WGLC for draft-ietf-stox-groupchat-04
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 12:52:05 -0000

On May 27, 2014, at 4:51 PM, Peter Saint-Andre wrote:

> On 5/2/14, 2:16 PM, Paul Kyzivat wrote:
>> I took a look at this. Disclaimer: It's been a long time since the
>> simple-chat work was done and I haven't been involved with it since. So
>> maybe I have forgotten or missed something.
>> 
>> Section 4:
>> 
>> Both F4 and F5 are 200 OK messages! It appears that F5 is unintended -
>> it doesn't seem to be referenced anywhere.
> 
> Yes, that's an extraneous line.
> 
>> In a variety of places in the MSRP examples:
>> 
>> The "gr=" URI parameter is used with sip URIs. It seems to be carrying
>> nicknames. I don't know where that usage is coming from - it doesn't
>> seem to come from draft-ietf-simple-chat-18. Should probably check with
>> one of the authors of simple-chat about this.
> 
> We do talk about the GRUU mapping in the stox-core spec (now RFC 7247). Here the GRUU valies (MUC) are mapping resourceparts of full JIDs, which in XMPP Multi-User Chat also serve as nicknames.
> 
> So, for instance, this is a mere resourcepart for a user's connected device:
> 
>   Contact: <sip:juliet@example.com>;gr=balcony
> 
> Whereas this is a resourcepart functioning as a MUC nickname:
> 
>   sip:verona@chat.example.org;gr=Romeo
> 
> Preserving this information from the XMPP side of the gateway seems like a good idea (or at least not a bad idea), but I am not sure if a standard MSRP implementation would make use of the information. Checking with the authors of draft-ietf-simple-chat seems like a reasonable thing to do.
> 
> Saúl, what does your implementation do with the GRUU in both cases (mere resourcepart and MUC nickname)?
> 

Hi,

Mere resourcepart is translated to a full JID. When using MUC, 2 things happen: the address is translated to a bare JID and a NICKNAME chunk is sent over MSRP in order to join the groupchat. The occupant JID is translated to a GRUU, which can be used for private messaging.

Hope that helps!

--
Saúl Ibarra Corretgé
AG Projects