IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Tue, 21 March 2017 19:05 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 347D61294F9 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 12:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 E0tcbjYU8mHr for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 12:05:03 -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 525DE1270A0 for <iasa20@ietf.org>; Tue, 21 Mar 2017 12:05:03 -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 v2LJ6xSb027900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Mar 2017 12:06:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1490123219; bh=myz+AKSXylsRKqOiS7copP7ZspbguLoOic4AUmX7Guc=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=Bhk6ykyYetjt8A2DcWWMaqdz7SSnsiKGiJW61bAjcCXhmW0vzu3GUNtCWZZN+LbGu cIogbyodYkwXu/Emo//bSYJZt82GTrc4cmceLS9PDipHb9UvBlf1OJ6eZfQWWiHQ91 t2rZhymhPKSORMIBn24bamkrLUhYzhmw/G5GvmSE=
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Bob Hinden <bob.hinden@gmail.com>
References: <148941528136.16867.3807046327704023886@ietfa.amsl.com> <2938563f-6ad6-57a8-122f-805b8cf41ed5@gmail.com> <93fd4140-d72a-93d0-a57f-2375d788b762@dcrocker.net> <4815b979-4729-e1b2-f5a1-3d8bb2645865@gmail.com> <f2161cbb-2c2e-38fd-dc23-c1e6e894444a@cs.tcd.ie> <AFBEB86C-E1EC-499C-8269-473782E7DA71@gmail.com> <7a59cd20-19a5-5e35-49ca-2d5e11759416@cs.tcd.ie>
Cc: iasa20@ietf.org
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <12e590ee-fca4-818c-0427-851397d57732@dcrocker.net>
Date: Tue, 21 Mar 2017 12:04:51 -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: <7a59cd20-19a5-5e35-49ca-2d5e11759416@cs.tcd.ie>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/47plp-_L5QhrmTFYj9Na_PJ8-QQ>
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 19:05:05 -0000

On 3/21/2017 12:01 PM, Stephen Farrell wrote:
> And indeed I see the meetings ctte is now split into staff
> and volunteer member lists which is a good start. (I forget
> if that split is new or not.)
>
> But even in that case, it's not clear who does what. I can


Clarifying these, and ensuring that ongoing efforts conform to those 
clarifications, is certainly appropriate to do.

But I believe it will have almost no effect on confusion about 
authority, roles and accountability, between the IETF and ISOC.

That involves inter-organization clarity (between IETF and ISOC), not 
within-organization (IETF) committee clarification.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email