Re: [stir] SIPCoin - a new cryptocurrency for stopping robocalls

Tim Hollebeek <tim.hollebeek@digicert.com> Mon, 19 March 2018 10:49 UTC

Return-Path: <tim.hollebeek@digicert.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED9D127522 for <stir@ietfa.amsl.com>; Mon, 19 Mar 2018 03:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=digicert.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 NK296PIiaa2H for <stir@ietfa.amsl.com>; Mon, 19 Mar 2018 03:49:16 -0700 (PDT)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.199]) (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 BF8C4128D2E for <stir@ietf.org>; Mon, 19 Mar 2018 03:49:11 -0700 (PDT)
Received: from [216.82.242.46] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-7.bemta-8.messagelabs.com id 99/FC-03133-6A59FAA5; Mon, 19 Mar 2018 10:49:10 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTe0xTVxzHPffetldt9VCq/CTi4y5LJgYsGrN GY3xtseqIJEtM1rBsF722nX2Qe6vBJUYMghE0dls7sT6qs5WhsMYhA9xgE51kdhEFI2gkKo9o SwwQ/mDM5709xcf94+Rzft/f43tOzmVpfUCTzgpFHkF08Q5OPYXpnlefkhX2RyxG3yHO9MeLn zSm4ch/yFTy+KzGVFX7G7WKMYdC45S5s30EmUsjR5E50NTP5DEWld1V4C76WmW7dqFRU/h9BB VVH6uji9Gzk6gcTWEZPERBWYRs9PhHCkIXTmrI5iGCutYuVTmazKqxEe40t1EKG/Aa2D8QpxW mcS7s29+pUTgVrwffiaFkzgYYjdSrJ/LvV3TIOaw87kNoatilhHU4H04PhZKD6xD82dOT6DkZ L4ORthZGYYRnwtj1GorMSoN7/cEEAzbAo1tRNeEZEOt7qSL5+XBitDUZ5+DpgE9FOAM6ghWI8 EUKan//lnAWDPv9NOFc+DlWmTAEuAPB8QPeZEEmPNwbZghvB2+NN1mwAV79e5gmBSEauvb5ku 5mQ2XdYRURflBDc2l7woYebwXfOcWeIjyjoKHlBuVFmYF3jheQNRoHEVx5EFQFEheVAv8c7Wd IkgWqS5oQ4Uzw18aT8YVw9vQgHZDvmMYL4Fon935Y4eVQ+f9lNeH54Kt4pCG8FAb/HkGn0NRz 6CNJEHcKYlaOMbtAtFttHidvd8g7U7ZTkCTeKjj4Ail7i9v5K5Jf5ST5a0SR0rWtaBZLcTN07 u8iFv20AvfWXTZesn0l7nAIUiuazbIc6Lw+WUsRBatQtM3ukJ/2hAysljPoriiyTirknZLdSq TraCV7+8jjMpq92BuT178Sa/eTwTJaz7jcLiE9TXdJKcNKmW2H603TiV+mA2Wkp+qQbFOvLRR Ep93zvh5HaSziUnVBpYvW7vK8mR2XbVGyrc/CNYotD/9WSi9G3dvNn8TaGqN7TuGub/rWbrTO yYvtLm9x8e5Dhc9zzgervxiOwmjfllfnbZvuln5ZhV/Mudu0eMw48GBJS/tL1fjB6Vp9qGR8L HeuIeif9MsHV+Prdt/YvOhMxacN0Yyl4Xpmz8cmusfw+YqDC/OLcbjZOCZe7V29uVdrecrYbn ZFOUay8TmZtCjxrwHhj8hILQQAAA==
X-Env-Sender: tim.hollebeek@digicert.com
X-Msg-Ref: server-10.tower-96.messagelabs.com!1521456548!90845232!1
X-Originating-IP: [216.32.181.17]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22869 invoked from network); 19 Mar 2018 10:49:09 -0000
Received: from mail-co1nam03lp0017.outbound.protection.outlook.com (HELO NAM03-CO1-obe.outbound.protection.outlook.com) (216.32.181.17) by server-10.tower-96.messagelabs.com with AES256-GCM-SHA384 encrypted SMTP; 19 Mar 2018 10:49:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digicert.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=dpGVHzV6vEs7nHqXxIirEWgWeFeh6kC8Rc6sFHwLmwc=; b=pWyzIS6Mv0rLGDZlQ2Y9lydUuxAafwc+hnFPJFFET0KYaV/xx6TYKST4tMW/a/ZyxmBk36EECAq7+W38SNWju0XZsz1N/ox6+InIFw17syZxvSIrOmOtGj5TdgjkMvg5Kj1ZkbLWRB/Bv7GkFX2Xvr0RHH3n5HiT3rIxQZ94rlY=
Received: from MWHPR14MB1376.namprd14.prod.outlook.com (10.173.232.139) by MWHPR14MB1373.namprd14.prod.outlook.com (10.173.232.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.588.14; Mon, 19 Mar 2018 10:49:07 +0000
Received: from MWHPR14MB1376.namprd14.prod.outlook.com ([fe80::7929:3f48:4a4f:1e32]) by MWHPR14MB1376.namprd14.prod.outlook.com ([fe80::7929:3f48:4a4f:1e32%18]) with mapi id 15.20.0588.016; Mon, 19 Mar 2018 10:49:07 +0000
From: Tim Hollebeek <tim.hollebeek@digicert.com>
To: Cullen Jennings <fluffy@iii.ca>, Adam Roach <adam@nostrum.com>
CC: Jonathan Rosenberg <jdrosen@jdrosen.net>, "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] SIPCoin - a new cryptocurrency for stopping robocalls
Thread-Index: AQHTsngsTnylzONuGkmJ8pKXnnc3mKO/NE2AgAccMICAESQ4YA==
Date: Mon, 19 Mar 2018 10:49:07 +0000
Message-ID: <MWHPR14MB137600365A7F41D94D760B7383D40@MWHPR14MB1376.namprd14.prod.outlook.com>
References: <CA+23+fFUEESKoQXtoAwg6ySovUb5-Eiy98_wdukcLKQNOrcn3A@mail.gmail.com> <64ca7065-a73d-ce53-d715-a5569823a3c2@nostrum.com> <9E1327D0-EEE7-4AFD-9E42-91A355683820@iii.ca>
In-Reply-To: <9E1327D0-EEE7-4AFD-9E42-91A355683820@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [31.133.148.144]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR14MB1373; 7:85Fq7q2AM4+5yRoAutgCybIWMTAQeyGLQhHq/t5Z9bgDrVn+yRIJvQPTiM2vMqj3v7TXElKophC7A4LgHk3XQ8Y3ae+ts292KyA/65aDVmv8KGBCaaF65H5qqeT3yx+FWHJXWnFDKxkSbWjqCrPOJYTPKdVxmRhR4C3OsAum6z48Giiekl5lgXJBCiavhO5M+PfiFwOcnTfl2V/GmwI54YWgHFqbNgEytzRVRXQDvz6CFgq2bruRkDNIdAv32JJr
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 54d1747c-a79a-46ae-a006-08d58d870a10
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(49563074)(7193020); SRVR:MWHPR14MB1373;
x-ms-traffictypediagnostic: MWHPR14MB1373:
x-microsoft-antispam-prvs: <MWHPR14MB13733195A448013FBE57D05A83D40@MWHPR14MB1373.namprd14.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231221)(944501244)(52105095)(3002001)(93006095)(93001095)(6041310)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:MWHPR14MB1373; BCL:0; PCL:0; RULEID:; SRVR:MWHPR14MB1373;
x-forefront-prvs: 06167FAD59
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39850400004)(39380400002)(396003)(376002)(346002)(189003)(199004)(478600001)(606006)(53386004)(102836004)(561944003)(6246003)(33656002)(966005)(74316002)(66066001)(2950100002)(186003)(3846002)(26005)(8936002)(229853002)(81156014)(81166006)(5660300001)(99936001)(14454004)(8676002)(790700001)(55016002)(97736004)(7736002)(6116002)(68736007)(3660700001)(4326008)(236005)(54896002)(2900100001)(6306002)(53936002)(3280700002)(5250100002)(106356001)(6506007)(53546011)(25786009)(316002)(9686003)(59450400001)(105586002)(7696005)(110136005)(6436002)(54906003)(2906002)(86362001)(76176011)(99286004); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR14MB1373; H:MWHPR14MB1376.namprd14.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: digicert.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: F65++x5lJ3EesvOyJA7upnNpHrUh7xZd6D+slKrFBlvXjcF+9a4hCL/gOIC7Xa+8nuskUMbjLbXHqm2Mk9mFGQmSpI2zzEEw/sIV7AvcFHcy0mfF3DUwiKMhjzTmK52KDkWTGNZDzjtQuwlSyxfTrCJ1K3CAAxpB4HZDoryjug4ipRiHcd1CGRF13427shlmWRjxLuYoXhFlqgrCqCCDVlVNlKbBU8ZYn1AYdXvkqS5xtSdGH0cCyiJwqmV0XOY3N4GWVykAe76bQ6hVGIKpAz/OPQ3f0Cj4GneoNzPm54ChkuBb1Vf1cJ2XL054WGmb8zT7XYgScyBfzTGq1QbNpQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="2.16.840.1.101.3.4.2.1"; boundary="----=_NextPart_000_0419_01D3BF6F.E5C5FFF0"
MIME-Version: 1.0
X-OriginatorOrg: digicert.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 54d1747c-a79a-46ae-a006-08d58d870a10
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2018 10:49:07.0193 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf813fa1-bde5-4e75-9479-f6aaa8b1f284
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR14MB1373
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/SkX61VIzkawgTNCmWq-RnJR7gPI>
Subject: Re: [stir] SIPCoin - a new cryptocurrency for stopping robocalls
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 10:49:24 -0000

 

So, that environmental computation assumes that the energy input comes from fossil fuel, and the heat output is a useless waste product that has no value.

 

This is in fact largely true for mining operations that are sited primarily based on access to the cheapest carbon electricity in order to maximize profits, and then cool them to keep them operating.  Which is likely to be true today in many cases.

 

However, there are other use cases where you put your crypto miners in a location where you would otherwise be using an electric heater, using responsibly sourced electricity.  Crypto miners can also be seen as very expensive electric heaters, that also produce a computational side benefit.

 

>From that point of view (setting aside the question of whether mining cryptocurrency is useful computational work and whether there is another kind of computation that is more valuable for the same energy cost), is there an economical way to upgrade all the world’s electric heaters to provide useful computation resources available on demand as part of some sort of network?

 

That would have a much larger ecological impact if someone figures it out.  Moving computation to where heating is required makes more sense than providing cooling where computation is required.  Unfortunately it’s also generally much harder, which is why we often don’t do it today.

 

But I just wanted to throw it out there in case it inspires someone else.

 

-Tim

 

From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Cullen Jennings
Sent: Thursday, March 8, 2018 12:41 PM
To: Adam Roach <adam@nostrum.com>
Cc: Jonathan Rosenberg <jdrosen@jdrosen.net>; stir@ietf.org
Subject: Re: [stir] SIPCoin - a new cryptocurrency for stopping robocalls

 

 

So as a super casual analysis of the current draft, 

 

Lets say we need order of magnitude 10 cents to stop spam, that equates to something like 1KW, which equates to something like 1Kg of CO2. Each of of those steps is only an order go magnitude estimate so this cab be way out but you get the idea. So we would have a one time, assuming major carriers shared validation data,  ( or small number of times ) validation of the self signed cert and each validation would take about 1 Kg CO2. That sounds really bad. But for comparisons sake, your flight to IETF is probably over 1000 Kg and it is not a one time event

 

But all that said, I don’t think we would actually go for with something as simple as pure proof of work based approach so I don’t think that is a realistic look at the power usage. There are a bunch of techniques that add to the complexity but greatly reduce the reliance on proof work and more move to things like proof of stake or more risk based approaches. Solutions like that could greatly reduce the power usage. Keep in mind reducing the amount of spam calls would reduce the power usage of the whole phone system. 

 





On Mar 3, 2018, at 5:06 PM, Adam Roach <adam@nostrum.com <mailto:adam@nostrum.com> > wrote:

 

One of the issues that has arisen in parallel with cryptocurrencies is a recognition of the exorbitant energy (and therefore environmental) costs they entail. I think this document probably requires a section addressing this aspect of the system, including any ways that it varies significantly from traditional cryptocurrencies in this regard.

/a

On 3/2/18 4:45 PM, Jonathan Rosenberg wrote:

Cullen and I have just submitted this:
https://www.ietf.org/id/draft-rosenberg-stir-sipcoin-00.txt

which is a proposal for a new type of cyryptocurrency dedicated solely to preventing spam on the SIP-based phone network. It is designed to be fast, causing less than one second increases in call setup time. NOn-transferrable to avoid being a tool for fraud and avoid being tied to market whim; backed by public CAs with a new type of centralized ledger validation; trivially verifiable by receivers of calls. Also we suggest a technique for incremental deployment on the PSTN which has incremental benefits and economic benefits for each deployment phase. We've done some analysis on the economics to help motivate the solution.

WHen combined with our previous draft, and some nice whitelisting thrown in as described in here, I think this is a very interested technique to put this robocalling plague to rest.

I'm coming to London and looking forward to discussing. 

Comments are, of course, welcome.



-- 

Jonathan Rosenberg, Ph.D.
jdrosen@jdrosen.net <mailto:jdrosen@jdrosen.net> 
http://www.jdrosen.net <http://www.jdrosen.net/> 






_______________________________________________
stir mailing list
stir@ietf.org <mailto:stir@ietf.org> 
https://www.ietf.org/mailman/listinfo/stir

 

_______________________________________________
stir mailing list
stir@ietf.org <mailto:stir@ietf.org> 
https://www.ietf.org/mailman/listinfo/stir