Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01

Joseph Salowey writes: > Please respond if you have concern about early code point assignment for > the curves listed in draft-ietf-tls-curve25519-01 > . The above draft, and rfc4492bis and tls13-11, has known issues/inconsistencies relat

Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01

On Mon, Jan 11, 2016 at 12:12:47AM -0800, Watson Ladd wrote: > On Mon, Jan 11, 2016 at 12:03 AM, Ilari Liusvaara > > > > I don't think this is signficant. If you want protection from THS that > > actually works, you require EMS anyway (or ensure THS is of no > > consequence at application layer), n

Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01

On Mon, Jan 11, 2016 at 12:03 AM, Ilari Liusvaara wrote: > On Mon, Jan 11, 2016 at 09:28:57AM +0200, Ilari Liusvaara wrote: >> On Sun, Jan 10, 2016 at 07:53:08PM -0800, Joseph Salowey wrote: >> > Please respond if you have concern about early code point assignment for >> > the curves listed in dra

Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01

On Mon, Jan 11, 2016 at 09:28:57AM +0200, Ilari Liusvaara wrote: > On Sun, Jan 10, 2016 at 07:53:08PM -0800, Joseph Salowey wrote: > > Please respond if you have concern about early code point assignment for > > the curves listed in draft-ietf-tls-curve25519-01 > >

Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01

On Sun, Jan 10, 2016 at 07:53:08PM -0800, Joseph Salowey wrote: > Please respond if you have concern about early code point assignment for > the curves listed in draft-ietf-tls-curve25519-01 > . Wasn't that document effectively merged to RF

[TLS] Early code point assignment for draft-ietf-tls-curve25519-01

Please respond if you have concern about early code point assignment for the curves listed in draft-ietf-tls-curve25519-01 . Thanks, J&S ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mai