Re: Ombudsteam update

Abdussalam Baryun <> Wed, 16 January 2019 17:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6CA2D124BAA; Wed, 16 Jan 2019 09:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xrccm0NPkE82; Wed, 16 Jan 2019 09:22:07 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C139D124B0C; Wed, 16 Jan 2019 09:22:06 -0800 (PST)
Received: by with SMTP id w25so8379201otm.13; Wed, 16 Jan 2019 09:22:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JuDMQ8DZyKzW6ALGZyLAKRp30Xdw5YTOQrO8jx3PZ38=; b=WneFfs60R3L7GUtbVammS6e787kXMZrS6ifduoZenoMsd+MG+6B/dqe/9+K/3dxsiH 9WB7fqJSPZVAtB8B1YbN6GYQR8u+Hfkyh4BnoxLzkkud8iUbmFoe1sOAfPlv6vYHVwhj T+e9pUcxRma9ZdbmaQNWoCr4zOIQFypWcAAdBRr0/yjs47oM8nKFBbwpnIEIcJ1JoYIS kRc6t0d6Uf+ZTRcX/WY0hRKscOBFzV1njpSXc0LY2l0B3bAC34L0z13XbkuwvapuxjR6 F6ZyqwNaGzdj9tj8dDVpoFUG1TDwcZQDYBX1mftVeZb/2fHMkRKKiMaYx0RrFZIXixDI UyaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JuDMQ8DZyKzW6ALGZyLAKRp30Xdw5YTOQrO8jx3PZ38=; b=fEW/C1hCC2kb6rTKBenuicjEIgwV1EZ6IO7TUn8Wya/YdvvB7jDNoqcMYVaatXFwC1 ngURoVscllJ7lCe4kf8WaaMlRhMGRdaZryNATk7Qt66q1SLAj81ZeZNKpjpq1ZBu9ccF nUJ0GmVOBGXKfZHgdFNLWhNpj2yDpf+WDecsigkKLV5sgwiM6tbgQPVXNhACrdXP4BWq ASzEyf77DeA4MOa1osTSC+xnFU6uilsMVR974c5E2awTCjPm4R5c8rCiPocqnsfjAtdk ye3McHcRO6tlqboPWVn6HURya7oGdrqdAwI4uwSbRKLE8E98A/oAEdSQblo560mhALAE Wojg==
X-Gm-Message-State: AJcUukfI9U58idcvjrzXn6fCYLZyXHGvayIFmSo5Vli3rdJyIfq356Y5 UPmdc421IluobbladTzlnoZ6UW/EwovQNSsYLpc=
X-Google-Smtp-Source: ALg8bN4Ktp/HES+ZuybLqDQSSeFzUt34dmpoYQn1SUXf0m8pr63TK1VHRur6I9x8x9XVpBmv8385og9GQ2tlkoyesZk=
X-Received: by 2002:a05:6830:d:: with SMTP id c13mr6588325otp.82.1547659325943; Wed, 16 Jan 2019 09:22:05 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Wed, 16 Jan 2019 19:21:48 +0200
Message-ID: <>
Subject: Re: Ombudsteam update
To: Allison Mankin <>
Cc: ietf <>, IESG <>
Content-Type: multipart/alternative; boundary="0000000000005b33b3057f9684b9"
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: Wed, 16 Jan 2019 17:22:08 -0000

Hi Allison,

Yes I have the email which was sent on Monday 9th October 2017 at 6:06 AM
to, and I only sent once to
those addresses and my email was not sent in 2018.

IETF Participant from Africa,

On Tue, Jan 15, 2019 at 8:37 PM Allison Mankin <>

> 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 <
>> 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 <> 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 <>.
>>> Regards,
>>> Alissa Cooper
>>> IETF Chair