Re: [netconf] updates to client/server suite of drafts

Kent Watsen <kent+ietf@watsen.net> Thu, 21 November 2019 17:00 UTC

Return-Path: <0100016e8ee89f30-bf2de747-ca32-4ccf-8922-cd8ee910a58f-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 ECBF9120CB5 for <netconf@ietfa.amsl.com>; Thu, 21 Nov 2019 09:00:45 -0800 (PST)
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, RCVD_IN_MSPIKE_H2=-0.001, 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 jktuYMD1oXjk for <netconf@ietfa.amsl.com>; Thu, 21 Nov 2019 09:00:42 -0800 (PST)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C27A4120C72 for <netconf@ietf.org>; Thu, 21 Nov 2019 09:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1574355640; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=n/x0tIs4EJ9EXm0GmG532EgdpUwVrouSsANklsspQGc=; b=MqwWpP/CNTdZNgtc0wo00Ar5BF4XacKaNUDXhO1iCti+FAnYZ/ksBq0MzOvuS4lR 7fNWDsXx1dy1n4uM1FdbG89LHYHvGbhXAiZkflOrBfT7QIdkwSqxPbMH4xuf6y61CQX PDV6owyMJ7KrbRHgn7LavTy+FyIpaQt6JlnmAkSg=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016e8ee89f30-bf2de747-ca32-4ccf-8922-cd8ee910a58f-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4DFDC68B-296C-4569-9B5A-1749AAECC335"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 21 Nov 2019 17:00:40 +0000
In-Reply-To: <20191121.121027.792252830481287907.mbj@tail-f.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Martin Bjorklund <mbj@tail-f.com>
References: <0100016e8a7ebfef-d490b1b8-f55b-45f9-885c-b5bf1d90ec7f-000000@email.amazonses.com> <20191121.121027.792252830481287907.mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.11.21-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4xQZsZ7QshbMj3Xa0opbwE2Wa9k>
Subject: Re: [netconf] updates to client/server suite of drafts
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, 21 Nov 2019 17:00:48 -0000

Hi Martin,


>>   -  Added 'must' expressions asserting that the 'key-format' leaf
>>      exists whenever a non-hidden key is specified.
> 
> This can be made simpler:

True.  I got caught up in the following the pattern used for symmetric/private key groupings.

> OLD:
> 
>       <snip/>
> 
> Now, since public-key is mandatory, the 'when' expression on
> public-key-format will always be true (in a valid config).  Hence it
> isn't needed.  And also, since public-key is mandatory the must on
> public-key really just says that public-key-format is also mandatory:
> 
> NEW:
> 
>     <snip/>

Applied to my local copy.




>>   -  Added a questionable forward reference to "encrypted-*" leafs in a
>>      couple 'when' expressions.
> 
> Questionable indeed.  I suggest you remove the when expression
> instead. You have must expressions that says thatt the key-format leaf
> must exist in the relevant cases anyway.

Hmmm, but "private-key-format" should NOT be present (I think!) for a "hidden-private-key".  Maybe this?

OLD:
	when "../private-key or ../encrypted-private-key"

NEW:
	when "not(../hidden-private-key)"



BTW, the forward reference was "needed" due to the inability for the consuming module (ietf-keystone) to refine (?) the "when" expression when using the grouping.   Please add a YANG-next issue if you think this should be supported someday.


Kent // contributor