[core] Bockchain and IoT

Pascal Urien <pascal.urien@gmail.com> Tue, 17 July 2018 21:15 UTC

Return-Path: <pascal.urien@gmail.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB06130DEB; Tue, 17 Jul 2018 14:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6POHUksTVEQ; Tue, 17 Jul 2018 14:15:02 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98C27129C6B; Tue, 17 Jul 2018 14:15:01 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id p6-v6so2209404ljc.5; Tue, 17 Jul 2018 14:15:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=S1Ay7VHAREBtMaL9slmGhr2RB/zN+K1fPCO9OlRLWhM=; b=blhc0gJflfJ9Yaep0jCzrtruIUPR+LyOy8w6J5c0E9+q66jATOAcaxGSiGy8zJ/5kj cVizU4xZL88+qja3n2sJxtLSJ7mYbyj/NVwtq8VCA536hKt1InSKbd7hRJj839ZDyTxC LQSz7w4EYKiDFcHG1sglEieRY9iJXXiYlFikOGkLUo6nObVGD5+YqsQP5mof47bmvd5z NTT2hHldj66dskBkVGYHuIzfWrohivENEy3NyhX/idXU3L21ehIIYn8Rbok3wsB83c+C nbobBYR1NqMbqwwdmQ7ljAQO461kht2aIPiM3OAV88cmONq+yrq7PQ+Bls/hXRSXo+G2 mSLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=S1Ay7VHAREBtMaL9slmGhr2RB/zN+K1fPCO9OlRLWhM=; b=XUNIrFpE/Awq37/c3PAzw4IsPKEfXOPjwtFWU4UkLmG6gAJMwTGPeVGBvr5J/YQGCW 3Vsu1IzP3B8EZF9uMsE4l/5249/RKlOhqp+949EdVCFZdsL68uFHtplhUsMBzL2cPh0W U3tBTv2dWI3X2JlMFxYDNQ4KWLwZSpp/yQYzWLMtVkanS6BTbIiOHZjZsRNZZPYZJSGN BLusIJ44rhOv2fCG4oPIG2y3xreW0ybQNYEviXZMJQ67k5Q8EDu+jaDzv51F3hmHV7GL FLXfYZ1rYKDYY3psLbPxJRKE1nRLq37jmR1kJ1y2w3XfNmJqj3f8d7XADTLSikXdOQZf nASQ==
X-Gm-Message-State: AOUpUlF5XJ83we0+F5YIt4GndbL+5CI+n7TCtH41p6N3J4ijkHLUgT7u VKy5xHZNMx+k3PVkrug4aTgJiUUTkf0yI0Zs8yXBsBpf
X-Google-Smtp-Source: AAOMgpce/GsaACFL/lMv5xa3QnqocYmkUiFTrZPXavpSAyCCQ8Tpe00lYef551NcYd5YKh/A0iQ0F5iTmkZu0B9juWs=
X-Received: by 2002:a2e:2ac3:: with SMTP id q186-v6mr2454264ljq.123.1531862099580; Tue, 17 Jul 2018 14:14:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:2bce:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 14:14:59 -0700 (PDT)
From: Pascal Urien <pascal.urien@gmail.com>
Date: Tue, 17 Jul 2018 23:14:59 +0200
Message-ID: <CAEQGKXSP4nj_6aL5UnNDhJx9MGTHY4X4=MHMOhtbc=++X_1Jew@mail.gmail.com>
To: core <core@ietf.org>, core-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004a5c9e0571387077"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/VP6mT5ISmAdxQQo2RByizc9lrn0>
Subject: [core] Bockchain and IoT
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 21:15:06 -0000

The today paradigm of IoT is oriented towards cloud environments managed in
a way or another by a third trusted party.

One benefit of the blockchain technology is that there is no third trusted
party.

In the Blockchain IoT paradigm objects forward data in signed transactions,
what imply a relationship between a blockchain address and an object
(managing a private key).

The draft
https://www.ietf.org/id/draft-urien-core-blockchain-transaction-protocol-00.txt
 is a first tentative toward a “no third trusted party IoT architecture”

If some people are interested by this direction we can meet at the end of
the core session on Thursday ?

Draft  summary.

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.
Pascal Urien