Hi Dennis, I guess is a big combination of issues, but not having a sponsor is not exactly correct. I know several people tried to sponsor IETF, and have been waiting for long time. I'm biased here, obviously, but I offered myself for Madrid since summer 2001. Only after the Vienna one, they visited the venue. Is a long time to plan ahead ;-) Is not acceptable to me to say "Madrid venue is the best we have ever seen" (obviously, as is the bigger hotel in Europe, just 2 years old, and offers free IPv6 in every guest room), "but is not downtown", and then have one year later a meeting in San Diego which is not either downtown, more expensive, less efficient transport (only taxi, while in Madrid taxi is cheaper and there are two bus lines in front of the hotel), etc. We need to balance if we prefer a sponsor, planned ahead, even if we need to take a taxi or organize shuttles, as we offered for Madrid. Now even if I should have throw away the towel, already working for one more hosted in Barcelona. One year ago I also have realized that several organizations in Latin America are willing to sponsor it, in several big cities, and I'm working with them towards making this happening. So I will say that "not accepting" a sponsor is more correct in this case than "not having" a sponsor. In my opinion we need a 200% open process to qualify if a sponsor and venue are acceptable or not. I'm sure Brian will heard us on this ;-) Regards, Jordi > De: Dennis Fazio <dfz@xxxxxxx> > Responder a: <ietf-bounces@xxxxxxxx> > Fecha: Wed, 16 Mar 2005 07:19:00 -0600 > Para: "ietf@xxxxxxxx" <ietf@xxxxxxxx> > Asunto: Re:reflections from the trenches of ietf62 wireless > > --On March 15, 2005 09:46:49 PM +0100 JORDI PALET MARTINEZ > <jordi.palet@xxxxxxxxxxxxxx> wrote: > > [...] >> If the meetings are planned much more ahead, there will be more resources, >> and even probably will not need for volunteers, because will be possible to >> find a host. > > I'll also have to dispute that a lack of planning was a significant factor in > the wireless difficulties. I've been involved in building every Minneapolis > IETF (44, 50, 53, 58, and now 62) and there have been differing qualities in > planning efforts. Except for the difficulty in getting base stations, > planning efforts this time were more than adequate in spite of the short lead > time available. > > And no matter how far ahead one tries to plan, the secretariat is just not > always able to find sponsors, especially in the recent economic times. > > In Minneapolis, because of the good hotel infrastructure built up over the > past few years and the extensive support with local individual volunteers and > organizations (University of Minnesota, Onvoy), it's pretty easy now to put a > network together here. The volunteer crew could easily put a reliable > production-quality net together with gigabit access and backup links on 6 > weeks notice if necessary. > > If we want a true guaranteed professional production network, then we will > have to contract that to an experienced outfit who can bring in their own > familiar equipment and give contractural accountability of service. So far, > we have not been willing to fund that, so, you get the best that individual > sponsors or groups of volunteers can do, and mostly, that's not bad. > > The wired net and upstream systems were indeed professional and production > quality and did their job well. High-density, high-load radio stuff is just a > pain and maybe will always be; I don't know. > > But it is interesting to note that at one time we were perfectly capable of > conducting productive working group meetings and created great bunches of > very good Internet protocols at them without large numbers of open laptops on > our knees. But, the world changes and I guess that's not possible any more. > > -- > Dennis Fazio > Local Green Dot > > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf ************************************ Barcelona 2005 Global IPv6 Summit Call for Papers and information available at: http://www.ipv6-es.com 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