Re: [Ietf108planning] Registration open for IETF 108

S Moonesamy <sm+ietf@elandsys.com> Sun, 28 June 2020 17:40 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF0B3A0E18 for <ietf@ietfa.amsl.com>; Sun, 28 Jun 2020 10:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.687
X-Spam-Level:
X-Spam-Status: No, score=-1.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, LOTS_OF_MONEY=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 ldl5ljJTI3lr for <ietf@ietfa.amsl.com>; Sun, 28 Jun 2020 10:40:09 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id E4C8E3A0E17 for <ietf@ietf.org>; Sun, 28 Jun 2020 10:40:00 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.121.160]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 05SHdNjM028574 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 28 Jun 2020 10:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1593365978; x=1593452378; i=@elandsys.com; bh=xhwpoLE7L3L2vsnns5YcEAwGYAhL+rQJVSMpwwwSuT0=; h=Date:To:From:Subject:Cc; b=V9LuvsxEEBOqTJiUVb8PSml/fy+NToweMWfOOj61stpgEgb4HAYnMtbU8Ibs8RIBv q03uIR+phqPqC7geflrABz10FYE1EjzGyUTYMXALRHe8ydCAH42jFlDO7h/f9lwyzU NsEvurBkwjr2Y4fUz2xtpubkezP1WVTWdHHXSIiQ=
Message-Id: <6.2.5.6.2.20200628103520.0bfc8f88@elandsys.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 28 Jun 2020 10:37:50 -0700
To: Toerless Eckert <tte@cs.fau.de>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [Ietf108planning] Registration open for IETF 108
Cc: Christian Huitema <huitema@huitema.net>, Carsten Bormann <cabo@tzi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zcWhyKRb1_DZGud2VgwlmNltado>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jun 2020 17:40:15 -0000

Hi Toerless,
At 04:57 PM 12-06-2020, Toerless Eckert wrote:
>We already have a not very transparent system of patronage via
>options such as host, global host or whatever it is. Sure, its somewhere
>deep in some ISOC/LLC/IETC/meeting-committe/... web-pages. I for once
>would like to see a web page that lists all financial contributions.
>
>If someone wants a contribution to be anonymous, then the name
>of the contribution is hidden, but the contribution is shown.
>
>Adding more options for patronage would IMHO rather increase
>contributions on the lower end.
>
>More transparency comes at the cost, but i think more transparency is
>good for IETF.

Christian's example of operas and museums may be useful to get a 
general sense of how patronage works.  I don't think that it is 
directly applicable to the IETF as charitable organizations don't 
usually fund standards development.

The LLC only received $70,000 in sponsorship for the first quarter of 
the year.  After taking a look at the information which is published, 
I would say that it is likely that the IETF would run into financial 
difficulties.

Regards,
S. Moonesamy