Re: [Sip] Possible bug in "Non-INVITE Client Transaction" - 17.1.2.2
Robert Sparks <rjsparks@nostrum.com> Fri, 08 April 2011 14:06 UTC
Return-Path: <rjsparks@nostrum.com>
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 0E2673A6922 for <sip@core3.amsl.com>; Fri, 8 Apr 2011 07:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level:
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 MOeSkAxjC1bW for <sip@core3.amsl.com>; Fri, 8 Apr 2011 07:06:17 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id D43C73A690C for <sip@ietf.org>; Fri, 8 Apr 2011 07:06:16 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-57-91-217.dllstx.fios.verizon.net [173.57.91.217]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p38E7x4K051413 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Apr 2011 09:07:59 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="iso-8859-1"
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <BANLkTin-5OBTgn08tccUSt6Av_mAkiorzw@mail.gmail.com>
Date: Fri, 08 Apr 2011 09:07:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3EC948B-7948-4D51-84F6-C76F406FC6D3@nostrum.com>
References: <BANLkTimgohzMAtinJutHfeDRETduGzjZvg@mail.gmail.com> <4CE3ABC5-E50D-4EA9-B8C1-09991BC00E0A@softarmor.com> <BANLkTin-5OBTgn08tccUSt6Av_mAkiorzw@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 173.57.91.217 is authenticated by a trusted mechanism)
Cc: sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
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 14:06:18 -0000
Since, as Iñaki noted, implementations are almost always getting this right, I plan to put this errata into the "Hold for Document Update" state (see <http://www.ietf.org/iesg/statement/errata-processing.html>). RjS On Apr 8, 2011, at 2:56 AM, Iñaki Baz Castillo wrote: > 2011/4/8 Dean Willis <dean.willis@softarmor.com>: >> I think you're right that the spec is written incorrectly. I believe it should describe that the multiplier on T1 doubles with each reset. This is not clear in the existing text. So for example, if 8*T1 < T2, then the third reset is 8*T1, and if 16*T1 < T2, then the 4th reset is 16*T2 >> >> Otherwise said, MIN(2^N*T1,T2) where N is the repetition iterator. > > That would clarify it, right. > > >>> PS: Sorry for the cross-posting, I don't know which maillist is better >>> to report it. >> >> sipcore@ietf.org would probably be the right place. > > Finally I've reported an errata for RFC 3261 (hope it's also a good place): > > http://www.rfc-editor.org/errata_search.php?rfc=3261 > > > Thanks a lot. > > -- > Iñaki Baz Castillo > <ibc@aliax.net> > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP implementation. > Use dispatch@ietf.org for new developments on the application of sip. > Use sipcore@ietf.org for issues related to maintenance of the core SIP specifications.
- [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