IETF Logo Mail Archive

Re: [Anima] [Iot-onboarding] Device Certificate Deployment Automation with ACME using BRSKI

Michael Richardson <mcr@sandelman.ca> Tue, 06 August 2019 15:53 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EFD1203C4; Tue, 6 Aug 2019 08:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 v7Zd4KgAOqWs; Tue, 6 Aug 2019 08:52:59 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967FA12037B; Tue, 6 Aug 2019 08:52:59 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id AAC013818C; Tue, 6 Aug 2019 11:52:21 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D1DBF70D; Tue, 6 Aug 2019 11:52:56 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Kent Watsen <kent+ietf@watsen.net>
cc: "Owen Friel (ofriel)" <ofriel@cisco.com>, "iot-onboarding@ietf.org" <iot-onboarding@ietf.org>, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, "anima@ietf.org" <anima@ietf.org>
In-Reply-To: <0100016c6772e4e8-8ce5598b-2c2a-488e-b7c2-414d9003e46b-000000@email.amazonses.com>
References: <CAGL6epJRmAvDB4=M6RiQaC93wvy1XDgcbhOmuKUtqmEhBWC72w@mail.gmail.com> <DM6PR11MB3385FD834E826E25160B53AADBD50@DM6PR11MB3385.namprd11.prod.outlook.com> <DM6PR11MB33851A9026943624FC5BD478DBD50@DM6PR11MB3385.namprd11.prod.outlook.com> <0100016c6772e4e8-8ce5598b-2c2a-488e-b7c2-414d9003e46b-000000@email.amazonses.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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: text/plain; charset="us-ascii"
Content-ID: <16868.1565106776.1@localhost>
Date: Tue, 06 Aug 2019 11:52:56 -0400
Message-ID: <16869.1565106776@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/fesxsPBriZ4nt9IsWZht3zuRawo>
Subject: Re: [Anima] [Iot-onboarding] Device Certificate Deployment Automation with ACME using BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2019 15:53:11 -0000

Kent Watsen <kent+ietf@watsen.net> wrote:
    > Skimming quickly, I see now the direction to go to a cloud registrar to
    > be redirected to a local registrar.  I feel compelled to point out that
    > this is exactly what SZTP (RFC 8572) does, or at least, supports.
    > Actually, as a more general statement, it was originally said that the
    > two WG's approaches were different, but they are now becoming more and
    > more alike.  Well, since SZTP is published already, it's more like the
    > ANIMA approach is becoming more like SZTP, albeit seemingly with more
    > complexity.

Yes, I had hoped to push towards this view.

    > Regarding ACME integration during bootstrap, I think the basic desire
    > is to configure a device to obtain a certificate via ACME,
    > configuration which so happens to be provided at the time of the
    > bootstrap event, but could also happen at anytime thereafter.  Support
    > for such configuration should be added to
    > https://tools.ietf.org/html/draft-ietf-netconf-keystore

agreed.

v2.23.0 | Report a Bug | By Email