Re: Ombudsteam update

"Livingood, Jason" <> Tue, 15 January 2019 17:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1011F130DF6 for <>; Tue, 15 Jan 2019 09:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rOF3T5Njmfoc for <>; Tue, 15 Jan 2019 09:38:41 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1805C130DCB for <>; Tue, 15 Jan 2019 09:38:41 -0800 (PST)
X-AuditID: a2962c47-c11ff700000011d4-2e-5c3e1a8853fc
Received: from ( []) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by (SMTP Gateway) with SMTP id 3A.C1.04564.88A1E3C5; Tue, 15 Jan 2019 10:38:16 -0700 (MST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 15 Jan 2019 12:38:33 -0500
Received: from ([fe80::3aea:a7ff:fe36:8a94]) by ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1466.012; Tue, 15 Jan 2019 12:38:33 -0500
From: "Livingood, Jason" <>
To: Abdussalam Baryun <>, ietf <>
Subject: Re: Ombudsteam update
Thread-Topic: Ombudsteam update
Thread-Index: AQHUqdQpuGJ1eio+80OmC4CUvovQOKWrq68AgATy7AA=
Date: Tue, 15 Jan 2019 17:38:33 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_45EDBC1F2A3C4EA0B31761D9C5073AB3cablecomcastcom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsWSUDRnsm6HlF2MwZs2BYtvN1qZLJ5tnM/i wOSxc9Zddo8lS34yBTBFhdsUpRaXJuVmligUpxaVZSan2iolJxYr2XEpYACg0pzUxOJUx+SS zPy8Yn0MNTb6MMPsEsIzdjw6wFSwI6HidtNPtgbGp7FdjBwcEgImEqcaK7oYuTiEBHYxSTxs 3MII4bQAOR1voJzTjBLLHr9i62Lk5GATMJO4u/AKM4gtIuAhsezufDBbWEBO4tCxRewQcXmJ q7+fQtVYSUx+sgzMZhFQlZi36QcTiM0r4CJx/fsOFhBbSKCJUeLgHScQm1MgUOLInstgcUYB MYnvp9aA1TMLiEvcejIfzJYQEJBYsuc8M4QtKvHy8T9WEFtUQF/iwacD7BBxBYnt+7exQPSm S+z4O4MZYq+gxMmZT1ggasQlDh/ZwTqBUWwWkhWzkLTMQtIyCxhgzAKaEut36UOUKEpM6X7I DmFrSLTOmQtlW0lMmP+UCVnNAkaOVYy8hmZGeoamBnomJnrmhpsYgYli0TQd9x2MH87HHmIU 4GBU4uENErOLEWJNLCuuzD3EKMHBrCTCW+ZkEyPEm5JYWZValB9fVJqTWnyIUZqDRUmc9+wz oJRAemJJanZqakFqEUyWiYNTqoExb3Ixx6mGBa9KVHMWqh9ua7xtu6BWgGP+tbod5V0SgVIp WQ/Ova6N33vbsXXlx1P6Moc+xFnHR8S1f9eunJvipP7syJuHv3SWqZ1V41RuLX/ZtEDZZjfv 7p2ix2sYX2xld6qx0t5W2uzZnf971j3DupN/H3ec+PvM/VzNHsfVLl3K+aYXcnKUWIozEg21 mIuKEwEWO4ZREAMAAA==
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Jan 2019 17:38:44 -0000

Sounds like a tools sort of issue. Maybe they need a webform that opens a ticket for the reporter. That person can then check back in online for status. And on the backend the Ombudsteam can automatically report on issues reported over time, current issues open, and issues closed by resolution type (e.g. no action taken, 1:1 coaching, removal from position), etc. On the other hand, I suspect the volume of issues is quite low and that may fail to justify this sort of automation.


From: ietf <> on behalf of Abdussalam Baryun <>
Date: Saturday, January 12, 2019 at 4:04 AM
To: ietf <>
Cc: "" <>
Subject: Re: Ombudsteam update

Hi Alissa,

I hope this ombudsteam procedure is working well with no issues. How does the procedure monitor the time/delay of respond/action? I remember in 2017, I send an email to its email and cc to one person's name mentioned in your email. I did not get any reply (that email sent was ignored by both emails, and is still waiting for reply with very long delay), I noticed then that this ombudsteam is not working well as needed. Maybe there is a problem in implementation of rfc7776 or the procedure needs to be update for better practice.  IETF is about implementing procedures for best practices and for the community needs.

Best Regards

On Fri, Jan 11, 2019 at 7:36 PM IETF Chair <<>> wrote:
The IETF ombudsteam <> is a designated group of people who have been selected to handle reports of potential harassment in the IETF. The ombudspeople serve in support of maintaining an IETF environment in which people of many different backgrounds are treated with dignity, decency, and respect, per our Anti-Harassment Policy <>.

Earlier this week, Linda Klieforth stepped down from the ombudsteam. I would like to thank Linda for her foundational contributions to the team and for all she has done to help create a welcoming environment in the IETF.

Melinda Shore has graciously agreed to join the ombudsteam. Many thanks to Melinda for her willingness to take on this role in addition to her existing duties. Allison Mankin and Pete Resnick continue to serve on the team.

As always, the ombudsteam can be reached at<> or at their individual addresses listed on the web page above. The IETF Anti-Harassment Procedures (RFC 7776) that govern the ombudsteam's operations can be found at <>.

Alissa Cooper
IETF Chair