Re: [netconf] Adoption-suitability for draft-kwatsen-netconf-sztp-csr

Russ Housley <housley@vigilsec.com> Sat, 08 August 2020 16:18 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4409B3A0929 for <netconf@ietfa.amsl.com>; Sat, 8 Aug 2020 09:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 2GBJHjLnb5Gt for <netconf@ietfa.amsl.com>; Sat, 8 Aug 2020 09:18:51 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E2C23A0912 for <netconf@ietf.org>; Sat, 8 Aug 2020 09:18:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 87489300B7D for <netconf@ietf.org>; Sat, 8 Aug 2020 12:18:48 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id UsOAnSRijqZH for <netconf@ietf.org>; Sat, 8 Aug 2020 12:18:46 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id D7A9C300AA4 for <netconf@ietf.org>; Sat, 8 Aug 2020 12:18:46 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4F4738BC-AF93-4824-9598-0170CC83D6D4"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Date: Sat, 8 Aug 2020 12:18:48 -0400
References: <01000173c0b4ee99-d5627c91-eac2-4ea9-ba1b-b86e37c5293a-000000@us-east-1.amazonses.com> <01000173cabb057c-4236d605-0617-411c-a237-cd60f7545b79-000000@email.amazonses.com>
To: "netconf@ietf.org" <netconf@ietf.org>
In-Reply-To: <01000173cabb057c-4236d605-0617-411c-a237-cd60f7545b79-000000@email.amazonses.com>
Message-Id: <802E95DD-AFD4-434F-B38C-E37A02242AAA@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/KKlGG28_P0om_mXmqp1vtQxpxtk>
Subject: Re: [netconf] Adoption-suitability for draft-kwatsen-netconf-sztp-csr
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Aug 2020 16:18:53 -0000

> 
> NETCONF WG,
> 
> Per the previous email sent moments ago, the chairs would like to solicit input on the following draft:
> 
>    Title: Conveying a CSR in an SZTP Bootstrapping Request
>    Link: https://tools.ietf.org/html/ <https://tools.ietf.org/html/>draft-kwatsen-netconf-sztp-csr
>    Abstract:
> 
>       This draft extends the "get-bootstrapping-data" RPC defined in
>       RFC 8572 to include an optional certificate signing request (CSR),
>       enabling a bootstrapping device to additionally obtain an identity
>       certificate (e.g., an LDevID, from IEEE 802.1AR) as part of the
>       "onboarding information" response provided in the RPC-reply.
> 
> 
> In particular, please discuss adoption-suitability as it regards to the following questions:
> 
>     1) is the problem important for the NETCONF WG to solve?

I believe that it is important to configure an LDevID certificate as part of the bootstrap, and authentication based on the IDevID seems like the most pragmatic way to do so.

>     2) is the draft a suitable basis for the work?

As a co-author I am biased; however, I think this is a good start at the work to be done.  I am aware of one implementation that is underway.

If adopted, I am willing to continue to work on the document as a co-author.

Russ