Re: RFC 7776 and the team that can be reached for help regarding harassment concerns
joel jaeggli <joelja@bogus.com> Sat, 02 April 2016 20:56 UTC
Return-Path: <joelja@bogus.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 6AFC112D156; Sat, 2 Apr 2016 13:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 qIxyBuuqziCH; Sat, 2 Apr 2016 13:56:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1047012D0BB; Sat, 2 Apr 2016 13:56:11 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:51ca:6ceb:88d2:12]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u32Ku7u1065871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 2 Apr 2016 20:56:09 GMT (envelope-from joelja@bogus.com)
Subject: Re: RFC 7776 and the team that can be reached for help regarding harassment concerns
To: IETF Chair <chair@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, 95all@ietf.org
References: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <785eec9c-6a03-2a68-de8c-120992f1567c@bogus.com>
Date: Sat, 02 Apr 2016 17:56:06 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="E8hAb135BihJ7pK9M2oCfd6JN9LaG9D11"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gRSHuedHJTqX3-W4zSlzV_K1ZDw>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 02 Apr 2016 20:56:12 -0000
On 4/1/16 1:52 PM, IETF Chair wrote: > > In 2013, the IESG set the IETF anti-harassment policy. Last year, we > concluded the process to write a BCP that defines the anti-harassment > procedures. That BCP has now been published as RFC 7776. The RFC > specifies that there shall be a specialist team that can be reached > for help, advice, and possible actions regarding harassment > concerns. Arriving at the point was not easy task. I would like to believe that the ietf community and the individuals that make it up will be well served by it.
- RFC 7776 and the team that can be reached for hel… IETF Chair
- Re: RFC 7776 and the team that can be reached for… Olle E. Johansson
- Re: RFC 7776 and the team that can be reached for… joel jaeggli
- Re: RFC 7776 and the team that can be reached for… Niels ten Oever