Re: Ombudsteam update

Abdussalam Baryun <> Sat, 12 January 2019 09:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 87BAF12785F; Sat, 12 Jan 2019 01:04:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mxGt8Kk09RZS; Sat, 12 Jan 2019 01:04:17 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 67CB9124408; Sat, 12 Jan 2019 01:04:17 -0800 (PST)
Received: by with SMTP id a77so14203681oii.5; Sat, 12 Jan 2019 01:04:17 -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=LjVQs+FtpDq0WoMWxpDFiX6z8ZyPWO1p0fY5XO5hJEg=; b=ZH1yVEe58/3FHneSn5/rrZaEJnuJN07fF38rcQZXI/hyHbRZ51mCmTCnG8QqEnLz/w JNY1vwcIwxGvGTi0OxwUJcJEYGQPEa3JDlJx3FFGBzfbPB4n9xokCynxP1rl39uDpzif x1cuxDE3drgbXRODD+GBm4D1I3k62on59Jfky1vZZahDEsvtnw5dGUYQLrCebMQ0djFw ghkkEC2NdHDRYYzB2KgoYayXmzBguevZdlu8r+uXZTjx6l3vonDCr/vIGaOzB/PBS9Md 4ukLWLGM1If4/VIx9kwzkiLTC7Q95d/5C0lvimqTPRsdMtIBv3yBWe+56Cv7BrbV8NNs J83Q==
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=LjVQs+FtpDq0WoMWxpDFiX6z8ZyPWO1p0fY5XO5hJEg=; b=CvLDPzd6hoAiUYbpG1+1KF9FfZ/D0phCXPkAD0Q7j6oIOYjPB3l0qwq5rcR6IUKflA DMWyX7vOVsL0MYfvW6QMU29LZpKuQHgsBmvk8xoJqmDPX6QmhqB5F/CW8txiG+XgYIDZ gNEfPyALsLQuMBjIZn72jIOLDcVdkjVHVYF4ARSQ92/DQNBhXC0NlxBREfHK3/sLHMp9 iK7kff7rxynURRtUaw1yZz2uOmdSKCW7GeISAf10gopK0GIuN3ntH0sekf0EZdNcHuq8 yaGPqNyxzLiysEPasSDAMIXEQA5xCUYb7wDEt+/lIv4k3+20PUILbeE7uDO9sWlO56jC sUjA==
X-Gm-Message-State: AJcUukfFlFC7k1vsBfJtCXyM/pQxLXtPYMe9M/i8AY00iTM8YYvkK7/0 HFI91E9BlfulSvduEiuwxttRCzWypWPZmM/d8R/qLsR/
X-Google-Smtp-Source: ALg8bN5ZqMTSG54em4TzI4KVCl+PRTZbGWRoOHT/SzWcS083Bgw/FmnuQg9lHfITBttQzgNZ3l4Ec8YsC0ClZ07ADRE=
X-Received: by 2002:aca:2d3:: with SMTP id 202mr10721303oic.214.1547283856488; Sat, 12 Jan 2019 01:04:16 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Sat, 12 Jan 2019 11:04:02 +0200
Message-ID: <>
Subject: Re: Ombudsteam update
To: ietf <>
Content-Type: multipart/alternative; boundary="000000000000a1fdd3057f3f1867"
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: Sat, 12 Jan 2019 09:04:20 -0000

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