Hi, I see now that the two paragraphs you send seems to be contradicting each other
https://tools.ietf.org/html/rfc8446#section-2 A failure of the handshake or other protocol error triggers the termination of the connection, optionally preceded by an alert message (Section 6). https://tools.ietf.org/html/rfc8446#section-6.2 Whenever an implementation encounters a fatal error condition, it SHOULD send an appropriate fatal alert and MUST close the connection without sending or receiving any additional data. Unclear if Error alert is optional or SHOULD..... Maybe you should ask the TLS WG. John -----Original Message----- From: John Mattsson <john.matts...@ericsson.com> Date: Friday, 5 February 2021 at 20:36 To: EMU WG <emu@ietf.org> Subject: [Emu] EAP-TLS and TLS alerts Hi, Alerts are definitly not mandatory in TLS 1.3. Adding a note stating that alerts are not mandatory seems like a good idea. But "suggests" seems like the wrong word and optional != SHOULD. I would like more feedback from other people before adding new requirements on TLS. Can an application typically enforce Error alerts in TLS? John _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
