Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets

Perhaps we should follow the example of Oxford and Cambridge and make them
sit at a different table and do menial tasks for the Gentlemen students.

Oh wait, they abolished that in the 19th Century.

The IETF business model certainly has problems, but the proportion of
attendees paying for meetings is not one of them. The problem with a
business model based on conference fees is that conferences are cyclic.

If I was running ICANN I would observe that my organization directs a vast
cash flow but a very narrow political constituency. I would therefore look
to funnel some of that cash flow into organizations that can enhance my
political position.

On Fri, Nov 12, 2010 at 7:03 AM, Shane Kerr <shane@isc.org> wrote:

> Yoav,
>
> On Fri, 2010-11-12 at 11:08 +0200, Yoav Nir wrote:
> > On Nov 12, 2010, at 7:36 AM, JORDI PALET MARTINEZ wrote:
> >
> > > I don't agree. If there is people "essential" to the meeting but can't
> pay,
> > > as we all pay for that, we have the right to know.
> >
> > I disagree with that. There is a privacy issue here. If x can't pay
> > his way, and needs a comp ticket, it's enough that the IETF chair
> > knows about this. It's not our right to know of their financial
> > situation.
>
> While I don't agree that we have a "right" to know who is getting free
> access to IETF meetings, I do agree with Jordi that it seems like a
> reasonable thing to make public.
>
> Sometimes transparency trumps privacy. This is especially true when
> money is changing hands (or not changing hands, in this case).
>
> For example, in some elections if you want to be a candidate you must
> publish part of you your finances (for example, your tax records). This
> is to prevent corruption. Some people refuse to do this, and so may not
> run for office.
>
> It is sometimes possible to create systems to meet the needs of privacy
> and oversight - for example a closed review board - but I think just
> publishing a list of who gets free access to each IETF is probably good
> a good idea.
>
> Cheers,
>
> --
> Shane
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

-- 
Website: http://hallambaker.com/