Gateway Identification and Discovery for Decentralized Ledger Networks
draft-chen-dlt-gateway-identification-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Shiping Chen , Thomas Hardjono | ||
| Last updated | 2021-12-09 (Latest revision 2021-06-07) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Today there is a growth in the number of blockchain and decentralized ledger networks (DLN) around the world, and interoperability across different networks represents a challenge for the value proposition of these networks. One approach for blockchain interoperability to be achieved is to employ gateways that permit assets to flow across the relevant networks of blockchains. However, a core requirement for interoperability is the correct identification of computer systems that act as gateways and the correct validation of the ownership of the gateway. A secondary requirement is for a gateway to inquire as to the existence of an entity address (public key) within a given decentralized ledger network. This memo discusses options with regards gateway identification and verification strategies. It looks at addressing the problem from the application layer and from the network layer. It also discusses other options, such as relying on a third-party blockchain-registered identifiers and resolver services
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)