[Tools-discuss] Re: Deb/IESG: Re: [Last-Call] Warnin g and removal of message

Nathanael Ritz <[email protected]> Tue, 19 May 2026 10:44:28 -0600
Newsgroups gmane.ietf.tools,gmane.ietf.general
Message-ID <CAHxYnaPsLHjJP1L2FazdCsjR3KM+T-wQ=4d_XPQymWcMh_1=eQ@mail.gmail.com>
Given the back and forth (that I just stepped on), I’ll jump in and add my
agreement to the suggestion by Toerless.

Cheers,

Nathanael

On Tue, May 19, 2026 at 10:22 AM Eric Rescorla <[email protected]> wrote:

> On this matter, I largely agree with Toerless. Messages sent to the IETF
> lists, even inappropriate ones, are part of the record of our process.
>
> While may be contexts in which the IETF is required to remove messages
> from its archives, this does not seem to be such a case.
>
> -Ekr
>
>
>
> On Tue, May 19, 2026 at 7:59 AM Toerless Eckert <[email protected]> wrote:
>
>> Dear Deb, IESG
>>
>> For matters of full historical transparency i would really like to see
>> those "redacted"
>> messages not be completely eliminated, but instead moved to some
>> "quarantine" mail archive
>> location, so people who want to make their own judgements can do so. And
>> for example
>> only an email like what you sent here could contain a pointer to such a
>> redacted message,
>> and i wouldn't need to be otherwise searchable.
>>
>> As an example of who and when someone would want to make a judgement:
>> I for once would likely be interested to inform myself about such cases
>> if i was in
>> Nomcom and wanted to get an idea who folks running for re-election are
>> doing their job.
>>
>> Standard disclaimer: This suggestion is of course NOT meant for cases,
>> where legal
>> reasons would make this transparent archiving inadvisable.
>> of cour
>>
>> Cheers
>>     Toerless
>>
>> P.S.: Please don't take this in any shape or form as having an opinion
>> about the
>> decision one way or another, this is purely about the described process
>> detail.
>>
>>
>> On Tue, May 19, 2026 at 10:37:48AM -0400, Deb Cooley wrote:
>> >  This is an official warning to Soatok Dreamseeker per RFC 3934 Section
>> 2
>> > [0], regarding the message sent in reply to
>> > https://mailarchive.ietf.org/arch/msg/tls/YuPYdAeSRJkSkfPZsVxGtbLwAb4/
>> > (also sent to the last-call list).  The content of this message is
>> > disruptive to both the TLS working group progress and IETF Last Call
>> > progress.
>> >
>> > In addition to this warning, the message will be hidden from the mail
>> > archive for TLS and last-call.
>> >
>> > Deb Cooley
>> > Security AD
>> >
>> > [0] https://www.rfc-editor.org/rfc/rfc3934.html#section-2
>>
>> > --
>> > last-call mailing list -- [email protected]
>> > To unsubscribe send an email to [email protected]
>>
>> -----------------------------------------------
>> Tools-discuss mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> https://mailarchive.ietf.org/arch/browse/tools-discuss/
>
>

-----------------------------------------------
Tools-discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mailarchive.ietf.org/arch/browse/tools-discuss/