IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@cisco.com> Fri, 06 June 2008 22:04 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 C4A503A6B8C; Fri, 6 Jun 2008 15:04:31 -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 E26063A6B8C for <sipping@core3.amsl.com>; Fri, 6 Jun 2008 15:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level:
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 5mErGog5s1jJ for <sipping@core3.amsl.com>; Fri, 6 Jun 2008 15:04:30 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id ED46A3A67D4 for <sipping@ietf.org>; Fri, 6 Jun 2008 15:04:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,602,1204520400"; d="scan'208";a="10373279"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 06 Jun 2008 18:04:40 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m56M4eI2000462; Fri, 6 Jun 2008 18:04:40 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m56M4dpR002739; Fri, 6 Jun 2008 22:04:40 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.1830); Fri, 6 Jun 2008 18:04:39 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 6 Jun 2008 18:04:39 -0400
Message-ID: <4849B4A5.6090906@cisco.com>
Date: Fri, 06 Jun 2008 18:05:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Anders Kristensen <andersk@cisco.com>
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>
In-Reply-To: <48499AD6.4060701@cisco.com>
X-OriginalArrivalTime: 06 Jun 2008 22:04:39.0184 (UTC) FILETIME=[509A8900:01C8C821]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=880; t=1212789880; x=1213653880; c=relaxed/simple; s=rtpdkim1001; 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[Sipping]=20Liaison=20Statement=20on=20 offer/answer=20procedures |Sender:=20 |To:=20Anders=20Kristensen=20<andersk@cisco.com>; bh=AFJMlhl/0diAjFmmdvgc4BBLfaCPeqZ6pQzX6UtemrA=; b=leT0rrpEI14jGvOd4jQ6e/PLdjwHIH5Jnf+lxLX/QePYhucjGXfOMJLIbG SYkJgEkSRkRNlaPCQuRVuSHaCK3++g3HONOE28vyOZ8TPWO+5bKMg/fVtHqd l/OPTXNonp;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "Elwell, John" <john.elwell@siemens.com>, Mary Barnes <mary.barnes@nortel.com>, Christer Holmberg <christer.holmberg@ericsson.com>, sipping List <sipping@ietf.org>
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


Anders Kristensen wrote:
> 
> Christer Holmberg wrote:
>>> - 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.

	Paul
_______________________________________________
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

v2.23.0 | Report a Bug | By Email