OK We'll ask for early code point assignment for

ecdh_x25519 (29), ecdh_x448 (30)


On Tue, Jan 19, 2016 at 10:59 AM, Andrei Popov <andrei.po...@microsoft.com>
wrote:

> Yes, please allocate, esp. 25519. MS will start testing interop soon.
>
>
>
> Cheers,
>
>
>
> Andrei
>
>
>
> *From:* TLS [mailto:tls-boun...@ietf.org] *On Behalf Of *David Benjamin
> *Sent:* Tuesday, January 19, 2016 10:01 AM
> *To:* Joseph Salowey <j...@salowey.net>; Brian Smith <br...@briansmith.org>
> *Cc:* Adam Langley <a...@imperialviolet.org>; Simon Josefsson <
> si...@josefsson.org>; tls@ietf.org
> *Subject:* Re: [TLS] Correction: early codepoint assignment for
> Curve25519, Curve448, Ed25519 and Ed448
>
>
>
> BoringSSL has a pair of implementations ready (in C and in our fork of
> Go's TLS stack for testing). We're using the value in the TLS 1.3 draft, so
> 29. It's not currently enabled in any Chrome builds, but I'm expecting to
> change this soon.
>
>
> David
>
>
>
> On Tue, Jan 19, 2016 at 12:54 PM Joseph Salowey <j...@salowey.net> wrote:
>
> Any objections to early allocation for X25519 and X448?  Are there
> implementers with code ready to test interop?
>
>
>
> Thanks,
>
>
>
> Joe
>
>
>
> On Thu, Jan 14, 2016 at 3:22 PM, Brian Smith <br...@briansmith.org> wrote:
>
> Simon Josefsson <si...@josefsson.org> wrote:
>
> Allocating a code point for X25519 could be done and is long overdue
> (first draft September 2013).  X448 is also stable.  Code points for
> Ed25519 and Ed448 is more problematic since TLS authentication has
> historically had interaction with PKIX certs.  I agree with Yoav's
> assertion that the curve point verification issue is not big enough to
> stall code point allocation.
>
>
>
> I agree with this.
>
>
>
> Cheers,
>
> Brian
>
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ietf.org%2fmailman%2flistinfo%2ftls&data=01%7c01%7cAndrei.Popov%40microsoft.com%7cf98a69f5749b4201db9608d320fa7d41%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=5vehoTyQrunKJOKqeWolH9TSAndHSWhX4zKz5RsBcJ0%3d>
>
>
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to