Re: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom Network not under NOC Control)

Thomas Froment <Thomas.Froment@alcatel-lucent.fr> Tue, 29 July 2008 10:19 UTC

Return-Path: <72attendees-bounces@ietf.org>
X-Original-To: 72attendees-archive@ietf.org
Delivered-To: ietfarch-72attendees-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2186D28C20A; Tue, 29 Jul 2008 03:19:06 -0700 (PDT)
X-Original-To: 72attendees@core3.amsl.com
Delivered-To: 72attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D628428C20D for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 03:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h10wbQLwgtst for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 03:19:03 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 96E9A28C20A for <72attendees@ietf.org>; Tue, 29 Jul 2008 03:19:03 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com [155.132.6.76]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m6TAIjrN029914; Tue, 29 Jul 2008 12:18:54 +0200
Received: from [127.0.0.1] ([155.132.188.70]) by FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Tue, 29 Jul 2008 12:18:45 +0200
Message-ID: <488EEE84.700@alcatel-lucent.fr>
Date: Tue, 29 Jul 2008 12:18:44 +0200
From: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: jordi.palet@consulintel.es
References: <C4B4A8FF.1CC061%jordi.palet@consulintel.es>
In-Reply-To: <C4B4A8FF.1CC061%jordi.palet@consulintel.es>
X-OriginalArrivalTime: 29 Jul 2008 10:18:45.0057 (UTC) FILETIME=[7B786310:01C8F164]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: 72attendees@ietf.org
Subject: Re: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom Network not under NOC Control)
X-BeenThere: 72attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the attendees of IETF 72 meeting." <72attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/72attendees>
List-Post: <mailto:72attendees@ietf.org>
List-Help: <mailto:72attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

Well, I don't know, but I believe this mailing list is not here for 
"settling the score" with ietf location selection process...

JORDI PALET MARTINEZ a écrit :
> And when you find volunteer hosts which find the money, the venue and so on,
> such as myself in Madrid, trying for several years, then you disqualify the
> venue because is not in down-town ... A very fair comparison with this one
> or even San Diego.
>
> Madrid venue was much better (even being the first hotel in the world that
> offered IPv6 in the guest rooms several years ago, no filtered
> ports/protocols at all !), much better located, much cheaper, better
> commuting to downtown (cheaper and shorter), better food, more restaurant
> choices in the venue and around, etc.
>
> So the first that make the possible hosts and sponsors to step down is the
> organization itself with ridiculous decisions which are then taken as
> irrelevant for other venues (and Dublin is a very good example).
>
> Now I'm not sure wanting to spend anymore my cycles in retrying this again
> unless there is a firm commitment. I bothered the government to much to
> raise +150.000 Euros for sponsoring this and I'm not even sure they will
> consider it again.
>
> Regards,
> Jordi
>
>
>
>
>   
>> From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
>> Reply-To: <72attendees-bounces@ietf.org>
>> Date: Tue, 29 Jul 2008 11:18:31 +0200
>> To: Iljitsch van Beijnum <iljitsch@muada.com>
>> Cc: <72attendees@ietf.org>
>> Subject: Re: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom
>> Network not under NOC Control)
>>
>>
>> On 29 jul 2008, at 10.41, Iljitsch van Beijnum wrote:
>>
>>     
>>> On 29 jul 2008, at 0:07, Kurt Erik Lindqvist wrote:
>>>
>>>       
>>>> "the powers that be" are trying to optimize location /
>>>> internationalization / the host that PAYs preferences to location
>>>>         
>>> The interesting thing is that the attendees ALSO pay for this.
>>>
>>> Now I understand that the IETF needs to get its funding where it can
>>> find it, but it can hardly be a surprise that if you make two sets
>>> of people pay for the same thing and optimize for the convenience of
>>> one party, the other is unhappy.
>>>       
>> If you would have quoted a bit more of my email -  I actually further
>> said 'This equation is far from easy, '. The problem is that - as has
>> been discussed at length at IETFs for a long time - the attendance
>> fees, the host sponsorship and the contributions from ISOC, all pays
>> for the meetings AND the secretariat. At trust me from the years on
>> the IAOC - running the IETF is not a money making business. If we
>> can't find hosts, the attendance fees would have to go up
>> significantly. Add to that the the ROI in marketing for a hosts on
>> sponsoring an IETF in the first place is miniscule. Add to it the all
>> the negative comments from the IETFXX-lists and have that attached to
>> your brand and the marketing value is negative.
>>
>> Personally I believe that we simply don't give the hosts (and the NOC
>> volunteers) enough credit for stepping up to the task of organizing a
>> meeting.
>>
>> Best regards,
>>
>> - kurtis -
>>
>>
>> PS, as most people have seems to have missed or ignored Andrews mail -
>> issues with the hotel network should go to the hotel, not the IETF list.
>>
>> _______________________________________________
>> 72attendees mailing list
>> 72attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/72attendees
>>     
>
>
>
>
> **********************************************
> 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.
>
>
>
> _______________________________________________
> 72attendees mailing list
> 72attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/72attendees
>   

_______________________________________________
72attendees mailing list
72attendees@ietf.org
https://www.ietf.org/mailman/listinfo/72attendees