Re: [netconf] I-D Action: draft-ietf-netconf-crypto-types-23.txt

Kent Watsen <kent+ietf@watsen.net> Wed, 25 May 2022 17:19 UTC

Return-Path: <01000180fc3b0d6b-c249c60e-eadb-4e4e-8500-a9321242efd8-000000@amazonses.watsen.net>
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 51B96C2B62E1 for <netconf@ietfa.amsl.com>; Wed, 25 May 2022 10:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tDYhms0eJRN for <netconf@ietfa.amsl.com>; Wed, 25 May 2022 10:19:31 -0700 (PDT)
Received: from a48-94.smtp-out.amazonses.com (a48-94.smtp-out.amazonses.com [54.240.48.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B87EDC1D5ACF for <netconf@ietf.org>; Wed, 25 May 2022 10:19:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1653499170; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=IyYheHBnuvQ07EZrPH3Xbap/Kd1IKqkVy6p86Harwo0=; b=Kcy5Q1medG7l4DVqHiFINiqMlSeXJy5sQfebA8DE8+i7z3pbZVbtihm8M9lgmVWm AZTGSFpBnOqr61NqWlZks6f7fUEnjEG9xRhk7Cfq6hs+ZxCQ/Shjg+78HicxlnZjCKV AU2AY5RfO0ZnEjhZiz0s6D1X3kUZIO6SBNwUOKS0=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <01000180fc3b0d6b-c249c60e-eadb-4e4e-8500-a9321242efd8-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_502F6999-161D-4BD8-A35F-16024C1DFCBE"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Wed, 25 May 2022 17:19:30 +0000
In-Reply-To: <GV2PR10MB621090331EDB0C6E5BE4761FFED69@GV2PR10MB6210.EURPRD10.PROD.OUTLOOK.COM>
Cc: "netconf@ietf.org" <netconf@ietf.org>, Russ Housley <housley@vigilsec.com>, Sean Turner <sean@sn3rd.com>
To: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
References: <165344424906.49053.17666786351914063450@ietfa.amsl.com> <GV2PR10MB621090331EDB0C6E5BE4761FFED69@GV2PR10MB6210.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2022.05.25-54.240.48.94
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/irsL9yhLE1k2PJLjDNbQF6_d53g>
Subject: Re: [netconf] I-D Action: draft-ietf-netconf-crypto-types-23.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.34
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: Wed, 25 May 2022 17:19:32 -0000

Hi Hendrik,

The requests to add support for CMP and CMC were made to the sztp-csr draft, so no cascading opportunity in crypto-types was searched for, including any possible opportunity to more aggressively refactor parts to crypto-types.

The sztp-csr ship has sailed, but I'm not opposed to adding CMP/CMC support to crypto-types, especially if you  can help out.  Roughly, we'd want to map the following sztp-csr groupings to crypto-types's YANG as follows:

  SZTP-CSR Grouping  |  ietf-crypto-types
---------------------+-----------------------
csr-support-grouping |  feature statements
csr-request-grouping |  "input" parameters
csr-grouping         |  "output" parameters

Kent // author of both drafts


> On May 25, 2022, at 3:57 AM, Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote:
> 
> Kent
> 
> There is the grouping grouping generate-csr-grouping for certificate signing requests defined in this document offering usage of PKCS#10 format.
> This topic is also addressed by draft-ietf-netconf-sztp-csr with the grouping csr-support-grouping offering PKCS#10, CMP and CMC request formats.
> Is there a reason for the overlap and for not just reusing what is defined in draft-ietf-netconf-sztp-csr regarding CSRs also in draft-ietf-netconf-crypto-types?
> 
> Hendrik
> 
>> Von: netconf <netconf-bounces@ietf.org> Im Auftrag von internet-
>> drafts@ietf.org
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Network Configuration WG of the IETF.
>> 
>>        Title           : YANG Data Types and Groupings for Cryptography
>>        Author          : Kent Watsen
>> 	Filename        : draft-ietf-netconf-crypto-types-23.txt
>> 	Pages           : 63
>> 	Date            : 2022-05-24
>> 
>> Abstract:
>>   This document presents a YANG 1.1 (RFC 7950) module defining
>>   identities, typedefs, and groupings useful to cryptographic
>>   applications.
>>