Re: [Iasa20] 6635bis

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 02 May 2019 14:32 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1281203CF for <iasa20@ietfa.amsl.com>; Thu, 2 May 2019 07:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 UeqPzZYFST98 for <iasa20@ietfa.amsl.com>; Thu, 2 May 2019 07:32:18 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 76E891203BF for <iasa20@ietf.org>; Thu, 2 May 2019 07:32:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 44vyQS0xbLz1rxfq; Thu, 2 May 2019 07:32:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1556807536; bh=F2rJvXZVqeKDR060Qyox5d64VHCICbxPvpKvxecFYi0=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WuK8tI1a01BdU59SAVNafpsDg0tSpNlInU/vO44h5KDBiVTmein56Mc9QuM8llVyZ jTl51jSQFeRt/SE6CFZuojYvty1LKUyucimHb0hmvD84VI91HbzeI23Oyx8HeDCWGm FN0wfjuI5EIjKyd+R2HKCty/jMqt+vF0Q/nUclXs=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 44vyQR4Vztz1rxfm; Thu, 2 May 2019 07:32:15 -0700 (PDT)
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IASA 2 WG <iasa20@ietf.org>
References: <20190428034407.4EC3B20130AC13@ary.qy> <43D5554EEDD8418CC4E0C195@PSB> <CAL02cgSnpP1pA=mStxkEahG8rmqEFL0CkAVkgq1b3mp_Kif9Sg@mail.gmail.com> <58df809e-44dc-88b8-ff11-1c7ef1ccb8f6@joelhalpern.com> <02C8F2A9-D8E5-4E3B-A185-B8C9C9AC410D@cooperw.in> <37d6031a-b0c6-c082-d4e7-008a67ba02b4@joelhalpern.com> <AFC2A44B-2F42-4BD6-BF16-3A4F9895B9B7@cooperw.in> <f6bf4fea-64d0-4616-17d9-25c3b1e961d3@joelhalpern.com> <82D23000-AADA-4534-89A8-DF43861CB468@sn3rd.com> <d2341f9c-f941-5c16-f6ca-a8884de6191a@joelhalpern.com> <0bcd5cf5-014c-36a8-45b0-903b19f27f7b@joelhalpern.com> <D66DC87A-0E92-4B27-8E74-E2E02285E4A8@cooperw.in> <30bf0dee-9947-13a2-f60c-930f70192933@joelhalpern.com> <CA+9kkMCvj1zXbbY9GL0JJNDrPm9K6Wiz_xm=8-YjhG59_Psm_g@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c911a473-e543-e3ed-5917-bd31cee11904@joelhalpern.com>
Date: Thu, 02 May 2019 10:32:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CA+9kkMCvj1zXbbY9GL0JJNDrPm9K6Wiz_xm=8-YjhG59_Psm_g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/d1wzXEat5hL32JNWFwKpg6cQJFE>
Subject: Re: [Iasa20] 6635bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 14:32:20 -0000

Trimmed for readability.

Comments after yours.

On 5/2/19 10:25 AM, Ted Hardie wrote:
...
> If the IAB takes a matter to the Executive Director saying that there is 
> a problem with contract deliverables, they seem to be placing it in the 
> LLC hands at that point.  In the terms of my previous comment, that's 
> the equivalent of the task requester telling the contracting officer 
> there is a problem. From that point on, it is in the ED's hands to 
> resolve, returning to the RSOC/IAB only with any changes that require 
> their approval (e.g. modifying the tasks).
> 
> Does that match your understanding?
> 
> regards,
> 
> Ted
...

I would be cautious about following the government contracting officer 
model too far.  We as a community do not have rules creating such strict 
separation, nor do we have the level of problems that cause the 
government to require those rules.

My understanding is that in general, yes, if the problems rose to the 
level that ED efforts to remediate are needed, one would expect the ED 
to have point on that.
The IAB can be as general or as specific as they deem necessary in what 
they ask the ED to do.
And the ED can use good judgment in when to ask for more input from the 
IAB and if appropriate the RSE.
And of course the actions of the IAB and the RSE have to be grounded 
somehow in the community (although the exact means of grounding is not 
specified, nor in my opinion should it be.)  And such grounding can be 
tricky, as if it is individual staff misbehavior taking that to the 
community would border on disastrous for myriad reasons.

Yours,
Joel