Re: [Sip] RE: Identity after reinvite

Cullen Jennings <fluffy@cisco.com> Tue, 16 November 2004 17:52 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24274 for <sip-web-archive@ietf.org>; Tue, 16 Nov 2004 12:52:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7XI-0003La-TQ for sip-web-archive@ietf.org; Tue, 16 Nov 2004 12:54:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU7Qk-0003PZ-Ax; Tue, 16 Nov 2004 12:47:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU79h-0008Gq-Gv for sip@megatron.ietf.org; Tue, 16 Nov 2004 12:30:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22160 for <sip@ietf.org>; Tue, 16 Nov 2004 12:30:11 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7Bu-0002jJ-O7 for sip@ietf.org; Tue, 16 Nov 2004 12:32:33 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 16 Nov 2004 09:42:40 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAGHTb3O014620; Tue, 16 Nov 2004 09:29:37 -0800 (PST)
Received: from [10.32.131.85] ([10.32.131.85]) by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUA67998; Tue, 16 Nov 2004 09:29:36 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Tue, 16 Nov 2004 09:29:38 -0800
Subject: Re: [Sip] RE: Identity after reinvite
From: Cullen Jennings <fluffy@cisco.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, Jon Peterson <jon.peterson@neustar.biz>
Message-ID: <BDBF7902.1A871%fluffy@cisco.com>
In-Reply-To: <4199B4D0.30606@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: "sip@ietf.org" <sip@ietf.org>, Paul H Kyzivat <pkyzivat@cisco.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

On 11/16/04 12:05 AM, "Jonathan Rosenberg" <jdrosen@cisco.com> wrote:

> The solution, which rfc3261 warns of, is that a UA has to put its actual
> identity in the From field URI, not what it saw in the To field of the
> original request. This will break all compatibility with rfc2543, but
> will work with other rfc3261 compliant endpoints, since the URI is no
> longer used for dialog identification.

At this point, I really see two paths forward for the connected party
problem.

1) We do as suggested above and allow everything in the From and To other
than the tags to be changed in a Re-INVITE or UPDATE.

2) We create a new thing that is like invite with replaces but add a new tag
that is called say "subsumes". So if A and B have a dialog, or early dialog,
and one of them wants to change a From. The UA sends an INVITE for a new
dialog, indicates it replaces the old dialog, and indicates that it subsumes
it. The subsumes flag would mean that any existing media session, qos
reservations, etc did not change and got moved to the new dialog. 



_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip