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

Wang Haiguang <wang.haiguang.shieldlab@huawei.com> Sun, 28 April 2019 08:31 UTC

Return-Path: <wang.haiguang.shieldlab@huawei.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 E153E12008A for <netconf@ietfa.amsl.com>; Sun, 28 Apr 2019 01:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 ONT2abJK5MUI for <netconf@ietfa.amsl.com>; Sun, 28 Apr 2019 01:31:24 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF070120006 for <netconf@ietf.org>; Sun, 28 Apr 2019 01:31:23 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B2A55EF99623940A8E2F; Sun, 28 Apr 2019 09:31:21 +0100 (IST)
Received: from lhreml708-chm.china.huawei.com (10.201.108.57) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 28 Apr 2019 09:31:21 +0100
Received: from lhreml708-chm.china.huawei.com (10.201.108.57) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Sun, 28 Apr 2019 09:31:21 +0100
Received: from SINEML705-CAH.china.huawei.com (10.223.161.55) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Sun, 28 Apr 2019 09:31:20 +0100
Received: from SINEML521-MBX.china.huawei.com ([169.254.1.224]) by SINEML705-CAH.china.huawei.com ([10.223.161.55]) with mapi id 14.03.0415.000; Sun, 28 Apr 2019 16:31:16 +0800
From: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
To: Kent Watsen <kent+ietf@watsen.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types
Thread-Index: AdT7E8hZAPIgEzoMT+CWvaCRHboBx///tkyAgACgJICAAAoVAIAAEN+AgAAQfICAACo1gIAABpQAgAEXiQCAA0bhxA==
Date: Sun, 28 Apr 2019 08:31:16 +0000
Message-ID: <0AE05CBFB1A6A0468C8581DAE58A31309E3DD12B@SINEML521-MBX.china.huawei.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> <0100016a5660266f-69525394-213b-4cc1-ae5c-89d8d93a6160-000000@email.amazonses.com> <20190425214516.n2fi3bc3volpv5lr@anna.jacobs.jacobs-university.de>, <0100016a5a09b22c-052a4155-dd9d-466d-a16f-9e84adfbc852-000000@email.amazonses.com>
In-Reply-To: <0100016a5a09b22c-052a4155-dd9d-466d-a16f-9e84adfbc852-000000@email.amazonses.com>
Accept-Language: en-SG, en-US
Content-Language: en-SG
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.46.157]
Content-Type: multipart/alternative; boundary="_000_0AE05CBFB1A6A0468C8581DAE58A31309E3DD12BSINEML521MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/QAfS4Rh1FPuBItIE4IkUgLtbmhs>
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: Sun, 28 Apr 2019 08:31:26 -0000

Hi, Kent and all

Sorry for the late reply due to time differences.

I will post the link to i2nsf tonight and let them aware the discussion in netconf.

Best regards.

Haiguang


________________________________
From: Kent Watsen [kent+ietf@watsen.net]
Sent: Friday, 26 April, 2019 10:25:46 PM
To: Juergen Schoenwaelder
Cc: Martin Bjorklund; Wang Haiguang; netconf@ietf.org
Subject: Re: [netconf] The maintenance of the algorithm identifiers in draft-ietf-crypto-types



On Apr 25, 2019, at 5:45 PM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>> wrote:

On Thu, Apr 25, 2019 at 09:21:43PM +0000, Kent Watsen wrote:

In the meanwhile, what's the stop-gap solution?   - crypto-types
shouldn't be blocked on YANG Next...


What we have been doing so far is publishing identities / enumerations
without having a common way for implementations to declare the subset
they do support. This seems reasonable since once we add a common
mechanism to report the subset actually implemented, we do not have to
go back and revise the definitions of identities and enumerations.

Sounds right, with the clarification that crypto-types should have identities for all (within reason) known algorithms, even if deprecated or obsolete, and that for those algorithms that are deprecated or obsolete, the identity's "status" statement should be set to "deprecated" or "obsolete" accordingly.

Haiguang, can you please point the i2nsf group to this thread?

Thanks,
Kent