IETF Logo Mail Archive

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

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 02 August 2013 10:41 UTC

Return-Path: <saul@ag-projects.com>
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 5DB9A11E827E for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.824
X-Spam-Level:
X-Spam-Status: No, score=-0.824 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3, 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 Iv-P02voQ-fw for <stox@ietfa.amsl.com>; Fri, 2 Aug 2013 03:41:32 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 80BD011E8210 for <stox@ietf.org>; Fri, 2 Aug 2013 03:41:32 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id E12A1B35DE; Fri, 2 Aug 2013 12:41:31 +0200 (CEST)
Received: from dhcp-152d.meeting.ietf.org (dhcp-152d.meeting.ietf.org [130.129.21.45]) by mail.sipthor.net (Postfix) with ESMTPSA id 41A97B017A; Fri, 2 Aug 2013 12:41:31 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C418E2E@ESESSMB209.ericsson.se>
Date: Fri, 02 Aug 2013 12:41:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4D337C3-A7B6-45C1-98DB-74DC29978A66@ag-projects.com>
References: <7594FB04B1934943A5C02806D1A2204B1C418E2E@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "stox@ietf.org" <stox@ietf.org>
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: Fri, 02 Aug 2013 10:41:38 -0000

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

v2.23.0 | Report a Bug | By Email