Re: [72attendees] Guestroom Network not under NOC Control

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 29 July 2008 06:23 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 D04083A6A87; Mon, 28 Jul 2008 23:23:35 -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 064713A69EB for <72attendees@core3.amsl.com>; Mon, 28 Jul 2008 23:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
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 A+mF0KwtBcbf for <72attendees@core3.amsl.com>; Mon, 28 Jul 2008 23:23:33 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 5114D3A69C3 for <72attendees@ietf.org>; Mon, 28 Jul 2008 23:23:33 -0700 (PDT)
Received: from [130.129.22.27] ([130.129.65.5]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6T6MNel033215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <72attendees@ietf.org>; Mon, 28 Jul 2008 23:22:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080fc4b465d03e13@[130.129.22.27]>
In-Reply-To: <488DFDB6.6070001@ericsson.com>
References: <66F9363AB70F764C96547BD8A0A3679E154B84@USDALSMBS05.ad3.ad.alcatel.com> <488DFDB6.6070001@ericsson.com>
Date: Tue, 29 Jul 2008 07:21:21 +0100
To: 72attendees@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [72attendees] 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: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

At 7:11 PM +0200 7/28/08, Balazs Lengyel wrote:
>I think the guest-room network should be controlled by the NOC. Or 
>if control is a too strong term, then they should try to assure 
>somehow that it works properly. As the number of mails on this and 
>on previous IETF shows us, there is a real need to use it.

Fully disagree. If I can work from my room, great; if not, the lobby 
and bar and terminal room are in walking distance.

On top of us being rude (loudly talking over the host's welcoming 
talk at the Sunday reception) and demanding (not being willing to 
wait in a slowish line to buy sandwiches like regular people do), do 
we also have to be lazy? There was a time when IETFers were thankful 
when we were offered semi-reliable meeting amenities above what 
typical conference people got.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
72attendees mailing list
72attendees@ietf.org
https://www.ietf.org/mailman/listinfo/72attendees