Re: Ombudsteam update

Allison Mankin <allison.mankin@gmail.com> Wed, 16 January 2019 18:09 UTC

Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B70E2124BF6; Wed, 16 Jan 2019 10:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0KbVOUfKO_v; Wed, 16 Jan 2019 10:09:54 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82CFC124BAA; Wed, 16 Jan 2019 10:09:54 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id w4so3390202plz.1; Wed, 16 Jan 2019 10:09:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2KFHsr27FxFlqK9A4+v8G96wr3eaJ/fb8RF6pHygYpE=; b=b+hEQIbxcFeLZMfLoIXewWvnRejCtCLOMInRzg0yLRidJTaHubap5US7WaYeA13yp0 vQc6sFUsHaA16d9fZuodmc5ifTULWY3M9SbI7WyUZDV1Q6nvCSDZpMZPv0HPLC2UIU52 ms2dqkthft6rYPtbYwbhbQxjETrcrhjYlIJY7w+OWdSDI52XEbC1SZRUrO2um7grq2CN IUAV9oaHDEaQByETaEePT2ezJv9X8BIfC0tnUPO5YeCcbHOiFx+MpCMvRQAb0Fwak7P5 Pd50mXAXpUyejnFdoa5o5kEgOy2CSQZoO0nJpGnPageCS0SVS+qpaHpNTg5Fknv44sc5 gDTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2KFHsr27FxFlqK9A4+v8G96wr3eaJ/fb8RF6pHygYpE=; b=r3cOpvO8u8Gv8u5tNpX1CoXIe4yhGF865LjdHGVMLQUDUtqCGe4pKO35f9NNRXIsV3 nW+9qHIXMyk/6hu9z1deKKrHXlpdSlNTdMbuIdKGPqelyuH6pSbuHOQhc/ItMsJ8SPGG RK1v0j2BtYVLu9B0PAHb3/Hpz/NSHfuyN8xf5kT2IqKvRYhBLnxHtg01Ogl/nGDIewHg rZRHBnhPldEP5wvNjJgAPc0VR7aWuJCjs2BvjiaH5SDtq8ID15jDZC5PJOyqXrTSuZVd Q5Qq+nXIwi37JQO+DCENpyvEMSSiGrrW18Fnwii7Ue676neRQLIr36UpUOFdE5ko2H7U L+4w==
X-Gm-Message-State: AJcUukcw7xxc7rbZnSRzeDRRZ1wC9AlmAAwDtlczvUEvp9Vatk41Zsyn upL+eygDK1XfL3a1oJ/rxlKbOqmc2jGg1+o/BDIMuQ==
X-Google-Smtp-Source: ALg8bN4H+7DLNj1UjQEQvcVlOlmbYpFSz69YF1aZ1B6QQzayN/fxcs605XvhlaAQ9FjuM3Iln++AZeqrXg7uk5u0bYc=
X-Received: by 2002:a17:902:8d8e:: with SMTP id v14mr11069742plo.133.1547662193826; Wed, 16 Jan 2019 10:09:53 -0800 (PST)
MIME-Version: 1.0
References: <82BCE48D-9B20-4819-82A0-BD8378AFBED5@ietf.org> <CADnDZ8_6SbSe3QP2FkWjW_fkDehiVUt9HPPAFyF1itz8ZfyBBA@mail.gmail.com> <CAP8yD=vAk1+pkPY9LQktV6mHKYC=uWRreV513W2rPj6U=jgtzg@mail.gmail.com> <CADnDZ88m51dADnQLkOMcLVtJY=3kOwGzCRFPu9YZJ9THednAHA@mail.gmail.com>
In-Reply-To: <CADnDZ88m51dADnQLkOMcLVtJY=3kOwGzCRFPu9YZJ9THednAHA@mail.gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Wed, 16 Jan 2019 13:11:29 -0500
Message-ID: <CAP8yD=uhp-GKoTg9BmO7vYAErDA2jKWF8uFjUV=_gd1Jd28wog@mail.gmail.com>
Subject: Re: Ombudsteam update
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: ietf <ietf@ietf.org>, IESG <iesg@ietf.org>, Ombudsteam <ombudsteam@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ba1c7057f972ff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5sVW1wnHV0ZenVL-e1opOYQxbK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2019 18:09:58 -0000

Hi, Abdussalam,

You are right, I misread the date on the mail when I was writing yesterday
(I have a kind of calendar dyslexia).   I too have that mail, but what I
wrote yesterday is still the case.

Please let ombudteam know (adding back ombudsteam to this email) if you
have a continuing issue, as my mail said yesterday.

I will send you another message that is between you and me and my
colleagues in ombudsteam, because of the confidentiality rules in our BCP
(RFC 7776).

Allison



On Wed, 16 Jan 2019 at 12:22, Abdussalam Baryun <abdussalambaryun@gmail.com>;
wrote:

> Hi Allison,
>
> Yes I have the email which was sent on Monday 9th October 2017 at 6:06 AM
> to ombudsteam@ietf.org, and allison.mankin@gmail.com. I only sent once to
> those addresses and my email was not sent in 2018.
>
> Abdussalam,
> IETF Participant from Africa,
>
> On Tue, Jan 15, 2019 at 8:37 PM Allison Mankin <allison.mankin@gmail.com>;
> wrote:
>
>> Hi, Absussalam,
>>
>
> my name is Abdussalam, meaning serving God the peace,
>
>
>> I can't find the 2017 issue, but I did find the one in 2018, and not my
>> reply.  I recall sending you a reply.  I'm going to send you another one
>> now, with apologies since you did not receive it.  Also you should inform
>> me if you find a request from 2017.
>>
>> Allison
>>
>> On Sat, 12 Jan 2019 at 04:04, Abdussalam Baryun <
>> abdussalambaryun@gmail.com>; wrote:
>>
>>> 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
>>> AB
>>>
>>> On Fri, Jan 11, 2019 at 7:36 PM IETF Chair <chair@ietf.org>; wrote:
>>>
>>>> The IETF ombudsteam <https://www.ietf.org/contact/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 <
>>>> https://www.ietf.org/blog/ietf-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 ombudsteam@ietf.org 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 <https://tools.ietf.org/html/rfc7776>;.
>>>>
>>>> Regards,
>>>> Alissa Cooper
>>>> IETF Chair
>>>>
>>>