Re: [Cfrg] Submission of curve25519 to NIST from CFRG -> was RE: On "non-NIST"

I have submitted Goldilocks to this workshop, and if it is accepted I can present general IRTF EC choices alongside it.

— Mike

> On Mar 11, 2015, at 3:06 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Hiya,
> 
> On 11/03/15 08:09, Eggert, Lars wrote:
>> Hi,
>> 
>> dropping NIST from the CC for now.
>> 
>> On 2015-3-10, at 22:37, Paul Lambert <paul@marvell.com> wrote:
>>> 
>>> Given that this illustrious Internet Research Task Group (IRTG) 
>>> subcommittee, the Crypto Forum Research Group (CFRG), has a 
>>> consensus to recommend the use of 'curve25519' for TLS, and
>>> given that NIST is soliciting input on elliptic curves it would
>>> be an opportune time for the Chairs of the CFRG to formally send
>>> the CFRG's draft recommendation 
>>> (https://tools.ietf.org/html/draft-irtf-cfrg-curves-01) to NIST
>>> for the upcoming NIST Workshop on 'Elliptic Curve Standards' ( 
>>> http://www.nist.gov/itl/csd/ct/ecc-workshop.cfm ).
>>> 
>>> "NIST encourages presentations and reports on preliminary work
>>> that participants plan to publish elsewhere."
>> 
>> The IRTF isn't really set up to send (or receive) formal liaisons
>> to other standards bodies - but the IETF certainly is. So if the
>> CFRG made their recommendation to the TLS WG, the TLS WG, Security
>> Area Directors. or the IESG as a whole could send such a liaison.
> 
> We can liaise sure. I chatted with Kenny about this before and I
> think the plan was for the CFRG chairs (or one of 'em) to submit
> a short position paper on what's being done in CFRG. I think that
> would be better than a liaison.
> 
> But if that's not going to happen we can certainly liaise. So
> CFRG chairs - will you get around to that this week or have you
> done it already?
> 
> Cheers,
> S.
> 
> 
> 
>> 
>> Lars
>> 
>> 
>> 
>> _______________________________________________ Cfrg mailing list 
>> Cfrg@irtf.org <mailto:Cfrg@irtf.org> http://www.irtf.org/mailman/listinfo/cfrg <http://www.irtf.org/mailman/listinfo/cfrg>
>> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iQEcBAEBAgAGBQJVABOKAAoJEC88hzaAX42ievwH/0mhNjJCsCglov5FSu3f+3jx
> mHJ88aHtyTZT2fFwGuY9iFCQztrt1MTtbCli2mJxErz3B1rICOBip63IirrQ1k8s
> XkKKRHefIHY+aIk3A6jhtQ8I64gX+MaHmX5IdFVO6MK6TVMrQv5D0rL6toe0Rnoy
> rVV/X6B7M+bwHR9Yf4/C8HeFIGYtJAc/XctI0qg0Py658JEzwxaE40y87B0dmd25
> nxPDDBoAf3vN488rrk3jah+tFzi+drTSdI6QYvq9TuAdNJDeBwvBBGl34jxf4faV
> ZMC2iXyiDyIS2zq9knODtkv/Mcn5Ujr9J5O/8Jlh4SeZZN2cXe98G1zt+J+nI+E=
> =2PEU
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org <mailto:Cfrg@irtf.org>
> http://www.irtf.org/mailman/listinfo/cfrg <http://www.irtf.org/mailman/listinfo/cfrg>