On May 16, 2014, at 7:29 AM, Colm MacCárthaigh <c...@allcosts.net> wrote: >> And even 4096b RSA signatures only take a handful of milliseconds to >> construct on the fly, you can cache signature validity for minutes even in >> the very dynamic case, and this is one of those operations that parallelize >> obscenely well. >> > You won't survive a trivial DOS from a wristwatch computer with that approach > :) Having static answers around greatly increases capacity, by many orders of > magnitude.
Actually, you can. You prioritize non-NSEC3 records, since thats a finite, identifiable, priority set, and cache the responses. Thus if you have 10k valid names, each with 100 different possible responses, and have a max 1 minute TTL on signatures, thats only 16k signatures/s in the absolute worst case, which you can do on a single, 16 core computer. -- Nicholas Weaver it is a tale, told by an idiot, nwea...@icsi.berkeley.edu full of sound and fury, 510-666-2903 .signifying nothing PGP: http://www1.icsi.berkeley.edu/~nweaver/data/nweaver_pub.asc
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
