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

"Francois Audet" <audet@nortel.com> Thu, 24 February 2005 23:49 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 SAA09123 for <sip-web-archive@ietf.org>; Thu, 24 Feb 2005 18:49:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Sjb-0008Kz-8r for sip-web-archive@ietf.org; Thu, 24 Feb 2005 18:49:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4SfK-000196-AZ; Thu, 24 Feb 2005 18:45:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4SfH-00018N-C9 for sip@megatron.ietf.org; Thu, 24 Feb 2005 18:45:04 -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 SAA08746 for <sip@ietf.org>; Thu, 24 Feb 2005 18:44:59 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4SfH-0008Dl-A0 for sip@ietf.org; Thu, 24 Feb 2005 18:45:03 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j1ONioj04899; Thu, 24 Feb 2005 18:44:50 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1J5BFKPB>; Thu, 24 Feb 2005 18:44:50 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0198028F@zrc2hxm0.corp.nortel.com>
From: Francois Audet <audet@nortel.com>
To: 'David R Oran' <oran@cisco.com>
Subject: RE: [Sip] draft-jennings-sip-hashcash-01
Date: Thu, 24 Feb 2005 18:44:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
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>
Content-Type: multipart/mixed; boundary="===============1234877586=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451

Hi Dave,

I understand this. I guess I wasn't clear.

It is in the OTHER direction that I see a problem. I mean when the UAC
is, for example, a big gateway.

In other words, if a bunch of SIP "phones" UAS all decide to send 419's to
the UAC in the Gateway.


> -----Original Message-----
> From: David R Oran [mailto:oran@cisco.com] 
> Sent: Thursday, February 24, 2005 12:53
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: 'Cullen Jennings'; 'sip@ietf.org'
> Subject: Re: [Sip] draft-jennings-sip-hashcash-01
> 
> 
> 
> On Feb 24, 2005, at 2:30 PM, Francois Audet wrote:
> 
> > We may need to explain some of the limitations of this. It 
> seems to me
> > that this mechanism would not be terribly appropriate for 
> applications  
> > that aggregate a large number of clients onto a single 
> platform. For  
> > example, this may be too computationally intensive for a 
> large PSTN  
> > Gateway, or even a large Proxy.
> >  
> That's the whole point! It's to prevent too many calls from 
> one place.  
> It's always under the calling UACs prerogative to give up 
> with "what a  
> bozo who wants me to blow smoke out of my Pentium for 2000ms. 
> Guess he  
> doesn't want to get the call, huh"?
> 
> I suspect a decently managed UA would only force you not the puzzle  
> palace if you weren't on the buddy list, or some other whitelist.
> 
> > Any ideas of how a UAS would make the decision to send the 
> 419 without
> > burdening the UAC? Should there be a supported/require 
> header for this  
> > functionality, so that a UAC could "opt out"?
> If the UAC can opt out the whole exercise is useless.
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of
> > Cullen Jennings
> > Sent: Tuesday, February 22, 2005 16:46
> > To: sip@ietf.org
> > Subject: [Sip] draft-jennings-sip-hashcash-01
> >
> >
> > I updated this draft on "SIP Computational Puzzles" so it 
> has enough  
> > detail to implement it. (Previous version did not). It is in the  
> > drafts directory and also in HTML form at:
> >
> > 
> http://scm.sipfoundry.org/rep/ietf-drafts/fluffy/draft-jennings-sip- 
> > hashcash-01.html
> >
> > Cullen
> > _______________________________________________
> > 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
> David R. Oran
> Cisco Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> Email: oran@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