Re: [netconf] ietf crypto types - identities

Wang Haiguang <wang.haiguang.shieldlab@huawei.com> Thu, 09 May 2019 16:26 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 1182512016A for <netconf@ietfa.amsl.com>; Thu, 9 May 2019 09:26:36 -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 ODLYO07Nin2b for <netconf@ietfa.amsl.com>; Thu, 9 May 2019 09:26:34 -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 02056120145 for <netconf@ietf.org>; Thu, 9 May 2019 09:26:34 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 0971F7BC22F9834D8777 for <netconf@ietf.org>; Thu, 9 May 2019 17:26:32 +0100 (IST)
Received: from sineml703-chm.china.huawei.com (10.223.161.110) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 9 May 2019 17:26:31 +0100
Received: from sineml705-chm.china.huawei.com (10.223.161.112) by sineml703-chm.china.huawei.com (10.223.161.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 10 May 2019 00:26:29 +0800
Received: from sineml705-chm.china.huawei.com ([10.223.161.112]) by sineml705-chm.china.huawei.com ([10.223.161.112]) with mapi id 15.01.1713.004; Fri, 10 May 2019 00:26:29 +0800
From: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
To: Martin Bjorklund <mbj@tail-f.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] ietf crypto types - identities
Thread-Index: AQHVAYDDQw6NNz34aE2qTUwOHqkIFaZjAwR+
Date: Thu, 9 May 2019 16:26:29 +0000
Message-ID: <d0fb4dbd25664c8698678c8a0356c45b@huawei.com>
References: <20190503.092032.2009186244613537120.mbj@tail-f.com>
In-Reply-To: <20190503.092032.2009186244613537120.mbj@tail-f.com>
Accept-Language: en-SG, en-US
Content-Language: en-SG
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.43.221]
Content-Type: multipart/alternative; boundary="_000_d0fb4dbd25664c8698678c8a0356c45bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/wiRhlaIP_MC26D2hU3HREaqB1I0>
Subject: Re: [netconf] ietf crypto types - identities
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, 09 May 2019 16:26:36 -0000

Hi, Martin,


Sorry for the late reply.


Thanks very much to point out the mistake. I think it is a careless mistake and I am going to check draft and try to fix the errors in next version.


Regarding the reference, if I am not wrong, RFC 6090 explains the mathematical formulas used by the ECDSA, RFC 5480 gives an object identifier of the curve.


I did some search found the NIST report FIPS 186-3  not only explains the mathematical formulas, but also list the recommended parameters. How do you think we put FIPS 186-3 as an additional reference for secp192r1, ...


https://csrc.nist.gov/csrc/media/publications/fips/186/3/archive/2009-06-25/documents/fips_186-3.pdf


Best regards.


Haiguang

________________________________
From: netconf <netconf-bounces@ietf.org>; on behalf of Martin Bjorklund <mbj@tail-f.com>;
Sent: Friday, 3 May 2019 3:20:32 PM
To: netconf@ietf.org
Subject: [netconf] ietf crypto types - identities

Hi,

It seems all sec* identities have the same description:

     identity secp192r1 {
       base asymmetric-key-algorithm;
       description
         "The ECDSA algorithm using a NIST P256 Curve.";
       reference
         "RFC 6090:
            Fundamental Elliptic Curve Cryptography Algorithms.";
     }

This I assume should have been "NIST P191 Curve".

Also, it wasn't clear to me by looking at the reference what this
actually means.  I had to google for "secp192r1", which lead me to RFC
5480 which defines the *curve* "secp192r1".  So I wonder if the
reference needs to be updated, and if the name of this identity is
really correct?


/martin

_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf