Re: [Sip] [Sip-implementors] Possible bug in "Non-INVITE Client Transaction" - 17.1.2.2

Iñaki Baz Castillo <ibc@aliax.net> Wed, 06 April 2011 17:10 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 3B4A43A695F for <sip@core3.amsl.com>; Wed, 6 Apr 2011 10:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level:
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=0.035, 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 V47-+IOuyyl5 for <sip@core3.amsl.com>; Wed, 6 Apr 2011 10:10:43 -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 95E4C28C0E5 for <sip@ietf.org>; Wed, 6 Apr 2011 10:10:42 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1234898qwc.31 for <sip@ietf.org>; Wed, 06 Apr 2011 10:12:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.75.196 with SMTP id z4mr1037160qcj.277.1302109946142; Wed, 06 Apr 2011 10:12:26 -0700 (PDT)
Received: by 10.229.35.72 with HTTP; Wed, 6 Apr 2011 10:12:25 -0700 (PDT)
In-Reply-To: <BANLkTikPyv4mfd1f9Fdj5E9rJgMzX_Vxqw@mail.gmail.com>
References: <BANLkTimgohzMAtinJutHfeDRETduGzjZvg@mail.gmail.com> <BANLkTikPyv4mfd1f9Fdj5E9rJgMzX_Vxqw@mail.gmail.com>
Date: Wed, 06 Apr 2011 19:12:25 +0200
Message-ID: <BANLkTikKYQ2HdQ3pu2LCZuYJmD1hw1oVpA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Pandurangan R S <pandurangan.r.s@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] [Sip-implementors] 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: Wed, 06 Apr 2011 17:10:46 -0000

2011/4/6 Pandurangan R S <pandurangan.r.s@gmail.com>:
>>> This process continues so that retransmissions occur with an exponentially
>>>  increasing interval that caps at T2.
>
> I think this actually means
>
>> - Initially => T1 = 0.5s
>> - Fires    => MIN(2*T1, T2) = 1s
>> - Fires    => MIN(4*T1, T2) = 2s
>> - Fires    => MIN(8*T1, T2) = 4s
>> - Fires    => MIN(16*T1, T2) = 4s
>
> 2,4, 8, 16... which is exponential.

Yes, assuming that after 4*T1 it becomes 8*T1 it works. However that
is not what I've understood by reading the section (but I must be
wrong as all the SIP stacks I've tested behave as you describe) :)

Thanks a lot.

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