IETF Logo Mail Archive

Re: [Blockchain-interop] Gatweay Crash Recovery Discussion #1

Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt> Mon, 30 November 2020 22:22 UTC

Return-Path: <rafael.belchior@tecnico.ulisboa.pt>
X-Original-To: blockchain-interop@ietfa.amsl.com
Delivered-To: blockchain-interop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 286343A11F1 for <blockchain-interop@ietfa.amsl.com>; Mon, 30 Nov 2020 14:22:05 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tecnico.ulisboa.pt
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 NtJkAUvdKiIQ for <blockchain-interop@ietfa.amsl.com>; Mon, 30 Nov 2020 14:22:01 -0800 (PST)
Received: from smtp1.tecnico.ulisboa.pt (smtp1.tecnico.ulisboa.pt [IPv6:2001:690:2100:1::15]) (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 0ED7C3A11D8 for <blockchain-interop@ietf.org>; Mon, 30 Nov 2020 14:22:00 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.tecnico.ulisboa.pt (Postfix) with ESMTP id DDF6E6759F56; Mon, 30 Nov 2020 22:21:58 +0000 (WET)
X-Virus-Scanned: by amavisd-new-2.11.0 (20160426) (Debian) at tecnico.ulisboa.pt
Received: from smtp1.tecnico.ulisboa.pt ([127.0.0.1]) by localhost (smtp1.tecnico.ulisboa.pt [127.0.0.1]) (amavisd-new, port 10025) with LMTP id gmBCWWkNYLwz; Mon, 30 Nov 2020 22:21:55 +0000 (WET)
Received: from mail1.tecnico.ulisboa.pt (mail1.ist.utl.pt [IPv6:2001:690:2100:1::b3dd:b9ac]) by smtp1.tecnico.ulisboa.pt (Postfix) with ESMTPS id C82986EEC533; Mon, 30 Nov 2020 22:21:55 +0000 (WET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tecnico.ulisboa.pt; s=mail; t=1606774915; bh=3JMrR0/qJe2dZg3odD+F4fBaU8v+lwnwMpkAIBZnWUc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=uyV7yhb38xeMSZYG51LAECN6Mxw72NW65lIXDScGieTLUuX2+RwxHHfMmd3GRRacS Bp4rnuHGtruDmRitQoHswKfhPZvCynwkvNgiV5hHPXkO3I+5OWDN1NeHVyjaA9QyIo 7n0mf2OC1wyr2JhGKH7G0RVrHXXFJ5JeBQ2m9lxc=
Received: from webmail.tecnico.ulisboa.pt (webmail4.tecnico.ulisboa.pt [IPv6:2001:690:2100:1::8a3:363d]) (Authenticated sender: ist180970) by mail1.tecnico.ulisboa.pt (Postfix) with ESMTPSA id 756E136006E; Mon, 30 Nov 2020 22:21:55 +0000 (WET)
Received: from vs1.ist.utl.pt ([2001:690:2100:1::33]) by webmail.tecnico.ulisboa.pt with HTTP (HTTP/1.1 POST); Mon, 30 Nov 2020 22:21:55 +0000
MIME-Version: 1.0
Date: Mon, 30 Nov 2020 22:21:55 +0000
From: Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt>
To: Thomas Hardjono <hardjono@mit.edu>
Cc: Rafael Belchior <rafael.belchior=40tecnico.ulisboa.pt@dmarc.ietf.org>, blockchain-interop@ietf.org
In-Reply-To: <a40dc7708df646b385e5ebbdcab43781@oc11expo23.exchange.mit.edu>
References: <666e283e0d7a452fbf31dc7a42ec71b6@tecnico.ulisboa.pt>, <a1666b75233e112cd7d828ea4fa4fada@tecnico.ulisboa.pt> <a40dc7708df646b385e5ebbdcab43781@oc11expo23.exchange.mit.edu>
Message-ID: <a87a56a2e6e85666e32145d1c83e892e@tecnico.ulisboa.pt>
X-Sender: rafael.belchior@tecnico.ulisboa.pt
User-Agent: Roundcube Webmail/1.3.15
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/blockchain-interop/L_DeMr2OxwZZl6thrLW9sZITtxw>
Subject: Re: [Blockchain-interop] Gatweay Crash Recovery Discussion #1
X-BeenThere: blockchain-interop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Blockchain Gateway Interoperability Protocol <blockchain-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/blockchain-interop>, <mailto:blockchain-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/blockchain-interop/>
List-Post: <mailto:blockchain-interop@ietf.org>
List-Help: <mailto:blockchain-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/blockchain-interop>, <mailto:blockchain-interop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2020 22:22:05 -0000

Thomas,
Thanks for your questions.

Inline:

A 2020-11-30 21:31, Thomas Hardjono escreveu:
> Thanks Rafael,
> 
> This is a great start to begin to address the various aspect of the
> crash-recovery.
> 
> A couple of questions:
> 
> -- Which mode (self-healing mode, or primary-backup mode) do you
> recommend?  (Which one would be the simplest approach for now, and
> what assumptions would we need to make).

The self-healing mode is simpler, as the same machine eventually 
recovers, continuing its operations since the latest log entry. It does 
not require, in principle, to read from the log storage API. However, we 
are assuming it eventually recovers, and while this happens the system 
is down, prejudicing availability.


> 
> -- Could we assume that the gateway that recovers (i.e. recovers or
> takes-over) has authenticated access to the log-metadata file.
> 

That is correct. We assume the communication gateway-storage is done 
through a safe channel (e.g., TLS/HTTPS), and on top of this, we could 
have OAuth. We could encode the access control policies into the "access 
control profile" field of the log, or delegate such responsibility to 
the log storage API manager (as in, out of scope).

Hope this clarifies.
Cheers,
Rafael

> 
> 
> -- thomas --
> 
> 
> 
> ________________________________________
> From: Blockchain-interop [blockchain-interop-bounces@ietf.org] on
> behalf of Rafael Belchior
> [rafael.belchior=40tecnico.ulisboa.pt@dmarc.ietf.org]
> Sent: Monday, November 30, 2020 11:49 AM
> To: blockchain-interop@ietf.org
> Subject: [Blockchain-interop] Gatweay Crash Recovery Discussion #1
> 
> Dear All,
> Attached, the slides of the first discussion on the crash recovery
> mechanism for gateways, that took place during the last meeting.
> 
> 
> Cheers,
> 
> --
> Rafael Belchior
> Ph.D. student in Computer Science and Engineering, Blockchain - Técnico
> Lisboa
> https://rafaelapb.github.io/
> https://www.linkedin.com/in/rafaelpbelchior/

-- 
Rafael Belchior
Ph.D. student in Computer Science and Engineering, Blockchain - Técnico
Lisboa
https://rafaelapb.github.io/
https://www.linkedin.com/in/rafaelpbelchior/

v2.23.0 | Report a Bug | By Email