Re: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types
Martin Bjorklund <mbj@tail-f.com> Thu, 25 April 2019 18:50 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 B36A3120252 for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 11:50:54 -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 38byqyL4YdHd for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 11:50:52 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 50F58120227 for <netconf@ietf.org>; Thu, 25 Apr 2019 11:50:43 -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 887801AE03B5; Thu, 25 Apr 2019 20:50:39 +0200 (CEST)
Date: Thu, 25 Apr 2019 20:50:39 +0200
Message-Id: <20190425.205039.1112892422143145313.mbj@tail-f.com>
To: kent@watsen.net
Cc: wang.haiguang.shieldlab@huawei.com, netconf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <0100016a559fd6c6-0deaad17-593f-434c-94b6-111ac0619a3c-000000@email.amazonses.com>
References: <0100016a554785f6-a0f918fc-5396-4410-8320-701f65abf6c0-000000@email.amazonses.com> <20190425.185116.1747028954255365462.mbj@tail-f.com> <0100016a559fd6c6-0deaad17-593f-434c-94b6-111ac0619a3c-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/_Ng46emliYwarQV7Sx_XfV91Llc>
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 18:50:55 -0000
Kent Watsen <kent@watsen.net> wrote: > > > > On Apr 25, 2019, at 12:51 PM, Martin Bjorklund <mbj@tail-f.com> wrote: > > > > 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 can be used for this? > > > > This requirement is already captured in #40. > > The issues are related, but seem like two sides of a coin: > > #40 regards deviating away what is not supported > #80 regards expressing what is supported > > Of course, what is supported could be form of implementing the module > and then deviating away what's not used, but is it ideal? Right, this is part of #40. IMO #40 states the *problem* but not the solution. It is unfortunate that the title indicates a solution, but that is the case for many of our other issues as well. /martin > > For instance, a server may implement different modules that use > different sets of identities (e.g., because they use different > libraries in the backend), such that what is not supported in one > module (and hence the deviated away) is supported in the other (and > hence shouldn't be deviated away). > > > Kent // contributor > >
- Re: [netconf] The maintenance of the algorithm id… tom petch
- [netconf] The maintenance of the algorithm identi… Wang Haiguang
- Re: [netconf] The maintenance of the algorithm id… Juergen Schoenwaelder
- Re: [netconf] The maintenance of the algorithm id… Kent Watsen
- Re: [netconf] The maintenance of the algorithm id… Martin Bjorklund
- Re: [netconf] The maintenance of the algorithm id… Kent Watsen
- Re: [netconf] The maintenance of the algorithm id… Martin Bjorklund
- Re: [netconf] The maintenance of the algorithm id… Kent Watsen
- Re: [netconf] The maintenance of the algorithm id… Juergen Schoenwaelder
- Re: [netconf] The maintenance of the algorithm id… Kent Watsen
- Re: [netconf] The maintenance of the algorithm id… Wang Haiguang