Re: [Sipping] Liaison Statement on offer/answer procedures

"Christer Holmberg" <christer.holmberg@ericsson.com> Sat, 07 June 2008 11:05 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5DF53A69DE; Sat, 7 Jun 2008 04:05:08 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E04713A69F4 for <sipping@core3.amsl.com>; Sat, 7 Jun 2008 04:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.153
X-Spam-Level:
X-Spam-Status: No, score=-6.153 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 BhY6hrkyx3Oa for <sipping@core3.amsl.com>; Sat, 7 Jun 2008 04:05:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id BE4773A693A for <sipping@ietf.org>; Sat, 7 Jun 2008 04:05:06 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 6BBCC20862; Sat, 7 Jun 2008 13:05:17 +0200 (CEST)
X-AuditID: c1b4fb3c-ab095bb00000193b-10-484a6b6dbcb3
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5E73420514; Sat, 7 Jun 2008 13:05:17 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sat, 7 Jun 2008 13:05:16 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 07 Jun 2008 13:05:16 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF046C780D@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Liaison Statement on offer/answer procedures
Thread-Index: AcjIIVLbmp7aH0xfSvWpIF11Dtr/wQAbEeMU
References: <4822983A.2090906@ericsson.com> <CA9998CD4A020D418654FCDEF4E707DF062C5DD8@esealmw113.eemea.ericsson.se> <482C2DE1.1080102@cisco.com> <CA9998CD4A020D418654FCDEF4E707DF062EC204@esealmw113.eemea.ericsson.se> <482C3F25.7070605@cisco.com> <0D5F89FAC29E2C41B98A6A762007F5D0BB548B@GBNTHT12009MSX.gb002.siemens.net> <482D8058.6030608@cisco.com><CA9998CD4A020D418654FCDEF4E707DF046C77CA@esealmw113.eemea.ericsson.se><48463DF1.7080109@ericsson.com> <4846B581.2070901@cisco.com><CA9998CD4A020D418654FCDEF4E707DF046C77F8@esealmw113.eemea.ericsson.se><484719AF.9060207@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0688EB10@esealmw113.eemea.ericsson.se><4847FF97.1030804@cisco.com><CA9998CD4A020D418654FCDEF4E707DF046C7805@esealmw113.eemea.ericsson.se> <48493CE6.3050800@cisco.com> <C0E80510684FE94DBDE3A4AF6B968D2D037D84FF@esealmw118.eemea.ericsson.se> <CA9998CD4A020D418654FCDEF4E707DF046C780A@esealmw113.eemea.ericsson.se> <48499AD6.4060701@cisco.com> <4849B4A5.6090906@cisco.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Anders Kristensen <andersk@cisco.com>
X-OriginalArrivalTime: 07 Jun 2008 11:05:16.0997 (UTC) FILETIME=[5E1D9F50:01C8C88E]
X-Brightmail-Tracker: AAAAAA==
Cc: sipping List <sipping@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Mary Barnes <mary.barnes@nortel.com>
Subject: Re: [Sipping] Liaison Statement on offer/answer procedures
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi,
 
>>>> - If an UPDATE (inside or outside of a reINVITE) fails, any o/a in
>>>> the UPDATE has no effect on the media session state.
>>>> [Ian Elz ] OK, but how will we determine if an UPDATE is inside or
>>>> outside a re-INVITE?
>>> 
>>> [Christer] I assume that any stateful entity must know whether it has
>>> a pending re-INVITE transaction for a specific call or not.
>>
>> That's not actually enough. A UAS (or dialog stateful proxy) cannot know
>> whether an UPDATE received shortly after a 2xx is sent upstream was sent
>> before or after the 2xx was received by the UAC. We could add an
>> explicit indication to that effect, I suppose...
>
>Yes. Taking this approach to the current problem requires that we find a
>solution to knowing whether the update was sent inside the reinvite or not.

If the UAS sends a 2xx response to the re-INVITE I guess it really doesn't matter when the UPDATE was sent.

But, if the UAS sends a non-2xx response to the re-INVITE I guess it would need to know when the UPDATE was sent: was it sent still assuming that the re-INVITE will succeed, OR was it sent bacause the re-INVITE did NOT succeed?

If we would go for the non-rollback alternative we wouldn't have this problem since the re-INVITE failure response doesn't affect UPDATE/PRACK offer/answers, and then it doesn't matter when the UPDATE was sent.

Regards,

Christer

 

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