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

"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Tue, 29 July 2008 13:30 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 1AD7C28C2DA; Tue, 29 Jul 2008 06:30:08 -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 A7A5E28C2DB for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 06:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.404
X-Spam-Level:
X-Spam-Status: No, score=0.404 tagged_above=-999 required=5 tests=[AWL=0.867, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 5Pa293NGDfw1 for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 06:30:05 -0700 (PDT)
Received: from paoakoavas09.cable.comcast.com (paoakoavas09.cable.comcast.com [208.17.35.58]) by core3.amsl.com (Postfix) with ESMTP id 5CCBA28C2D8 for <72attendees@ietf.org>; Tue, 29 Jul 2008 06:30:05 -0700 (PDT)
Received: from ([24.40.15.118]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.58315461; Tue, 29 Jul 2008 09:29:45 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 29 Jul 2008 09:29:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 29 Jul 2008 09:29:19 -0400
Message-ID: <45AEC6EF95942140888406588E1A66020413D9E6@PACDCEXCMB04.cable.comcast.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [72attendees] Clarifying Host Responsibilities (was Re:Guestroom Network not under NOC Control)
Thread-Index: AcjxXCUjB9h3OFbDR7u+cyUdA615CAAIbue8
References: <C4B41B20.76FCE%jonne.soininen@nsn.com><94A3C924-DB32-43B1-B9F5-66C54EA32926@muada.com><08E2EAD8-D4D6-41CF-B290-AF389F9C3A06@kurtis.pp.se><D568C900-F68B-410E-B5DE-25C276B39D29@muada.com> <8177A3E0-82ED-44FC-9DDE-187984886948@kurtis.pp.se>
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "Kurt Erik Lindqvist" <kurtis@kurtis.pp.se>, "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 29 Jul 2008 13:29:46.0552 (UTC) FILETIME=[2B0DBB80:01C8F17F]
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

As the host organizer for IETF 71, I can say from very recent experience that most people would be shocked by how many volunteers, how many hours of volunteer time, and, not least, how much money it takes to sponsor and to operate an IETF meeting - to say nothing of supporting organizations such as AMS.  There is so much behind the scenes that people have no idea about, and there is months of advance preparation.  It is an exceptionally large commitment of human resources and financial resources by a host like Alcatel-Lucent, and demonstrates a host's commitment to the IETF and what we all do here in a major way.
 
So kudos to Alcatel-Lucent and any other future hosts of IETF meetings.  While it's perfectly normal to expect a certain level of service and so on, and fix broken things, sometimes keeping things in perspective is a good thing as well.  
 
Regards
Jason

________________________________

From: 72attendees-bounces@ietf.org on behalf of Kurt Erik Lindqvist
Sent: Tue 7/29/2008 5:18 AM
To: Iljitsch van Beijnum
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


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