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

Dave Crocker <dhc@dcrocker.net> Tue, 21 March 2017 16:07 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 3F44F129AB3 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 09:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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, URIBL_BLOCKED=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 O5MSotWfmbB6 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 09:07:01 -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 A9159129ACC for <iasa20@ietf.org>; Tue, 21 Mar 2017 09:07:00 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v2LG90cv021040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Mar 2017 09:09:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490112540; bh=YcOzWVeXKmuFha+luCO3mS6jYdzKCUnZU8H1pdo887M=; h=Reply-To:Subject:References:To:From:Cc:Date:In-Reply-To:From; b=TjsKEbhllA8n5G6aF3/mIZWWDGOHNp1lrEF8Xswt7WOaBElqKwEQwO0KjVzPouScw QtJ5IQ/T4folHkyUzoksnrcaeL7UMXyFxSgdYJaYhBdT9zIbP78sdioiIFfg6G7Q6s 1bfwhAl6WUJTPQqAl3wQkbOTffyiaO9Q3I+rdWFU=
Reply-To: dcrocker@bbiw.net
References: <148941528136.16867.3807046327704023886@ietfa.amsl.com> <2938563f-6ad6-57a8-122f-805b8cf41ed5@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Cc: iasa20@ietf.org
Message-ID: <93fd4140-d72a-93d0-a57f-2375d788b762@dcrocker.net>
Date: Tue, 21 Mar 2017 09:06:52 -0700
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: <2938563f-6ad6-57a8-122f-805b8cf41ed5@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/uMlBH_ww5jl6Q-nAp46-afJTIgY>
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 16:07:03 -0000

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.

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/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net