Re: Meetings in other regions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



JORDI PALET MARTINEZ wrote:
> That's part of the problem, sponsorship should be managed from a different
> perspective, and totally decoupled from the venue itself.
>
> IETF should look for "global" sponsors, in a given time frame, for example
> for a year, or just a meeting if needed, but as said *decoupled* from the
> venue.
> 
> Local sponsors can take care of the social, breaks, etc.

As you know Jordi local sponsors have historically been invaluable in
getting access to local resources, like network connectivity and
handling the logistics of network setup.

having local support is always better than not having it.

> At this way the main costs (meeting rooms, AV, secretariat, etc.), are
> covered in a fair and planned way, and not dependant on each meeting itself.

Some costs. E.G. connectivity are in fact highly dependant on the
meeting location. You whole budget takes a bath the first time you have
to sign a 12 month lease with the ptt/ilec on an e/ds-3 to get
connectivity into a venue. Do you then go back to that venue for the
next meeting because you're still paying $8000 a month for the circuit?

> Also this provides the IAD the budget ahead so can book the most convenient
> venues at least 18 months up-front, and allow a cost reduction for both IETF
> itself, and attendees which can get better traveling deals and more time for
> those that need to request an authorization to their management, etc.
> 
> Regards,
> Jordi
> 
> 
> 
> 
>> De: YAO Jiankang <ietf@xxxxxxxx>
>> Responder a: <ietf-bounces@xxxxxxxx>
>> Fecha: Tue, 18 Jul 2006 11:31:56 +0800
>> Para: John L <johnl@xxxxxxxx>
>> CC: <ietf@xxxxxxxx>
>> Asunto: Re: Meetings in other regions
>>
>>
>> ----- Original Message -----
>> From: "John L" <johnl@xxxxxxxx>
>> To: "YAO Jiankang" <ietf@xxxxxxxx>
>> Cc: <ietf@xxxxxxxx>
>> Sent: Tuesday, July 18, 2006 10:34 AM
>> Subject: Re: Meetings in other regions
>>
>>
>>>>> I do think there is considerable merit in identifying a set of venues
>>>>> that are known to do a good job and using them whenever a meeting is
>>>>> scheduled for their part of the world.  Minneapolis is roughly in the
>>>>> middle of the populated part of North America, the hotel knows us,
>>>>> why not go back there?
>>>> it seems boring that everytime we go to the same venue.
>>> Not to put too fine a point on it, but if you don't find IETF meetings to
>>> be exciting enough on their own merits, it's OK if you don't go.
>> Why not kill two birds with a stone? after enjoying the nice merits of the
>> IETF meeting, you can appreciate the different life in the different cities at
>> the weekend.
>>
>>
>>>> It is also unfair to those who traveled from other regions such as
>>>> europe and asia.
>>> I said "whenever a meeting is scheduled for their part of the world."
>>> When it's time for a meeting in North America, hold it in Minneapolis.
>>> If we find similarly reliable venues in Europe or Asia, use them when the
>>> meetings are in those parts of the world.
>> Every IETF meeting is sponsored by the different companies. The sponsors
>> normally love holding the meeting in the local city where the sponsor is
>> located. Even you and me agree that the meeting is held in the same city, the
>> sponsor may disagree.
>>
>>
>>
>>> R's,
>>> John
>>>
>>> _______________________________________________
>>> 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 mailing list
> Ietf@xxxxxxxx
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]