Rich, Thank you very much. This is perfect for me, a huge help, and set me on the right path.
Much appreciated. Best regards, Robert Gallagher Director Industry Standards Mastercard | mobile 636.439.9249 [cid:[email protected]]<www.mastercard.com> From: Salz, Rich <[email protected]> Sent: Monday, January 19, 2026 4:28 PM To: Robert Gallagher <[email protected]>; [email protected] Subject: {EXTERNAL} Re: Inquiry Regarding ChaCha20 Implementation Alignment with BCP 195 I am trying to determine whether the use of the ChaCha20‑Poly1305 cipher fully conforms to the guidance in BCP 195 (“Recommendations for Secure Use of TLS and DTLS”). Could someone point me toward definitive guidance or confirm whether the ChaCha20‑Poly1305 * I am trying to determine whether the use of the ChaCha20‑Poly1305 cipher fully conforms to the guidance in BCP 195 (“Recommendations for Secure Use of TLS and DTLS”). * Could someone point me toward definitive guidance or confirm whether the ChaCha20‑Poly1305 AEAD cipher, as defined in RFC 8439, is considered compliant with the recommendations in BCP 195? You sort of have to read between the lines. Section 4.3 of RFC 9325 (part of the BCP) just points to RFC 8446, the TLS 1.3 specification. In other words, any crypto algorithm that is specified in 8446 is okay, and that includes ChaCha-Poly1305. Note that BCP 195 is getting a new RFC added to it, that will change things to “MUST TLS 1.3” and “MAY TLS 1.2” Hope this helps. /r$ CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the use of the intended recipient and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, any disclosure, distribution or other use of this e-mail message or attachments is prohibited. If you have received this e-mail message in error, please delete and notify the sender immediately. Thank you.
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
