Re: [Iasa20] Some observations

Dave Crocker <dhc@dcrocker.net> Fri, 24 March 2017 13:15 UTC

Return-Path: <dhc@dcrocker.net>
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 0DA3112968F for <iasa20@ietfa.amsl.com>; Fri, 24 Mar 2017 06:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 Zr608NTyPH_G for <iasa20@ietfa.amsl.com>; Fri, 24 Mar 2017 06:15:28 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 AEA901293F3 for <iasa20@ietf.org>; Fri, 24 Mar 2017 06:15:28 -0700 (PDT)
Received: from [192.168.0.158] (50-232-11-130-static.hfc.comcastbusiness.net [50.232.11.130]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2ODHUid006041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <iasa20@ietf.org>; Fri, 24 Mar 2017 06:17:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490361451; bh=Eo+VTTvD3NkU26v79mQU7m7Ut6U1unncAho3q7y31bc=; h=Subject:References:From:Reply-To:To:Date:In-Reply-To:From; b=CejxwUNDH8+BQUjbsOtVkPzBvgNgHp/WdK2f1buCvanKHbWF9iwjHCQiWsxveILkH x2VVKN42EDEaDnTeCJX5VVuvOdoxQlkcDsUZcw3vv4s3OGV4UJtYJSAyF+mAcGzsib NBXrvU3Ls+LxOzdX/CjQ25Sn93368Hm4HYtUIsPE=
References: <A86A4667-0403-4796-B2F6-8F584D7344D5@cooperw.in> <96b3036d-3ce1-2d25-a514-addee4f44fe3@dcrocker.net> <13a3c98a-6aa4-9176-6c9e-baa43617a194@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
To: iasa20@ietf.org
Message-ID: <23f6d396-ed7a-903d-2019-4454c7306efa@dcrocker.net>
Date: Fri, 24 Mar 2017 08:15:25 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <13a3c98a-6aa4-9176-6c9e-baa43617a194@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/vVAyRcOY5FQTwa6aEHiVKAtn6hk>
Subject: Re: [Iasa20] Some observations
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 24 Mar 2017 13:15:30 -0000

On 3/22/2017 4:47 PM, Brian E Carpenter wrote:
> On 23/03/2017 05:03, Dave Crocker wrote:
>> On 3/22/2017 6:31 AM, Alissa Cooper wrote:
>>> We've also talked about the IAD being overloaded
>>
>> This is a persistent reference but I don't recall seeing its foundation,
>> particularly given the reference for calling on up to 20 other ISOC
>> staffers.
>
> Isn't the point that only one FTE is *allocated*, in the person of
> the IAD, and since that clearly isn't enough and the rest of the
> staff work is "borrowed", there is a conflict between theory (1 FTE)
> and reality? In that situation, the IAD is pretty much guaranteed to
> be overloaded.


"Overloaded" appears to be an unfortunate choice of vocabulary, since 
it's focus on excess has created some background debate about it's 
specific meaning and applicability.

So I'll suggest skipping over that and, instead, moving towards the 
affirmative need to properly document the resources the IETF uses and 
who is allocated to perform them.

That is, who is needed and to do what?  Then, which of these is 
currently supplied by ISOC?  Should that sourcing continue?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net