Re: [Blockchain-interop] Charter discussion

[Michael McBride <[e-mail]>]

Hi Thomas,

The charter is specific to DLT I assume to limit scope. A broader scope would be more compelling, but I get how ietf works.

We could, alternatively, specify that the gateway api's provide interoperability between the resources any of the major database platforms, ie. interoperability between assets in Oracle or MySQL or blockchain using odap. And have DLT interoperability as the first use case. DDGP (Distributed Database Gateway Protocol) WG or something like that. But since we are limiting this to DLT we should perhaps call out the unique characteristics of DLT's in the charter. And mention what we mean by DLTs, ie blockchains vs tangles vs other DLT's. Looks like we are only focusing on Blockchain DLT and that should be clear.

And it could be a bit confusing having a charter titled DLT gateway protocol while having DLT's listed out of scope. Perhaps saying "modifications to the existing Blockchain machinery" is out of scope would help.

Thanks,
mike

-----Original Message-----
From: Blockchain-interop <[e-mail]> On Behalf Of Thomas Hardjono
Sent: Wednesday, January 6, 2021 6:39 AM
To: [e-mail]
Cc: Thomas Hardjono <[e-mail]>; Ned Smith ([e-mail]) <[e-mail]>; Martin Hargreaves <[e-mail]>
Subject: [Blockchain-interop] Charter discussion


Folks,

It would be great if we could start a Charter discussion so that we can have a draft charter going into IETF110 in the first week of March.

Below is a draft text that is basically taken from our slides at the previous IETF109 SecDispatch.

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2F109%2Fmaterials%2Fslides-109-secdispatch-draft-hardjono-blockchain-interop-arch-00&amp;data=04%7C01%7Cmichael.mcbride%40futurewei.com%7Ccb789b650f5841231ad208d8b250f67e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637455408106754663%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8a2%2FrrBq5t%2Fc34TpJ7Sh8m3bY2%2FdNywuhUgpIZuUnbA%3D&amp;reserved=0

The charter needs to be tight enough that we can deliver within time (e.g. deliver the 3 drafts by end of 2021).

Looking for your inputs.

---------------------------

Proposed name:  DLT Gateway Protocol (DGP)

The goal of DGP is to develop a gateway-to-gateway protocol for virtual asset transfers between distributed ledger technology (DLT) systems.

The gateway protocol must support the unidirectional secure transfer of  the digital representation of an asset between two gateways fronting DLTs, satisfying requirements of atomicity and non-repudiation, and agnostic to the higher-layer economic value of the asset. It must support cases where one or both DLT systems behind the gateways are private (where the interior resources are not externally accessible). Additionally, APIs defined must support cases where one gateway is fronting a Legacy system.

The gateway protocol must satisfy the well-known ACID properties. Atomicity: a transfer must either commit or entirely fail (failure means no change to asset ownership). Consistency: a transfer (commit or fail) must always result in the asset located in one DLT only. Isolation: while a transfer is occurring, the asset ownership cannot be modified (no double-spend). Durability: once a transfer is committed, it must remain so regardless of subsequent gateway crashes.

The gateway protocol will be based on the classic 2-Phase Commit (2PC or 3PC) design.  The interaction channel between the APIs endpoints at the gateways is assumed to be protected using TLS1.2 (TLS1.3).

Proposed Deliverables (2021):
-- Architecture document	
-- Gateway protocol document defining APIs and endpoint definitions (ODAP)
-- Use-cases & Requirements document

Optional:
-- Asset Profile JSON specification
-- Log-metadata JSON specification (crash recovery)

Existing drafts:
-- draft-hardjono-blockchain-interop-arch-01 
-- draft-hargreaves-odap-01 
-- draft-sardon-blockchain-gateways-usecases-00
-- draft-sardon-blockchain-interop-asset-profile-00


Out of scope:
-- Blockchains and DLT systems
-- Consensus & BFT protocols, PoW, PoS, etc.
-- Cryptocurrencies, tokenization, etc.
-- Incentive mechanisms, economic models; etc.
-- Zero-knowledge proof (ZKP) protocols
-- Authentication & Authorization protocols
-- Concurrency control algorithms
-- Identity management & privacy, etc. etc.


---------------------------


Best


-- thomas --


-- 
Blockchain-interop mailing list
[e-mail]
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fblockchain-interop&amp;data=04%7C01%7Cmichael.mcbride%40futurewei.com%7Ccb789b650f5841231ad208d8b250f67e%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637455408106754663%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=rGn98%2FTW%2BOFS%2FvnaSXMnMXocowkuLlst24L5Jv8Is1o%3D&amp;reserved=0