Right!
One comment on wording: it may cause an illusion that the condition "if the
exchange is successful" relates to the whole sentence and not just to
Crypto-Binding
TLV.
On Thu, Nov 12, 2020 at 5:33 AM Joseph Salowey wrote:
>
>
> On Tue, Nov 10, 2020 at 2:17 PM Oleg Pekar
> wrote:
>
>>
On Tue, Nov 10, 2020 at 2:17 PM Oleg Pekar
wrote:
> Section 3.3.2 says:
>> Upon receiving the response, the server
>>indicates the success or failure of the exchange using an
>>Intermediate-Result TLV.
>> It Should say:
>> Upon receiving the response, the server MUST
>>indicate the
>
> Section 3.3.2 says:
> Upon receiving the response, the server
>indicates the success or failure of the exchange using an
>Intermediate-Result TLV.
> It Should say:
> Upon receiving the response, the server MUST
>indicate the success or failure of the exchange using an
>
Revision for 8544. The wording needs some review. Additional revisions
were made to section 4.2.13 in 5775.
PR Section 5: https://github.com/emu-wg/teap-errata/pull/19
PR section 3: https://github.com/emu-wg/teap-errata/pull/22
PR section 3: https://github.com/emu-wg/teap-errata/pull/23
PR
On Mon, Oct 26, 2020 at 1:27 AM Oleg Pekar
wrote:
> Few comments:
> 1) It seems that the server MUST send Crypto-Binding TLV after a single
> EAP authentication method, after each of EAP authentications methods in a
> sequence, after no inner method but not after
> Basic-Password-Authentication.
Few comments:
1) It seems that the server MUST send Crypto-Binding TLV after a single EAP
authentication method, after each of EAP authentications methods in a
sequence, after no inner method but not after
Basic-Password-Authentication. Shouldn't we close this gap for the sake of
simplicity and
Errata 5844: https://www.rfc-editor.org/errata/eid5844
Status: Verified
Revision:
Section 3.3.2 says:
Upon receiving the response, the server
indicates the success or failure of the exchange using an
Intermediate-Result TLV.
It Should say:
Upon receiving the response, the server MUST
