Re: [Iasa20] problem statement needed
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 19 July 2017 09:46 UTC
Return-Path: <mcr@sandelman.ca>
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 D02B3131A86 for <iasa20@ietfa.amsl.com>; Wed, 19 Jul 2017 02:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 CW4VGCxQ7FK4 for <iasa20@ietfa.amsl.com>; Wed, 19 Jul 2017 02:46:26 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 121F0131A92 for <iasa20@ietf.org>; Wed, 19 Jul 2017 02:46:26 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:1998:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 23F831F8F6 for <iasa20@ietf.org>; Wed, 19 Jul 2017 09:46:24 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id DC18E2940; Wed, 19 Jul 2017 11:46:14 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iasa20@ietf.org
In-reply-to: <CABtrr-XFuho=i7x=DZhKu0tXz=98wcpS3ZPs_to=d_+i2ENLsQ@mail.gmail.com>
References: <FBABE063-4AC6-455D-8D69-915370351705@consulintel.es> <CABtrr-XFuho=i7x=DZhKu0tXz=98wcpS3ZPs_to=d_+i2ENLsQ@mail.gmail.com>
Comments: In-reply-to Joseph Lorenzo Hall <joe@cdt.org> message dated "Tue, 18 Jul 2017 17:16:54 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 19 Jul 2017 11:46:14 +0200
Message-ID: <13858.1500457574@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/3J4nHvVzowU6i2b-P0s7q-IpWJg>
Subject: Re: [Iasa20] problem statement needed
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: Wed, 19 Jul 2017 09:46:29 -0000
Joseph Lorenzo Hall <joe@cdt.org> wrote: > There is this, but we will draft something that is a separate and crisp > problem statement: > https://tools.ietf.org/html/draft-hall-iasa20-workshops-report-00 The fundamental problems are really described in: https://tools.ietf.org/html/draft-arkko-ietf-finance-thoughts-00 and to summarize them: we generate between 1/3 and 2/3 of the revenue to run the organization (including both the meetings and the rfc-editor) from meeting fees, and we need to accomodate having more remote attendance for a variety of reasons. The belief in the IASA2.0 BOF is that our current management structure may be unable to deal with the changes needed to deal with the fundamental problem. (I think that the *BOF* could well conclude that all is well, or that the needed changes are not so radical as to need IETF consensus are needed) -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Iasa20] problem statement needed JORDI PALET MARTINEZ
- Re: [Iasa20] problem statement needed Joseph Lorenzo Hall
- Re: [Iasa20] problem statement needed Michael Richardson
- Re: [Iasa20] problem statement needed Joseph Lorenzo Hall