IETF Logo Mail Archive

Re: [sipcore] New revision of the re-INVITE handling draft

Paul Kyzivat <pkyzivat@cisco.com> Fri, 10 July 2009 13:26 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23A2028C27D for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 06:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.587
X-Spam-Level:
X-Spam-Status: No, score=-6.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gW0pS0evpZWv for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 06:26:43 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id E9CC228C1BC for <sipcore@ietf.org>; Fri, 10 Jul 2009 06:26:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,378,1243814400"; d="scan'208";a="212161658"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 10 Jul 2009 13:27:07 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6ADR7eh024837; Fri, 10 Jul 2009 06:27:07 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n6ADR6qm011761; Fri, 10 Jul 2009 13:27:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 09:27:06 -0400
Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 09:27:06 -0400
Message-ID: <4A5741A9.8030200@cisco.com>
Date: Fri, 10 Jul 2009 09:27:05 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: OKUMURA Shinji <shin@softfront.co.jp>
References: <4A52019B.4030600@ericsson.com> <4A528AB2.7020206@cisco.com> <8CA0129D1A650shin@softfront.co.jp>
In-Reply-To: <8CA0129D1A650shin@softfront.co.jp>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jul 2009 13:27:06.0420 (UTC) FILETIME=[1E890740:01CA0162]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=881; t=1247232427; x=1248096427; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[sipcore]=20New=20revision=20of=20the=2 0re-INVITE=20handling=20draft |Sender:=20; bh=2H5Xm34LaVcluogoAlAO1Dsib7ul94lKgu00CV1UH5Q=; b=jDQ76tgrZtTAuuPH/4to8ipmimPZVWCXoarj4Hzq2jPdDi41aWxzSn+G5E yzbxp1ndwwTtqE7LVxoZwJvJe8ZIG4vKGJSSzI+hYAr+WalMRZgojCpOAmtQ 5bPnHwzxxp;
Authentication-Results: sj-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] New revision of the re-INVITE handling draft
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2009 13:26:44 -0000

OKUMURA Shinji wrote:

> But at this point, I have one doubt.
> May precondition procedure be started by UPDATE?

IMO yes it may. But perhaps it SHOULD NOT ???

I think it has always been possible to initiate an in-dialog o/a 
exchange, with or without preconditions, using UPDATE rather than reINVITE.

I guess it would also be possible to start an INVITE/reINVITE without 
preconditions, and then initiate the use of preconditions with an 
UPDATE. But I can't think of any good reason why you would want to do that.

AFAIK there are only a couple of places where UPDATE is needed, or 
preferable alternatives:

- its needed by UAC for 2nd and subsequent rounds of O/A exchange
   within an INVITE.

- its good for a dialog refresh/target refresh when you *don't*
   want to do a new O/A.

Other uses can be accomplished other ways.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email