Re: [sipcore] #4: The new "hit" parameter is gonna cause problems

"sipcore issue tracker" <trac@tools.ietf.org> Tue, 31 August 2010 15:47 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 AC0C93A69B7 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level:
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.027, 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 gPQUlrF48tk2 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 08:47:11 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 142E83A699A for <sipcore@ietf.org>; Tue, 31 Aug 2010 08:46:50 -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 1OqT3P-0004ou-Dp; Tue, 31 Aug 2010 08:47:19 -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 15:47:19 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/4#comment:1
Message-ID: <073.2f55d9628ccb5430d09e29c0ffed2c8f@tools.ietf.org>
References: <064.f8bb79c01723e8d8b3653963f8e4727a@tools.ietf.org>
X-Trac-Ticket-ID: 4
In-Reply-To: <064.f8bb79c01723e8d8b3653963f8e4727a@tools.ietf.org>
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: Re: [sipcore] #4: The new "hit" parameter is gonna cause problems
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 15:47:12 -0000

#4: The new "hit" parameter is gonna cause problems
------------------------------------+---------------------------------------
 Reporter:  hkaplan@…               |       Owner:            
     Type:  defect                  |      Status:  new       
 Priority:  major                   |   Milestone:  milestone1
Component:  rfc4244bis              |     Version:  2.0       
 Severity:  In WG Last Call         |    Keywords:            
------------------------------------+---------------------------------------

Comment(by worley@…):

 "hit" is defined as a URI-parameter on the Contact values in 3xx
 responses, but in reality, it is metadata *describing* the URI, not *part*
 of the URI.  Naively it would seem that "hit" should be a header
 parameter.

 This change would require some parallel changes in the description of
 proxy functioning.

 This change would remove some processing steps in which the "hit" URI-
 parameter value is removed from the URI portion of the Contact value.

 This change would also aid backward compatibility, in that a proxy that
 does not understand 4244bis that receives a 3xx response with a Contact
 header that contains a "hit" header parameter would automatically not
 transfer the "hit" value to the request-URIs of further forked requests.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/4#comment:1>
sipcore <http://tools.ietf.org/sipcore/>