Re: [Iasa20] IASA 2.0 minutes

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 April 2017 14:29 UTC

Return-Path: <brian.e.carpenter@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 177BB126D85 for <iasa20@ietfa.amsl.com>; Mon, 3 Apr 2017 07:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 HFDwHYCiFD-n for <iasa20@ietfa.amsl.com>; Mon, 3 Apr 2017 07:28:58 -0700 (PDT)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 62283126C89 for <iasa20@ietf.org>; Mon, 3 Apr 2017 07:28:58 -0700 (PDT)
Received: by mail-io0-x241.google.com with SMTP id 68so12220679ioh.3 for <iasa20@ietf.org>; Mon, 03 Apr 2017 07:28:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=quP3k3+rryXERuIfXEl69PmcI5NfIleVQ0REMnFXqsA=; b=UKC+SsLt7IGk7WePUz4BjUOkB4ZKG4tZIz3qGK0Aj42+62xdXPVDP2p95UVsYYSeQz PlJ9UrH73vANgzyojqWnNxr23OapbS4vco1tDtBNke7MyykW1C0JrZZ1zuhLyCm8YTRZ jV3kVXE1PJ6vkmdqijhuOy3x/Ug3t9sTJPKgSeVeJwIX7ifaRkIgB1KsShRW+l7/g6HM fadLks8RWFPUi2G2TmwK5Y3bh0PitBHszTgnCh533m62n7HKYnFt/m7ME46rTBsDD0xo kxMmlqoKn8jBaqk0xKEI/DqWhnoEbY6IVICFE14LXuG6BNAZzecegs5XnFuSCrPoyqld PytA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=quP3k3+rryXERuIfXEl69PmcI5NfIleVQ0REMnFXqsA=; b=UONp5/XJrKKFnwW+QCdvzIm+8mk/hT0xez5t+CtVNUSb4m7/edsXpHKvxoh4+S3CA1 cmEphYiru+v+qDPCN0M2OYtC7TM4fSrnMPOpFK9DAg6rz1Gj0zzcVCdmLfo61mp62hJW 289aph06Vf4CtrEQUYBv45bsylgdps0AzWUp7ciJnE7oFg+XoFsqWRcXKuac+GGKWhSp xr0MlBh9EJL8/gAiJZop5QIi6CH6TTscMy3f3E13NXOFiKsO/dsL7IMb0UxXm1GOsoi3 LpF2BFb6V3ZO14T5yhIgInXTo4RARleiNj41zwTIAlsZWKEKfLY/3K19Dy5BExQL+3h9 0/3w==
X-Gm-Message-State: AFeK/H23J5Muxqq7lDB89FNhGenxkcwRSxAQz8/bsYDdshL4YWzl7GVBOAbLtm8gHSmxTQ==
X-Received: by 10.107.63.135 with SMTP id m129mr16776780ioa.149.1491229737546; Mon, 03 Apr 2017 07:28:57 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id y7sm5836521itc.27.2017.04.03.07.28.56 for <iasa20@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Apr 2017 07:28:57 -0700 (PDT)
To: iasa20@ietf.org
References: <CABkgnnW2CYoLcfpTwgqKYo0WKfJAjK1gTmNuaamSp=mibtSDUg@mail.gmail.com> <9AE1C2CB-F2D1-4796-8D10-C625D16D41DC@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d6ecdbc2-bcbb-f4e8-d914-e57ad094714f@gmail.com>
Date: Tue, 04 Apr 2017 02:28:58 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <9AE1C2CB-F2D1-4796-8D10-C625D16D41DC@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/HqPJWex3z1LwZz2eBVHhYWMkqfA>
Subject: Re: [Iasa20] IASA 2.0 minutes
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, 03 Apr 2017 14:29:00 -0000

Hi,

Thanks for the minutes, especially since I had a clash and couldn't attend.

One "funder" said
> We sponsor both the ISOC and the IETF. We would like those to be very separable.
and others supported that view.

I understand that, but I have a question and a concern.

Question: Does that imply or require *legal* separation, or would it be satisfied
by accounting separation (i.e. two separate funds both administered by ISOC)?

Concern: From my experience while working for a large company that was a major
ISOC sponsor at the time, I noticed that the marketing people understood and could
related to ISOC activities (public policy, outreach...) but had no interest in
standards-making, yet the standards people found the non-corporate membership
and non-voting aspect of the IETF troubling. If that is a more general issue,
I have a concern that separating the sponsorship into two funds might do as much
harm as good, at least for the standards-making fund.

Regards
   Brian Carpenter