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

Martin Bjorklund <mbj@tail-f.com> Fri, 22 November 2019 08:23 UTC

Return-Path: <mbj@tail-f.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 DD439120143 for <netconf@ietfa.amsl.com>; Fri, 22 Nov 2019 00:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8JRYMgxPzn41 for <netconf@ietfa.amsl.com>; Fri, 22 Nov 2019 00:23:24 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8275012003E for <netconf@ietf.org>; Fri, 22 Nov 2019 00:23:24 -0800 (PST)
Received: from localhost (h-4-44.A165.priv.bahnhof.se [158.174.4.44]) by mail.tail-f.com (Postfix) with ESMTPSA id 85E4A1AE0310; Fri, 22 Nov 2019 09:23:22 +0100 (CET)
Date: Fri, 22 Nov 2019 09:23:22 +0100
Message-Id: <20191122.092322.920833985355675307.mbj@tail-f.com>
To: kent+ietf@watsen.net
Cc: netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <0100016e8ee89f30-bf2de747-ca32-4ccf-8922-cd8ee910a58f-000000@email.amazonses.com>
References: <0100016e8a7ebfef-d490b1b8-f55b-45f9-885c-b5bf1d90ec7f-000000@email.amazonses.com> <20191121.121027.792252830481287907.mbj@tail-f.com> <0100016e8ee89f30-bf2de747-ca32-4ccf-8922-cd8ee910a58f-000000@email.amazonses.com>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/MNyw8Yp7F8_ZPjFDwtl-I9HdZvw>
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: Fri, 22 Nov 2019 08:23:26 -0000

Kent Watsen <kent+ietf@watsen.net> wrote:
> 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)"

Or perhaps use a must in the 'hidden-private-key' instead:

  must 'not(../private-key-format)';



/martin


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