To the Security ADs, cc'ing [email protected]: I am writing to you to invoke the "may bring it to the attention of the Area Director(s)" provision of RFC 2026 regarding the matter below. For transparency, please carry out all discussion of this matter on the relevant public mailing list ([email protected]), including, but not limited to, any discussions of this matter among IESG members, IAB members, agents of IETF Administration LLC, etc.
As background, the TLS WG chairs sent email dated 14 Jul 2025 18:05:33 -0400 announcing a second "WG adoption call for draft-reddy-tls-slhdsa". Three weeks after the end of the specified call period, the chairs issued a statement making completely unclear what they are claiming the results of the call are. The chairs answered an initial round of questions by saying "The draft is adopted as a working group item". I asked a simple yes/no question as to whether the chairs are claiming that this has WG consensus; that was two weeks ago, and there still has been no reply. The chairs also said "The draft is 'parked' meaning there will not be a working group last call until the conditions have been met". I asked whether the chairs are claiming that this second statement has WG consensus. That was also two weeks ago, and there was again no reply. I think "the conditions" refers to the earlier chair text "sufficient external interest to publish it such as usage in another standard or a groundswell of significant implementations", and I asked whether I was correct in this understanding, but there was no reply to that either. The lack of clarity is procedurally unacceptable. Also, beyond clearly declaring the results of the call, the chairs have to make clear how they arrived at this declaration. BCP 9 requires the chairs to "maintain a publicly accessible record of" their work, including "complete and accurate minutes" of their meetings, and including copies of "all written contributions"; where are the records? The chairs ignored this question. ---D. J. Bernstein _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
