Re: Ombudsteam update

Allison Mankin <> Tue, 15 January 2019 18:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EC861130F37; Tue, 15 Jan 2019 10:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 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] 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 cHwxNWY1OcuE; Tue, 15 Jan 2019 10:45:46 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0B18F130F46; Tue, 15 Jan 2019 10:45:46 -0800 (PST)
Received: by with SMTP id c73so1704854pfe.13; Tue, 15 Jan 2019 10:45:46 -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=vk0x5eEj59VTV+2a5KYEe91kiKeUrtn8DYu+skPJRbI=; b=DCJGGG+bCRHcDBWPrq9XYzfGAWXJ9/7np2xyqZLzBV3thdD+yC43VXF6GNL0aOwKm8 rzpjhHSnIPSYkfMhU826LoZ4PUk/wy5A0epidMw9s2H7wQwpNAa8hzy/2h8iQaEMh2hP 44spLfRS8O5D2oUJoY81iWSXJVwWolzLHqyXxIzOeVsG08i0Gw+En9/QRJeW5GYJXN2E XWjbq4OEszvciFLVMAfaHhf9AFKIqyjhdU1FI7wB1IwZxlI7O8myS3SoJXGG948QoGsv a/3v4uJ0Ri+MmP3EEc3F+1T5y35yJon3OhUIZSe60bk3OK3fW004TdkLN9J+0YT9N5+Q eGAA==
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=vk0x5eEj59VTV+2a5KYEe91kiKeUrtn8DYu+skPJRbI=; b=haQnzbvdhx82hSmHxBe0czgpMS1Lsu4IghCw56fqaTcx7pAC93FPIDk7cc4dD1KX0S m+Z8keFMs4NujRjC6zrglCSRxsbMHVuPoFf7P9nnA+vo7jmWt5Q0vJQJbUueaZSLhDrT sa/yOW37haF/NdFV597FsI8IGCx0aMIE6Ffankm3lyHQga87YBt+sOsVv0ZPloUINvBu LKiVyeB7ayeqnAnEZnWEku5LyBpZr3Ov6+T1c5od1inS4BumH4cYt+emU8oMA3sbbjFt WEH7hCEMZc+2V3qV2LvoSJgWgtW6i6DzMY/o22qlD0pCnV6z+FpOelOmnCY8KK93wmiU b7sg==
X-Gm-Message-State: AJcUukehz6bev6ehjzSAGaEHhCX8GWiEqN9VniZ1pnlsYMtrvfhrf24u aLjSjetaVvA7+boWXffnuxnNJFLhQT/bhyA6sYDz1g==
X-Google-Smtp-Source: ALg8bN4+PSRDLdC2sEt+Z/7pC4XzuMrRn3M4za5+0p4uNa5nCDUscICaEJGXm/re5nIPGFGEzH6erQ43Ob0+MZUNP94=
X-Received: by 2002:a62:3603:: with SMTP id d3mr5628987pfa.146.1547577945502; Tue, 15 Jan 2019 10:45:45 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Allison Mankin <>
Date: Tue, 15 Jan 2019 13:47:17 -0500
Message-ID: <>
Subject: Re: Ombudsteam update
To: Abdussalam Baryun <>
Cc: ietf <>, IESG <>
Content-Type: multipart/alternative; boundary="000000000000b43af5057f83913b"
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 18:46:00 -0000

By the way, I agree very much that the ombudsteam should maintain a
responsive service to the community (your broader point).  This is an
important commitment for us to make.

Member of Ombudsteam

P.S. apologies for leaving out some letters of your name in the first
message I sent to you, IETF, and IESG.  Typo :-(

On Tue, 15 Jan 2019 at 13:39, Allison Mankin <>

> Hi, Absussalam,
> 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