[6tisch] Extending CoJP (minimal-security) for non-6TiSCH 802.15.4 networks

Christian Amsüss <christian@amsuess.com> Sun, 19 September 2021 11:10 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 377103A270D for <6tisch@ietfa.amsl.com>; Sun, 19 Sep 2021 04:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fE3dDkN_SxaB for <6tisch@ietfa.amsl.com>; Sun, 19 Sep 2021 04:10:19 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73A983A2709 for <6tisch@ietf.org>; Sun, 19 Sep 2021 04:10:17 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 83101400AD for <6tisch@ietf.org>; Sun, 19 Sep 2021 13:10:13 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 7AC51D7 for <6tisch@ietf.org>; Sun, 19 Sep 2021 13:10:10 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:f708:e761:e419:63b]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 132FB10A for <6tisch@ietf.org>; Sun, 19 Sep 2021 13:10:10 +0200 (CEST)
Received: (nullmailer pid 65863 invoked by uid 1000); Sun, 19 Sep 2021 11:10:09 -0000
Date: Sun, 19 Sep 2021 13:10:09 +0200
From: Christian Amsüss <christian@amsuess.com>
To: 6tisch@ietf.org
Message-ID: <YUcakTFqibo5wEfe@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="7nO8hN1YpPU2pACl"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/-WtZmLZGeP3x3FsrtDyWWF8ep3o>
Subject: [6tisch] Extending CoJP (minimal-security) for non-6TiSCH 802.15.4 networks
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Sep 2021 11:10:25 -0000

Hello 6TiSCH group,

have the discussions in the development of CoJP ever sidetracked to its
applicability for non-TSCH setups?

Sure, there would be differences: The joined devices would need to keep
track of time in some way on their own (possibly less precise than for
ASNs; a confident upper bound suffices), and someone (the JRC?) would
need to confidently keep some absolute time of the key. But in total, my
gut feeling would be that one or two new values to the CoJP Parameters
registry could suffice to make CoJP usable for DSME, NBE or BE (CAP /
CSMA/CA) modes.

Doing these extensions is clearly out of scope of 6TiSCH, but pointers
to any previous discussion or evaluation, or opitions on the feasability
of such an undertaking would probably best be obtained from here.

Thanks in advance

Yesterday is history, tomorrow is a mystery, and today is a gift. That
is why it is called the present.
  -- ancient saying