IETF Logo Mail Archive

Re: [6tisch] Updates to minimal-security-06

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 22 March 2018 17:39 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3332D126C0F for <6tisch@ietfa.amsl.com>; Thu, 22 Mar 2018 10:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 3zXHaiAdIxaZ for <6tisch@ietfa.amsl.com>; Thu, 22 Mar 2018 10:39:19 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74202126579 for <6tisch@ietf.org>; Thu, 22 Mar 2018 10:39:19 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 554021F95D; Thu, 22 Mar 2018 17:39:18 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 31D98E73; Thu, 22 Mar 2018 17:39:17 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "6tisch@ietf.org" <6tisch@ietf.org>, "c.amsuess@energyharvesting.at" <c.amsuess@energyharvesting.at>
In-reply-to: <CANDGjydb27-u3r2vG5M6-mWj1fmin52Uq5qPu0d5n2OQsJQVyw@mail.gmail.com>
References: <CANDGjydb27-u3r2vG5M6-mWj1fmin52Uq5qPu0d5n2OQsJQVyw@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?TWFsacWhYSBWdcSNaW5pxIc=?= <malisa.vucinic@inria.fr> message dated "Thu, 22 Mar 2018 16:56:32 +0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Thu, 22 Mar 2018 17:39:17 +0000
Message-ID: <31648.1521740357@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/KxFMVqyVGELZdsDFG6avpELxKCE>
Subject: Re: [6tisch] Updates to minimal-security-06
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 22 Mar 2018 17:39:21 -0000

Mališa Vučinić <malisa.vucinic@inria.fr> wrote:
    > in the network. Other than adding the Observe option, together with the
    > new link-layer key we also need to carry the ASN at which this key is
    > scheduled to be rolled out. What COSE parameter the ASN will be

I disagree with this method.

I think that the mechanism that was explained at:
  https://tools.ietf.org/html/draft-richardson-6tisch-minimal-rekey-02#section-4

is a better workable solution.  Deploy all the new keys (it may take some
days on sleep networks), and then have nodes switch when they see traffic
with the new key.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email