IETF Logo Mail Archive

Re: [Sip] Possible improvement in draft-ietf-sipcore-invfix (CANCEL processing)

Iñaki Baz Castillo <ibc@aliax.net> Mon, 24 May 2010 13:00 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E3E83A6B0C for <sip@core3.amsl.com>; Mon, 24 May 2010 06:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.549
X-Spam-Level:
X-Spam-Status: No, score=0.549 tagged_above=-999 required=5 tests=[AWL=-0.374, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 nzIL5-xpDMJH for <sip@core3.amsl.com>; Mon, 24 May 2010 06:00:56 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 806C83A6BC9 for <sip@ietf.org>; Mon, 24 May 2010 06:00:55 -0700 (PDT)
Received: by pva18 with SMTP id 18so822475pva.31 for <sip@ietf.org>; Mon, 24 May 2010 06:00:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.58.7 with SMTP id g7mr4078186rva.37.1274706044974; Mon, 24 May 2010 06:00:44 -0700 (PDT)
Received: by 10.140.252.19 with HTTP; Mon, 24 May 2010 06:00:44 -0700 (PDT)
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC7465C556F11E@ESESSCMS0354.eemea.ericsson.se>
References: <r2zcc1f582e1004301537w2f5a81b2xcbbd290a7a6f6e02@mail.gmail.com> <4BDCFCE8.6040107@cisco.com> <x2gcc1f582e1005020343t46f18e23mcbfc191e38398e4b@mail.gmail.com> <4BDDBED0.3020600@cisco.com> <w2wcc1f582e1005021117o191d2222v370ee4b941d922bd@mail.gmail.com> <FF84A09F50A6DC48ACB6714F4666CC7465C556F11E@ESESSCMS0354.eemea.ericsson.se>
Date: Mon, 24 May 2010 15:00:44 +0200
Message-ID: <AANLkTikG37fIUFG9Djb3P4SP1BDA56sT1wSaWNyNX9Vu@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "sip@ietf.org" <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Possible improvement in draft-ietf-sipcore-invfix (CANCEL processing)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2010 13:00:57 -0000

2010/5/24 Christer Holmberg <christer.holmberg@ericsson.com>om>:
>
> Hi,
>
> My understanding is that 200 OK for the CANCEL only means "Ok, I got the request".
>
> It is the INVITE response that matters. If the INVITE transaction was cancelled, the UAC would not have received a 200 OK for the INVITE.


Hi, let me re-explain my example (assuming the proxy implements invfix draft:


- alice sends INVITE to the proxy.
- The proxy relays it to bob.
- bob replies 200.
- The proxy relays the 200 to alice. The INVITE transaction in the
proxy remains in "Accepted" state (invfix addition).
- alice sends now a CANCEL (before receiving the 200 for the INVITE).
- The proxy receives the CANCEL and matches the existing INVITE
transaction (in "Accepted" state), what should it reply? "200
Canceled"? there is nothing to cancel right now as a 200 was already
received by the proxy.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.8.7 | Report a Bug | By Email