Re: [Din] Hyperledger evaluation on a mesh network

Jehan Tremback <jehan@altheamesh.com> Wed, 04 April 2018 23:43 UTC

Return-Path: <jehan@altheamesh.com>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA701126C2F for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 16:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 CMvv_sD6_hYx for <din@ietfa.amsl.com>; Wed, 4 Apr 2018 16:43:45 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E1531200A0 for <din@irtf.org>; Wed, 4 Apr 2018 16:43:45 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 62D712106D; Wed, 4 Apr 2018 19:43:43 -0400 (EDT)
Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Wed, 04 Apr 2018 19:43:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=rMXZuj tPJqQH+4Q+IlX99Ey9Pfaj01z0ATnJdIU72Ho=; b=D4lfdmdJ03etZ2t9eAQmNu 7UCINyejW4q9TR2V4z0f/0D6CDx7l9LO2O+jHOMUdSkCeB4pXaMvo7kQlvcX8VJh xc7bQXjHsw+JuOM3hU409w5OuWSSocayc6+PHV2C6j/KSKiEa1u6V4NcaFf7VTZk 3tvc4s7pTYcIsDKv9DYWoZjhPZXFCzTvzVExh0HIvLzOeY6tWwTK1Na+Mxjp5Tfa qneId2G34CZNuvxvGU3oHKfneCq+hzoTrjlIY7jSnYfJ1N+WUf1Q3jNGUBnDvdYE XbTXG7jFeVeRQ/1rzgrHNUQMFsS8jSUSiJxJoqB+YQqS7DokWsrKKsNT21EVHswQ ==
X-ME-Sender: <xms:L2PFWswy1P1PIahZ1qRXosduq5n0Mo7SJWOesKOfpNj2gAgXWJMMlg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3BA8A9E19C; Wed, 4 Apr 2018 19:43:43 -0400 (EDT)
Message-Id: <1522885423.2450300.1326960016.657AF135@webmail.messagingengine.com>
From: Jehan Tremback <jehan@altheamesh.com>
To: Leandro Navarro <leandro@ac.upc.edu>
Cc: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>, din@irtf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_152288542324503003"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-bb419338
References: <CAPaG1AnJjDQh4N+kiT-QhgiFyNwi69TM74jcYFx6xQiwPXB+EQ@mail.gmail.com> <1522807761.2691505.1325710912.72C042EF@webmail.messagingengine.com> <CAEeTejK71xdhXYowRS+fh=Ni-4dusbAui9h9BJ3K-n-8TTAPOg@mail.gmail.com> <1522857502.1313779.1326451800.352B185C@webmail.messagingengine.com> <DC5D2E36-D054-439E-83A6-05AC4DF9AB75@ac.upc.edu>
Date: Wed, 04 Apr 2018 16:43:43 -0700
In-Reply-To: <DC5D2E36-D054-439E-83A6-05AC4DF9AB75@ac.upc.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/P4kVaH5aYiLVLiaxQupXVXHbWgU>
Subject: Re: [Din] Hyperledger evaluation on a mesh network
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2018 23:43:48 -0000

Thanks Leandro. Our protocol does indeed leave pricing considerations
un-analyzed. This is something we will unfortunately not be testing
in a simulation like Jon, we'll have to see how things evolve in the
real world. Some of the insights gained from that paper may prove to
be useful.
The paper that Arjuna shared does indeed provide interesting and
rigorous experimental results on running a very small consensus
network in some specific network conditions. My criticisms were on the
"why" of doing that and do not detract from the quality of the paper.
Thanks for sharing.
--
  Jehan Tremback
  jehan@altheamesh.com



On Wed, Apr 4, 2018, at 4:08 PM, Leandro Navarro wrote:
> The paper that Arjuna shared looks to the general topic of this WG
> “Decentralized Internet Infrastructure”, with an evaluation of the
> Hyperledger framework when running on a edge scenario of small Debian
> servers spread in a mesh network (not in the routers), instead of a
> typical data center env.> 
> 
>> On 4 Apr 2018, at 17:58, Jehan Tremback <jehan@altheamesh.com> wrote:>> 
>> Even simpler, by adding a monetary price metric to a distance vector
>> protocol (we are currently testing this in production). Skimming your
>> paper, it looks like you are thinking along the same lines.> 
> Simpler but not too simple regarding pricing. Jon’s paper looked in
> 2010 at pricing related to congestion, fairness, incentives for
> cooperation, sending rates in flows and overall stability in a local
> mobile ad-hoc net. Still relevant work 8 years later.> 
>> Back to the Arjuna's post, the use of a blockchain implies that there
>> is some value to having an immutable transaction ordering mechanism.
>> In our protocol we conceptualize these ordered transactions as
>> "payments", while in Arjuna's paper the actual use of this
>> transaction ordering is left unspecified.> 
> … not an objetive of that research paper (evaluation of Hyperledger)
> != whitepaper.> 
>> Running the transaction ordering consensus protocol on the network
>> nodes themselves seems like a bad idea.>> These nodes have more of an incentive to mess with the ordering than
>> some faraway validators who know nothing about the specific
>> application and are only incentivized to order transactions
>> correctly. Also, the fact that there are always going to be many
>> fewer validators available on a local network means that the
>> consensus pool is smaller and more vulnerable to manipulation.> 
> Hyperledger has strong limitations when running in small servers,
> let’s forget about routers, but just relying on remote servers for
> local transactions can have drawbacks too.> 
>> I say, leave the transaction ordering to a global network of
>> validators who specialize in transaction ordering and leave the
>> networking to network hardware equipped with light clients. With
>> Althea, we are able to run everything on commodity routers on OpenWRT> 
> Thanks for your comments, Leandro.
> 
>> .
>> 
>> --
>>   Jehan Tremback
>>   jehan@altheamesh.com
>> 
>> 
>> 
>> On Wed, Apr 4, 2018, at 1:04 AM, Jon Crowcroft wrote:
>>> or a much simpler approach:
>>> https://hal.inria.fr/inria-00466747/document
>>> 
>>> On Wed, Apr 4, 2018 at 3:09 AM, Jehan Tremback
>>> <jehan@altheamesh.com> wrote:>>>> __
>>>> Why run full nodes on your networking hardware? One could achieve
>>>> the same security characteristics (or better) by simply using light
>>>> clients of a public blockchain on the networking hardware.>>>> 
>>>> --
>>>>   Jehan Tremback
>>>>   jehan@altheamesh.com
>>>> 
>>>> 
>>>> 
>>>> On Tue, Apr 3, 2018, at 4:44 AM, Arjuna Sathiaseelan wrote:
>>>>> we recently did an evaluation of the hyperledger fabric in a
>>>>> community wireless network within the famous guifi.net[1]..>>>>> 
>>>>> will be of interest https://arxiv.org/pdf/1804.00561.pdf
>>>>> 
>>>>> Regards
>>>>> 
>>>>> -- 
>>>>> 
>>>>> Arjuna Sathiaseelan
>>>>> University of Cambridge | Ammbr Research Labs
>>>>> Personal: http://www.cl.cam.ac.uk/~as2330/
>>>>> N4D Lab: http://www.cl.cam.ac.uk/~as2330/n4d
>>>>> _________________________________________________
>>>>> Din mailing list
>>>>> Din@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/din
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Din mailing list
>>>> Din@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/din
>>>> 
>> 
>> _______________________________________________
>> Din mailing list
>> Din@irtf.org
>> https://www.irtf.org/mailman/listinfo/din
> 
> --
> Leandro Navarro
> http://people.ac.upc.edu/leandro  http://dsg.ac.upc.edu


Links:

  1. http://guifi.net/