Re: [Iasa20] draft-haberman-iasa20dt-recs-00.txt

Bob Hinden <bob.hinden@gmail.com> Tue, 18 July 2017 06:13 UTC

Return-Path: <bob.hinden@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 32D5B129A96 for <iasa20@ietfa.amsl.com>; Mon, 17 Jul 2017 23:13:21 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 13PY6bGhuI2Q for <iasa20@ietfa.amsl.com>; Mon, 17 Jul 2017 23:13:19 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 16844127869 for <iasa20@ietf.org>; Mon, 17 Jul 2017 23:13:19 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id 12so13194444wrb.1 for <iasa20@ietf.org>; Mon, 17 Jul 2017 23:13:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=QDg3yuXHZpG3sxvXzMTXz9P5h3qEJmpRsc1l9nio97g=; b=CZRW0TVDX6cy3eJ9lmIl1ZhltYHHxZZwjkgGyBRAWEmb0D+TAhS+dtvOZJOEkl1Csk 78katBbyIpOxSxm/1WM3Q/cZkfSL8bUQIWV1vFLm5qd5vFUFQhtPYbm4yCzZQQkbPp+P Wmgqs8qE+Htm5H6gm1QemDMTIf1NDaOvSVl9PTlEPqh1KoZ2dhDoqRT7h0GPBgnmcxMR Fp4ZhgRmaYEIaTpd4jdeRF+GFMWHP3spnLpiBcKXDU2IME+M6UKxFNZJMoa065z19UIv CgFonXtADUV8z1LCnC66SLhntZoRCBNjeWXLt2EvMAbADKkyao4WY/s9/WykioWdRDsd Do0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=QDg3yuXHZpG3sxvXzMTXz9P5h3qEJmpRsc1l9nio97g=; b=qdqeFfSGUClfRmlDzLmdIY5HXj6eyT9SDlmcnWy/On+FdEwu5hXfB038cx3W9355+F qVQ3mKeYcLfiB3SYylCXr6I05zQUmhgh+zkK/yJUswDKlVoNIBkDNF+Bl9eHehVL9/dd DYebZgn93QnGJJT3bjiHCGgVhuc8e47vII3L0ShJ0xrL+BnRF97NbCy/Zm7ym/VQ/j39 cUMQH25wm8BBJg2plZ8ejJxx4kBPZILpk3LssG3GHqjTyF9H1hl6yhN3P53xKsDulpyg reJGwG6zD6VchPveFtGkLd7qbubnnfAeQ70Nsvti2V6tNK63dDmsuTiuVj3GMU16jDwK awmg==
X-Gm-Message-State: AIVw110iG/Vx3RZZjKxu5+SFzHgrtYFrxC1Zi+I3z2Ghm9XO+QS2PQVr 0xLf1g8bOAOVTg==
X-Received: by 10.223.174.194 with SMTP id y60mr6344wrc.19.1500358397664; Mon, 17 Jul 2017 23:13:17 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:21ab:aad7:416a:54c7? ([2001:67c:1232:144:21ab:aad7:416a:54c7]) by smtp.gmail.com with ESMTPSA id y35sm1502418wrc.51.2017.07.17.23.13.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2017 23:13:16 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <94A98DAC-EA10-4CC3-9F1E-074795CA2428@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D71D04E8-0E35-4F7D-B38C-BB67648BEC9B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 18 Jul 2017 08:13:13 +0200
In-Reply-To: <56BFDCF4-E72F-46E2-8538-DE92F91528E3@cooperw.in>
Cc: Bob Hinden <bob.hinden@gmail.com>, "iasa20@ietf.org" <iasa20@ietf.org>
To: Alissa Cooper <alissa@cooperw.in>
References: <CABtrr-VtbzvTuBxV1y8910m8zPNi53CWVKd9NGpvAfprwc8iEA@mail.gmail.com> <CA+9kkMDa1gkyeywF9zNa3Z3w5FDuD=J9p3fW_pPaQtoLsUXM5Q@mail.gmail.com> <CABtrr-X6rENwvScwJJCLO9XrgDDBLtw_v_G3PxQZhdHiB6xuew@mail.gmail.com> <B351229A-72C2-433B-BC19-C35099491EF6@piuha.net> <CA+9kkMBzgOY+K2w1Yhk3B9irGaMo4CRrJ2kT+oAXRUhLwW0ukg@mail.gmail.com> <D146FE44-3263-4379-A4DB-D89E3624C9B8@piuha.net> <90E524B1-730D-4F29-8987-3D0DBE5380E5@gmail.com> <4215151F-F5F7-4AF0-9806-F903438E9BA4@piuha.net> <56BFDCF4-E72F-46E2-8538-DE92F91528E3@cooperw.in>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/AedC5h1FcqKFtMCO6cb1feBxi_Q>
Subject: Re: [Iasa20] draft-haberman-iasa20dt-recs-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, 18 Jul 2017 06:13:21 -0000

Alissa,

> On Jul 17, 2017, at 9:00 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> Hi Bob,
> 
>> On Jul 15, 2017, at 9:38 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
>> 
>> 
>>> I think it’s critical to understand the financial implications of the different model.
>> 
>> Acknowledged and agreed.
> 
> Another note here about the DT’s work scope, since this is something I talked with them about before they started: I agree as well, but thought it would be useful for the DT to generate a few options for initial discussion before asking them to produce a full-on financial plan attached to each option. For one thing, they had about six weeks to get a draft together, so the scope of their work needed to make it feasible to produce something for discussion in that time frame. Furthermore, if it were the case that the community has no interest in some of the options, then it would not much be worth investigating and proposing funding models for them. So getting some initial substantive feedback before doing that seemed like it might expedite the process.

Understood, however I don’t think the community can realistically evaluate the options with out some information on how much each plan will increase our overhead.  This doesn’t need to be an detailed financial plan for each, but some high level estimates.  Otherwise it’s akin to going shopping for a car without knowing the prices and/or ones budget.

Thanks,
Bob