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

Alissa Cooper <alissa@cooperw.in> Mon, 17 July 2017 19:00 UTC

Return-Path: <alissa@cooperw.in>
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 C4C63131CE7 for <iasa20@ietfa.amsl.com>; Mon, 17 Jul 2017 12:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=waa0ai5f; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PuCojvqO
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 3UY6sBXqYOlK for <iasa20@ietfa.amsl.com>; Mon, 17 Jul 2017 12:00:16 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B55F3131CD2 for <iasa20@ietf.org>; Mon, 17 Jul 2017 12:00:15 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2AF6D209B4; Mon, 17 Jul 2017 15:00:15 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 17 Jul 2017 15:00:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=6DSAeCzjKK98UzTgQR j+7jnfCpRakoj/n5/vDZq3XGw=; b=waa0ai5fKAVtouBcz/FuOYRgNl5iVyHUCh vHzKu46xSHxKYiUR25EydO31HH31c5vfdZJ0F/sXpXbxfpD3ibKcmHFT6xtvPkpY ZNtrjR6WUYDyZ+n/Pygn9gn2E4t/reo8KCUISQd5+1+qQ/1JPPFeTMIyU4OcXEtS 2U9cQGnEJfsiL8P37wx061bk7zyGTk3tKFs8bFJZ+/y6HCIFRk1VbXDZYMHQuW+E 1ya/8qe6KmVO44Ay0TXLBFJnzXX7Rn4nu00Yaf/eUsuc1osGlnQgo0/pIjh+qvx3 Ut/Q3tu5p/eZTWA0ovCXz7grm74A/sIkA6f8cEOv0TsVRR9zM0nA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=6DSAeCzjKK98UzTgQRj+7jnfCpRakoj/n5/vDZq3XGw=; b=PuCojvqO iCIylG+8PckVgO/3ZGQFVAn+bqEcsVqtQJ7X6bgO/xlFC4GBkiX/FlDkocaf6Js1 G4eEwcoF6AtJOHIN9Qh3lOfRrMx7+k3jhlgIfy/h0mauS3QiyAEvTP6VGKYLEXqo 0fiQ+Bh+0RRJKcTYrsC2Qtm6QDoT2y7+yoJk2+s/BMrCsYR0yVSxwsuoBtlYu81H sf2AHLlVOEe6rYnq7boOhLQBhef2cnOdCiU98IpvunVRY/XoiJsgd+zapA7f3Ybm XNqWRruaN+GPsUJ5CG2c4Mxg+990UsunOo8G2A5a6+dWt3S18g/Z2JACRxdTKAem 9ASELCRevpPg6w==
X-ME-Sender: <xms:PwltWUBFK3UX7S7bP_UiVcO9yJmYO0DnmFDHlaI0N0ONiJe6ebMxQQ>
X-Sasl-enc: Ovn3oRK8c1Jj73BXehK4QnOlZGY8t5XPKbOevH87TS0I 1500318014
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.170]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A21D248D1; Mon, 17 Jul 2017 15:00:14 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4215151F-F5F7-4AF0-9806-F903438E9BA4@piuha.net>
Date: Mon, 17 Jul 2017 15:00:12 -0400
Cc: "iasa20@ietf.org" <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <56BFDCF4-E72F-46E2-8538-DE92F91528E3@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>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/V3qiOTBxTUB5zheK5Td3FUiGXcE>
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: Mon, 17 Jul 2017 19:00:25 -0000

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.

Alissa


> 
>> I think it’s important that the IETF Trust should be kept of of this.
> 
> (I think you meant “out of this”?)
> 
> FWIW, and I’m not speaking for anyone else than myself here, but I definitely agree. I think the Trust could be a part of the changes, but only to the extent that you separate the members of Trust and any other board that governs the rest. I don’t believe it would be useful to merge the Trust’s account or role with other entities. Even if we were to create an independent IETF organisation, there are good reasons to keep the ownership of IETF IPR separate. Separation of concerns, ensuring that IETF IPR is separate from any financial issues that IETF might otherwise have, etc.
> 
> Jari
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20