Re: [netconf] crypto-types and keystore comments

Kent Watsen <kent+ietf@watsen.net> Thu, 14 November 2019 15:41 UTC

Return-Path: <0100016e6a936a0d-47636ce9-345c-4009-8d74-9703905933aa-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 6795E120849 for <netconf@ietfa.amsl.com>; Thu, 14 Nov 2019 07:41:19 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyik_6_ZauB6 for <netconf@ietfa.amsl.com>; Thu, 14 Nov 2019 07:41:17 -0800 (PST)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF8EB120113 for <netconf@ietf.org>; Thu, 14 Nov 2019 07:41:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1573746076; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=HlhDfJCI9FHZg3zoylXx34arbpedxSALFXvIWsVL08Y=; b=j2aaDC4tGmuMgklcYnXQwtWvlftuLrt6Oq/fBE+EjND4F4bKVaelW7NKkGBlaCyL lNsaiY38bVNSfToPV9hSuAju6f6R9XXQ6faotBnjD4GrFUjpuNr4mMhbHMh2d0QOze5 uIV4/HtqnDJGlXKG0oE1nJlsaHL/G8eZVEYcy6io=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016e6a936a0d-47636ce9-345c-4009-8d74-9703905933aa-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8433317A-8DA1-470F-AAD4-F9401F8EE1E9"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 14 Nov 2019 15:41:16 +0000
In-Reply-To: <20191114.144738.728144006347516638.mbj@tail-f.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Martin Bjorklund <mbj@tail-f.com>
References: <0100016e69e99e3c-893fbfb4-3dc8-4725-b7ef-87bbf491dc2c-000000@email.amazonses.com> <20191114.140135.2027227966816173737.mbj@tail-f.com> <0100016e6a250215-e89c9f24-60d9-419d-bc24-221786cb6f85-000000@email.amazonses.com> <20191114.144738.728144006347516638.mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.11.14-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/bBZlMwsOCj1qH8_I6UGBCcc6SA0>
Subject: Re: [netconf] crypto-types and keystore comments
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, 14 Nov 2019 15:41:20 -0000

Hi Martin,

>> True.  But how can we define a way to get a list per instance?  Should
>> there be a "config false" list wherever the "algorithm" node appears
>> (i.e., put the list into the crypto-type groupings having the
>> algorithm node?)
> 
> I don't know, probably.  Do we really want that?  Probably not.

Per-instance may be too granular.   If thinking that said curations occur of protocol boundaries, then maybe have a config false list in ietf-ssh-common and ietf-tis-common?   Not perfect, as an application may use more than one SSH library or more than one TLS library, but it's much less likely.


> This is exaclty why I suggested earlier that we don't spend time
> trying to solve this problem at all now.  I'd rather not put in
> something that we know doesn't really work.

Wait, no, there is a very real issue here that cannot be ignored.  Or do you feel that we should give up entirely on trying to enable servers to proactively express what algorithms they support?



>>> Do you have a pointer to this?
>> 
>> There was an email from Juergen a few months back.
> 
> But that was based on a misunderstanding.  (or you mean something
> else)

Now I'm unsure what you're talking about, do you have a pointer to it?


Kent // contributor