Re: [netconf] Warren Kumari's No Objection on draft-ietf-netconf-crypto-types-29: (with COMMENT)

Kent Watsen <kent+ietf@watsen.net> Wed, 31 January 2024 20:58 UTC

Return-Path: <0100018d61510c81-676cf710-54cf-4685-8755-d9292fe8c678-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 81381C14F6A8; Wed, 31 Jan 2024 12:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 E9Z84CKNj91G; Wed, 31 Jan 2024 12:58:39 -0800 (PST)
Received: from a48-93.smtp-out.amazonses.com (a48-93.smtp-out.amazonses.com [54.240.48.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 306D5C14E515; Wed, 31 Jan 2024 12:58:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1706734718; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=3sbAWdBgggSqv/OpgsFE8SOYBbJdFRahVyGCK+iHcmk=; b=jkjU0Aa208kHKClWoreN6bCOO4oE6B5AiyrvErK4kHx5AoEG/OpJW0Mmsw0WPZYK mhbhO3OXa/vr8yLXHtUsW4ERa0EBZxEb/687d8sCRG671AvXrukzR79MPxWsDnHhHaI Enf2TLhndVKJ6ur9FIn3UMIQBC/BG5p3Sg9Kgsoc=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <170666063080.28855.16608655355568650650@ietfa.amsl.com>
Date: Wed, 31 Jan 2024 20:58:38 +0000
Cc: The IESG <iesg@ietf.org>, draft-ietf-netconf-crypto-types@ietf.org, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <0100018d61510c81-676cf710-54cf-4685-8755-d9292fe8c678-000000@email.amazonses.com>
References: <170666063080.28855.16608655355568650650@ietfa.amsl.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3731.600.7)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.01.31-54.240.48.93
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/yN0BYLJ5l5ldJbVPp6zqciWJI6A>
Subject: Re: [netconf] Warren Kumari's No Objection on draft-ietf-netconf-crypto-types-29: (with COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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, 31 Jan 2024 20:58:43 -0000

Hi Warren,

Thank you for your valuable comments.
Please find responses below.

Kent


> On Jan 30, 2024, at 7:23 PM, Warren Kumari via Datatracker <noreply@ietf.org> wrote:
> 
> Warren Kumari has entered the following ballot position for
> draft-ietf-netconf-crypto-types-29: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-crypto-types/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I couldn't really decide between No Objection and Discuss. I ended up deciding
> on No Obj.

:laugh:


> I'm **assuming** that the "hidden" is conceptually similar to a write-only
> variable (or like some device vendors who elide the password/keys/similar in
> their equivalent of 'show config'), but it's really really unclear -- this
> section could do with some more words to explain this…

I made this update per another review’s comment, does it address your concern?
If not, can you please point to which section could do with some more words?


OLD
-            "A hidden key.  How such keys are created is outside
-             the scope of this module.";

NEW
+            "A hidden key.  It is of type 'empty' as its value is
+             inaccessible via management interfaces.  Though hidden
+             to users, such keys are not hidden to the server and
+             may be referenced by configuration to indicate which
+             key a server should use for a cryptographic operation.
+             How such keys are created is outside the scope of this
+             module.";




Thanks again!
Kent