Re: Ombudsteam update

Allison Mankin <allison.mankin@gmail.com> Tue, 15 January 2019 18:37 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 9C28F130F06; Tue, 15 Jan 2019 10:37:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
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: 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 0DOLPyYKFtbG; Tue, 15 Jan 2019 10:37:56 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 BBDA1130F03; Tue, 15 Jan 2019 10:37:55 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id w4so1695079plz.1; Tue, 15 Jan 2019 10:37:55 -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=ejrMcIaP1oQ8JJZp0KH0GHHkTuksyUp4JjQfuunmcgQ=; b=ZtDkUQf9rtldtDcK9DRXVNWJzctk+gZnyJa69rq1JHBhsNWp7M+DG81hufBIwKljxe 3gtj+58WlkAjPoM8AmQNGifEtJdueF/lbY07dNAoOHPaCTl+YCBaBf8eD8dN2kT3dzH2 oIBYzjmf3exGd6yMJkI+0P+2A2zMvHQJr3NK1GnLY9iBErOHoGUWguwajV2WdrpBsS1h Oui6ADlizMXr1IUM5JCEMTnUq6LQtSJ8c+LiHaXnOIaygi/thjZpbpAVh359LWVdMdgj +K2MwQmcpTkC9Kcj5JJpdOJIDTdG7xeXrchNpFFZTppDMDB7LxhzlPU1WI1nHF6OJt0F M+/A==
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=ejrMcIaP1oQ8JJZp0KH0GHHkTuksyUp4JjQfuunmcgQ=; b=CE/uljqxS16GXy6PkVpRts7G/rnZtpSfZnmxEfP30iYsKqcKMhdDkQVX7vQLvdh0A4 YYI7BXOCNFfyDqLF3l71JhZG/l7PUB9eHQycgham09o1nyG6aRlCzyE7Lf0ORG3UJBTA QQJYcnA+nDUc2xNCXIjcGD+Y5ht8D/3jgcL/0zuHSLArApokm8WOIMMJaEoFsSq7Bc5c KPHstLKAfCVQ8nkLHstWQxsutCVhG/tsqwQP5567wHot1yYcFA2GbxbdvTvED63GRv6B DBK+UtXDjYV4EHUDNjtiVyGOPtgdblExWSNGLjhzQNRi5Tmu2nTUwk6+TwAYO04lYOEG 4vjQ==
X-Gm-Message-State: AJcUukejnCwyaIZPB3QPNXj5nUpdIAxPihByTa5u+UAlFswbIoUTsNSO EBIdFUmetLwA3rrhTOgGVh2aMqlsW0lIFlTlqbM=
X-Google-Smtp-Source: ALg8bN7DBaSiIlyC076q71dFEG2NYh1C6UL1y+Djyh1Cl6ZPtAuVCTEporXE/eWl5WELKufq5L7ZzB1yGrYlsyCU9qk=
X-Received: by 2002:a17:902:2a66:: with SMTP id i93mr5400689plb.113.1547577475245; Tue, 15 Jan 2019 10:37:55 -0800 (PST)
MIME-Version: 1.0
References: <82BCE48D-9B20-4819-82A0-BD8378AFBED5@ietf.org> <CADnDZ8_6SbSe3QP2FkWjW_fkDehiVUt9HPPAFyF1itz8ZfyBBA@mail.gmail.com>
In-Reply-To: <CADnDZ8_6SbSe3QP2FkWjW_fkDehiVUt9HPPAFyF1itz8ZfyBBA@mail.gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Tue, 15 Jan 2019 13:39:28 -0500
Message-ID: <CAP8yD=vAk1+pkPY9LQktV6mHKYC=uWRreV513W2rPj6U=jgtzg@mail.gmail.com>
Subject: Re: Ombudsteam update
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: ietf <ietf@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000acaa3e057f83750f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MsByO2g7z1HPlC9IDZ85fraWlEk>
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: Tue, 15 Jan 2019 18:37:59 -0000

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