Hi Lucy, Yes, I know is much more complex issue. Actually, I think is not fair that volunteers don't get their traveling expenses and registration paid, because as it has been said, being at the NOC, probably means they can't even actually participate in the meeting itself. And I think this is the same situation for IESG members. Answering also a previous response from Yoav Nir, it is not an IETF issue if a NOC member or an IESG member is getting paid from a company to do his job. Actually this is a big discrepancy, because the IETF participants ARE individuals, not companies, so obviously it is good that some companies allow IESG members to actually use most of his time for the IESG, and I agree with the policy that we can only have IESG members that are in that situation if we want to warranty they have the time to commit, but either we pay all them (NOC and IESG their expenses and registration), or none. We need a consistent policy. Looking for transparency at IETF, I think it is more clear for all that there is no waiver for anyone's registration fee. But if we opt for offer complimentary to some, it should be made clear and publicly who and why (NOC, IESG, host team, future host team, others). Regards, Jordi > From: Lucy Lynch <llynch@xxxxxxxxxxxxxxxx> > Reply-To: <llynch@xxxxxxxxxxxxxxxx> > Date: Tue, 16 Nov 2010 07:44:16 -0800 (PST) > To: JORDI PALET MARTINEZ <jordi.palet@xxxxxxxxxxxxxx> > Cc: "iaoc@xxxxxxxx" <iaoc@xxxxxxxx>, IETF discussion list <ietf@xxxxxxxx> > Subject: Re: [IAOC] Badges and blue sheets > > On Tue, 16 Nov 2010, JORDI PALET MARTINEZ wrote: > >> I just realized something ... >> >> Note that I'm not saying that volunteer NOC is not good, but, if they are >> waived from the registration fee ... Why IESG members not ? > > Jordi - > > With respect, this is a more subtle problem set then you're > seeing. I'm a NOC volunteer and I paid on own way this time > and have for most meetings. > > Back when I worked for the University of Oregon and volunteering > I had my registration covered for a couple of meetings when I > traveled on my own dime to help get me to the meeting (and the NOC). > > My current contributions are not core to getting the network up, > so I just figure out how manage my day job, the IETF, and the NOC > on my own. At least once as an IAOC member I paid my own registration > and travel as the UO didn't see any value in the process role. I > used vacation time and could manage the expense on my own, so I did. > > - Lucy > >> Is that we valuate less the effort of the IESG members, which is across all >> the time in the year, than NOC that is may be 6-7 weeks per year (assuming 2 >> weeks or so needed per meeting) ? >> >> I think we really need to have a balance on this. >> >> Regards, >> Jordi >> >> >> >> >>> From: JORDI PALET MARTINEZ <jordi.palet@xxxxxxxxxxxxxx> >>> Reply-To: <jordi.palet@xxxxxxxxxxxxxx> >>> Date: Sun, 14 Nov 2010 06:38:16 +0800 >>> To: IETF discussion list <ietf@xxxxxxxx> >>> Cc: "iaoc@xxxxxxxx" <iaoc@xxxxxxxx> >>> Subject: Re: [IAOC] Badges and blue sheets >>> >>> I'm still not convinced. >>> >>> 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. >>> >>> Moreover, and this needs to be answered, or we have a problem. What is the >>> RFC that allows this waiver ? >>> >>> Regards, >>> Jordi >>> >>> >>> >>> >>>> From: Marshall Eubanks <tme@xxxxxxxxxxxxxx> >>>> Reply-To: <tme@xxxxxxxxxxxxxx> >>>> Date: Fri, 12 Nov 2010 13:24:49 -0500 >>>> To: Yoav Nir <ynir@xxxxxxxxxxxxxx> >>>> Cc: "iaoc@xxxxxxxx" <iaoc@xxxxxxxx>, IETF discussion list <ietf@xxxxxxxx>, >>>> "jordi.palet@xxxxxxxxxxxxxx" <jordi.palet@xxxxxxxxxxxxxx> >>>> 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@xxxxxxxx >>>>> https://www.ietf.org/mailman/listinfo/ietf >>>>> >>>> >>>> _______________________________________________ >>>> Ietf mailing list >>>> Ietf@xxxxxxxx >>>> 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@xxxxxxxx >>> 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. >>> >>> >> >> >> >> ********************************************** >> 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@xxxxxxxx >> https://www.ietf.org/mailman/listinfo/ietf >> > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > 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@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf