the IETF TLS working group has limited time/energy.
the IETF TLS working group has limited time/energy. He has been (very successfully) taking up a good deal of this with very annoying procedural techniques (and his most recent move, spreading falsehoods regarding an RFC then asking people to brigade a vote on the RFC). Explicitly, this slows down standards, which delays the PQ transition. Again explicitly, this is not the main RFC for PQ TLS, which details a hybrid construction. This is an RFC with "recommended to implement = N" marked about how to do PQ TLS 1.3 in environemnts where hybrids are too expensive, for example hardware where it necessitates both a SHA2 and SHA3 impl.
Posted by mswphd on Jul 2, 2026, 7:36 PM
Tags
Related issues
- Yeah, the plan is far too expensive for what it provides.
- Crashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
- /dev/random is much too expensive for this.
- Yeah, this always bugged me.
- A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
- The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
pricing (Other)
Yeah, the plan is far too expensive for what it provides.
NewCrashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
New/dev/random is much too expensive for this.
Yeah, this always bugged me.
A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
There's a talk from Travis Kalanick recently on a podcast about this.
>nobody ever bought German cars for their low prices, except the Beetle Huh?
the IETF TLS working group has limited time/energy.
the IETF TLS working group has limited time/energy. He has been (very successfully) taking up a good deal of this with very annoying procedural techniques (and his most recent move, spreading falsehoods regarding an RFC then asking people to brigade a vote on the RFC). Explicitly, this slows down standards, which delays the PQ transition. Again explicitly, this is not the main RFC for PQ TLS, which details a hybrid construction. This is an RFC with "recommended to implement = N" marked about how to do PQ TLS 1.3 in environemnts where hybrids are too expensive, for example hardware where it necessitates both a SHA2 and SHA3 impl.
Comments (0)
No comments yet. Start the discussion.