DLT Gateway Crash Recovery Mechanism
draft-belchior-gateway-recovery-00

Document Type Active Internet-Draft (individual)
Authors Rafael Belchior  , Miguel Correia  , Thomas Hardjono 
Last updated 2021-01-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                              R. Belchior
Internet-Draft                                                M. Correia
Intended status: Informational      INESC-ID, Instituto Superior Tecnico
Expires: July 16, 2021                                       T. Hardjono
                                                                     MIT
                                                        January 12, 2021

                  DLT Gateway Crash Recovery Mechanism
                   draft-belchior-gateway-recovery-00

Abstract

   This memo describes crash recovery mechanisms for the Open Digital
   Asset Protocol (ODAP).  The memo presents ODAP-2PC, a protocol
   assures that gateways running ODAP are crash fault-tolerant, meaning
   that the atomicity of asset transfers are assured even if gateways
   crash.  This protocol includes the description of the messaging and
   logging flows necessary for gateways to keep track of current state,
   the crash-recovery protocol, and a rollback mechanism.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 16, 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Belchior, et al.          Expires July 16, 2021                 [Page 1]
Internet-Draft           Gateway Crash Recovery             January 2021

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Gateway Crash Recovery  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Gateway Transfer Model  . . . . . . . . . . . . . . . . .   4
     3.2.  Crash Recovery Model  . . . . . . . . . . . . . . . . . .   6
     3.3.  Recovery Procedure  . . . . . . . . . . . . . . . . . . .   6
     3.4.  Log Storage . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Format of log entries . . . . . . . . . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   Gateway systems that perform virtual asset transfers among DLTs must
   possess a degree of resiliency and fault tolerance in the face of
   possible crashes.  A key component of crash recovery is maintaining
   logs that enable either the same or other backup gateways to resume
   partially completed transfers.  Another key component is an atomic
   commit protocol (ACP) that guarantees that the source and target DLTs
   are modified consistently (atomicity) and permanently (durability),
   e.g., that assets that are taken from the source DLT are persisted
   into the recipient DLT.

   This document proposes: (i) the parameters that a gateway must retain
   in the form of logs concerning message flows within asset transfers;
   (ii) a JSON-based format for logs related to asset transfers.

2.  Terminology

   There following are some terminology used in the current document:

   o  Gateway: The nodes of a DLT system that are functionally capable
      of handling an asset transfer with another DLT.  Gateway nodes
      implement the gateway-to-gateway asset transfer protocol.

   o  Primary Gateway: The node of a DLT system that has been selected
      or elected to act as a gateway in an asset transfer.

Belchior, et al.          Expires July 16, 2021                 [Page 2]
Internet-Draft           Gateway Crash Recovery             January 2021

   o  Backup Gateway: The node of a DLT system that has been selected or
Show full document text