Re: [Iasa20] IASA 2.0 minutes

[Michael Richardson <[e-mail]>]

Glenn Deen <[e-mail]> wrote:
    >> But general-purpose support is more useful than support that can only
    >> be spent on certain things. I think we want to give sponsors choices
    >> as to what things are *branded* as having received their support,
    >> without being restricted by actually spending the money received from
    >> a sponsor on exactly only those things.

    > We actually are more general purpose already. The current sponsorship

...

    > What I'm picking up in these exchanges is that what are currently do in
    > terms of variety sponsorship modes for meetings is acceptable, and that
    > the modes of sponsorship, general, acknowledgement for a meeting
    > feature, or in kind, are acceptable.

Yes, I think you are reading this well.

    > The core problem isn't the modes of sponsorships, it's in the long term
    > stability and funding reliability for the IETF, as well as the ability
    > to direct how the funding is applied to benefit the IETF.  We currently
    > are operating on a shorter term scale financially and without having
    > long term financial control of our own established, it's very hard to
    > have the independence to do long term planning.

Actually, I think that many of the "modes of sponsorship" are a core problem
in that much of it is tied to events that occur at the "meetings".

I do like the SIGCOMM model, and I think we are mostly there, btw, but it's
hard to be recognized as the sponsor of the Tuesday Lunch, if there wasn't a
Tuesday Lunch.  Do the SIGCOMM conference fund other parts of SIGCOMM?

As such, as part of the IASA2, I would like to introduce new "modes of
sponsorship" that are not tied to the physical meetings.  Right now, each
meeting lets us raise about $0.5M to support the operation of the IETF's
non-meeting operations.   If we were reduce the number of physical meetings
to 2 a year, we'd be missing $0.5M in revenue.

What other places can we give sponsor's recognition?
     semi-serious:   RFC8000 to RFC8999 -- brought to you by RedBull!
     serious:   RFC9000 to RFC9999 -- created in partnership with ITU.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-