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:29 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 2449821F9D98 for <stox@ietfa.amsl.com>; Wed, 14 Aug 2013 13:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.165
X-Spam-Level:
X-Spam-Status: No, score=0.165 tagged_above=-999 required=5 tests=[AWL=-0.268, 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 8ZgQQl8+vqms for <stox@ietfa.amsl.com>; Wed, 14 Aug 2013 13:29:02 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 38A7321F9B26 for <stox@ietf.org>; Wed, 14 Aug 2013 13:29:02 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta15.westchester.pa.mail.comcast.net with comcast id Chf31m0031YDfWL5FkV12Z; Wed, 14 Aug 2013 20:29:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id CkV11m00h3ZTu2S3gkV1SY; Wed, 14 Aug 2013 20:29:01 +0000
Message-ID: <520BE88D.6080802@alum.mit.edu>
Date: Wed, 14 Aug 2013 22:29:01 +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> <6AEF2E47-5093-4E86-9D32-4254C713985E@ag-projects.com>
In-Reply-To: <6AEF2E47-5093-4E86-9D32-4254C713985E@ag-projects.com>
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=1376512141; bh=aCje3/jkArF7lIbFU8fdGjx0zwCyjI4gp7o0gfuDBxw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=o/N/EKg2zepOTOPrC7Lm0Nmd06wlo6uJzWEN7OJYZUIEHtyT/iM5lM52EzCJolzV9 t5msMfV6QvyJgX+9dwZbl08T1ty/WwYrgbX9KxgGjB24YvoWYCjsJq4cxJf6kW6rJz jYYkP0LpkO2Lz1nQrdJ0hk70fAxn2fknFeBo3nS437L36hAKPq8drheRyFajtMf5bR mawYV3LlrPdiYfa9crodjg6PYyaGOPuVlEO3z6AjlrWwaghhKwk9j/8OWfZUE1h2/4 y4myiqpbDHv0gG9q6OzEq1o1NRgBS8VmZTEdyPpkxg+/HpdJRb3XiHyprJtIDgSQdM XO+rU+pWwf+uw==
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:29:08 -0000

On 8/2/13 12:54 PM, Saúl Ibarra Corretgé wrote:
>
> On Aug 2, 2013, at 12:50 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>> If you want to signal who sent the message, I believe we can find another mechanism for that.
>>
>
> I guess we are open to suggestions :-)
>
>> 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.
>>
>
> -core defines how we use GRUU which is required, in a nutshell, a GRUU is translated to a full JID and vice versa. Now, IIRC GRUUs are used just in the Contact header (which we can't use here) and not in the From header, for instance.

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.

	Thanks,
	Paul