Re: [Sip] [Technical Errata Reported] RFC3261 (2769)

Dean Willis <dean.willis@softarmor.com> Wed, 13 April 2011 04:46 UTC

Return-Path: <dean.willis@softarmor.com>
X-Original-To: sip@ietfc.amsl.com
Delivered-To: sip@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 83BE4E07C4 for <sip@ietfc.amsl.com>; Tue, 12 Apr 2011 21:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level:
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LbLx+iz2N4q for <sip@ietfc.amsl.com>; Tue, 12 Apr 2011 21:46:16 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfc.amsl.com (Postfix) with ESMTP id D55F0E0716 for <sip@ietf.org>; Tue, 12 Apr 2011 21:46:16 -0700 (PDT)
Received: by ywi6 with SMTP id 6so138653ywi.31 for <sip@ietf.org>; Tue, 12 Apr 2011 21:46:16 -0700 (PDT)
Received: by 10.150.173.10 with SMTP id v10mr154139ybe.119.1302669976358; Tue, 12 Apr 2011 21:46:16 -0700 (PDT)
Received: from [192.168.2.126] (cpe-66-25-14-128.tx.res.rr.com [66.25.14.128]) by mx.google.com with ESMTPS id p33sm2009808ybk.2.2011.04.12.21.46.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 21:46:14 -0700 (PDT)
References: <20110408075247.7F888E075D@rfc-editor.org> <4D9F8B50.2080809@nostrum.com>
In-Reply-To: <4D9F8B50.2080809@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <4FD93CD5-990B-49A7-86D9-716F596B0AB8@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Date: Tue, 12 Apr 2011 23:46:12 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1084)
Cc: sip@ietf.org
Subject: Re: [Sip] [Technical Errata Reported] RFC3261 (2769)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Apr 2011 04:46:17 -0000

On Apr 8, 2011, at 5:25 PM, Adam Roach wrote:

> I don't think this is warranted. This behavior of Timer E is well documented in RFC 3261. It does not bear reiteration every time it is mentioned.
> 
> In particular, the quoted paragraph is quite clear on the topic, if one is to finish reading it:
> 

Other than the fact that it appears to disagree with itself, 3261 is quite clear.

While it is true that the behavior of the timer is correctly-described in one part of the spec, it seems to be incorrectly (or at least misleadingly) described in an early passage. So while reiteration may not be needed, correct initial iteration is probably warranted. Or the misleading initial passage could be excised.

If you say something only once, say it right. If you must say it again, don't say something different. Just say it more clearly.

--
Dean