Re: [Iasa20] I-D Action: draft-hall-iasa20-workshops-report-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 21 March 2017 17:26 UTC

Return-Path: <brian.e.carpenter@gmail.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 7527A127A90 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 10:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oKeR_GUgYzFq for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 10:26:55 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D404A12708C for <iasa20@ietf.org>; Tue, 21 Mar 2017 10:26:55 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id z13so52750961iof.2 for <iasa20@ietf.org>; Tue, 21 Mar 2017 10:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ig17NT+7dxVZvGn4lRhblIYpfYlICoy2XWbayxKEAVA=; b=f9SN2TnTJ0qonm4vZKeExl7KE12Zk94sodhY6bg5UVTeHFutOyBDZYNTlT5wuA4gG5 SkHk/z4xCRmbzbZQTLCy2KPhLnWqG1AdzhcyHFr8+8XRPfcPb8jeVuXR5cy3KTexYSdD CKNccu4dAm3RFBtZ8ElDWi8H4FFhKKJymrLtoQAELW8HgXuY8qv4NZ3IGTrz3SMz++d2 JkW6DDUm6c0acI+ae7e+9WwSY7e8k+y0jq+qkWKmssxfvSZbVOWkwMoVA4i7bQaFDknA sg3wIXa//MhZmTmKrV22xEKEtgjbflxD3NJD10lEDihIjJkXKIy4ODRDGvQ3jJIEalEs 6zVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ig17NT+7dxVZvGn4lRhblIYpfYlICoy2XWbayxKEAVA=; b=cRVRuoFzKc5vzHyZsfbd0tUva4roZQwe1ZZyTOY5gAlbN7WYZ0v1DEqBDjUVJPDIvr nmxaNUyemXbd6R/o/3Bq9/c6F4JSemUfSSPjlfBCRnn2vtH640HIawSQ3JjJfqm5MiDs q7bWsCGwdfANfeRxfLYWcLf4OqX7sPsG15uU5CUyS2MS7AneBWHo/+hB0B0+pqB5CRsq 9T4ECviLRSU9t+5mRn3efyLUcwJlGY0y9bZnhDJbUKt3pQJiPMfdpHmoGh7IDpTBDA5M sGCOUxATM4A9XNO2bRg4xu1HkUVv9bGyyo3SmX1yO1A5jU+HCgs3Jte//VBNzQ5eeCBy 1S0A==
X-Gm-Message-State: AFeK/H22WwSuauRZyWx3fk4u9a1/PyH0NXgcBwHndxNmF6ZRVVXz6cAoDqqxN/uJYNoyFQ==
X-Received: by 10.107.19.222 with SMTP id 91mr36310712iot.211.1490117215116; Tue, 21 Mar 2017 10:26:55 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id d142sm7044698itd.18.2017.03.21.10.26.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 10:26:54 -0700 (PDT)
To: dcrocker@bbiw.net
References: <148941528136.16867.3807046327704023886@ietfa.amsl.com> <2938563f-6ad6-57a8-122f-805b8cf41ed5@gmail.com> <93fd4140-d72a-93d0-a57f-2375d788b762@dcrocker.net>
Cc: iasa20@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <4815b979-4729-e1b2-f5a1-3d8bb2645865@gmail.com>
Date: Wed, 22 Mar 2017 06:26:58 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <93fd4140-d72a-93d0-a57f-2375d788b762@dcrocker.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/4Jk75BMI3-Lpv6PNoFhfNHJttI4>
Subject: Re: [Iasa20] I-D Action: draft-hall-iasa20-workshops-report-00.txt
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: Tue, 21 Mar 2017 17:26:57 -0000

Hi Dave,

On 22/03/2017 05:06, Dave Crocker wrote:
> On 3/20/2017 6:29 AM, Brian E Carpenter wrote:
>>>    o  The line between the IETF and ISOC is not organizationally clear-
>>>       cut,
>> Better get used to it. Since the IETF is intentionally not incorporated
>> and intentionally run by a rough consensus process, that line will never
>> be clear-cut.
> 
> 
> The premise that the IETF's lack of incorporation somehow dictates 
> ambiguous lines of authority and/or management makes no sense.  The 
> latter are dictated by clarity of organization structure and crispness 
> of task and personnel management, not legal status.

That's not quite what I was getting at; and I do believe that responsibilities
can and should be well-defined. My point was that, having observed the IETF
and various other organisations with a mixture of professional and volunteer
effort, there is *always* a lack of crispness about what actually gets done
by the volunteers as opposed to staff. That's just a result of human nature
and the motivations and incentives that are at work. I'm not saying it's a
bad thing, either, but it's life.

   Brian

> 
> Incorporated organizations hire unincorporated individuals all the time. 
>   Unincorporated individuals hire Incorporated organizations. 
> Individuals hire individuals.
> 
> Each of these can be done with good or poor definition and operation of 
> lines of responsibility and lines of authority.
> 
> There is no reason the IETF/ISOC relationship necessarily has the 
> ambiguities we've operated with.
> 
> Rather, it is lack of resolve to make things clear and operate 
> accordingly.  We are quite lucky that everyone involved is committed to 
> making things work, but perhaps contrarily that luck serves to obfuscate 
> the problems here.  (It does not help that the IETF's operation came out 
> of the 'daddy pays' funding and operations model, since that created the 
> foundation for this continuing administrative confusion.)
> 
> d/
> 
>