On Thu, May 21, 2026, at 02:41, D. J. Bernstein wrote: > This spec doesn't have WG consensus, > doesn't have WG "rough consensus", and doesn't have "consensus of the > IETF community".
Wearing nothing but my own hat here, and with my experience as a chair (selected by the IESG) and having watched the operations of many working groups. You get to have an opinion on working group rough consensus, I get to have an opinion on working group rough consensus. Neither of us get to declare whether or not it's present. The working group chairs do. Working Group Rough Consensus does not mean "everybody agrees", it means "everybody was heard". I don't think there's a single person who is paying any level of attention to the IETF who hasn't heard your opinion on this document! So *the document DOES have WG consensus, because the chairs declared that it does, and that's their job*. They get to decide this. They might be wrong in their application of the rules, but they are the authority with the ability to declare it, and they have. It now needs to get IETF consensus to proceed further, which is does NOT have. The last-call process is the process by which that consensus is assessed, and we're in that now. The people who can declare IETF-wide consensus are the members of the IESG; who were selected by the nomcom. If you don't like that, it's a pity - but your remedy is to go find another standards body with different rules - because that's the rules of this one. For those on this list who would like to persuade the IESG of their views on this document, it would behoove them to understand the people who are assessing consensus, what kinds of arguments and presentation would persuade them, and tailor their comments to the people they need to persuade. That's my take on the IETF's process. Independent of the merits of any particular document. Bron. -- Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC [email protected]
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
