Re: [art] Thursday lunch discussion on new techniques for stopping robocalling

Ned Freed <ned.freed@mrochek.com> Mon, 19 March 2018 17:06 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386B612D7FC; Mon, 19 Mar 2018 10:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id biwMuF4vzBVt; Mon, 19 Mar 2018 10:06:33 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C885128959; Mon, 19 Mar 2018 10:06:32 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQBGF789KG00EC0K@mauve.mrochek.com>; Mon, 19 Mar 2018 10:01:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1521478888; bh=qJdSy78SvZvCnpNxOKS32IRVUcjXQzNpVAORkG/z8J8=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=kNfMmet/I8mpDgRYJTxgKAhkA4cIf9ECANEciSG5YiTpdDBgUGOcByLZHClRtHgS8 EsWibXezHgL3Eqtu9eQH6sRdDZkpCJRcrplQ4GwzTttFaEgBuxlIO205G5o9oHjzRr nsoqGa4hSZJG21ScKBN9oY+fw5LEn4JnDTMFs1Lg=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QQ1J13T4YO00CZTT@mauve.mrochek.com>; Mon, 19 Mar 2018 10:01:26 -0700 (PDT)
Cc: Applications and Real-Time Area Discussion <art@ietf.org>, stir@ietf.org
Message-id: <01QQBGF58BIE00CZTT@mauve.mrochek.com>
Date: Mon, 19 Mar 2018 10:00:56 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 17 Mar 2018 13:49:13 -0700" <1760564F-45CC-4EE2-869A-76EDB434694A@wordtothewise.com>
References: <CA+23+fFxLXt8v-TF=vyn-AptHHMJfJC14jh315z3CJF-AYGf_Q@mail.gmail.com> <CA+9kkMDtEhti-HTsY3K_KMU0r3ReNh5M0Xnt9XMMk9AXPfMWew@mail.gmail.com> <1760564F-45CC-4EE2-869A-76EDB434694A@wordtothewise.com>
To: Steve Atkins <steve@wordtothewise.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/OoK2QPeacEZKU2WjbVtixoIQiNg>
Subject: Re: [art] Thursday lunch discussion on new techniques for stopping robocalling
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 17:06:35 -0000

> > On Mar 17, 2018, at 10:58 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> >
> > Hi Jonathan, Cullen,
> >
> > I was somewhat surprised that the draft did not have a direct reference to the SIP Hashcash work (especially since Cullen was the author of https://tools.ietf.org/html/draft-jennings-sip-hashcash-06).  From my perspective at least, it still looks to be a useful historical antecedent to consult, since it is a proof-of-work system (and one on which a bunch of later cryptocurrencies draw).  In particular, its view that this is about a demonstration of work rather than a payment to send may still be a valuable perspective.
> >
> > http://www.hashcash.org/ still appears to be up, by the way, for folks that want to see how its original use case tied into thwarting denial of service attacks.

> I hope someone is soliciting input from the email community, who went through
> this process a decade or so ago and noted that bad actors have much, much
> cheaper access to CPU for proof-of-work than good actors do.

+1

And if anything it's even more lopsided now.

				Ned