Re: [netconf] universal crypto algorithm registry - yet more delay?

Andy Bierman <andy@yumaworks.com> Mon, 22 July 2019 20:05 UTC

Return-Path: <andy@yumaworks.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 E4B1A12008C for <netconf@ietfa.amsl.com>; Mon, 22 Jul 2019 13:05:34 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
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 bnJr3t91iFeN for <netconf@ietfa.amsl.com>; Mon, 22 Jul 2019 13:05:32 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F85412008F for <netconf@ietf.org>; Mon, 22 Jul 2019 13:05:32 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id d24so38787751ljg.8 for <netconf@ietf.org>; Mon, 22 Jul 2019 13:05:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=TNuBL+tSOtFwEdPNuGaewgqFmf5BB+qB5H0fLnmA5OQ=; b=xyDI/AjQnczf8x4DCPczxv905XTtbFOc/8KrfE7SaNPujEvr3wwIVmeLC8MzMDwe4r 2BAMc7UPsGoTWVIxE6fL11kaizkpj0J1Wd2cjYs9ZF6bL52rRqnQKZwBsHy7X0OSrX4Z q+yDfOe84LwLR1M5wyw9Z9WwlY3kSxImjOMXXNKERTeFyhv1R8uSpsfInoHpVq5d458q jN+TCvhWiUEbo2RqR/kk1Sh7vVdeSBT/X6klE5gnCQCaPxTXkTj9m838paKKdKg/t4rp tj9u84Rmo70jZAjpMVx7njuUHgLVpjqJl4GbVQ0sdYB3j4R9oMZWYV983FhVX+W5zYUe JaGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=TNuBL+tSOtFwEdPNuGaewgqFmf5BB+qB5H0fLnmA5OQ=; b=XQIHiFFnDNNhA0qwYQTddtIIU8PqEa2kBfdQDxuZI7L4kbXkFGgqlOR/yD11UBwjvl 7HJhApCk4DD3WemhmRxP4QAKAMEwTLdxxXz7nbtPEJiwidnc7u7p5VnXtIy69DNOA0ut ykcJletk20EtfPweA8Zm+E9++QlHiRA0Ark5fIw5DMC/uctzYXyXVYWLW40omhmMa2G7 boOcX3RQ8fqeKyMQdQV3m5RRiqhahyFREUCgWxDFsu3DwnTmJD9DwmLohp5NUpes+D9Q kDTib0yMERZMe7MIwqCDm9GeT6dLtFZ1EZlRHWz0VAG/OscFmvRHs5NN57nKcPtJDm9z i32g==
X-Gm-Message-State: APjAAAWwsIE4SCxZDDot4DMV17+Gywr1smSopyoWxviOOo6JpeiEgRAl IYn6fAVmC8woesXsf+fuSHoHg7jWqA6G7ZYQoI+xxg==
X-Google-Smtp-Source: APXvYqwAMYi+1ZVck7VEV/EPZNjgnQu+DFReia5CERi+9zfz0Oa1rB1PeyrcYQTpjmXQUIOVP8dmEa47KV2RyTma+IM=
X-Received: by 2002:a2e:b0ea:: with SMTP id h10mr31153646ljl.50.1563825930229; Mon, 22 Jul 2019 13:05:30 -0700 (PDT)
MIME-Version: 1.0
References: <20190722153036.qzltp6y5osod7idy@anna.jacobs.jacobs-university.de>
In-Reply-To: <20190722153036.qzltp6y5osod7idy@anna.jacobs.jacobs-university.de>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 22 Jul 2019 13:05:18 -0700
Message-ID: <CABCOCHQgU3Lk+Lz5WrYKdR2L4cHBVMs4dfkNRyvF-hz+0FW7nQ@mail.gmail.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000fef86058e4a9901"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/OTqiCm5mRR88c4bjH0ENOgwEfCc>
Subject: Re: [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 20:05:35 -0000

On Mon, Jul 22, 2019 at 8:30 AM Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> 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?
>
>

+1 to 'no more delays'.
These drafts have been very unstable and seeing the slide that showed 1 of
4 parts done
and 3 of 4 that need to be done over suggests this is not going to change
any time soon.



> /js
>
>
Andy



> --
> 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 mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>