[Chapter-delegates] Proposal for IETF Registration fee support for Chapters

[Eric Burger]

So my question is, more especially if the IETF is local, why would that person not be going anyway?

If the answer is because they cannot afford it, perhaps we should be expanding the IETF Fellows program?

If the answer is because they are involved with a chapter, that could cover just about every IETF participant, more especially IETF participants who are not coming from big companies who are paying their way already. This would have a significant impact on IETF and ISOC revenues and surplus, respectively.

I could see a powerful draw for Chapter involvement - “If you are involved in the IETF, get involved with your chapter and you might not have to pay IETF registration fees.” However, I can also see a powerful temptation for abuse. Who decides who gets the subsidy? Is it fair? What about an individual who separated from their large employer, and has no intent of ever joining a chapter? (I am thinking of a real person who has served on the ISOC board, not a hypothetical fiction of my imagination.) Is it fair to them, or the IETF, if we do not let them be eligible for subsidy?

> On Mar 8, 2017, at 10:50 PM, Susannah Gray <susannah.gray at gmail.com> wrote:
> 
> - Our chapter certainly wouldn't be sending random people: if we were
> able, we'd send someone who is technically competent and able to
> participate fully in WG sessions and who is interested in standards
> development with the clear purpose of reporting back to the Board and to
> the membership on the latest developments.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://elists.isoc.org/mailman/private/chapter-delegates/attachments/20170309/db24b3b4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP
URL: <https://elists.isoc.org/mailman/private/chapter-delegates/attachments/20170309/db24b3b4/attachment.asc>