IETF Logo Mail Archive

Re: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types

Martin Bjorklund <mbj@tail-f.com> Thu, 25 April 2019 16:51 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 930DA120223 for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 09:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 AOSCzZYmsNCq for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 09:51:20 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id C58F01201DC for <netconf@ietf.org>; Thu, 25 Apr 2019 09:51:19 -0700 (PDT)
Received: from localhost (h-4-215.A165.priv.bahnhof.se [158.174.4.215]) by mail.tail-f.com (Postfix) with ESMTPSA id 21C8A1AE03B5; Thu, 25 Apr 2019 18:51:17 +0200 (CEST)
Date: Thu, 25 Apr 2019 18:51:16 +0200
Message-Id: <20190425.185116.1747028954255365462.mbj@tail-f.com>
To: kent@watsen.net
Cc: j.schoenwaelder@jacobs-university.de, wang.haiguang.shieldlab@huawei.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <0100016a554785f6-a0f918fc-5396-4410-8320-701f65abf6c0-000000@email.amazonses.com>
References: <0AE05CBFB1A6A0468C8581DAE58A31309E3CB0F5@SINEML521-MBX.china.huawei.com> <20190425064201.lfuwspbkkwatbg6h@anna.jacobs.jacobs-university.de> <0100016a554785f6-a0f918fc-5396-4410-8320-701f65abf6c0-000000@email.amazonses.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/9wSYHWo41LtWZ12C0lL6gILwyCQ>
Subject: Re: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types
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, 25 Apr 2019 16:51:22 -0000

Kent Watsen <kent@watsen.net> wrote:
> 
> 
> > This issue touches on an open issue that we never managed to solve:
> > Given an arbitrarily extensible set of identifiers, how does an
> > implementation announce the subset actually supported? And related to
> > that, can a YANG module define a subset that is expected to be
> > supported (i.e., a conformance requirement)? I am not sure we have
> > a YANG next issue for this, but we should.
> 
> Just submitted https://github.com/netmod-wg/yang-next/issues/80
> <https://github.com/netmod-wg/yang-next/issues/80>.
> 
> Perhaps YANG Library be used for this?

This requirement is already captured in #40.


/martin

v2.23.0 | Report a Bug | By Email