RE: Ombudsteam remedies and confidentiality

["Adrian Farrel" <adrian@xxxxxxxxxxxx>]

Hooray and thank you!

 

Sorry / not sorry for making you do this. But I hope it helps bolster the important work the team does.

 

Cheers,

Adrian

 

From: Allison Mankin <allison.mankin@xxxxxxxxx>
Sent: 05 November 2024 21:58
To: Roman Danyliw <rdd@xxxxxxxx>
Cc: S Moonesamy <sm+ietf@xxxxxxxxxxxx>; ietf@xxxxxxxx; Pete Resnick <resnick@xxxxxxxxxxxx>; Ombudsteam <ombudsteam@xxxxxxxx>
Subject: Re: Ombudsteam remedies and confidentiality

 

Closing the loop here - it took a little longer than we hoped, but the documentation of the Ombudsteam procedures is now available on the ombudsteam page:

 

https://www.ietf.org/contact/ombudsteam/procedures/

 

 

 

On Wed, 28 Aug 2024 at 13:43, Allison Mankin <allison.mankin@xxxxxxxxx> wrote:

Hi S and Roman,

 

We appreciate the interest of the community in this, starting with Adrian's plenary question. 

 

As Pete mentioned, we want to complete the new ombudsteam members' onboarding process before we publish the methods document. The training sessions, if all goes well, will be complete September 20th. This makes us a little bit behind Pete's statement in Vancouver, but not much. We have started the document and hope to share it within September. 

 

Allison for the Ombudsteam 

 

On Wed, Aug 28, 2024 at 08:54 Roman Danyliw <rdd@xxxxxxxx> wrote:

Hi!

> -----Original Message-----
> From: S Moonesamy <sm+ietf@xxxxxxxxxxxx>
> Sent: Wednesday, August 28, 2024 3:03 AM
> To: ietf@xxxxxxxx
> Subject: Re: Ombudsteam remedies and confidentiality
>
> Warning: External Sender - do not click links or open attachments unless you
> recognize the sender and know the content is safe.
>
>
> Hello,
>
> RFC 7776 (Section 4.1) stated that: "These [operating] practices must be
> discussed with the IESG and published in a publicly visible place (such as on the
> IETF web site).  Discussion with the IETF community is encouraged and, ..."
>
> RFC 7776 was published in 2016.
>
>    (a) The operating practices have not been published up to this day.

I'll let the Ombudsteam answer for itself on their planned next steps.

I will share that when Adrian Farrel asked an almost identical version of this question at the IETF 120 plenary, Pete Resnick provided a timeline of publishing these practices as "well before the next IETF Meeting" [1].

==[ snip ]==
> ADRIAN FARREL:
...
RFC 7776 is now eight years old. One of the things it says is the Ombudsteam is
responsible for devising and documenting their operating practices. These practices must
be discussed with IESG and published in a publicly visible place, such as on the IETF
website.
It was understandable in the first couple of years, the processes were not written up
because they were being developed, and it's a self-organizing team, but what I would like
to do is ask you to put a bit of pressure on them now to get those processes properly
published.
...
>> PETE RESNICK: Funny you should mention that, Adrian.
Yes, we are very much aware of this, and we agree it is something we need to do.
...
We are, I believe, going to pull it off the first or so week of September. Once we
get everybody onboarded and trained up, we're using that moment to sit down and write
up what we currently do, make changes to what we think now we really should do, and get
those to the IESG and the public. Hopefully, you should see those well before the next IETF
meeting.
==[ snip ]==

Regards,
Roman

[1] https://datatracker.ietf.org/meeting/120/materials/minutes-120-ietf-202407250030-00