[netconf] universal crypto algorithm registry - yet more delay?
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 22 July 2019 15:30 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 859E9120313 for <netconf@ietfa.amsl.com>; Mon, 22 Jul 2019 08:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 NQi_8V2aYRiX for <netconf@ietfa.amsl.com>; Mon, 22 Jul 2019 08:30:39 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4BF120297 for <netconf@ietf.org>; Mon, 22 Jul 2019 08:30:39 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 3A5B1830 for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:38 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.198]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id XgX94iCAG08r for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:38 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:38 +0200 (CEST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id 239DF2012C for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:38 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id v9ZX1fx5waTg for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:37 +0200 (CEST)
Received: from exchange.jacobs-university.de (sxchmb03.jacobs.jacobs-university.de [10.70.0.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "exchange.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by hermes.jacobs-university.de (Postfix) with ESMTPS id C6C1F20129 for <netconf@ietf.org>; Mon, 22 Jul 2019 17:30:37 +0200 (CEST)
Received: from anna.localdomain (10.50.218.117) by sxchmb03.jacobs.jacobs-university.de (10.70.0.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Mon, 22 Jul 2019 17:30:37 +0200
Received: by anna.localdomain (Postfix, from userid 501) id F09C62DC25D; Mon, 22 Jul 2019 17:30:36 +0200 (CEST)
Date: Mon, 22 Jul 2019 17:30:36 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: netconf@ietf.org
Message-ID: <20190722153036.qzltp6y5osod7idy@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: netconf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: NeoMutt/20180716
X-ClientProxiedBy: SXCHMB04.jacobs.jacobs-university.de (10.70.0.156) To sxchmb03.jacobs.jacobs-university.de (10.70.0.155)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IPzrlZ21OfV2MkSjAsfE7HGO54A>
Subject: [netconf] universal crypto algorithm registry - yet more delay?
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: Mon, 22 Jul 2019 15:30:47 -0000
Hi, I have listened to the WG discussions today and I am wondering whether NETCONF should really be defining a universal crypto algorithm registry. To me, this seems to be an activity that (if needed) should be done in the security area. My concern is not so much an organizational one but more about the time it takes to deliver the client and server configuration drafts. The first WG server configuration draft was posted on May 2014, more than 5 years ago (draft-ietf-netconf-server-model-00). I do appreciate Kent's efforts to generalize the solution every year but we also need to deliver something at some point in time that people can implement and use. It seems that creating a universal crypto algorithm registry may be yet another unknown we dive into. Can we not design what we have in such that we may in the future use such a universal crypto algorithm registry (but we do not have to create it and wait for it to be created)? Or is this universal crypto algorithm registry just a small short effort given the other open issues that are still being discussed? /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
- [netconf] universal crypto algorithm registry - y… Juergen Schoenwaelder
- Re: [netconf] universal crypto algorithm registry… Andy Bierman
- Re: [netconf] universal crypto algorithm registry… Balázs Lengyel