Please, take the opportunity that you are going to modify the registration page to remind about the invoices. In many economies/accounting systems, if you don't have an invoice, you can't account (legally speaking) the cost of the IETF attendance. I've been asking for this for more than 3 years already ... Hopefully now is going to happen ! I've been already in the case where auditors reject it and needed to pay from my own pocket instead of the company expenses. I think there is no excuse at all for IETF not doing so. Actually, and this is not fault, there is not excuse at all for not having done this just right after the first request 3 years ago or even sooner (if somebody else requested first). Regards, Jordi > De: Ray Pelletier <rpelletier@xxxxxxxx> > Responder a: <ietf-bounces@xxxxxxxx> > Fecha: Tue, 11 Jul 2006 11:14:23 -0400 > Para: "Gray, Eric" <Eric.Gray@xxxxxxxxxxx> > CC: <ahawrylyshen@xxxxxxxxxxxxx>, <ietf@xxxxxxxx> > Asunto: Re: The IETF 66 Attendees Alias > > > > Gray, Eric wrote: > >> Ray, >> >> May I make a suggestion for the next time around? >> >> How about if the registration page asks if you want >> to be subscribed to this list? >> >> > Will do. > >> As I understood it, this experiment was performed at >> the request of people on the ietf discussion mailing list. >> >> > Nope. It was my attempt to provide *useful*, *important* info to > attendees only, and a list to send a meeting survey sometime after the > meeting. I did not implement it well. > >> That list is _not_ the appropriate place to talk about >> cookie shortages, mail and netowrk problems and issues with >> the hotel, _either_. >> >> Since the registration page already has a number of >> questions it ask about things we might or might not want to >> do. Why not add one more - and assume the default answer >> is "no"? >> >> I like the idea of having a separate list because it >> allows me to decide quickly what I can safely ignore most >> of the time. >> >> > -- > >> Eric >> >> --> -----Original Message----- >> --> From: Ray Pelletier [mailto:rpelletier@xxxxxxxx] >> --> Sent: Monday, July 10, 2006 10:53 PM >> --> To: ahawrylyshen@xxxxxxxxxxxxx >> --> Cc: ietf@xxxxxxxx >> --> Subject: Re: The IETF 66 Attendees Alias >> --> >> --> Alan, et al. >> --> Message received. >> --> I agree. >> --> Changes being made. >> --> Experiment provided valuable information. >> --> Sorry for the pain. >> --> Ray >> --> IAD >> --> >> --> >> --> Alan Hawrylyshen wrote: >> --> >> --> > Folks; >> --> > >> --> > I understand the utility and need for the administrative >> --> staff to have >> --> > a mailing alias for all registered delegates for the 66th >> --> IETF event. >> --> > However, in all the meetings I have attended - which is >> --> more than a >> --> > few, but less than most of you - I have never been >> --> deluged with such a >> --> > volume of non-critical announcements in my main inbox. >> --> > >> --> > I hope that people will understand my strong desire and sympathize >> --> > with my point of view when I request that all general >> --> IETF messages be >> --> > posted uniquely to the IETF general list and that this address be >> --> > reserved only for the critical or emergency announcements by the >> --> > administrative staff. One step better would be for this >> --> address to be >> --> > moderated so we no longer receive various complaints about water >> --> > closets and wifi unless we seek them out on the IETF >> --> discussion lists. >> --> > :-) >> --> > >> --> > Perhaps if there is a strong desire to have a 'hallway or >> --> watercooler >> --> > style' list for discussions pertaining uniquely to IETF >> --> 66 attendees, >> --> > we could create a NEW mailing list that is OPT-IN called >> --> > 66attendees-chat (or similar) at ietf.org. I'd even >> --> volunteer to set >> --> > one up (at a different domain of course) for the duration >> --> of IETF 66. >> --> > >> --> > My sincere apologies if I have misunderstood the purpose of the >> --> > 66attendees address but my BlackBerry is going crazy with >> --> things that >> --> > I would not normally choose to have in my commercial, >> --> corporate email >> --> > box. >> --> > >> --> > Respectfully, >> --> > >> --> > Alan Hawrylyshen >> --> > >> --> > _______________________________________________ >> --> > Ietf mailing list >> --> > Ietf@xxxxxxxx >> --> > https://www1.ietf.org/mailman/listinfo/ietf >> --> > >> --> >> --> _______________________________________________ >> --> Ietf mailing list >> --> Ietf@xxxxxxxx >> --> https://www1.ietf.org/mailman/listinfo/ietf >> --> >> >> >> > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.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@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf