Post #970821

2026-04-05 19:49 UTC

New blog post &quot;NSA and IETF, part 7: Counting votes.&quot; https://blog.cr.yp.to/20260405-votes.html Turns out to be 22 votes against, 21 votes for: not even a majority in favor, never mind consensus. IETF management is throwing the votes away, insisting on a replay, and trying to silence opponents.

Replies (5)

@juliank@mastodon.social 2026-04-05 19:59

@djb ah yes the classic "keep voting until the results are right"

Open ##1249835
@equinox@chaos.social 2026-04-05 20:13

@djb I don't think you're making the right argument there. There's simply no consensus for this document. There's a lot of cases where that's a hard determination to make; a pretty even split is not one of them. If anything, showing that it is in fact even (and not biased by random drive-bys or sockpuppets), and then insisting on the conclusion of no consensus would be the way to go. They can publish on the individual stream. The bar to cipher suite numbers is only "specification required" ffs.

Open ##1249836
@octade@soc.octade.net 2026-04-05 22:13

Vote HARDER!

Open ##1249841
@KoosPol@mastodon.nl 2026-04-06 03:50

@djb I trust you. But I'm not in the loop and dont want to be. Is there a simple 1-2-3 step action plan I can follow to help? Is it worth to mobilize Fedi?

Open ##1249843
@NohatCoder@mastodon.gamedev.place 2026-04-06 17:25

@djb It is funny how you find one of the best arguments against in the "yes" crowd: "I have customers that, despite our recommendations will want to 'pure' ML-KEM."

Open ##1249844