[openpgp] cryptocurrency standardisation

Ian G <iang@iang.org> Thu, 05 November 2015 19:21 UTC

Return-Path: <iang@iang.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C18011AD244 for <openpgp@ietfa.amsl.com>; Thu, 5 Nov 2015 11:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id W-xsmXlflyBN for <openpgp@ietfa.amsl.com>; Thu, 5 Nov 2015 11:21:26 -0800 (PST)
Received: from virulha.pair.com (virulha.pair.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 528E31ACE9E for <openpgp@ietf.org>; Thu, 5 Nov 2015 11:21:26 -0800 (PST)
Received: from Agent86.local (iang.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by virulha.pair.com (Postfix) with ESMTPSA id F1D036D747; Thu, 5 Nov 2015 14:21:24 -0500 (EST)
To: openpgp@ietf.org
References: <5623AA95.4060903@googlemail.com> <874mh3q3ol.fsf@alice.fifthhorseman.net> <56385818.2000606@googlemail.com> <20151103092006.3cd3e900@latte.josefsson.org> <CABtrr-W_24_CumkdGuxW4Ve=NUA_7qa0v=utbaWN0CDoodhfpw@mail.gmail.com> <CADZ5=vtV20dMua+D0O_0Hc8OAXwv0ej-VnH=B2NMj2fZK23jpQ@mail.gmail.com> <CABtrr-XVhGitJVik96Xc3kRbUH8ZoGPArdaNoKgOZtK7fPGVCQ@mail.gmail.com> <563955F4.9030607@cs.tcd.ie> <87mvus26qp.fsf@latte.josefsson.org> <CADZ5=vs6_RJ1E89VyMHTv1WwHD_y+0+Sf_jb7bxrN0-2G3tKCg@mail.gmail.com> <B93BD8EB-6D1D-48C2-90A2-64EABFA06A81@josefsson.org>
From: Ian G <iang@iang.org>
Message-ID: <563BAC33.7020501@iang.org>
Date: Thu, 05 Nov 2015 19:21:23 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <B93BD8EB-6D1D-48C2-90A2-64EABFA06A81@josefsson.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/0w_Ewnw36ahpxWfbvwjt0CdhYCw>
Subject: [openpgp] cryptocurrency standardisation
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 19:21:27 -0000

On 05/11/2015 11:31, Simon Josefsson wrote:
> There is not a lot of cryptocurrency standardisation going on in the IETF, alas. What do you think about using the term "proof of work" in the title instead? It appears to be the cryptographic property that cryptocurrencies (and other applications!) want from a primitive. I perceive that other PoW-ideas may be standardized in the IETF before currencies are.

If argon is being proposed for a proof of work only then it should not 
include cryptocurrency in the title.

Also, standardisation in the cryptocurrency world works a bit different 
to how it works in IETF WG fashion - I'm not sure I can see the 
benefit.  Standardisation works best when the system is already out 
there and in use, not as sort of trial balloon - is argon in use in any 
systems as a PoW?

Colour me skeptical!


> Have you or anyone provided security reductions for Argon2 btw? Similar to the reductions that are available for Catena.  They would help to substantiate any claims in the document that Argon2 is secure for its intended uses.
> /Simon
> Alex Biryukov <alex.biryukov@uni.lu> skrev: (5 november 2015 12:07:17 CET)
>> We discussed it briefly, would it be possible to add "cryptocurrency"
>> to
>> the title to cover two main usage areas. Then it would  make sense to
>> keep
>> both Argon2i and Argon2d in the standard.
>> "The memory-hard Argon2 password and cryptocurrency hash function
>> draft-josefsson-argon2-00