The following errata report has been submitted for RFC8879, "TLS Certificate Compression".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8738 -------------------------------------- Type: Technical Reported by: Kazu Yamamoto <[email protected]> Section: 5 Original Text ------------- After decompression, the Certificate message MUST be processed as if it were encoded without being compressed. This way, the parsing and the verification have the same security properties as they would have in TLS normally. Corrected Text -------------- After decompression, the Certificate message MUST be processed as if it were encoded without being compressed, with the exception of the handshake transcript. The CompressedCertificate message is hashed into the handshake transcript (Section 4.4.3 of [RFC8446]) in place of a Certificate message. Notes ----- The corrected text is suggested by Martin Thomson. 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. -------------------------------------- RFC8879 (draft-ietf-tls-certificate-compression-10) -------------------------------------- Title : TLS Certificate Compression Publication Date : December 2020 Author(s) : A. Ghedini, V. Vasiliev Category : PROPOSED STANDARD Source : Transport Layer Security Stream : IETF Verifying Party : IESG _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
