[sipcore] #40: Clarify mp-value

"sipcore issue tracker" <trac@tools.ietf.org> Tue, 31 August 2010 18:22 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 F2ECF3A6A84 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 11:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level:
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.026, 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 KA29iGgERL0k for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 11:22:19 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 1C47B3A6A10 for <sipcore@ietf.org>; Tue, 31 Aug 2010 11:22:19 -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 1OqVTu-0004qg-2b; Tue, 31 Aug 2010 11:22:50 -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: worley@alum.mit.edu
X-Trac-Project: sipcore
Date: Tue, 31 Aug 2010 18:22:50 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/40
Message-ID: <061.a74db9472c31e13651a0ab46005b8128@tools.ietf.org>
X-Trac-Ticket-ID: 40
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: worley@alum.mit.edu, 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] #40: Clarify mp-value
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: Tue, 31 Aug 2010 18:22:20 -0000

#40: Clarify mp-value
---------------------------------+------------------------------------------
 Reporter:  worley@…             |       Owner:            
     Type:  defect               |      Status:  new       
 Priority:  minor                |   Milestone:  milestone1
Component:  rfc4244bis           |     Version:            
 Severity:  In WG Last Call      |    Keywords:            
---------------------------------+------------------------------------------
 In section 6.3.5, the rules for the value part of the mp parameter of an
 hi-entry aren't given very clearly, but the idea seems to be that the
 value is the index of the hi-entry that contains the URI which was mapped
 into the request-URI of this hi-entry.  There seem to be two cases:

 - The mapping was done by the proxy on its own authority, in which case
 the mp-value is the parent index of the hi-entry's index.

 - The mapping was done due to receiving a 3xx response, in which case the
 mp-value is an earlier sibling of the hi-entry's index, that of the
 downstream request which received the 3xx response.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/40>
sipcore <http://tools.ietf.org/sipcore/>