Re: [dnsext] draft-ietf-dnsext-dnssec-algo-imp-status-01

Scott Rose <scottr.nist@gmail.com> Tue, 27 March 2012 16:32 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D352A21F842A; Tue, 27 Mar 2012 09:32:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1332865927; bh=EYUAt+ey1MMo2L+WjEE1BPKGQA0MZeRPHbkUYGRdy3w=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=k8MkBajIbQ5mM2H5Epxmscm8Xl/ltpUwiNZOPjFCC/oOuwdxchrGlRM9SN+Um+jbs ZvMhKAGwkH9gYfjo+hBf+pVUp2DI6gfwq7BtuA7iXolTYgRer/+zp6ohDq2F1iQiNc a4QG/x/f/pXr/dQkkEbKzmMR3pyWaHNgeTz6HX0s=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486F221F8546 for <dnsext@ietfa.amsl.com>; Tue, 27 Mar 2012 09:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.512
X-Spam-Level:
X-Spam-Status: No, score=-6.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVxvG22OtPAN for <dnsext@ietfa.amsl.com>; Tue, 27 Mar 2012 09:31:49 -0700 (PDT)
Received: from smtp.nist.gov (rimp2.nist.gov [129.6.16.227]) by ietfa.amsl.com (Postfix) with ESMTP id 939F021E8168 for <dnsext@ietf.org>; Tue, 27 Mar 2012 09:31:49 -0700 (PDT)
Received: from 107-140.antd.nist.gov (107-140.antd.nist.gov [129.6.140.107]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id q2RGVewM021832 for <dnsext@ietf.org>; Tue, 27 Mar 2012 12:31:40 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
From: Scott Rose <scottr.nist@gmail.com>
In-Reply-To: <CAF4+nEHqOA+wbxVqoEMuJE21XEyeSuxyEiUr3H5uMh5WB+XanA@mail.gmail.com>
Date: Tue, 27 Mar 2012 12:31:40 -0400
Message-Id: <42D1FE92-AC0C-43F8-8253-3D663C931D3D@gmail.com>
References: <4DE8BF39-7E68-4F10-BFBE-F4D408628929@gmail.com> <CAF4+nEHqOA+wbxVqoEMuJE21XEyeSuxyEiUr3H5uMh5WB+XanA@mail.gmail.com>
To: DNSEXT Working Group <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scottr.nist@gmail.com
Subject: Re: [dnsext] draft-ietf-dnsext-dnssec-algo-imp-status-01
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

Suits me - we have a push to use ECDSA for digital signing (by 2015 for DNSSEC), so I don't have a problem with it.  I just wanted WG consensus before making the change.

Scott

On Mar 26, 2012, at 7:34 PM, Donald Eastlake wrote:

> From the very first days of DNSSEC, I've always thought the EC crypto,
> with its more compact keys and signatures, was the way to go
> eventually...
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 
> On Mon, Mar 26, 2012 at 6:29 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>> On Monday, 26th March 2012, Scott Rose wrote, in part:
>>> If the group thinks any of the assigned implementation status
>>> for entries should be changed - please state so.
>>> 
>>> Personally, I'm thinking ECDSA might be moved to "Recommended..."
>>> since there are some advantages, but willing to leave it as is.
>> 
>> All,
>> 
>> I support the idea of moving ECDSA to "Recommended".
>> 
>> Most of us are likely to end up deploying ECDSA eventually,
>> we might as well encourage folks to support it sooner
>> rather than later.  An earlier start to implementation
>> enables earlier widespread interoperability, which in
>> turn enables widespread deployment.  These things all
>> take time.  There is no value in delay.
>> 
>> * The financial sector already seems to be migrating
>>  from RSA to EC for a wide range of things.
>> 
>> * Separately, the published literature indicates that
>>  MUCH shorter EC keys have strength equivalent to
>>  MUCH longer RSA keys, so EC appears to scale better.[1][2]
>>  For example, [2] indicates that an ECC key size of
>>  163 bits has strength equivalent to an RSA key size
>>  of 1024 bits.
>> 
>> * Published literature also indicates that EC is less
>>  computationally expensive than RSA for equivalent-strength
>>  key sizes.  So EC is better for systems with smaller CPUs
>>  or that need to perform higher volumes of transactions.[3]
>> 
>> Yours,
>> 
>> Ran
>> 
>> 
>> 
>> REFERENCES:
>> 
>> [1] K. Lauter, "The Advantages of Elliptic Curve Cryptography for
>>    Wireless Security", IEEE Wireless Communications, Volume 11,
>>    Issue 1, IEEE, Piscataway, NJ, USA, February 2004.
>> 
>> [2] V. Gupta, et alia, "Performance Analysis of Elliptic Curve
>>    Cryptography for SSL", Proceedings of 1st ACM Workshop on
>>    Wireless Security, ACM, Atlanta, GA, September 2002.
>> 
>> [3] Nils Gura, et alia, "Comparing Elliptical Curve Cryptography
>>    and RSA on 8-bit CPUs", Proceedings of 6th International Workshop
>>    on Cryptographic Hardware and Embedded Systems '04, published in
>>    Volume 3156, Lecture Notes in Computer Science, Springer-Verlag,
>>    Berlin, DE, 2004.
>> 
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext

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