Blockchain Transaction Protocol for Constraint Nodes
draft-urien-core-blockchain-transaction-protocol-05
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Pascal Urien
|
|
Last updated |
|
2020-12-15
|
|
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)
|
CORE Working Group P. Urien
Internet Draft Telecom Paris
Intended status: Experimental
December 15 2020
Expires: June 2021
Blockchain Transaction Protocol for Constraint Nodes
draft-urien-core-blockchain-transaction-protocol-05.txt
Abstract
The goal of the blockchain transaction protocol for constraint nodes
is to enable the generation of blockchain transactions by constraint
nodes, according to the following principles:
- transactions are triggered by Provisioning-Messages that include
the needed blockchain parameters.
- binary encoded transactions are returned in Transaction-Messages,
which include sensors/actuators data. Constraint nodes, associated
with blockchain addresses, compute the transaction signature.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
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 http://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 June 2021.
.
Urien Expires June 2021 [Page 1]
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
(http://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.
Urien Expires June 2021 [page 2]
Blockchain Transaction Protocol for Constraint Nodes December 2020
Table of Contents
Abstract........................................................... 1
Requirements Language.............................................. 1
Status of this Memo................................................ 1
Copyright Notice................................................... 2
1 Overview......................................................... 4
2 Overview of the Blockchain Transaction Protocol for Constraint
Nodes.............................................................. 4
2.1 Architecture................................................ 4
2.2 An Ethereum Use Case........................................ 5
3 Blockchain Transaction Protocol Messages Definition.............. 6
3.1 Provisioning Message........................................ 6
3.1.1 Encoding example in JSON syntax ...................... 6
3.2 Transaction Message......................................... 6
3.2.1 Encoding example in JSON syntax ...................... 6
4. Blockchain Transaction Protocol Messages Binary Encoding........ 7
4.1 CoAP messages............................................... 7
4.2 HTTP Messages............................................... 7
5 IANA Considerations.............................................. 7
6 Security Considerations.......................................... 7
6 References....................................................... 7
6.1 Normative References........................................ 7
6.2 Informative References...................................... 7
7 Authors' Addresses............................................... 7
Urien Expires June 2021 [Page 3]
Show full document text