On Tue, Oct 14, 2025 at 9:19 AM D. J. Bernstein <[email protected]> wrote:
> To the Security ADs: > > I am writing to file the following complaint with both of you: > > > https://web.archive.org/web/20251014135826/https://cr.yp.to/2025/20251014-non-hybrid.md > > I'm cc'ing the relevant public mailing list, [email protected]. For > transparency, please use that list for all discussion of this matter. > Please acknowledge receipt, and please confirm that you will "attempt to > resolve the dispute" as required by RFC 2026. Thanks in advance. > > I tried sending essentially the same *.md text as inline email yesterday > (rather than via a separate URL), and the ietf.org mail system accepted > the message (receipt 7168872B5B8C for [email protected], receipt 7458772B5B8E > for [email protected]), but as far as I can tell the mail system did not > deliver the message. At this point that message is superseded by the > *.md linked above, but I'd still like an explanation of what happened > here, so I'm cc'ing [email protected] to request an explanation. > Isn't it this message? https://mailarchive.ietf.org/arch/msg/tls/pxFgT-VA6hgdd-cAoIkA_7xS99Y/ -Ekr > > ---D. J. Bernstein > > > ===== NOTICES ==== > > This document may not be modified, and derivative works of it may not be > created, and it may not be published except as an Internet-Draft. (That > sentence is the official language from IETF's "Legend Instructions" for > the situation that "the Contributor does not wish to allow modifications > nor to allow publication as an RFC". I'm fine with redistribution of > copies of this document; the issue is with modification.) > > _______________________________________________ > TLS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
