[6tisch-security] continuum of bootstrap solutions/requirements

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 12 December 2017 03:00 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 6tisch-security@ietfa.amsl.com
Delivered-To: 6tisch-security@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26451292D3; Mon, 11 Dec 2017 19:00:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 PyhCi-5zqMVF; Mon, 11 Dec 2017 19:00:18 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F62D128DF3; Mon, 11 Dec 2017 19:00:18 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 20CB620090; Mon, 11 Dec 2017 22:03:30 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 95EBF81AFF; Mon, 11 Dec 2017 22:00:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: 6tisch-security@ietf.org
CC: Benjamin Damm <bdamm@silverspringnet.com>, Kent Watsen <kwatsen@juniper.net>, Panos Kampanakis <pkampana@cisco.com>, Ari Keränen <ari.keranen@ericsson.com>, anima-chairs@ietf.org, max pritikin <pritikin@cisco.com>, Sandeep Kumar <sandeep.kumar@philips.com>, Eliot Lear <lear@cisco.com>, kathleen moriarty ietf <kathleen.moriarty.ietf@gmail.com>, =?utf-8?Q?G=C3=B6ran?= Selander <goran.selander@ericsson.com>
In-Reply-To: <11320.1513002565@obiwan.sandelman.ca>
References: <1636.1513000283@obiwan.sandelman.ca> <11320.1513002565@obiwan.sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 11 Dec 2017 22:00:16 -0500
Message-ID: <11784.1513047616@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/Hgoa1V4-Pcwhy1F56qziJ8gGlbs>
X-Mailman-Approved-At: Mon, 11 Dec 2017 23:53:12 -0800
Subject: [6tisch-security] continuum of bootstrap solutions/requirements
X-BeenThere: 6tisch-security@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Extended Design Team for 6TiSCH security architecture <6tisch-security.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch-security/>
List-Post: <mailto:6tisch-security@ietf.org>
List-Help: <mailto:6tisch-security-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Dec 2017 03:00:21 -0000

BACKGROUND:

The original diagram presented to the 6tisch security design team this morning:

https://bitbucket.org/6tisch/draft-richardson-6tisch-dtsecurity-secure-join/src/d61cbe958d37626fda9096084ec3906de46ea0fa/technology-components.svg?at=master&fileviewer=file-view-default

Revised diagram for discussion from discussion:

https://bitbucket.org/6tisch/draft-richardson-6tisch-dtsecurity-secure-join/src/092899562470eeecd5aaa72c60f0a6c474f28237/technology-components-v2.svg?at=master&fileviewer=file-view-default

and a copy at:
http://www.sandelman.ca/SSW/ietf/6tisch/technology-components-v2.svg

We have named the "yellow" portion as a new vertical, and called it:
   "Transition to constrained bootstrap"

I will add in RFCxxxx/I-D.ietf-xyz to the boxes later today.
Maybe a roadmap/applicability document for iot-dir might explain it all.

I have added to the left, the 6tisch minimal-security, and I also added to
the bottom the set of join proxy technologies that have been considered/defined.

KEY POINT:
    We would up with the constrained bootstrap voucher format as yet-another-new
    document.  Here is a strawman document which is extracted from the
    6tisch-zerotouch-join document.
    The SID tooling has come along a lot in the past two weeks, btw.

    https://datatracker.ietf.org/doc/draft-richardson-anima-ace-constrained-voucher/

    (It took two revisions to make the yang nits happy, but I'm still missing
    5.1.2 SID values section)

There is a belief that this should be considered as new work for ANIMA.


Peter van der Stok is going to report if/who/what/where the
yellow/"transition to constrained bootstrap" document might be written.
It could be that it gets written outside of the IETF.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-