[sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory text
"sipcore issue tracker" <trac@tools.ietf.org> Thu, 26 August 2010 17:02 UTC
Return-Path: <trac@tools.ietf.org>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A69403A6AE3 for <sipcore@core3.amsl.com>; Thu, 26 Aug 2010 10:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level:
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-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 m1bRsE90scMZ for <sipcore@core3.amsl.com>; Thu, 26 Aug 2010 10:02:21 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 05B4A3A69D2 for <sipcore@ietf.org>; Thu, 26 Aug 2010 10:02:21 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1Oofqm-0003aY-Vj; Thu, 26 Aug 2010 10:02:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: sipcore issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: hkaplan@acmepacket.com
X-Trac-Project: sipcore
Date: Thu, 26 Aug 2010 17:02:52 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/6
Message-ID: <064.2794ed3170efd1bfd91e2bbde05e1c7b@tools.ietf.org>
X-Trac-Ticket-ID: 6
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: hkaplan@acmepacket.com, sipcore@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: sipcore@ietf.org
Subject: [sipcore] #6: Editorial: incorrect 6.3.4 rule 4 explanatory text
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2010 17:02:22 -0000
#6: Editorial: incorrect 6.3.4 rule 4 explanatory text ------------------------------------+--------------------------------------- Reporter: hkaplan@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: rfc4244bis | Version: 2.0 Severity: In WG Last Call | Keywords: ------------------------------------+--------------------------------------- Section 6.3.4 rule 4 says: 4. Retargeting based upon a Response: In the case of retargeting due to a specific response (e.g., 302), the index would be calculated per rule 3. That is, the lowest/last digit of the index is incremented (i.e., a new branch is created), with the increment of 1. For example, if the index in the History-Info header of the received request was 1.2, then the index in the History-Info header field for the new hi-targeted- to-URI would be 1.3. That last sentence is incorrect. If the *received* request was 1.2, and it was sent to Bob, it's now 1.2.1, and if Bob responds with a 302, the new request is now 1.2.2. If the *sent* request (which got redirected) was 1.2, then 1.3 would be right. Change the sentence to say "... of the sent request was 1.2, and it was responded to with a 302, then the index in the History-Info header field for the new hi-targeted-to-URI would be 1.3.". -- Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/6> sipcore <http://tools.ietf.org/sipcore/>
- [sipcore] #6: Editorial: incorrect 6.3.4 rule 4 e… sipcore issue tracker
- Re: [sipcore] #6: Editorial: incorrect 6.3.4 rule… Mary Barnes