RE: Ombudsteam update

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 11 January 2019 18:08 UTC

Return-Path: <adrian@olddog.co.uk>
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 728171277CC for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2019 10:08:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 UyN_WgJBCSVE for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2019 10:08:40 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 356F0127AC2 for <ietf@ietf.org>; Fri, 11 Jan 2019 10:08:40 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x0BI8b3u032110; Fri, 11 Jan 2019 18:08:37 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 83D2922042; Fri, 11 Jan 2019 18:08:37 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 6E4CB22040; Fri, 11 Jan 2019 18:08:37 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.189.92]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x0BI8a8e004949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Jan 2019 18:08:37 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'heasley'" <heas@shrubbery.net>, <ietf@ietf.org>
References: <82BCE48D-9B20-4819-82A0-BD8378AFBED5@ietf.org> <20190111174301.GA85567@shrubbery.net>
In-Reply-To: <20190111174301.GA85567@shrubbery.net>
Subject: RE: Ombudsteam update
Date: Fri, 11 Jan 2019 18:08:34 -0000
Organization: Old Dog Consulting
Message-ID: <03cb01d4a9d8$ab41e700$01c5b500$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQHIZwtwFM/Yy+ZXepjNUq5AgflP+AHmbnIPpbOumGA=
X-Originating-IP: 87.112.189.92
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24356.001
X-TM-AS-Result: No-2.914-10.0-31-10
X-imss-scan-details: No-2.914-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24356.001
X-TMASE-Result: 10-2.913600-10.000000
X-TMASE-MatchedRID: scwq2vQP8OHxIbpQ8BhdbMK7fT3t6J55oA9Le8XJpboUWf/cATIRrFlz o9zSKaiKVfKQMHxL/ue6QumZsbIA/nrU/bn+VagUIVtayz0CBbNR3sGN+j7mNBKIr6MHZFJ19kZ 14G/bCrQIHarpPzq729KKxkecinYFXSJ4c3nT+QfCtSG/SQAC8fqk6wqWEsjCRfmFzyKgHb4RGo GJcaPeDwRV6p+xh04z/ah9yE/VPSU3KXWd30Ii3Tl/1fD/GopdyJ1gFgOMhOmLZAVphLW/bSq2r l3dzGQ1w5JO3j0kuyX99pY6I4uiEfgA2wP4w4WPAtf8bSDCmv41YgWs3AId/F0kQuPV36Rho6ig Pw9YwL1tdincGtnTkJeedShXWr/+A3H3aqOdUmSvcsTuUejg0omQ2vqumwAFVUH85vIcwrmE513 t7Gwk0EMMprcbiest
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AiWBfMx0zGO0iBdWl8saOuKy9cc>
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: Fri, 11 Jan 2019 18:08:42 -0000

See 3.2 of RFC 7776

The underlying assumption was that the team requires a skillset that is rare
in the IETF context and also hard to assess (we, as regular IETF
participants, lack the topic-specific knowledge to make choices between
candidates).

The IETF chair, therefore, is instructed by RFC 7776 to look for candidates
and take advice as widely as necessary in order to make selections and form
a team.

Section 3.8 tells you what to do if you believe there is a problem with the
way the IETF chair has made the selection, although I would encourage you to
first have a private email exchange with the IETF chair in this case.

Regards,
Adrian (co-pen-holder for RFC 7776)



-----Original Message-----
From: ietf <ietf-bounces@ietf.org>; On Behalf Of heasley
Sent: 11 January 2019 17:43
To: ietf@ietf.org
Cc: IETF-Announce <ietf-announce@ietf.org>;
Subject: Re: Ombudsteam update

Fri, Jan 11, 2019 at 12:35:40PM -0500, IETF Chair:
> 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.

Why are these appointed rather than elected positions?