Re: [6tisch-security] minimal security draft

Tero Kivinen <kivinen@iki.fi> Thu, 09 February 2017 13:15 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Message-ID: <22684.27510.499873.955382@fireball.acr.fi>
Date: Thu, 09 Feb 2017 15:15:34 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Mališa Vučinić <malisa.vucinic@inria.fr>
In-Reply-To: <6D6AE790-1234-403B-9429-992B4E168AF3@inria.fr>
References: <1f99708ffbacaa7235d05b535f669291@xs4all.nl> <6D6AE790-1234-403B-9429-992B4E168AF3@inria.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/fILxDbXy_MLyVDcIjj6pMloDR1s>
Cc: 6tisch Security <6tisch-security@ietf.org>, consultancy@vanderstok.org
Subject: Re: [6tisch-security] minimal security draft
Precedence: list

Mališa Vučinić writes:
> Hello Peter,
> 
> We use COSE Key Set structure to transport link-layer keys. Key set
> is a CBOR array, while each key in the array is specified as a CBOR
> map object. This is quite flexible and relies on the already
> standardized document (COSE). We then bundle Key Set object together
> with a short 15.4 address to create a response that fits within a
> single 15.4 frame. For more details refer to Section 4.4 of
> minimal-security draft. 

You would also need to have 802.15.4 specific key identification
information, i.e. the KeyIdMode, KeyIndex (if KeyIdMode is not 0) and
KeySource (if KeyIdMode is 2 or 3).
-- 
kivinen@iki.fi

[6tisch-security] minimal security draft peter van der Stok
Re: [6tisch-security] minimal security draft Mališa Vučinić
Re: [6tisch-security] minimal security draft Tero Kivinen
Re: [6tisch-security] minimal security draft Mališa Vučinić
Re: [6tisch-security] minimal security draft peter van der Stok
Re: [6tisch-security] minimal security draft Mališa Vučinić