[sipcore] #13: Section 7 item 2 is not complete
"sipcore issue tracker" <trac@tools.ietf.org> Mon, 30 August 2010 19:08 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 F16193A6837 for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 12:08:16 -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 uuC2f4qMFLkV for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 12:08:15 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id CFC803A684D for <sipcore@ietf.org>; Mon, 30 Aug 2010 12:08:15 -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 1Oq9io-0007P0-Bp; Mon, 30 Aug 2010 12:08:46 -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: Mon, 30 Aug 2010 19:08:46 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/13
Message-ID: <064.6c32c8048648b3e859ada9acae1f68a3@tools.ietf.org>
X-Trac-Ticket-ID: 13
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] #13: Section 7 item 2 is not complete
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: Mon, 30 Aug 2010 19:08:17 -0000
#13: Section 7 item 2 is not complete
------------------------------------+---------------------------------------
Reporter: hkaplan@… | Owner:
Type: defect | Status: new
Priority: major | Milestone: milestone1
Component: rfc4244bis | Version: 2.0
Severity: In WG Last Call | Keywords:
------------------------------------+---------------------------------------
Section 7 item 2 says:
2. Entry prior to last entry with hi-target of "rc" in the Request
received by a UAS - i.e., the Request URI associated with the
destination of the request was determined based on a Registered
Contact.
That is only true if no forking occurred, and the request wasn't contact-
routed multiple times in series (i.e., as an SBC might cause).
A more correct sentence (I think) would be:
2. Last non-"rc" entry of the same branch, prior to last entry with
hi-target of "rc" in the Request
received by a UAS - i.e., the Request URI associated with the
destination of the request was determined based on a Registered
Contact.
--
Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/13>
sipcore <http://tools.ietf.org/sipcore/>
- [sipcore] #13: Section 7 item 2 is not complete sipcore issue tracker
- Re: [sipcore] #13: Section 7 item 2 is not comple… Mary Barnes
- Re: [sipcore] #13: Section 7 item 2 is not comple… Mary Barnes