We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·Jul 3·5 min read
A [non-hybrid tls-mlkem] standard by any other name: How IETF evades responsibility for its actions
TL;DR
The IETF, a key standards organization for the Internet, has been criticized for its vague labeling of standards, which obscures accountability. A current debate involves the potential adoption of solo ML-KEM, a cryptographic method, as part of the TLS 1.3 standard, driven by NSA influence.
✦ Why It Matters
Engineers should be aware of the implications of adopting new cryptographic standards influenced by government agencies.
Key Takeaways
- Understand the implications of IETF's standard labeling.
- Stay informed about the ongoing TLS 1.3 vote.
- Evaluate the security of solo ML-KEM versus ECC.
- Consider the influence of government agencies on industry standards.
Full Summary
The Internet Engineering Task Force (IETF) is responsible for developing standards that govern Internet technologies, but it often uses ambiguous terminology to avoid accountability for its decisions. Currently, there is a contentious vote regarding the inclusion of solo ML-KEM (a key exchange method) in the TLS 1.3 standard, which is being pushed by the NSA.
This proposal is still in draft form and has not yet been approved. Proponents argue that adopting solo ML-KEM is crucial, despite its lack of widespread deployment compared to the established Elliptic Curve Cryptography (ECC) combined with ML-KEM.
The outcome of this vote, which is open until July 7, 2026, could significantly influence how companies implement encryption standards. If passed, it may lead to increased pressure from the NSA on companies to adopt this method, potentially impacting security practices across the industry.