Re: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types
Kent Watsen <kent@watsen.net> Thu, 25 April 2019 21:21 UTC
Return-Path: <0100016a5660266f-69525394-213b-4cc1-ae5c-89d8d93a6160-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 41ADE120226 for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 14:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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, RCVD_IN_MSPIKE_H2=-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 wWtcetFythLh for <netconf@ietfa.amsl.com>; Thu, 25 Apr 2019 14:21:44 -0700 (PDT)
Received: from a8-31.smtp-out.amazonses.com (a8-31.smtp-out.amazonses.com [54.240.8.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9604B12015D for <netconf@ietf.org>; Thu, 25 Apr 2019 14:21:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1556227303; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=f0olK7TuJxE4tr0yQ4/OZhWRhokjlhUnRf2p981t1xc=; b=bF0d+l+5Sxf3QWDjihG+gng8qMnqA24b8K1Eqqe9/QeUJl25pjLM8qz75SoJ5p10 UKVFLPK6+8xBdggNLW32KUlafpXImrgWH6HJ2T6EJF3Ko8ZnLrJ+BscfZltOnBxtWwf ts5TawxasrEeVaEryOZ1nkTkVwHtBr5Ws0zTxZsA=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016a5660266f-69525394-213b-4cc1-ae5c-89d8d93a6160-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B3E01AAF-0356-46B5-B87D-FE11323C22B2"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 25 Apr 2019 21:21:43 +0000
In-Reply-To: <20190425.205039.1112892422143145313.mbj@tail-f.com>
Cc: wang.haiguang.shieldlab@huawei.com, "netconf@ietf.org" <netconf@ietf.org>
To: Martin Bjorklund <mbj@tail-f.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> <20190425.205039.1112892422143145313.mbj@tail-f.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.04.25-54.240.8.31
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/SQo76vzuQhIiaOj19A8eFzemhYY>
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 21:21:47 -0000
>>> 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. The titles can and should be updated to reflect the true problem. Could you update #40 and close #80 with label "Duplicate"? In the meanwhile, what's the stop-gap solution? - crypto-types shouldn't be blocked on YANG Next... Kent
- 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