Re: [Cfrg] Validation performance Re: new curves vs. algorithms

[Olafur Gudmundsson <[e-mail]>]

On Mar 21, 2014, at 1:56 PM, Santosh Chokhani <[e-mail]> wrote:

> You cannot expect EC to match RSA for public key operation performance given the typical 17 bit exponent for RSA public key.
> 
> The perform problem for EC and discrete logs in finite field gets worse for pubic key operations when taking PKI into consideration because of a number of certificates and their revocation status need to be checked (all use public key operations) before trust in a public key is established.
> 
Santosh, 

FWIW, all I care about is raw performance of core operations, as that is what is used by the protocols i work on and 
that is what can be used for comparisons when selecting algorithms. 
Different protocols/systems add different overheads and in many cases these overhead are algorithm independent. 

	Olafur

> -----Original Message-----
> From: Cfrg [mailto:[e-mail]] On Behalf Of Olafur Gudmundsson
> Sent: Friday, March 21, 2014 1:20 PM
> To: [e-mail]
> Subject: [Cfrg] Validation performance Re: new curves vs. algorithms
> 
> 
> While we are it, here is another criteria to keep in mind when designing/recommending new curves. 
> This relates to an old question I asked on CFRG in 2006 (wow that is a long time ago) in regards to using ECC in DNSSEC http://www.ietf.org/mail-archive/web/cfrg/current/msg01170.html
> 
> Since then DNSSEC has specified the use of 3 curves P256, P384[RFC6605] and ECC-GOST[RFC5933], none of these seems to be in wide spread use, as support is rolling out. 
> 
> What we have learned in the mean time (from DNS perspective), is verification time is the most critical part as the world wants happy eyeballs to work and any microseconds that verification takes add up.
> Consider the case that most web pages have in excess of 50 links and many of those are unique and can not be reused by resolvers/validators. 
> 
> Fast signing is nice as that may enable on the fly signing off unique names. 
> 
> As for criteria I would propose the following, as starting point for discussion 
> 	verification time < verification of 2048 bit RSA signature
> 	signing time      <  signing with 1024  bit RSA key 
> 
> As an example comparing here is comparison of performance of RSA1024 and 2048 bit keys  vs NIST P256 and P384 on modern hardware, only relative performance should be derived. 
> 
>> OpenSSL> version
>> OpenSSL 1.0.1 14 Mar 2012
>> OpenSSL> speed rsa1024 rsa2048 ecdsap256 ecdsap384
>> Doing 1024 bit private rsa's for 10s: 38935 1024 bit private RSA's in 
>> 9.97s Doing 1024 bit public rsa's for 10s: 621683 1024 bit public 
>> RSA's in 9.98s Doing 2048 bit private rsa's for 10s: 5792 2048 bit 
>> private RSA's in 9.98s Doing 2048 bit public rsa's for 10s: 187826 
>> 2048 bit public RSA's in 9.97s Doing 256 bit sign ecdsa's for 10s: 
>> 58772 256 bit ECDSA signs in 9.98s Doing 256 bit verify ecdsa's for 
>> 10s: 23120 256 bit ECDSA verify in 9.97s Doing 384 bit sign ecdsa's 
>> for 10s: 34564 384 bit ECDSA signs in 9.97s Doing 384 bit verify 
>> ecdsa's for 10s: 7695 384 bit ECDSA verify in 9.98s OpenSSL 1.0.1 14 
>> Mar 2012 built on: Tue Jun  4 07:26:06 UTC 2013
>> options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) 
>> blowfish(idx)
>> compiler: cc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DOPENSSL_NO_TLS1_2_CLIENT -DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
>>                  sign    verify    sign/s verify/s
>> rsa 1024 bits 0.000256s 0.000016s   3905.2  62292.9
>> rsa 2048 bits 0.001723s 0.000053s    580.4  18839.1
>>                              sign    verify    sign/s verify/s
>> 256 bit ecdsa (nistp256)   0.0002s   0.0004s   5889.0   2319.0
>> 384 bit ecdsa (nistp384)   0.0003s   0.0013s   3466.8    771.0
> 
> 
> As you can see these ECC curves verification performance SUCKS big time when we compare smallest sizes. 
> I know the RSA code is much more mature than the ECC code but the verification code needs to improve by 25x For these curves Signing speeds meets the criteria. 
> 
> 	Olafur 
> 
> 
> _______________________________________________
> Cfrg mailing list
> [e-mail]
> http://www.irtf.org/mailman/listinfo/cfrg