[email protected] writes: > What is the magic incantation? See https://web.archive.org/web/20251011204330/https://mailarchive.ietf.org/arch/msg/ietf/yfoyRhLt5QrJxmfl9YuZrB4F6OI/ for a guide through the maze of IETF documents leading eventually to the magic incantation "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" to express the situation that "the Contributor does not wish to allow modifications nor to allow publication as an RFC".
As an example of how well buried this is, yesterday a former IETF chair wrote "it continues to puzzle me why anyone trying to contribute to the IETF standards process would send email to a WG with an added condition forbidding derivative works based on that email ... I see no reason why the IETF would suggest boilerplate text for such email" as if the incantation weren't already specified in IETF rules. But there _are_ occasional examples of people using the incantation, and the rules are clear once you manage to dig them up. ---D. J. Bernstein P.S. For readers bumping into this message who haven't seen the context: Please see https://blog.cr.yp.to/20251004-weakened.html to understand what's actually going on here. ===== 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]
