Re: [Emu] TEAP - RFC 7170 - Errata ID 5768

2020-06-29 Thread Joseph Salowey
On Mon, Jun 29, 2020 at 6:49 AM Oleg Pekar wrote: > Jorge, Joe, thank you for your comments. So the updated proposal should be: > > 1) In Section "4.2.13. Crypto-Binding TLV" make "EMSK Compound MAC" and > "MSK Compound MAC" fields variable length depending on the number of output > bits of the

Re: [Emu] TEAP errata 5770

2020-06-29 Thread Oleg Pekar
Joe, nice proposal. Few questions: 1. We have a case of Basic Password Authentication instead of inner method thus we should also use Crypto-Binding TLV based on Zero-MSK after it 2. As Eliot mentioned, we have a case of no inner method at all - we should use Crypto-Binding TLV based on Zero-MSK af

Re: [Emu] TEAP - RFC 7170 - Errata

2020-06-29 Thread Oleg Pekar
Jorge, thanks for correction: Intermediate-Result TLV must be sent at the end of Basic Password Authentication. I think we also need to list all four inner method cases that I mention in above explicitly, for example in "3.3.3. Protected Termination and Acknowledged Result Indication" section. Si

Re: [Emu] TEAP - RFC 7170 - Errata ID 5768

2020-06-29 Thread Oleg Pekar
Jorge, Joe, thank you for your comments. So the updated proposal should be: 1) In Section "4.2.13. Crypto-Binding TLV" make "EMSK Compound MAC" and "MSK Compound MAC" fields variable length depending on the number of output bits of the MAC function negotiated by TLS protocol. A field "Compound MA