Re: [Iasa20] IASA 2.0 minutes

Glenn Deen <rgd.ietf@gmail.com> Sat, 22 April 2017 15:41 UTC

Return-Path: <rgd.ietf@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 7D31812944C for <iasa20@ietfa.amsl.com>; Sat, 22 Apr 2017 08:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable 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 OqrWpgjI-3rH for <iasa20@ietfa.amsl.com>; Sat, 22 Apr 2017 08:41:06 -0700 (PDT)
Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (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 D1F9F12943D for <iasa20@ietf.org>; Sat, 22 Apr 2017 08:31:57 -0700 (PDT)
Received: by mail-it0-x243.google.com with SMTP id x188so4368974itb.3 for <iasa20@ietf.org>; Sat, 22 Apr 2017 08:31:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=H6kJUYFw6V1uCQMuR/hGqRbHwNCFy4pJm+OaGPT/qOc=; b=CLfLrlTSNKSQejRMZBG0eKYuZOr89BiTKSyEgcRK8iYwuNfNz5eIZlSNI/6s4jIXY6 6B1bHaOuQTodeiC/vFmHx7R086ttWz0tDYkTsGKSkHXmFEDfmX5aU1Jo21n14K9vOdp/ GEdXcfp6moG0mm5LE2Te73M/I1VCz8Q875z+9EViOQMTxMi30JDVHpsr+Nzt2JKUb5Db LJ4paf0jNf/erbrE8vKbprT0OwTlL9NV8hmGjv0UC4+wPrF8uuRS0QuVVGC7jeEilAj8 b3XOK/13kLaQ26jvyrG0hUaykQtFWSFNh74FCIYabDhUBnQ8xNiiTpCtfKa6x8fScUqn sRNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=H6kJUYFw6V1uCQMuR/hGqRbHwNCFy4pJm+OaGPT/qOc=; b=RAjG2UdIox/Rw+2DjKm9vcG5lKuBQd/qzljQOn0pqKHx+tFtXTQgOMHlr8FKOkz9kN oBw3IMeuFNReAH2VnuzL5Wx36HDWMRBYfWy96urcG96F4k4ERgP8A7b6ryRnqQOOwLWI n8zUxDxG2YHPVH7d1izssdCWlnNyl10SIHFPgQAQHyUzGtBcXXyFEF17/4QgIp97MoLF Lw+WFCqgeM4jeuQwdFIe52pFfDJUjiFo8TKLV8L3CHR2gZ/2f/lqAicK3JcNnKfxnnOk qKev4muMqwT41J1NU2D2guvt1h2DhcR9ptdvJv1HvbsYokJOgqQIbihOUEI4lE4zs+0z 4oiA==
X-Gm-Message-State: AN3rC/4YvTSajAjMwr32S7xdRLQ98yp6FjRbMja87zxDicIQaUNenQm0 59P6Qj8tWu5jdw==
X-Received: by 10.84.209.174 with SMTP id y43mr22433740plh.132.1492875117115; Sat, 22 Apr 2017 08:31:57 -0700 (PDT)
Received: from ?IPv6:2605:e000:141b:18d:ed88:7518:9e43:53b5? ([2605:e000:141b:18d:ed88:7518:9e43:53b5]) by smtp.gmail.com with ESMTPSA id n65sm22110515pga.8.2017.04.22.08.31.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Apr 2017 08:31:56 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Glenn Deen <rgd.ietf@gmail.com>
X-Mailer: iPad Mail (14E304)
In-Reply-To: <592432f8-68a9-8069-1c90-fe7dd70d97fc@gmail.com>
Date: Sat, 22 Apr 2017 08:31:55 -0700
Cc: Jari Arkko <jari.arkko@piuha.net>, "Livingood, Jason" <Jason_Livingood@comcast.com>, "iasa20@ietf.org" <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1609C31-505A-4149-9757-E1226CFD195E@gmail.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> <aca56723-49cf-206f-ae57-13c35498a974@gmail.com> <68A7AFC8-A2BE-4906-9767-4ED2B4BA2268@piuha.net> <592432f8-68a9-8069-1c90-fe7dd70d97fc@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/bG_spFu0R5WOFyHH82KZnrxpau4>
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: Sat, 22 Apr 2017 15:41:07 -0000

There is a big difference between letting a sponsor sponsor breaks and a sponsor saying this money can only go for WG X work, or even more specifically WG X and only if it adopts proposal Y.

Today, IETF sponsorships are broken down and directed to things like breaks, connectivity, receptions, etc and this is done without any influence problem to either the sponsor or the IETF.   

I don't read the "no influence" goal as saying you can't sponsor specific events like breaks, receptions, or even hackathons or bits-n-bites, or connectivity.    Those are all sponsored without either influencing or being dependent to the decisions made by the IETF.

Where the "no influence" line is crossed is when a supporter links their support to decisions, actions, or statements made by the IETF.  For example, selection of WG chairs or ADs, or what documents get discussed in a WG agenda and what others don't get agenda time.   That is not acceptable at any level from any sponsor and is not how the IETF works.

There is only one acceptable way to influence the IETF - contribute to discussions, drafts, and of course running code.

I will say that it's clearer to explain and justify to the decision makers at sponsor if you can say "we spent $X and sponsored the afternoon break at IETFxyx".   than the more generic "we donated $X to the IETF" even when X is the same amount.  Some many argue that it's the same amount and so what's the difference?  The difference is that the sponsor sees more value in being acknowledged for sponsoring a break than for contributing money to a generic bucket.

If we moved away from being able to identify specific meeting elements that the sponsors have sponsored and get acknowledged for, we would likely see a drop off in sponsorships at-least in the $ amount from the sponsors.  When budgets get challenged at the sponsors office it's much easier to drop that $20,000 sponsorship to $5,000 when there isn't any direct impact to the sponsor from the cut.  If however, that missing $15,000 means that the new reduced  break food is awful and would reflect badly on the sponsor then the sponsor is motivated not to make the cut.

That doesn't mean the sponsorship fees simply equal the cost of what they are sponsoring. It's a sponsorship and not a direct contribution by the sponsor. The actual planning and delivery is done by the IASA.

Glenn Deen

Sent from my iPad

> On Apr 21, 2017, at 1:19 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> very, very careful that if money is earmarked for the IETF, it is absolutely neutral with
> regard to the content of the IETF's work program.
> 
>   Brian