RE: I-D.farrresnickel-harassment

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 16 January 2015 09:09 UTC

Return-Path: <adrian@olddog.co.uk>
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 E55281AC3AC; Fri, 16 Jan 2015 01:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level:
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 M2WskUmfoRqM; Fri, 16 Jan 2015 01:09:09 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 688A41AC3AA; Fri, 16 Jan 2015 01:09:07 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0G995Sp026035; Fri, 16 Jan 2015 09:09:05 GMT
Received: from 950129200 (62-46-241-88.adsl.highway.telekom.at [62.46.241.88]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id t0G99389025996 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 16 Jan 2015 09:09:04 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'James Woodyatt' <jhw@nestlabs.com>, 'IETF discussion list' <ietf@ietf.org>, draft-farrresnickel-harassment@ietf.org
References: <CADhXe52X+-1yjNUPWGCmbRhgHguMPTC+X6DTYsN=CMY46-sGhw@mail.gmail.com>
In-Reply-To: <CADhXe52X+-1yjNUPWGCmbRhgHguMPTC+X6DTYsN=CMY46-sGhw@mail.gmail.com>
Subject: RE: I-D.farrresnickel-harassment
Date: Fri, 16 Jan 2015 09:09:03 -0000
Message-ID: <03e101d0316c$13dc5460$3b94fd20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03E2_01D0316C.13DE9E50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ2NVy4x7K4/+aFd1ozWgeoAWMgj5t2a+4g
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21256.003
X-TM-AS-Result: No--19.331-10.0-31-10
X-imss-scan-details: No--19.331-10.0-31-10
X-TMASE-MatchedRID: HLMPCFyIyBOnykMun0J1wv6gIMmwXvI9/kqO2xYqX5YAIXlMppp3X9JT KqJ/jqv4QvfyOpU8D1dnklUsX189Ys1whNtuCqf2KWuiyZLRI4AZskwWqoib3DhgoAzehG32YNA Ef9mlmAxkMY8YxZE5LS19piampdWRMH15eekLeUhgP1dNF1ow7eGxenV8i/7hf7RPWCFK8GIb1r R7E3wvI+A3xpHWPaRmeSwJDTNFbzHAR9qqnQ7ZmhIRh9wkXSlFIcCiCHZJTlcjkUFLcRYBY6uBz gYaP0JhHIz4h07EShRYhNO+WfCIjkdb73gUDwkXQr2qXCJMSV+uiAW0p38/t7rfxlRjqBJ3gC46 pyJTSnTV4yn6Kf1r098KgvULLt4X/fqypUX9VmhLc5N+0s1+DZT1elWqouGw8cWgFw6wp7OI+yd 48zjY3SWuqxiUeEX6MLog80/xRYlR4vrwuhcS/AVOLlPuctdqLdLfmiFS7fuSs1st/hpgblzOKV R59i8DP5mpBtPr/e7et/aEQRVJHkNKRRr2LbXrWCjDJRYeAZ0BL/XzNFFmHxS11FlOYRohT3bHV zoTp+QXlh2Nyyp8x7Rd0WwZSVdNNJyAyqAmcb/kcOvbQGFzRnG1ZiUO5FClte8MfJIL55TUGg7Q VcvSyFQoq/z/x5QQnsUiwVqDOARSEgm2SMwgWSI9MxSOQ6CSXgqwd9ijktB+nKfe95RZCUv+Gv9 gyZL/yLEZfWzun2U9L+XNrNJvTNJ24xzpGcj5lwmT5LSTn4MtlZY1WAfRjbLLTvamG8BJo8WMkQ Wv6iXoC+VlRHhOyGsBqFAbBCa34AUIEeXqwJr3V3w27mlzMJOUEVxYAD7P5kfXvX+EskY2Opgs2 d++JQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4kjVHZoQdw0EGX8NyD9lQncKzYQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Fri, 16 Jan 2015 09:09:13 -0000

James,
 
Thanks for reading, supporting, and commenting.
 
I think you have raised valid points. They're not on the main path, but they are close enough to it to warrant some thought. 
 
I'll talk with Pete and see whether we can concoct a line or two.
 
Cheers,
Adrian
 
 
From: James Woodyatt [mailto:jhw@nestlabs.com] 
Sent: 15 January 2015 23:46
To: IETF discussion list; draft-farrresnickel-harassment@ietf.org
Subject: I-D.farrresnickel-harassment
 
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