IETF Logo Mail Archive

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

Henning Schulzrinne <hgs@cs.columbia.edu> Wed, 02 March 2005 19:03 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 OAA14689 for <sip-web-archive@ietf.org>; Wed, 2 Mar 2005 14:03:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6Z9I-0008DI-1l for sip-web-archive@ietf.org; Wed, 02 Mar 2005 14:04:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6Z5x-0005lZ-73; Wed, 02 Mar 2005 14:01:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D6Z5v-0005lS-2K for sip@megatron.ietf.org; Wed, 02 Mar 2005 14:01:15 -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 OAA14428 for <sip@ietf.org>; Wed, 2 Mar 2005 14:01:13 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D6Z77-00088m-5p for sip@ietf.org; Wed, 02 Mar 2005 14:02:30 -0500
Received: from lion.cs.columbia.edu (IDENT:qKOXG7CYXxjC9y2lmYJWy8nB/UQMr/MB@lion.cs.columbia.edu [128.59.16.120]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j22J04ir005383 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 2 Mar 2005 14:00:04 -0500 (EST)
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206]) (authenticated bits=0) by lion.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id j22J03Rn004950 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Mar 2005 14:00:03 -0500
Message-ID: <42260D2E.50503@cs.columbia.edu>
Date: Wed, 02 Mar 2005 13:59:58 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Thomas <mat@cisco.com>
Subject: Re: [Sip] draft-jennings-sip-hashcash-01
References: <1ECE0EB50388174790F9694F77522CCF01980E18@zrc2hxm0.corp.nortel.com> <4225924C.6030100@cisco.com> <1109789547.22395.2.camel@thomasm-lnx.cisco.com>
In-Reply-To: <1109789547.22395.2.camel@thomasm-lnx.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: 'Cullen Jennings' <fluffy@cisco.com>, "'sip@ietf.org'" <sip@ietf.org>, Francois Audet <audet@nortel.com>
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: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

Also, applications like "reverse 911" (community emergency alert 
systems) would be severely hampered by such approaches. With verifiable 
source domains and domain-level trust mechanisms, I think we have better 
tools at hand that don't require the 'make everyone suffer' approach.

Michael Thomas wrote:
> The big problem I have with hashcash is the advent of 
> zombie armies. With them in mind, about them only
> thing you do is punish legitimate UA's with itsy-bitsy
> CPU's, and leave the spammers essentially unaffected 
> with their near limitless CPU resources.

_______________________________________________
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

v2.23.0 | Report a Bug | By Email