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

Hadriel Kaplan <HKaplan@acmepacket.com> Mon, 30 August 2010 20:48 UTC

Return-Path: <HKaplan@acmepacket.com>
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 32D053A6874 for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 13:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level:
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599]
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 aa98AGl0dZib for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 13:48:26 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 2E82A3A6859 for <sipcore@ietf.org>; Mon, 30 Aug 2010 13:48:26 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 30 Aug 2010 16:48:56 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Mon, 30 Aug 2010 16:48:56 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Mon, 30 Aug 2010 16:48:55 -0400
Thread-Topic: [sipcore] #4: The new "hit" parameter is gonna cause problems
Thread-Index: ActIhMMNuiiZYlXOSy6l/tJ4JwZjGw==
Message-ID: <42833A4B-F051-406B-9FFA-F9246C7D423A@acmepacket.com>
References: <D8058F83-99AD-4A9D-9713-46D0985FA626@acmepacket.com>
In-Reply-To: <D8058F83-99AD-4A9D-9713-46D0985FA626@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org" <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
Precedence: list
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 20:48:27 -0000

On Aug 30, 2010, at 1:51 PM, Hadriel Kaplan wrote:

>> 
>> > Third, it should be a
>> >  header param not a URI param, I think (which would solve the previous
>> >  issues).
>> 
>> [MB] It's not at all clear to me why you think this needs to be a
>> header parameter or how such would solve the problems you anticipate
>> (although that's because I don't understand what problems you think
>> will happen with the current approach).[/MB]
>> 
> If it's a header param, then it's not part of the URI in the contact that becomes the request-uri of the recursed/new request, does not matter if it's SIP or TEL, and is ignored if not understood.

And once we agree on it being a header param, the next thing I'll ask for is to not make it a "hit=" but rather just the two params "rc" and "mp".  Then all the proxy needs to do is copy the contact-URI to H-I, as it would have done with a request-URI.  It doesn't have to look for the "hit" param and convert its value to a new param name.  Seems simpler to me.

-hadriel