Re: [netconf] Roman Danyliw's No Objection on draft-ietf-netconf-sztp-csr-12: (with COMMENT)
Russ Housley <housley@vigilsec.com> Thu, 16 December 2021 14:50 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 EF41F3A0FCC for <netconf@ietfa.amsl.com>; Thu, 16 Dec 2021 06:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 klNIvVNHpdUp for <netconf@ietfa.amsl.com>; Thu, 16 Dec 2021 06:50:24 -0800 (PST)
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 6016F3A0FCA for <netconf@ietf.org>; Thu, 16 Dec 2021 06:50:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BB4B9300C52 for <netconf@ietf.org>; Thu, 16 Dec 2021 09:50:26 -0500 (EST)
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 fibJkU6oTrCa for <netconf@ietf.org>; Thu, 16 Dec 2021 09:50:25 -0500 (EST)
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 B7559300BE8; Thu, 16 Dec 2021 09:50:24 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <163961310503.29838.2930717052258225050@ietfa.amsl.com>
Date: Thu, 16 Dec 2021 09:50:20 -0500
Cc: IESG <iesg@ietf.org>, draft-ietf-netconf-sztp-csr@ietf.org, netconf-chairs@ietf.org, netconf@ietf.org, mjethanandani@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <B752721B-E1AB-4596-A13A-90D981C118EA@vigilsec.com>
References: <163961310503.29838.2930717052258225050@ietfa.amsl.com>
To: "Roman D. Danyliw" <rdd@cert.org>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/qm5_5w5O1BRXy_cG0hgJzXIW9tA>
Subject: Re: [netconf] Roman Danyliw's No Objection on draft-ietf-netconf-sztp-csr-12: (with COMMENT)
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: Thu, 16 Dec 2021 14:50:28 -0000
> ** Section 4.1.1. > > For instance, an NMS controller/orchestrator > application could periodically prompt the SZTP-client to generate a > new private key and provide a certificate signing request (CSR) or, > alternatively, push both the key and an identity certificate to the > SZTP-client using > > I don’t have a sense of the classes of endpoints that would rely on SZTP. > Would it include highly constrained or battery powered devices for which this > re-keying would be too expensive? Sure. Perhaps we should say that devices with the power and computation resources should periodically generate fresh keying material. Russ
- [netconf] Roman Danyliw's No Objection on draft-i… Roman Danyliw via Datatracker
- Re: [netconf] Roman Danyliw's No Objection on dra… Russ Housley
- Re: [netconf] Roman Danyliw's No Objection on dra… Kent Watsen