> On Mar 27, 2015, at 9:20 PM, [email protected] wrote: > - chacha20poly1305 > http://www.ietf.org/proceedings/92/slides/slides-92-ipsecme-2.pdf > > Yoav presenting > > Yaron: does arm have aes acceleration? > Yoav: no. it has something called neon - not in phones but in tablets. has > some advantages > Steve Kent: the "civilian part" keep in mind several industry sectors make > use of FIPS approved algos for liability > purpose. If the motivation is performance, that is not a good argument > anymore. Russ Housley chatted with NIST people > and made optimized miplementation og P-256 so the performance of Curve25519 > is not different enough. Performance is not > a good reason. > Tero: you cannor use curve25519 .... same for blake.... ? > Tero: I hate the names A B and C. C for civilian is not a good name. Move UI > out and do UI in separate document > Yoav: I thought we'd have the answer of CRFG by now.... > ??? from NIST: We received documents and proposal claiming they have to > implement P-256 faster than Curve25519. Has not > been verified. It is just a claim. > PaulH: who will support with review or code: Tero,PaulW, Michael and Valery
Hi In the meeting Kathleen asked how long the draft was. With all the algorithm details moved to the CFRG draft, the entire document is six pages, including introduction, IANA and security considerations, references, and the UI suite stuff (that I agree with Tero that should be moved out). The real “meat” of the document is section 2, which spans a little over one page. HTH Yoav _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
