Re: [Sip] Possible bug in "Non-INVITE Client Transaction" - 17.1.2.2
Iñaki Baz Castillo <ibc@aliax.net> Fri, 08 April 2011 12:13 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 6032C28C0F9 for <sip@core3.amsl.com>; Fri, 8 Apr 2011 05:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.644
X-Spam-Level:
X-Spam-Status: No, score=-2.644 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 aMYxGbQsRhRo for <sip@core3.amsl.com>; Fri, 8 Apr 2011 05:13:02 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id BBA3C28C0E2 for <sip@ietf.org>; Fri, 8 Apr 2011 05:13:02 -0700 (PDT)
Received: by qwc23 with SMTP id 23so2527456qwc.31 for <sip@ietf.org>; Fri, 08 Apr 2011 05:14:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.221.131 with SMTP id ic3mr1686576qcb.239.1302264887670; Fri, 08 Apr 2011 05:14:47 -0700 (PDT)
Received: by 10.229.35.72 with HTTP; Fri, 8 Apr 2011 05:14:47 -0700 (PDT)
In-Reply-To: <4D9EF9C2.7090101@solwisetelephony.co.uk>
References: <BANLkTimgohzMAtinJutHfeDRETduGzjZvg@mail.gmail.com> <4CE3ABC5-E50D-4EA9-B8C1-09991BC00E0A@softarmor.com> <BANLkTin-5OBTgn08tccUSt6Av_mAkiorzw@mail.gmail.com> <4D9EF9C2.7090101@solwisetelephony.co.uk>
Date: Fri, 08 Apr 2011 14:14:47 +0200
Message-ID: <BANLkTikPDoMOhawdQ7VGHy1x+TBNduSEFQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Peter Hanratty <peter@solwisetelephony.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: sip@ietf.org
Subject: Re: [Sip] Possible bug in "Non-INVITE Client Transaction" - 17.1.2.2
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: Fri, 08 Apr 2011 12:13:03 -0000
2011/4/8 Peter Hanratty <peter@solwisetelephony.co.uk>: > While youre at it, the INVITE server transaction could use some rethinking. > Terminating on a 2xx but on no other final response is a bit daft and makes > people like me want to cut corners rather than use other objects such as the > dialog or session to handle the ACK, which doesn't really make for a nice > logical model :) The ACK is attached to a single transaction and should > handled by that transaction (as it is for a non-2xx final response). Hi Peter, you should take a look to RFC 6026 "Correct Transaction Handling for 2xx Responses to SIP INVITE Requests". ;) -- Iñaki Baz Castillo <ibc@aliax.net>
- [Sip] Possible bug in "Non-INVITE Client Transact… Iñaki Baz Castillo
- Re: [Sip] [Sip-implementors] Possible bug in "Non… Iñaki Baz Castillo
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Dean Willis
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Iñaki Baz Castillo
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Peter Hanratty
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Iñaki Baz Castillo
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Robert Sparks
- Re: [Sip] Possible bug in "Non-INVITE Client Tran… Iñaki Baz Castillo