Re: [Stox] Instant Messaging (draft-ietf-stox-im-00) and SIP Contact header field

Peter Saint-Andre <stpeter@stpeter.im> Tue, 20 August 2013 14:49 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C480711E8225 for <stox@ietfa.amsl.com>; Tue, 20 Aug 2013 07:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.797
X-Spam-Level:
X-Spam-Status: No, score=-101.797 tagged_above=-999 required=5 tests=[AWL=-0.368, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2p94KwIGBe2l for <stox@ietfa.amsl.com>; Tue, 20 Aug 2013 07:49:35 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB1711E8240 for <stox@ietf.org>; Tue, 20 Aug 2013 07:49:32 -0700 (PDT)
Received: from ergon.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 83DCA41276; Tue, 20 Aug 2013 08:52:47 -0600 (MDT)
Message-ID: <521381ED.9040101@stpeter.im>
Date: Tue, 20 Aug 2013 08:49:17 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
References: <7594FB04B1934943A5C02806D1A2204B1C418E2E@ESESSMB209.ericsson.se> <C4D337C3-A7B6-45C1-98DB-74DC29978A66@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C418FF1@ESESSMB209.ericsson.se> <6AEF2E47-5093-4E86-9D32-4254C713985E@ag-projects.com> <520BE88D.6080802@alum.mit.edu> <0F637313-0900-4796-91A1-A4D1AC18137E@ag-projects.com> <5212E067.1020503@stpeter.im> <AF33614A-A30F-470D-AB19-E09C1E0DA653@ag-projects.com>
In-Reply-To: <AF33614A-A30F-470D-AB19-E09C1E0DA653@ag-projects.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: stox@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Stox] Instant Messaging (draft-ietf-stox-im-00) and SIP Contact header field
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 20 Aug 2013 14:49:40 -0000

On 8/20/13 1:13 AM, Saúl Ibarra Corretgé wrote:
> 
> On Aug 20, 2013, at 5:20 AM, Peter Saint-Andre wrote:
> 
>> On 8/16/13 2:14 AM, Saúl Ibarra Corretgé wrote:
>>>>
>>>> There is nothing to *prevent* use of a gruu in From, but it isn't
>>>> what is normally used.
>>>>
>>>> If you happen to find a gruu in From, then it probably makes sense
>>>> to translate it to a full JID.
>>>>
>>>
>>> I thought it could only be used in the Contact header, but as you
>>> said, RFC5627 doesn't enforce that. So I guess we should mention this
>>> in the -im spec. This could also be used if someone writes a spec to
>>> map XMPP chat messages to SIP MESSAGE in the future.
>>>
>>> Thanks!
>>
>> And in this instance the SIP From header would be added by the gateway,
>> right?
>>
> 
> Yes, by translating the from attribute of the XMPP message stanza. So I think we are good. It would be nice to have this in the examples, that is, no Contact header, and the GRUU in the From.

Yes, that will be added in the next revision of the stox-im I-D. :-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/