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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 14 August 2013 20:26 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 9EA8321F9B26 for <stox@ietfa.amsl.com>; Wed, 14 Aug 2013 13:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.152
X-Spam-Level:
X-Spam-Status: No, score=0.152 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_MLH_Stock1=0.87]
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 Tajo18BR23Yv for <stox@ietfa.amsl.com>; Wed, 14 Aug 2013 13:26:17 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id B4EB921F9A14 for <stox@ietf.org>; Wed, 14 Aug 2013 13:26:16 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta08.westchester.pa.mail.comcast.net with comcast id Cbj21m0071c6gX858kSGkp; Wed, 14 Aug 2013 20:26:16 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id CkSF1m0193ZTu2S3jkSGt9; Wed, 14 Aug 2013 20:26:16 +0000
Message-ID: <520BE7E7.70602@alum.mit.edu>
Date: Wed, 14 Aug 2013 22:26:15 +0200
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: stox@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C418E2E@ESESSMB209.ericsson.se> <C4D337C3-A7B6-45C1-98DB-74DC29978A66@ag-projects.com> <7594FB04B1934943A5C02806D1A2204B1C418FF1@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C418FF1@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1376511976; bh=auK2gTRiZahdFQKdcM2aEfFyU0zHoD+KbfTESAqvSEQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=kozjNcky7L1kcsOwHx6djUoAjDSJv5wpfRERp664lZNUs7GAnoHcSzjfi6IMx++qz VwP/qC1WVujOttixKgflJ9BclbbHGQnAHBH7IupIeW6OAhhFb9q3FzIlAvmIMNVW2L sPslNrny4L4OAOxnTHCQ8GQvCI8AAUupTIjkdRv+udnIgoRHHxMFnTU7uKPPSEXCOy +vGi1Zg+89QPaHOkcDtfow0HmI5ufLyxitvNv5s6uDjjgDQQeY/VBOeX5SJi/U3oQ9 WKcmdXmY8Yl4POdOTn2CJCmG6zAbVfAOqaRhFLQvfZdFa3+8dRuEeeEWaY0wNsPWeL 9Ah9HeUBE59cg==
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: Wed, 14 Aug 2013 20:26:21 -0000

On 8/2/13 12:50 PM, Christer Holmberg wrote:
> Hi,
>
> If you want to signal who sent the message, I believe we can find another mechanism for that.

I don't think so. This is a *gateway* function. We aren't expecting the 
SIP or XMPP endpoints to do anything special. If the SIP user sends a 
MESSAGE, then that normally doesn't contain a URI of the sending 
endpoint. So we have nothing to put into the XMPP.

I could imagine using Reply-To for this purpose. There is nothing to 
*prevent* use of this. But neither is there currently any reason to 
expect that it will be used.

	Thanks,
	Paul

> The GRUU is not really intended to indicate user identity anyway, and IF you want to use GRUU I believe you need to define how the gateway gets assigned the GRUU.
>
> Regards,
>
> Christer
>
> -----Alkuperäinen viesti-----
> Lähettäjä: Saúl Ibarra Corretgé [mailto:saul@ag-projects.com]
> Lähetetty: 2. elokuuta 2013 13:42
> Vastaanottaja: Christer Holmberg
> Kopio: stox@ietf.org
> Aihe: Re: [Stox] Instant Messaging (draft-ietf-stox-im-00) and SIP Contact header field
>
> Hi Christer,
>
> On Aug 2, 2013, at 12:13 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>> As I indicated at the STOX session, the SIP MESSAGE examples in the draft contain a Contact header field, which is explicitly forbidden.
>>
>> Section 4 of RFC 3248 says:
>>
>> 	"MESSAGE requests do not initiate dialogs.  User Agents MUST NOT
>> 	insert Contact header fields into MESSAGE requests."
>>
>> My question in the meeting was whether this is simply an editorial
>> bug, or whether the Contact header field is actually used for something (there is nothing in the normative text), e.g. to ensure that MESSAGE requests are routed to the correct user agents (someone mentioned that GRUU might be needed).
>>
>
> I was the one who mentioned GRUU. We do need it if we want to know who sent the message exactly, but since the -im spec just deals with pager mode messages maybe we can live with just strangulating the bare JID. Peter?
>
>
> Regards,
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
>
>
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox
>