Paul Wouters writes:
> Your email dated Oct 13 2025 still contains a disclaimer that attempts
> to modify the IETF Standards Process.
Please clarify what your claim here is referring to.
1. Are you referring to the sentence saying "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."?
2. Are you referring to the next sentence, which says "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'."?
3. Are you referring to the sentence after that, which says "I'm fine
with redistribution of copies of this document; the issue is with
modification."?
4. Are you referring to something else in the document?
> I also already explained why your current process modifier boilerplate
> cannot be valid in any stretch of interpretationi [4].
Please clarify what your claim here is referring to.
5. Are you referring to something the previous claim was referring to?
(Previous claim meaning the "Your email ..." sentence quoted above.)
6. Are you referring to something the previous claim wasn't referring
to?
My understanding is that your refusal to process this complaint is
subject to appeal, but for this I need clarity regarding which aspect of
the complaint you're objecting to. With all due respect: Your wording
("disclaimer" and "process modifier boilerplate") is very far from
clear, and I'm having trouble filling in the blanks given that your
claims seem divorced from reality no matter how they're interpreted.
Dodging clarification questions would be an abuse of power, forcing me
to spend time addressing multiple interpretations of your claims while
you leave yourself free to then claim that I'm attacking a strawman.
---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]
