Re: Ombudsteam update

Abdussalam Baryun <> Fri, 18 January 2019 06:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 36BE0131124; Thu, 17 Jan 2019 22:18:51 -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 6dN-bMqYjone; Thu, 17 Jan 2019 22:18:49 -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 DED1413111E; Thu, 17 Jan 2019 22:18:48 -0800 (PST)
Received: by with SMTP id s13so13463875otq.4; Thu, 17 Jan 2019 22:18:48 -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=JkgO3r9v+tqROrHsnWbvxNUx0myzXQ0qe7yJ94a1muU=; b=dpxgVlY/SD1hlNoL2M0Vf/op8/tRMcdDANJsb/vZ2NjHcZbQ54M5lRykxIbwhASTwH qWA8CT22dXm6Gfljk9r1+2+KvhtPzEu1+6XsAoV168cppu7Yr/vfAhFR9iPshBeRTrZC U/1ALNVE1IaaNrkJSpq21xMoCujOhksabt+yQk8R6RQBUBI3KsBXzep3PqHNcH7FWS7L Hmda9jopNc40CdxOLyrBJau3mkGmZTuqx62jvHA2l3ImbLNJDoAtWgMpv5X9LGqUyUKe Kwxl2rUgcaXxtU1Q7wK7g9ORQpT8p9p9ti+3NmVi9wZY9kzYm7W709EsmL28daeUOes1 l7wA==
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=JkgO3r9v+tqROrHsnWbvxNUx0myzXQ0qe7yJ94a1muU=; b=iQ7K9No6GGfzVPb3DNAOBgpj7bM7xnMyqElZnn6QiL1OmahwN15FVbjPPVtn3NEX6l b4OP0Ex6SP01LgjARPMRGRw8FczMtmwC4iH0GuQUdSEMfCPfUdl4mxDNnIHzCIP92apR Y6gQrq8A8a5kNvv/hsXY47r6W33mXbDreqReTRJbRHAm4TP+N1D6g3s6Gfy/BmAy/+th wcX+YnFh7UjAVfa18MIUVhnNVIRUZuFKkTk0rGrri1lgOifCm5j/kHJwioOa6d+IOULS QvBkQEOcQD0RPrGuhyB0/8YbFJsbZza5/2Kln6xWAIi4Qh4LrapFRcyRYBToAYaK1SUT 02Vg==
X-Gm-Message-State: AJcUukfQGHyElrn6pAaN/ekQCnY94tKCd+e1gYkw0+GbGpBVeOxzrkMm QDb0S9Dfd0/peFBhR9wN3J3Q521z8NgOWof8JKU=
X-Google-Smtp-Source: ALg8bN7v+FAMFVc4QsIAjn1nXg55fh9nDvejApl0X5WUdU5B/I6GLuwyV3LCKPHnRN/JMRCkq66NXGqK8LnZwleY9rg=
X-Received: by 2002:a9d:7b42:: with SMTP id f2mr9919368oto.184.1547792328212; Thu, 17 Jan 2019 22:18:48 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Fri, 18 Jan 2019 08:18:31 +0200
Message-ID: <>
Subject: Re: Ombudsteam update
To: Allison Mankin <>
Cc: ietf <>, IESG <>, Ombudsteam <>
Content-Type: multipart/alternative; boundary="000000000000e8c573057fb57ba3"
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: Fri, 18 Jan 2019 06:18:51 -0000

On Wed, Jan 16, 2019 at 8:09 PM Allison Mankin <>;

> 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.

Yes I have a continuing issues, and the ombudsteam will be informed in the
coming days, however, the biggest problem/issue was the IPWAVE AD and
chair MUST follow up to make discussions easy and productive. My formal
public message was ignored by IETF AD office, then formal private message
ignored by ombudsteam, so I was powerless. It is strange that it is easy of
IETF-members/selected-members to ignore/drop formal
emails/messages/letters/requests in IETF/IESG.

IETF should update such procedure that gives that opportunity/error, so
that IETF becomes fair and treats all world communities equal.

> 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).

ok, this will be my last public message related to the subject, the purpose
was to help make procedures/RFCs fair/updated/working-right. However,
making things private/confidential without management can help issues to
grow with no fair solutions.

IETF Participant from Africa,

> On Wed, 16 Jan 2019 at 12:22, Abdussalam Baryun <
>>; wrote:
>> 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.
>> Abdussalam,
>> IETF Participant from Africa,
>> On Tue, Jan 15, 2019 at 8:37 PM Allison Mankin <>;
>> 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 <
>>>>; 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