The following errata report has been submitted for RFC9190, "EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8094 -------------------------------------- Type: Technical Reported by: Eliot Lear <l...@lear.ch> Section: 2.1.1 Original Text ------------- Certificates can be of any type supported by TLS including raw public keys. Corrected Text -------------- Certificates can be of any type supported by TLS. Raw public keys may also be used. Notes ----- A raw public key specifically is **not** a certificate. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC9190 (draft-ietf-emu-eap-tls13-21) -------------------------------------- Title : EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3 Publication Date : February 2022 Author(s) : J. Preuß Mattsson, M. Sethi Category : PROPOSED STANDARD Source : EAP Method Update Stream : IETF Verifying Party : IESG _______________________________________________ Emu mailing list -- emu@ietf.org To unsubscribe send an email to emu-le...@ietf.org
