On Tue, Oct 14, 2025 at 10:32 AM D. J. Bernstein <[email protected]> wrote:
> Eric Rescorla writes: > > Isn't it this message? > > https://mailarchive.ietf.org/arch/msg/tls/pxFgT-VA6hgdd-cAoIkA_7xS99Y/ > > _Now_ it's there, yes, after a massive delay inside the IETF mail > system, specifically at the following step: > > Received: from mail2.ietf.org (localhost [127.0.0.1]) > by mail2.ietf.org (Postfix) with ESMTP id A0C0C733A91A > for <[email protected]>; Tue, 14 Oct 2025 > 07:35:28 > -0700 (PDT) > X-Original-To: [email protected] > Delivered-To: [email protected] > Received: from localhost (localhost [127.0.0.1]) > by mail2.ietf.org (Postfix) with ESMTP id 5910E72B5B96 > for <[email protected]>; Mon, 13 Oct 2025 13:34:00 -0700 (PDT) > > See the jump from 13 Oct 2025 13:34:00 -0700 to 14 Oct 2025 07:35:28 > -0700? That's 18 hours on hold inside mail2.ietf.org. > Based on the headers, I think the issue is that it ran afoul of some maximum message size rule and so had to be manually approved: X-Mailman-Rule-Hits: max-size X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; news-moderation; no-subject; digests; suspicious-header Message-ID-Hash: FTPVZFUV2EU2IBSPALF5CX56446A4277 X-Message-ID-Hash: FTPVZFUV2EU2IBSPALF5CX56446A4277 X-Mailman-Approved-At: Tue, 14 Oct 2025 07:35:10 -0700 -Ekr > ---D. J. Bernstein > > > ===== NOTICES REGARDING IETF ===== > > It has come to my attention that IETF LLC believes that anyone filing a > comment, objection, or appeal is engaging in a copyright giveaway by > default, for example allowing IETF LLC to feed that material into AI > systems for manipulation. Specifically, IETF LLC views any such material > as a "Contribution", and believes that WG chairs, IESG, and other IETF > LLC agents are free to modify the material "unless explicitly disallowed > in the notices contained in a Contribution (in the form specified by the > Legend Instructions)". I am hereby explicitly disallowing such > modifications. Regarding "form", my understanding is that "Legend > Instructions" currently refers to the portion of > > > https://web.archive.org/web/20250306221446/https://trustee.ietf.org/wp-content/uploads/Corrected-TLP-5.0-legal-provsions.pdf > > saying that the situation that "the Contributor does not wish to allow > modifications nor to allow publication as an RFC" must be expressed in > the following form: "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 expression hereby applies to this message. > > I'm fine with redistribution of copies of this message. There are no > confidentiality restrictions on this message. The issue here is with > modifications, not with dissemination. > > For other people concerned about what IETF LLC is doing: Feel free to > copy these notices into your own messages. If you're preparing text for > an IETF standard, it's legitimate for IETF LLC to insist on being > allowed to modify the text; but if you're just filing comments then > there's no reason for this. > > _______________________________________________ > 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]
