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

Christer Holmberg <> Fri, 02 August 2013 10:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 09C0411E81B0 for <>; Fri, 2 Aug 2013 03:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.301
X-Spam-Status: No, score=-5.301 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rkNg6q9lx9SJ for <>; Fri, 2 Aug 2013 03:50:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8CECF21E8084 for <>; Fri, 2 Aug 2013 03:50:26 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f0b6d0000002d5-54-51fb8ef0ea25
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 47.47.00725.0FE8BF15; Fri, 2 Aug 2013 12:50:25 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Fri, 2 Aug 2013 12:50:24 +0200
From: Christer Holmberg <>
To: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <>
Thread-Topic: [Stox] Instant Messaging (draft-ietf-stox-im-00) and SIP Contact header field
Thread-Index: Ac6PaH9ohcb2KEe7R4e8vX8J74gjh///5y4A///cfAA=
Date: Fri, 2 Aug 2013 10:50:23 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: fi-FI
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvre7Hvt+BBnd38Vks3beGxeL/jiZW ByaPlv5JLB5LlvxkCmCK4rJJSc3JLEst0rdL4Mo4NnsZS0Ejb8Wcxp9MDYzruboYOTkkBEwk 9v39xgxhi0lcuLeerYuRi0NI4DCjxKZ3K5khnMWMEttedTN2MXJwsAlYSHT/0wYxRQRcJPqX BICYzALKEoemyIKYwgIxEt+euIBMFBGIlTi96xQThG0lsXTteTYQm0VARWJqYwM7iM0r4Cux 6coRsBohgTZGicMr/EBsTgFniee/3oPVMwJd9v3UGrAaZgFxiQ8Hr0NdLCCxZM95KFtU4uXj f6wQtpJE45InrBD1ehI3pk5hg7C1JZYtfM0MsVdQ4uTMJywTGMVmIRk7C0nLLCQts5C0LGBk WcXInpuYmZNebriJERgdB7f81t3BeOqcyCFGaQ4WJXHeTXpnAoUE0hNLUrNTUwtSi+KLSnNS iw8xMnFwSjUwppvJzxf8dkVb0XWblIKu7txTPoxXJidYzeqqmsw3q1W8e3mDQ/tZfdW+42cX N+x/U2s2IWbRKZ4Xr4UMI388mrV1wbE359w4mtv/77nUv9TH+5F2Vb/Xpne6u5i4n57yOnJf +K/Zu6gDaw4EcF5+fLqEL5Z5phXj8tSj726JttjMzr7E92tCnRJLcUaioRZzUXEiAPkt7k9c AgAA
Cc: "" <>
Subject: Re: [Stox] Instant Messaging (draft-ietf-stox-im-00) and SIP Contact header field
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Aug 2013 10:50:38 -0000


If you want to signal who sent the message, I believe we can find another mechanism for that. 

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.



-----Alkuperäinen viesti-----
Lähettäjä: Saúl Ibarra Corretgé [] 
Lähetetty: 2. elokuuta 2013 13:42
Vastaanottaja: Christer Holmberg
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 <> 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?


Saúl Ibarra Corretgé
AG Projects