Allied and private blockchain as detnet use case
draft-blockchain-as-detnet-use-case-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel Huang | ||
| Last updated | 2017-12-30 (Latest revision 2017-06-28) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
This draft brings blockchain into the detnet use case list. Generally speaking, blockchain is both a technical term and a blockchain-based industry, which is spreading into a wide range of industries other than the thriving bitcoin. Blockchain would have to require the supporting network offer deterministic networking service rather than the ongoing best-effort, because of its inherent p2p and frequent multicast working mechanism. Blockchain working process, its current network mechanism and challenges ahead, as well as requirements to detnet will be illustrated in the draft.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)