Subject: Re: [netconf] updates to the client/server suite of drafts
From: Kent Watsen <[email-masked]>
To: Martin Bjorklund <[email-masked]>
Cc: "[email-masked]" <[email-masked]>, [email-masked]
Date: Mon, 21 Oct 2019 16:39:37 +0000
List-Id: NETCONF WG list <netconf.ietf.org>

Hi Martin,

Thanks for double-checking on such things.

> I note that the issue with the union of enum and uint16 is not
> resolved (see thread
> https://mailarchive.ietf.org/arch/msg/netconf/p8oBYkx7Ps7J8ATsqFslX4ApvWg)

Right, but tentative (pending the IANA template discussion) plan is replace the enumeration with an identity, or perhaps a string.

This was what was meant by:

	Not yet incorporated:

	 1. a resolution to the "algorithms" problem in the
	    crypto-types draft.  (IANA templates?)

> Also, there is no explanation of what a "key-format" really is.
> There are just a bunch of identities.

Not completely true, for instance:

    leaf key-format {
      nacm:default-deny-write;
      when "../key";
      type identityref {
        base symmetric-key-format;
      }
      description "Identifies the symmetric key's format.";
    }

That said, if we choose to pursue this approach (using a "key-format" leaf), we should add more detail to its definition to improve understandability.

Kent // contributor