IETF Logo Mail Archive

Re: [Iasa20] IASA 2.0 minutes

"Livingood, Jason" <Jason_Livingood@comcast.com> Tue, 11 April 2017 22:26 UTC

Return-Path: <Jason_Livingood@comcast.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 51CBC126DEE for <iasa20@ietfa.amsl.com>; Tue, 11 Apr 2017 15:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level:
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, LOTS_OF_MONEY=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 EH-LdUF6se6S for <iasa20@ietfa.amsl.com>; Tue, 11 Apr 2017 15:26:23 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF455128656 for <iasa20@ietf.org>; Tue, 11 Apr 2017 15:26:22 -0700 (PDT)
X-AuditID: 60721c4c-b47ff7000000bcc0-90-58ed580cae6d
Received: from VAADCEX38.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id AC.C3.48320.C085DE85; Tue, 11 Apr 2017 18:26:21 -0400 (EDT)
Received: from VAADCEX37.cable.comcast.com (147.191.103.214) by VAADCEX38.cable.comcast.com (147.191.103.215) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 11 Apr 2017 18:26:19 -0400
Received: from VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0]) by VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0%19]) with mapi id 15.00.1263.000; Tue, 11 Apr 2017 18:26:19 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "iasa20@ietf.org" <iasa20@ietf.org>
Thread-Topic: [Iasa20] IASA 2.0 minutes
Thread-Index: AQHSqWWSW8lYo4tL+k6DrHSC8dclRKGz/YUAgAAmHwCADK7XAA==
Date: Tue, 11 Apr 2017 22:26:19 +0000
Message-ID: <6CC36D20-B293-4F9B-984B-A1A88CFD7F83@cable.comcast.com>
References: <CABkgnnW2CYoLcfpTwgqKYo0WKfJAjK1gTmNuaamSp=mibtSDUg@mail.gmail.com> <9AE1C2CB-F2D1-4796-8D10-C625D16D41DC@cooperw.in> <d6ecdbc2-bcbb-f4e8-d914-e57ad094714f@gmail.com> <A15970F6-4D71-4C98-A057-393D5CD510EA@cable.comcast.com>
In-Reply-To: <A15970F6-4D71-4C98-A057-393D5CD510EA@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [68.87.29.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AB8441AFB3233C43821B8498084A8B58@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsWSUOxpocsb8TbCYPYfLYsl0zcyOTB6LFny kymAMYrLJiU1J7MstUjfLoEr493j66wF00Qr5p9dz9zAeEGki5GDQ0LAROJ2i0kXIxeHkMB2 JolTS1ewQjiHGCW+HuhjhHBOMkr0vVzE0sXIycEmYCZxd+EVZhBbREBdYkP3HLC4sICaRMOx eYww8cYZZ1kgbCeJL78uM4HYLAKqEpf7+8B6eQVcJPY828AOseATo8S199vYQRKcAq4S3VP6 wJoZBcQkvp9aA9bMLCAucevJfDBbQkBAYsme88wQtqjEy8f/WEFsUQE9iZk7/zJCxHUkzl5/ AmUbSGxduo8FwpaXODLhHwvI+8wCmhLrd+lDjHeQ2L2ykx3CVpSY0v2QHeJOQYmTM59AtYpL HD6yg3UCo9QsJBfNQpg0C8mkWUgmzUIyaQEj6ypGubLExJTk3Iz80hIDI73kxKScVL3k/Nzk xOISEL2JERS1RTI+Oxg/TfM4xCjAwajEw9vl9jZCiDWxrLgyFxg9HMxKIrwtLkAh3pTEyqrU ovz4otKc1OJDjNIcLErivF43b0UICaQnlqRmp6YWpBbBZJk4OKUaGLWV5v/L9WJrW7f6o8fM +4svTdpxxS9gldSlssaLETwWrNHq82UOmugYnmxoClRcc/mV4Kv6Jysdznetv3BKR/7DNYFK 3oWzJEtXVB0ITw6t6P/72LqqynQqZ6Ht19268xlPPBU+t3HHjDfaS60i05WK3xRVOjMudG98 MUPisjLnpvffSqxtO5RYijMSDbWYi4oTAUbyqEXWAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/FyM5wwLcQLzL22sbCVjzk9T4_rg>
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: Tue, 11 Apr 2017 22:26:24 -0000

Adding one more note on this. When you sponsor ISOC at the Platinum level (not sure if this is the case for other levels), you can allocate portions of your USD$100,000 to different special project areas, such as Cryptech. I knew something was amiss this year when one of the special projects came to me seeking a donation and I thought it odd they were unaware that one had already been made. As it turns out, due to some sort of snafu, the funds were never allocated to the specified projects and those projects were not aware of the intended allocations either.

To ISOC’s credit, this was rapidly resolved. But I think it does provide a recent illustration of why it’d be nice to have greater / more clear lines of financial separation. When we’re talking about hundreds of thousands to millions of dollars per year this seems to me the prudent thing to do and will make everything easier and more transparent.

Jason

On 4/3/17, 4:45 PM, "Livingood, Jason" <Jason_Livingood@comcast.com> wrote:

    On 4/3/17, 10:28 AM, "iasa20 on behalf of Brian E Carpenter" <iasa20-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:
    > 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)?
        
    Accounting separation is IMO what we have today, not what is being proposed. That is legal/financial separation, such as a different accounts payable name and tax ID number for example.   
    
    > 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.
    
    IIRC there were at least 3 global hosts who went to the mic line to express the opposite – that this would make sponsorships easier on an administrative level for sponsors (which tends to stimulate rather than suppress sponsorships).
    
    - Jason

v2.23.0 | Report a Bug | By Email