Re: [TLS] Harmonizing 4492bis with TLS 1.3

2016-12-16 Thread Benjamin Kaduk
On 12/13/2016 11:56 PM, Martin Thomson wrote: > On 14 December 2016 at 16:42, Yoav Nir wrote: >> Aren’t we going to have separate registries for 1.2 and 1.3? We don’t want >> to force anyone to make the changes you had made (as part of 1.3) just to >> get EdDSA..And I need to request things fro

Re: [TLS] Harmonizing 4492bis with TLS 1.3

2016-12-13 Thread Martin Thomson
On 14 December 2016 at 16:42, Yoav Nir wrote: > Aren’t we going to have separate registries for 1.2 and 1.3? We don’t want > to force anyone to make the changes you had made (as part of 1.3) just to get > EdDSA..And I need to request things from IANA based on 1.2 registries. Yes, but I was thi

Re: [TLS] Harmonizing 4492bis with TLS 1.3

2016-12-13 Thread Yoav Nir
> On 14 Dec 2016, at 3:33, Martin Thomson wrote: > > On 13 December 2016 at 22:47, Yoav Nir wrote: >> 2. Change 4492bis: >> a. no new curves for ed25519 and ed448. >> b. Two new signature algorithms, and request values 7 and 8 for them. >> c. new hash algorithm 0x08 and call it some

Re: [TLS] Harmonizing 4492bis with TLS 1.3

2016-12-13 Thread Martin Thomson
On 13 December 2016 at 22:47, Yoav Nir wrote: > 2. Change 4492bis: > a. no new curves for ed25519 and ed448. > b. Two new signature algorithms, and request values 7 and 8 for them. > c. new hash algorithm 0x08 and call it something like “intrinsic” This, but with a small tweak: don

Re: [TLS] Harmonizing 4492bis with TLS 1.3

2016-12-13 Thread Ilari Liusvaara
On Tue, Dec 13, 2016 at 01:47:28PM +0200, Yoav Nir wrote: > Hi > > 1. Leave it as its current inconsistent state > 2. Change 4492bis: > a. no new curves for ed25519 and ed448. > b. Two new signature algorithms, and request values 7 and 8 for them. > c. new hash algorithm 0x08 and c