Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Joe Touch <touch@strayalpha.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	IETF Discussion Mailing List <ietf@ietf.org>,
	Dave Taht <dave.taht@gmail.com>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>,
	The IESG <iesg@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] [tsvwg] travel funds for ietf for the next SCE talk?
Date: Fri, 10 May 2019 07:12:24 -0700	[thread overview]
Message-ID: <B091A35A-265F-4D8E-93E1-AF6071BF6E12@strayalpha.com> (raw)
In-Reply-To: <4C8193B9-586C-4ED9-B01E-6BA37071600A@fugue.com>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]



> On May 10, 2019, at 7:00 AM, 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.

Nor academics. I stopped coming because I couldn’t find a gov’t agency interested in supporting my participation either (and my current employer doesn’t either).

This is a problem not only for general attendance but also for the IESG - which impacts some decisions being made as well.

Joe


[-- Attachment #2: Type: text/html, Size: 2549 bytes --]

  reply	other threads:[~2019-05-10 14:12 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   ` [Ecn-sane] " 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         ` Joe Touch [this message]
2019-05-10 20:33           ` [Ecn-sane] [tsvwg] " 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         ` [Ecn-sane] " Joel Jaeggli
2019-05-12 23:02           ` 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=B091A35A-265F-4D8E-93E1-AF6071BF6E12@strayalpha.com \
    --to=touch@strayalpha.com \
    --cc=dave.taht@gmail.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=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