Return-Path: <0100016def3037d2-786844fa-da22-40de-a017-334b8382f005-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 ECA9F12010F for ; Mon, 21 Oct 2019 09:39:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 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, 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 tcuNlOsoTB0r for ; Mon, 21 Oct 2019 09:39:39 -0700 (PDT) Received: from a8-32.smtp-out.amazonses.com (a8-32.smtp-out.amazonses.com [54.240.8.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E79B120108 for ; Mon, 21 Oct 2019 09:39:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1571675977; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=9WDFzIA59SCnMBJFo6FbLB9kli7YF/ENlDw+t1zVyQI=; b=Kfze9feYK9PX8ujdw3qtlJpk4P3HhnZAIY3i7idK4la34ly5nHcwqygsj4/Twdjp 3GLSnkiHXSBx43I/pQGcrjvzxJOwVsALN+bBlv/hfyQZ8HyZSiCRC1gcrdZKt3Hs1GL orWAP01RBIjJqbyiR9YRp3D2JjcKmgAK5gNRpHvQ= From: Kent Watsen Message-ID: <0100016def3037d2-786844fa-da22-40de-a017-334b8382f005-000000@email.amazonses.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_B7D56481-6B23-4D0A-8015-CE0E01E68F4F" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Mon, 21 Oct 2019 16:39:37 +0000 In-Reply-To: <20191021.140735.219423443110079719.mbj@tail-f.com> Cc: "netconf@ietf.org" , wang.haiguang.shieldlab@huawei.com To: Martin Bjorklund References: <0100016de0fbf0b3-98fbdb4a-8f25-44ed-b35b-b58a8912aad6-000000@email.amazonses.com> <20191021.140735.219423443110079719.mbj@tail-f.com> X-Mailer: Apple Mail (2.3445.104.11) X-SES-Outgoing: 2019.10.21-54.240.8.32 Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES Archived-At: Subject: Re: [netconf] updates to the client/server suite of drafts X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: NETCONF WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2019 16:39:41 -0000 --Apple-Mail=_B7D56481-6B23-4D0A-8015-CE0E01E68F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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 --Apple-Mail=_B7D56481-6B23-4D0A-8015-CE0E01E68F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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/p8oBYkx7Ps7J8ATsq= FslX4ApvWg)

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

= --Apple-Mail=_B7D56481-6B23-4D0A-8015-CE0E01E68F4F--