IETF Logo Mail Archive

RE: I-D.farrresnickel-harassment

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 16 February 2015 19:12 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 5A4771A009E; Mon, 16 Feb 2015 11:12:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level:
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[BAYES_20=-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 Li3R6COxohSL; Mon, 16 Feb 2015 11:11:58 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C1891A1BCD; Mon, 16 Feb 2015 11:11:37 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id t1GJBZQc016453; Mon, 16 Feb 2015 19:11:35 GMT
Received: from 950129200 ([195.76.232.154]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id t1GJBWEo016375 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 16 Feb 2015 19:11:35 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: Mon, 16 Feb 2015 19:11:30 -0000
Message-ID: <000601d04a1c$60ee3cf0$22cab6d0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ2NVy4x7K4/+aFd1ozWgeoAWMgj5uno4bQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21336.002
X-TM-AS-Result: No--3.082-10.0-31-10
X-imss-scan-details: No--3.082-10.0-31-10
X-TMASE-MatchedRID: O/y65JfDwws4HKI/yaqRm5VIEKhlTKpsOFrEjYh/1F5JlXrNacJ2uZKj tgG1Urj8SRaXrcKaFjmas0rFUiAJUcBH2qqdDtmaEhGH3CRdKUUhwKIIdklOVyORQUtxFgFj771 /bOVE87opDKicsTbpeoGwaIKd6VKFxeit2rvNhiXmAId+2bAQwn0tCKdnhB58O5QxsrU10s/6C0 ePs7A07Y6HM5rqDwqtgDHvnbbkdnwG/wpbecSxx+2Xt2/KL6LpDFAi1TFFzHjup18WWp6ZVMKQm VmdOvbkaoFL/5CdFGorWcQmgHlCkEyTbA3iVJwnr2OAW6CLOu6x4TAPWg6bof1siDYOTKnanrKc vPhN+mtD4WaejT+ZHw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WaId6XJQwJC47t-H3ziiAE70EMM>
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: Mon, 16 Feb 2015 19:12:00 -0000

Hi James,

Belated reply.

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

Agreed, and adding a few words.

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

I think we have this in Section 4, and combined with the fix to your previous point we have it covered.

Many thanks,
Adrian

v2.23.0 | Report a Bug | By Email