From: Joel Jaeggli <joelja@bogus.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Joe Touch <touch@strayalpha.com>,
Magnus Westerlund <magnus.westerlund@ericsson.com>,
IETF Discussion Mailing List <ietf@ietf.org>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
The IESG <iesg@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] travel funds for ietf for the next SCE talk?
Date: Sun, 12 May 2019 15:27:00 -0700 [thread overview]
Message-ID: <617F1DC0-E891-4548-8BD0-56054ED64E6E@bogus.com> (raw)
In-Reply-To: <4C8193B9-586C-4ED9-B01E-6BA37071600A@fugue.com>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
> On May 10, 2019, at 07:00, Ted Lemon <mellon@fugue.com> wrote:
>
> On May 10, 2019, at 9:47 AM, Joe Touch <touch@strayalpha.com <mailto:touch@strayalpha.com>> wrote:
>> The only people who get a fully free ride that I know of are the IEEE Comsoc Board.
>
> Hm. I’ve never paid to attend IETF. Granted, this is not because IETF comped me, but because I was fortunate enough to have an employer who could afford to send me at no cost to me.
>
> This model unfortunately doesn’t work for open source developers who are not on the payroll of a company with deep pockets.
>
That's an odd definition of having never paid. At the point of registration, you either provided a credit card or requested an invoice. The nominal cost of your involvement in the IETF borne on the part of you or your employer(s) is no doubt considerable, especially during your term on the IESG when the time commitment was also considerable..
For most of the 4 years I spent on the IESG I paid the costs of attending out of my own pocket. I did that, because it was what i signed up for, because it needed to get done and because I believed there was value in the work being done in the operations and management area. Back as an individual contributor I come when I have something to do and some way to pay for it otherwise I wouldn't be there.
joel
[-- Attachment #2: Type: text/html, Size: 3126 bytes --]
next prev parent reply other threads:[~2019-05-12 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw7eZ0Rfvc+tUKx0mG_Bdxqos-DTBn=ojYJCM0UCh38ScA@mail.gmail.com>
[not found] ` <HE1PR0701MB25221DA057496B1A89FD391B95390@HE1PR0701MB2522.eurprd07.prod.outlook.com>
2019-05-10 9:17 ` Dave Taht
2019-05-10 11:35 ` Magnus Westerlund
2019-05-10 12:01 ` Dave Taht
2019-05-10 13:47 ` Joe Touch
2019-05-10 14:00 ` Ted Lemon
2019-05-10 14:12 ` [Ecn-sane] [tsvwg] " Joe Touch
2019-05-10 20:33 ` Brian E Carpenter
2019-05-11 17:24 ` Rodney W. Grimes
2019-05-13 3:11 ` Brian E Carpenter
2019-05-10 15:10 ` Tom Herbert
2019-05-10 15:53 ` Ted Lemon
2019-05-12 22:27 ` Joel Jaeggli [this message]
2019-05-12 23:02 ` [Ecn-sane] " Ted Lemon
2019-05-10 14:23 ` Eric Rescorla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=617F1DC0-E891-4548-8BD0-56054ED64E6E@bogus.com \
--to=joelja@bogus.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=iesg@ietf.org \
--cc=ietf@ietf.org \
--cc=magnus.westerlund@ericsson.com \
--cc=mellon@fugue.com \
--cc=touch@strayalpha.com \
--cc=tsvwg@ietf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox