[Emu] TEAP Errata 5768
We need to come to resolution on how to resolve these errata. I hope there has been enough time for implementors to catch up with Jouni's implementation. The Crypto-Binding TLV is fixed at 20 octets and the draft does not say how to handle longer MACs. The discussion seems to indicate that we should make the TLV variable length to handle longer MACs. Is anyone else taking this approach with their implementation? Is there any objection to move forward with making the MAC variable length? Cheers, Joe ___ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
Re: [Emu] POST WGLC Comments draft-ietf-emu-eap-tls13
On Oct 7, 2019, at 10:55 AM, Eliot Lear wrote: > > If we evolve draft-lear-eap-teap-brski into a more generic TEAP update we > could cover TLS 1.3 there. Given Jouni's experience with implementing TEAP, that may be best. i.e. TEAP cannot be implemented as-is. The spec needs to be updated so that we can create inter-operable versions. Alan DeKok. ___ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
Re: [Emu] POST WGLC Comments draft-ietf-emu-eap-tls13
> On 7 Oct 2019, at 15:10, Alan DeKok wrote: > > On Oct 7, 2019, at 2:32 AM, John Mattsson > wrote: >> >> Joseph Salowey wrote: >> >>> Is the current published version up to date with the rest of the comments? >> >> Yes, to my knowledge, the current draft handles all the other comments. If >> we decide to leave EAP-TLS PSK discussions for another draft, I think >> draft-ietf-emu-eap-tls13-07 is ready to move forward in the publication >> process. > > I agree. > > My one worry is that if we update EAP-TLS without also updating PEAP and > TTLS, then bad things will happen. > > My $0.02 is to remove the discussion of FAST and TEAP from > draft-dekok-emu-tls-eap-types, as the remaining items are not controversial. > The document should then be published simultaneously with the EAP-TLS updates. If we evolve draft-lear-eap-teap-brski into a more generic TEAP update we could cover TLS 1.3 there. Eliot signature.asc Description: Message signed with OpenPGP ___ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
Re: [Emu] POST WGLC Comments draft-ietf-emu-eap-tls13
On Oct 7, 2019, at 2:32 AM, John Mattsson wrote: > > Joseph Salowey wrote: > >> Is the current published version up to date with the rest of the comments? > > Yes, to my knowledge, the current draft handles all the other comments. If we > decide to leave EAP-TLS PSK discussions for another draft, I think > draft-ietf-emu-eap-tls13-07 is ready to move forward in the publication > process. I agree. My one worry is that if we update EAP-TLS without also updating PEAP and TTLS, then bad things will happen. My $0.02 is to remove the discussion of FAST and TEAP from draft-dekok-emu-tls-eap-types, as the remaining items are not controversial. The document should then be published simultaneously with the EAP-TLS updates. Alan DeKok. ___ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
