I-D.farrresnickel-harassment

James Woodyatt <jhw@nestlabs.com> Thu, 15 January 2015 23:46 UTC

Return-Path: <jhw@nestlabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 580051A9090 for <ietf@ietfa.amsl.com>; Thu, 15 Jan 2015 15:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.079
X-Spam-Level:
X-Spam-Status: No, score=-0.079 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 KGVLfPn-VddC for <ietf@ietfa.amsl.com>; Thu, 15 Jan 2015 15:46:19 -0800 (PST)
Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A0991A906B for <ietf@ietf.org>; Thu, 15 Jan 2015 15:46:19 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id uz6so788363obc.11 for <ietf@ietf.org>; Thu, 15 Jan 2015 15:46:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=WCOoEI0NK+Xv8qpNbEEMvHRvAfSoa6Vt6NKnhyNtvqA=; b=a5XlV5eCFIV9CKCW2dQiuBFm5qmBjq9YJCnjL7UXf58szz+TR7lF0SXcOwaR9/JDNA 8n0cLddpdVXAFwGY6u4uZl8xXXoLkBJHY4iCafAfvPJsjyMhTBR8nkNnl5MianlSAtxF cqCeEwufZOEJyQZfEdD3v+/cgkLcy+065rqd3u/MOn5b3FnK9ZyCnzK5t1QevvsGq2gX 6yzotKq7YBR84f0Xr+rt8/3AtFlyRrmV4oKK3h+FOvz0+JNkl4+YMOaLGAF850OfnmmV ouhxR+rgNudY7PUtU87SvDP85Pypfj06PC+3ki39aD5oD+YQnmXlLhTli2U0DrL3IEmI /sNQ==
X-Gm-Message-State: ALoCoQmdOncxA5qxguly2m31DtTBt3Ir3K59YWWghbPnv1aBGxxCJjV2yFfruCBg+Sb+LSn3w5RO
MIME-Version: 1.0
X-Received: by 10.202.94.132 with SMTP id s126mr7203899oib.70.1421365578653; Thu, 15 Jan 2015 15:46:18 -0800 (PST)
Received: by 10.76.150.2 with HTTP; Thu, 15 Jan 2015 15:46:18 -0800 (PST)
Date: Thu, 15 Jan 2015 15:46:18 -0800
Message-ID: <CADhXe52X+-1yjNUPWGCmbRhgHguMPTC+X6DTYsN=CMY46-sGhw@mail.gmail.com>
Subject: I-D.farrresnickel-harassment
From: James Woodyatt <jhw@nestlabs.com>
To: IETF discussion list <ietf@ietf.org>, draft-farrresnickel-harassment@ietf.org
Content-Type: multipart/alternative; boundary="001a113d51606977e7050cb97650"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/AD_V1DFJLw09a6PSNnNnn-dff7I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 15 Jan 2015 23:46:21 -0000

Everyone—

Having reviewed I-D.farrresnickel-harassment, I have a comment, but first I
want to express my vigorous support for this effort to establish
anti-harassment procedures in IETF.

It occurs to me that the Lead Ombudsperson has a variety of functions
related to the application of remedies, and the draft doesn't clearly
indicate what happens when the term of service ends for a Lead Ombudsperson
with unresolved cases.

It seems obvious that the draft intends to leave this policy for the
Ombudsteam to set, and I suppose that's adequate, but I think the draft
would be improved if Section 3.7 were to make explicit note of that. You
know, so as to remind the Ombudsteam that they really need to plan for
that, because it's a thing that will happen.

I can also imagine one scenario where the procedures in the draft might
become troubled.

Consider the case where a Reporter informs the Lead Ombudsperson they
believe another Ombudsperson should recuse themselves, then later, before
the case is resolved, that Lead Ombudsperson is removed from the
Ombudsteam. If that scenario happened to me, then I'd very much want to be
consulted in the selection of a replacement for the Lead Ombudsperson for
my case.

Perhaps Section 3.7 should say something to the effect that the Ombudsteam
shall in each case select a replacement for the Lead Ombudsperson from
among its members with the agreement of the Reporter.


-- 
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering