Re: [Uta] Recall Petition pursuant to § 7.1. 1 of RFC 8713: SEC AD Deb Cooley
SohaAli <[email protected]> Tue, 21 Jul 2026 11:32:19 +0000
| Newsgroups | gmane.ietf.general,gmane.ietf.uta,gmane.ietf.tls |
|---|---|
| Message-ID | <DBAPR05MB7000D57275CBF408B3A5D390F6C22@DBAPR05MB7000.eurprd05.prod.outlook.com> |
I really want to unsubscribe. Having some trouble doing it. Could someone please assist Sent from Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Brian E Carpenter <[email protected]> Sent: Tuesday, 21 July 2026 02:14:57 To: Eric Rescorla <[email protected]>; Timo Gerke <[email protected]> Cc: Unsing TLS in Applications Mailinglist (IETF) <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: [Uta] Recall Petition pursuant to § 7.1.1 of RFC 8713: SEC AD Deb Cooley Eric, In fairness, it was copied to the IETF list, so one of the conditions in RFC 8713 was met ("announced to the IETF community"). The others are not, as far as I can see. Regards/Ngā mihi Brian Carpenter On 21-Jul-26 05:33, Eric Rescorla wrote: > This is not how recalls work. A recall petition needs to be signed by 20 nomcom-eligible > IETF community members and is sent to the ISOC President [0]: > > https://datatracker.ietf.org/doc/html/rfc8713#name-member-trustee-and-director <https://datatracker.ietf.org/doc/html/rfc8713#name-member-trustee-and-director> > > What you have here is just an email to the TLS mailing list, which has no effect. > > -Ekr > > > [0] The ombudsteam can also initiate a recall in cases of harassment but you don't appear to be claiming that this is that. > > > > On Mon, Jul 20, 2026 at 10:26 AM Timo Gerke <[email protected] <mailto:[email protected]>> wrote: > > Dear Community, > > I hereby initiate a Recall Petition pursuant to § 7.1.1 of > RFC 8713 against SEC AD Deb Cooley, regarding a significant > breach in confidentiality of communication. > > While her technical competence within the Security Area is > recognized without a doubt, the NomCom MAY consider to verify the > trustworthiness of the named SEC AD based on the documented > procedural infractions. > > To safeguard the fundamental integrity of the IETF standards > process, the technical evidence regarding this unauthorized > backchannel disclosure is provided below. > > TECHNICAL EVIDENCE OF SECURITY LACK > > 1. My Private Notice to SEC AD Deb Cooley's officially in > Datatracker regisered Mailaddress > Message-ID: <[email protected] <mailto:[email protected]>> > Date: Tue, 12 May 2026 10:15:36 +0200 > MIME-Version: 1.0 > User-Agent: Mozilla Thunderbird > Content-Language: en-US, de-DE > From: Timo Gerke <[email protected] <mailto:[email protected]>> > To: "Deb Cooley (IETF, AD Security Area)" <[email protected] <mailto:[email protected]>> > Subject: Notice: Operational Analysis & Cluster C430 Deadlock > (TLS/UTA) > > 2. SEC AD Deb Cooley's response > References: <[email protected] <mailto:[email protected]>> > In-Reply-To: <[email protected] <mailto:[email protected]>> > From: Deb Cooley <[email protected] <mailto:[email protected]>> > Date: Wed, 13 May 2026 06:42:16 +0100 > Subject: Re: Notice: Operational Analysis & Cluster C430 Deadlock > (TLS/UTA) > To: Timo Gerke <[email protected] <mailto:[email protected]>> > Cc: Eric Rescorla <[email protected] <mailto:[email protected]>>, [email protected] <mailto:[email protected]> > > > Best regards, > > Timo Gerke > _______________________________________________ > Uta mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] <mailto:[email protected]> >