Re: [IAOC] Badges and blue sheets

Ok, so then let's ask for comp status.

I've been paying from my own pocket all my IETF registration and traveling
expenses from the last 2 years, and can't further do it, specially because
it seems to me that the systems is unfair if we don't have good reasons to
justify each case.

Let me know what the IAOC needs from me to justify my case. I'm happy to
send it publicly.

Regards,
Jordi

From: Bob Hinden <bob(_dot_)hinden(_at_)gmail(_dot_)com>
Reply-To: <bob(_dot_)hinden(_at_)gmail(_dot_)com>
Date: Tue, 16 Nov 2010 09:17:42 -0800
To: <jordi(_dot_)palet(_at_)consulintel(_dot_)es>
Cc: "iaoc(_at_)ietf(_dot_)org" <iaoc(_at_)ietf(_dot_)org>, Bob Hinden 
<bob(_dot_)hinden(_at_)gmail(_dot_)com>, IETF
discussion list <ietf(_at_)ietf(_dot_)org>
Subject: Re: [IAOC] Badges and blue sheets

Jordi,

On Nov 13, 2010, at 2:38 PM, JORDI PALET MARTINEZ wrote:

I'm still not convinced.


Understood.


If you accept to be waived, you should accept that the waiver is made
public. It is not a matter of privacy, you're not forced to.



I disagree, in some cases it would be embarrassing for the people involved and
likely cause us to loose important contributors.  Not everyone would like
their status to be public.

I don't see any issue with reporting of the total number of comps, but without
listing the people involved.  Not sure if you have noticed that there are
comps listed on the attendee list.  Most of the comps go to the host who makes
a large financial contribution to host the meeting.


Moreover, and this needs to be answered, or we have a problem. What is the
RFC that allows this waiver ?



No RFC defines this level of detail, nor should it.  BCP101 gives the
authority to the IAOC to plan and operate IETF meetings.  This, like many
other meeting related decisions (e.g., size of cookies, registration fees,
venues, etc.) falls under that authority.  The IAOC works very hard to listen
to the community, but it wouldn't work to define all of the details of
meetings in an RFC.

Bob

From: Marshall Eubanks <tme(_at_)americafree(_dot_)tv>
Reply-To: <tme(_at_)americafree(_dot_)tv>
Date: Fri, 12 Nov 2010 13:24:49 -0500
To: Yoav Nir <ynir(_at_)checkpoint(_dot_)com>
Cc: "iaoc(_at_)ietf(_dot_)org" <iaoc(_at_)ietf(_dot_)org>, IETF discussion 
list <ietf(_at_)ietf(_dot_)org>,
"jordi(_dot_)palet(_at_)consulintel(_dot_)es" 
<jordi(_dot_)palet(_at_)consulintel(_dot_)es>
Subject: Re: [IAOC] Badges and blue sheets


On Nov 12, 2010, at 4:08 AM, Yoav Nir wrote:


On Nov 12, 2010, at 7:36 AM, JORDI PALET MARTINEZ wrote:

Hi Henk,

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.


+1

Marshall

This is an open organization right ? I will be VERY concerned if we don't
have this information being made public immediately. It sounds really
really
strange to me.


You pay for everything the Spanish government does, which, I assume,
includes
some kinds of welfare like unemployment benefits. You don't get a list of
all
people who get these benefits, do you?

Is it documented in any RFC ?

Moreover, if I'm in between jobs, or need a new job, or whatever, I think
is
good for me that others know, in case I can get some new offers.


People look for jobs in various ways at their discretion. Being from Spain,
there are only 6 more of your countrymen at the Beijing meeting. How many
relevant job offers would you get?
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the use of the 
individual(s) named above. If you are not the intended recipient be aware that 
any disclosure, copying, distribution or use of the contents of this 
information, including attached files, is prohibited.



_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf