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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 21 March 2017 19:01 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 EECE912EE46 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 12:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-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=cs.tcd.ie
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 70yz4QwQxzG7 for <iasa20@ietfa.amsl.com>; Tue, 21 Mar 2017 12:01:35 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40D4812F253 for <iasa20@ietf.org>; Tue, 21 Mar 2017 12:01:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 35336BE80; Tue, 21 Mar 2017 19:01:25 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZWXlPFW6WWA; Tue, 21 Mar 2017 19:01:23 +0000 (GMT)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D0FFFBEB0; Tue, 21 Mar 2017 19:01:19 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1490122880; bh=2i16gf8nlXf15qFrw+iR7wMyqcy76rgyHb5yY4sUYMU=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=DaRv7lyOJ/j6swIq9Oesn5Nh0Irqf4+NgCO/TM5OaE9bMSeR6OexIhscBvZIKX80l oOk+A4StScl9gcNvxwU9K6dw0HgWti6JxSBRcizLmY+AAPQ5LaUIeS5KqirwaiUgRn 8rn+7eJ/3Jy4TjA8aD/laWKYYeDKCpk6lIc4RSww=
To: 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>
Cc: iasa20@ietf.org, Dave Crocker <dcrocker@bbiw.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <7a59cd20-19a5-5e35-49ca-2d5e11759416@cs.tcd.ie>
Date: Tue, 21 Mar 2017 19:01:19 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <AFBEB86C-E1EC-499C-8269-473782E7DA71@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="wbJDP29t7stgOR2A9cii4NsL2hkDp5Xsp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/VZxj4HMhvKTreG03uDDl4801lIE>
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:01:39 -0000

Hiya,

On 21/03/17 18:47, Bob Hinden wrote:
> 
> To some level it’s documented at iaoc.ietf.org, but I think we need more than that.

Putting it on the web site would be fine. I guess at [1].
Or maybe something allowing version control (an I-D or
git repo) might be better, not sure.

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
imagine (but am guessing) that kind of thing might have
contributed to some of the IAOC related mega-discussions
we've had on lists when things do go a bit wrong, e.g. if
a scenario occurred where staff feel they can't be the ones
who respond on lists, but volunteers haven't got the right
information (or don't explain it well because it's third
hand).

Cheers,
S.

[1] https://iaoc.ietf.org/committees.html