IETF Logo Mail Archive

Re: [Iasa20] Memo exploring options for IASA 2.0 models

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 16 February 2018 18:47 UTC

Return-Path: <ajs@anvilwalrusden.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 02980126C2F for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 10:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=Ta64Q1ME; dkim=pass (1024-bit key) header.d=yitter.info header.b=JXmn3SB6
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 GZR3u2eizNSU for <iasa20@ietfa.amsl.com>; Fri, 16 Feb 2018 10:47:57 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B7E912422F for <iasa20@ietf.org>; Fri, 16 Feb 2018 10:47:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 93B1EBD351 for <iasa20@ietf.org>; Fri, 16 Feb 2018 18:47:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1518806846; bh=w2T+IxyyCUII6FYxyvNl3yGIBu9+PFNtlHht86P6XPc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Ta64Q1MEQ6Gupe1XF3eAeZYG8ABkBZ9BzvNx9GrhTLMA1eiFED8JD13Z3MG7yHLYR eMl2H+99its/ei5eoHUPsDzkEI05xltXV+RZVQWASDKKgxX8BGZJPOxt2QmuhF/sTm r3V+bbkdEN8ofsm8xyZ3u/pU9Xz9QjOp+cweDU9U=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c4lFu7BU1Sk1 for <iasa20@ietf.org>; Fri, 16 Feb 2018 18:47:25 +0000 (UTC)
Date: Fri, 16 Feb 2018 13:47:23 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1518806845; bh=w2T+IxyyCUII6FYxyvNl3yGIBu9+PFNtlHht86P6XPc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=JXmn3SB629JFShtZJK4w98J6QZBHt9BIDtx2YVpGln+kMJhqDeaQsR4vX1gtxuZmZ vl0SECVm00k/89wbtD+r9JmLk2Jp020+wRnAmOJaB9WVKjZvJbdCpU0Hb90FNW6h+j D3EAl9KXT/16qMa/Uxng/+uy+jAqjQ90c+c+Ifmg=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: iasa20@ietf.org
Message-ID: <20180216184723.y7go5mygc7hc6qiy@mx4.yitter.info>
References: <4483006c-1652-7340-19f8-8d0579af8213@cdt.org> <CA+9kkMBK0YzWmVZqFnRuzKj_mTZeSHy4xhZSgrjjNr7NnO68DQ@mail.gmail.com> <CABtrr-V88xYcRDNMDz8aH_6Jq-fvtDLMwpYxxXFxLZv-S25SSg@mail.gmail.com> <CAL02cgQu-zi_FySTsDX_HbPOt+FrFYypSvPLwY8QfnfffR3QrQ@mail.gmail.com> <CA+9kkMC_BjV4DdxNSk5LrgR0uU1vVF3YDyqobFYc7-t_idx60w@mail.gmail.com> <CAPdOjkhqQiqgeWUeMRb-Q3MzKtk=fEYxzQdmaaWoaGvZsQ8+Bg@mail.gmail.com> <CA+9kkMAQijV+vFZXosFPT3tFen_Azjitjdf=cEEKz2ZRc+tbqQ@mail.gmail.com> <CAL02cgQFg+XVnhKW8FveHv11ZrL85R4Ddjj1T8t00QwR2B3k4Q@mail.gmail.com> <CA+9kkMD2YpkPjCEiSGFMAY+w_U6FRYTXoBvMxzEj7AUdw0PLSA@mail.gmail.com> <CAL02cgQ+OD90gddHnWoMgyYRDV8CkMLHoVX7vxrUDbUQ8VLg_A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAL02cgQ+OD90gddHnWoMgyYRDV8CkMLHoVX7vxrUDbUQ8VLg_A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/twRQeodmymyHdSopSMHe1dRp6d0>
Subject: Re: [Iasa20] Memo exploring options for IASA 2.0 models
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: Fri, 16 Feb 2018 18:47:59 -0000

On Fri, Feb 16, 2018 at 01:35:17PM -0500, Richard Barnes wrote:
> IIUC, people who want to donate directly to IETF would write a check to
> IETFAdminOrg (or whatever we call the subsidiary) -- that's the entity that
> owns the account where the check is going to get deposited.  ISOC would just
> have to do some verification on the back end to make sure that those
> contributions are compatible with its tax position.

They'd also issue the tax receipt, right?  That is, IETFAdminOrg
wouldn't be able to issue such receipts, so from the accountant's
point of view the donation or sponsorship will have to ISOC, maybe?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email