[netconf] Virtual hum on the question of keygen

Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 08 May 2020 19:25 UTC

Return-Path: <mjethanandani@gmail.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 91AA43A0DF9 for <netconf@ietfa.amsl.com>; Fri, 8 May 2020 12:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 Y4IL13Nf5BFF for <netconf@ietfa.amsl.com>; Fri, 8 May 2020 12:25:15 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 60A9C3A0DFB for <netconf@ietf.org>; Fri, 8 May 2020 12:25:15 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id a21so2846675ljj.11 for <netconf@ietf.org>; Fri, 08 May 2020 12:25:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oGyiY+zZ7Vu603sBAkz1Ls3x094vTENVLy04FGB/iZ4=; b=mD2crQhak7P4pRg8Fz46IU8qdo5Bn6beR4I5dlUnCvzjSIYZhS5Qx7fVXSWmHdubCV F/FbgbavDTuQQKm/+HQ9ijyc8qM7wUQgGSHkp6YgeeORqALNVPO+/stAGzfiwzkCSafq nScSWYUQ6tVZvqKcmatzkm1QdNQjcVsINBb0XYejJYoJWPiqKuEyXkggHYC3nv0ZaSKo oGU3mom63OzjA1dmP5yNKSOFoTbxg1f8zteh4CTxHmlG/CMKYO9sd8cI/YOxrYu2RybN nLRNOe6QdxzJKLT9W665QOqAFZoIrJSztURxHVHI/dE8GNoOaSkVCphXKuFMiL3V/3Wd WevQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oGyiY+zZ7Vu603sBAkz1Ls3x094vTENVLy04FGB/iZ4=; b=LPYzekUnFa1YCp4cTyQRioeU3WTAJkUYOvoxdhCHSj+EulwYr5dPwByRlqBIfVbIhA vLH9mXyjncIpJagWUGQWikDW1ka3266k8pY2dWGPGsyxMaUvUTmiUQZNMbbvxPPRaHP0 m18iN8trSQ1yfeLigDE3Z5bVUsiZQTIiKA9SX8QYevINaxssgeDCFZvK0ekINWEh5Cyu gT68LTtJVODvI/ZzG6iH3XLw1BKntsdlorVX6NCYzsadKy2iCssu6IavU7aG5yY7556r DsJDRKG20/ccERRR6fUiBuuFya4W6BNSs9LhEaE5FT1ZIXgCJn7bjz6KN75ERO1OwoJH YWIQ==
X-Gm-Message-State: AOAM530kMxAZJEFdJYIDZf6cRk03SrmIEdSS3lSypqOca9E1edO0cQpJ LOfr/VQ+edkyrLXCV5hgLeit3ah0ZKf6ShuHBvVvfRuz2jg0QA==
X-Google-Smtp-Source: ABdhPJwHcc/bREyg2oGwLzZtF25f2q/iJqK3vhWpmzytHrIT9F0NUxQvcGcbY8TlmQlCjW8AiAtoojzGBGj64ZCs+ZQ=
X-Received: by 2002:a2e:8693:: with SMTP id l19mr2655788lji.63.1588965913323; Fri, 08 May 2020 12:25:13 -0700 (PDT)
MIME-Version: 1.0
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Date: Fri, 08 May 2020 12:25:02 -0700
Message-ID: <CAAchPMsbAahBh4REq8jtc_=0ct2VSQ=BA+vSTTKh0K09L0EEOQ@mail.gmail.com>
To: Netconf <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2ed1e05a527f4ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/x4uAXouT0iZV1cfQPh6BS5Q8Q4Y>
Subject: [netconf] Virtual hum on the question of keygen
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: Fri, 08 May 2020 19:25:18 -0000

[Sorry if this e-mail appears multiple times. I seem to be having issues
with Google's SMTP server]

This e-mail closes the virtual hum on the question of keygen as it relates
to draft-ietf-netconf-crypto-types.

The poll was a weighed average poll, with folks asked to order their
preferences. The overall results of the poll did not indicate a clear
consensus. The tie was between keeping keygen and support at SSH/TLS layer,
and not supporting keygen at this time, with the latter having a slight
preference. What was interesting about the poll was an overwhelming support
for not supporting keygen at this time as the first preference, with the
2nd option more evenly weighed between first and second preference.

As explained before not supporting keygen at this time does not preclude it
from being added later on. The WG has indicated a desire to get this work
done soon, which may be why the 3rd option may be carrying more support.

At this point with no clear consensus, I am going to make it authors
decision.

Thanks.

Mahesh Jethanandani (as co-chair)
mjethanandani@gmail.com