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

Dale Worley <dworley@pingtel.com> Tue, 29 July 2008 10:21 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 1E91A28C26B; Tue, 29 Jul 2008 03:21:18 -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 6053828C281 for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 03:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1]
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 XmgvKvD5GM-u for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 03:21:16 -0700 (PDT)
Received: from mail.pingtel.com (host117.155.212.198.conversent.net [155.212.198.117]) by core3.amsl.com (Postfix) with ESMTP id 8AFA528C24C for <72attendees@ietf.org>; Tue, 29 Jul 2008 03:21:16 -0700 (PDT)
Received: from [127.0.0.1] (ssh.pingtel.com [10.1.20.8]) by mail.pingtel.com (Postfix) with ESMTP id 76EC06C018 for <72attendees@ietf.org>; Tue, 29 Jul 2008 06:21:25 -0400 (EDT)
From: Dale Worley <dworley@pingtel.com>
To: 72attendees@ietf.org
In-Reply-To: <94A3C924-DB32-43B1-B9F5-66C54EA32926@muada.com>
References: <C4B41B20.76FCE%jonne.soininen@nsn.com> <94A3C924-DB32-43B1-B9F5-66C54EA32926@muada.com>
Date: Tue, 29 Jul 2008 06:21:24 -0400
Message-Id: <1217326884.3851.12.camel@victoria.pingtel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
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

It's certainly acceptable to examine the good and bad points of any
venue.  But there is a question of attitude -- we have paid for certain
things, and have a right to expect those, but there are things we have
*not* paid for and we can't *complain* that we haven't gotten them.

(Actually, given the huge level of volunteers and sponsor support, we
have the right to a considerable amount of stuff that we have *not* paid
for -- and we should be thankful.)

But all of this trades off against cost.  Not so long ago on the list,
people were complaining of the excessive cost of the meeting.  Yes, it's
straightforward to reduce cost -- what services are you willing to
forgo?  It's also straightforward to improve services -- what are you
willing to pay?

It also doesn't help that this is a one-week event unlike any event the
venue has ever had, or ever will have again.  There's not a lot of time
for everyone to learn how to optimize all these trade-offs for this
particular audience, and certainly no incentive for the venue to make
capital expenditures to improve service for us.

Dale


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