Open Digital Asset Protocol
draft-hargreaves-odap-00

Document Type Active Internet-Draft (individual)
Authors Martin Hargreaves  , Thomas Hardjono 
Last updated 2020-10-09
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                            M. Hargreaves
Internet-Draft                                             Quant Network
Intended status: Informational                               T. Hardjono
Expires: April 13, 2021                                              MIT
                                                        October 10, 2020

                      Open Digital Asset Protocol
                        draft-hargreaves-odap-00

Abstract

   This memo describes the Open Digital Asset Protocol (ODAP).  ODAP is
   intended for describing assets held on distributed ledgers in an open
   and interoperable format, session negotiation and message passing
   between gateways connecting disparate blockchain systems.

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 April 13, 2021.

Copyright Notice

   Copyright (c) 2020 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
   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.

Hargreaves & Hardjono    Expires April 13, 2021                 [Page 1]
Internet-Draft                    ODAP                      October 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Open Digital Asset Protocol . . . . . . . . . . . . . . .   3
   2.  Conventions used in this document . . . . . . . . . . . . . .   4
   3.  ODAP: Elements of the proposal  . . . . . . . . . . . . . . .   4
     3.1.  ODAP Message Flow Context . . . . . . . . . . . . . . . .   4
     3.2.  ODAP Message Format . . . . . . . . . . . . . . . . . . .   4
     3.3.  Digital Asset Resource Descriptors  . . . . . . . . . . .   5
       3.3.1.  Organisation Identifier . . . . . . . . . . . . . . .   5
       3.3.2.  DLT Gateway / Endpoint ID . . . . . . . . . . . . . .   5
       3.3.3.  DLT Identifier  . . . . . . . . . . . . . . . . . . .   5
       3.3.4.  Resource  . . . . . . . . . . . . . . . . . . . . . .   6
       3.3.5.  Examples  . . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Digital Asset Resource Client Descriptors . . . . . . . .   6
       3.4.1.  Organization Identifier . . . . . . . . . . . . . . .   6
       3.4.2.  DLT Gateway / Endpoint ID . . . . . . . . . . . . . .   6
       3.4.3.  Organizational Unit . . . . . . . . . . . . . . . . .   7
       3.4.4.  Name  . . . . . . . . . . . . . . . . . . . . . . . .   7
       3.4.5.  Examples  . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Gateway Level Access Control  . . . . . . . . . . . . . .   7
     3.6.  Negotiation of Security Protocols and Parameters  . . . .   8
       3.6.1.  TLS Established . . . . . . . . . . . . . . . . . . .   8
       3.6.2.  Client offers supported credential schemes  . . . . .   8
       3.6.3.  Server selects supported credential scheme  . . . . .   8
       3.6.4.  Client asserts of proves identity . . . . . . . . . .   8
       3.6.5.  Sequence numbers initialized  . . . . . . . . . . . .   8
       3.6.6.  Messages can now be exchanged . . . . . . . . . . . .   9
     3.7.  Digital Asset Resource Discovery  . . . . . . . . . . . .   9
       3.7.1.  Format  . . . . . . . . . . . . . . . . . . . . . . .   9
     3.8.  Accessing Resources via a DLT Gateway . . . . . . . . . .   9
       3.8.1.  Backward Compatibility  . . . . . . . . . . . . . . .   9
   4.  Security Consideration  . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Consideration  . . . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   There is a lack of interoperability between individual blockchains,
Show full document text