Re: [Sip] draft-jennings-sip-hashcash-01

Jonathan Rosenberg <jdrosen@cisco.com> Fri, 04 March 2005 03:55 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19286 for <sip-web-archive@ietf.org>; Thu, 3 Mar 2005 22:55:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D73ve-00037y-5l for sip-web-archive@ietf.org; Thu, 03 Mar 2005 22:56:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D73sC-00080a-Bf; Thu, 03 Mar 2005 22:53:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D73sA-00080V-4l for sip@megatron.ietf.org; Thu, 03 Mar 2005 22:53:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19132 for <sip@ietf.org>; Thu, 3 Mar 2005 22:53:03 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D73td-00034T-N2 for sip@ietf.org; Thu, 03 Mar 2005 22:54:39 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-3.cisco.com with ESMTP; 03 Mar 2005 21:09:02 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,134,1107734400"; d="scan'208"; a="231279044:sNHT9538822814"
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com [171.71.163.28]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j243qmYO017586; Thu, 3 Mar 2005 19:52:49 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-1.cisco.com [10.86.240.1]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AIF66762; Thu, 3 Mar 2005 19:52:47 -0800 (PST)
Message-ID: <4227DB8E.7000900@cisco.com>
Date: Thu, 03 Mar 2005 22:52:46 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [Sip] draft-jennings-sip-hashcash-01
References: <1ECE0EB50388174790F9694F77522CCF01A71139@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF01A71139@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: 'Cullen Jennings' <fluffy@cisco.com>, "'sip@ietf.org'" <sip@ietf.org>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit

Sigh.... probably. Its been on my todo list forever, and its one of 
these things where the cure may be worse than the disease. But perhaps 
others have a better idea how to fix it than I did. That solution was 
discussed here:

http://www.jdrosen.net/papers/draft-rosenberg-sip-unify-00.txt

-Jonathan R.



Francois Audet wrote:

> As a separate note, shouldn't we try to solve the HERFP problem?
> 
> 
>  > -----Original Message-----
>  > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>  > Behalf Of Cullen Jennings
>  > Sent: Wednesday, March 02, 2005 12:16
>  > To: Jonathan Rosenberg
>  > Cc: sip@ietf.org
>  > Subject: Re: [Sip] draft-jennings-sip-hashcash-01
>  >
>  >
>  > On 3/2/05 2:15 AM, "Jonathan Rosenberg" <jdrosen@cisco.com> wrote:
>  >
>  > > 1. The mechanism interacts badly with forking at the moment. One
>  > > problem is HERFP. If I have a mix of endpoints, some of
>  > which support
>  > > this (and thus send a 419), and others that don't (and thus
>  > ring the
>  > > phone), then you'll end up always completing the call on
>  > the endpoints
>  > > that don't support the extension.
>  >
>  > Good point. I think will mention this in the draft but
>  > clearly I won't attempt to solve the well studied HERFP
>  > problem. As a separate issues, some day the WG should discuss
>  > the limitations of the "If it hurts don't do it" solution to
>  > the HERFP problem.
>  >
>  > >
>  > > 2. THe mechanism doesn't provide a way for a proxy to aggregate
>  > > multiple Puzzle headers from forked branches. It needs to
>  > do something
>  > > like WWW-Authenticate where a proxy collects these from the various
>  > > 419 and places all of them in the 419 forwarded upstream. That will
>  > > also require something akin to realm, that allows a
>  > UA/proxy to pull
>  > > out its own puzzle.
>  >
>  > Oops. Excellent point. Thanks, will fix this.
>  >
>  >
>  > _______________________________________________
>  > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>  > This list is for NEW development of the core SIP Protocol
>  > Use sip-implementors@cs.columbia.edu for questions on current
>  > sip Use sipping@ietf.org for new developments on the
>  > application of sip
>  >
>  >
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip