Re: [Din] Databases vs. ledgers for infrastructure
Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Mon, 05 February 2018 15:23 UTC
Return-Path: <Jon.Crowcroft@cl.cam.ac.uk>
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 740101242F7 for <din@ietfa.amsl.com>; Mon, 5 Feb 2018 07:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 Jh4w4a1Jat6E for <din@ietfa.amsl.com>; Mon, 5 Feb 2018 07:23:22 -0800 (PST)
Received: from mta0.cl.cam.ac.uk (mta0.cl.cam.ac.uk [128.232.25.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB0412D848 for <din@irtf.org>; Mon, 5 Feb 2018 07:23:17 -0800 (PST)
Received: from ely.cl.cam.ac.uk ([128.232.64.213] ident=jac22) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>) id 1eiibz-00081u-66; Mon, 05 Feb 2018 15:23:15 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
To: Jordi Paillissé Vilanova <jordip@ac.upc.edu>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, din@irtf.org, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
In-reply-to: <5d34c117-4471-465a-2808-5b78d3c19778@ac.upc.edu>
References: <5C8B3827-B1FA-4808-92C4-BAA5AE3102B8@icann.org> <e43dbd76-dd30-9fe9-b1ae-6d5dcaa33018@gmail.com> <5d34c117-4471-465a-2808-5b78d3c19778@ac.upc.edu>
Comments: In-reply-to Jordi Paillissé Vilanova <jordip@ac.upc.edu> message dated "Mon, 05 Feb 2018 13:57:01 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1283.1517844195.1@ely.cl.cam.ac.uk>
Date: Mon, 05 Feb 2018 15:23:15 +0000
Message-Id: <E1eiibz-00081u-66@mta0.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/4831_Q37ncsHUI-9-Vi_vbey_lU>
Subject: Re: [Din] Databases vs. ledgers for infrastructure
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: Mon, 05 Feb 2018 15:23:24 -0000
> Generally speaking, I'd say it depends on your trust policy. If you trust > all the nodes inside your infrastructure, just put the ledger on one of > them and let the others query it. If you are concerned that a node may be > compromised, put the ledger in all the nodes, so they can detect undesired > modifications. > there was this cool old protocol suddenly occured to me we could revisit w.r.t standards for blockchains, maybe: https://tools.ietf.org/html/draft-mrose-blocks-architecture-01 > > Regards, > > Jordi > > > El 03/02/18 a les 20:21, Brian E Carpenter ha escrit: > > On 03/02/2018 06:20, Paul Hoffman wrote: > > Greetings. In prepping for our upcoming meeting, I was re-reading > the charter and find that a lot of it is about ledgers, particularly > blockchain systems. However, I am being uncreative and cannot think of > any use cases for infrastructure needing to see a local copy of a ledger, > just needing to see the current state of the database. Of course, people > making policy for infrastructure get value from ledgers or a time series > of database snapshots > > Do we have a list of use cases where the infrastructure itself > needs to have a ledger in order to act without human intervention? > > I think that will depend on what some particular infrastructure > component is trying to do. Just let me wave my hands a bit: consider a > node that is trying to diagnose a problem with a particular IP address. > If it includes an AI component or just some clever heuristics, it might > need to know who was using that address two days ago. Did that address > get black listed, for example? We don't want to rely on a centralized > database for this, because that's also a centralized single point of > failure. > > More generally - if we're going to distribute management functions, > we potentially need to distribute management data too, for both speed and > reliability. > > Brian > > _______________________________________________ > 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] Databases vs. ledgers for infrastructure Paul Hoffman
- Re: [Din] Databases vs. ledgers for infrastructure Brian E Carpenter
- Re: [Din] Databases vs. ledgers for infrastructure Jordi Paillissé Vilanova
- Re: [Din] Databases vs. ledgers for infrastructure Jon Crowcroft