Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Eric Rescorla <ekr@rtfm.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>,
	 tsvwg IETF list <tsvwg@ietf.org>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>,
	 The IESG <iesg@ietf.org>,
	IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: [Ecn-sane] travel funds for ietf for the next SCE talk?
Date: Fri, 10 May 2019 07:23:53 -0700	[thread overview]
Message-ID: <CABcZeBMG9o94pJTV7JTDpHjt9XT5e3i-GQZXN3Tcb2K9Z4kRuQ@mail.gmail.com> (raw)
In-Reply-To: <C302B225-7806-4D6D-9ECE-FA3EFD6D7CA4@strayalpha.com>

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

On Fri, May 10, 2019 at 6:47 AM Joe Touch <touch@strayalpha.com> wrote:

> Although this is a side issue....
>
> > On May 10, 2019, at 2:17 AM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > Unlike all the other conferences we attend, speakers are not
> > recompensed for their costs in the IETF, either.
>
> Speakers at conferences are not compensated. They register like everyone
> else - that has been ACM, IEEE, IFiP, and OSA policy - I know because in
> some cases, I *wrote* the policy. Students are typically required to
> register at the full rate if they present. In the majority of cases, even
> the chairs pay their own way or at best are comp’d registration.
>

It actually varies. I have been comped where I was asked to give an Invited
Talk.

That said, the IETF is very different from an academic conference, and i
think it would clearly be impractical for the IETF to comp registration for
everyone who presented.

-Ekr


>
> Speakers at trade shows are paid, as are some (but not all) keynotes and
> tutorial presenters.  The latter often get only honoraria and a comp’d reg,
> not enough for travel/lodging in most cases.
>
> The only  people who get a fully free ride that I know of are the IEEE
> Comsoc Board.
>
> Joe
>

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

      parent reply	other threads:[~2019-05-10 14:24 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         ` [Ecn-sane] " Joel Jaeggli
2019-05-12 23:02           ` Ted Lemon
2019-05-10 14:23       ` Eric Rescorla [this message]

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=CABcZeBMG9o94pJTV7JTDpHjt9XT5e3i-GQZXN3Tcb2K9Z4kRuQ@mail.gmail.com \
    --to=ekr@rtfm.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=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