IETF Logo Mail Archive

Re: [68ATTENDEES] Network shutdown time

Tim Chown <tjc@ecs.soton.ac.uk> Fri, 23 March 2007 10:35 UTC

Return-path: <68attendees-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUh7A-0007bS-GZ; Fri, 23 Mar 2007 06:35:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUh79-0007bA-PD for 68attendees@ietf.org; Fri, 23 Mar 2007 06:35:19 -0400
Received: from [2001:630:d0:f102:230:48ff:fe77:96e] (helo=owl.ecs.soton.ac.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUh77-0002XE-KJ for 68attendees@ietf.org; Fri, 23 Mar 2007 06:35:19 -0400
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l2NAZ3Zm029587; Fri, 23 Mar 2007 10:35:03 GMT
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe23:58df]) by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l2NAYjG2020813; Fri, 23 Mar 2007 10:34:45 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.12.11.20060308/8.11.6) id l2NAYjOc007480; Fri, 23 Mar 2007 10:34:45 GMT
Date: Fri, 23 Mar 2007 10:34:45 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Bob Hinden <bob.hinden@nokia.com>
Subject: Re: [68ATTENDEES] Network shutdown time
Message-ID: <20070323103444.GD5344@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.33L.0703230611560.20808-100000@minbar.fac.cs.cmu.edu> <E2D550D4-FD35-4A78-B252-AE909CFA5185@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E2D550D4-FD35-4A78-B252-AE909CFA5185@nokia.com>
User-Agent: Mutt/1.4i
X-Null-Tag: 8a9fa72166edeee3c4f87b3de623d2e0
X-Null-Tag: 56081f73397a37fc6f08b34135bd249a
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 68attendees@ietf.org
X-BeenThere: 68attendees@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Mailing list for IETF 68 attendees." <68attendees.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/68attendees>, <mailto:68attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/68attendees>
List-Post: <mailto:68attendees@ietf.org>
List-Help: <mailto:68attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/68attendees>, <mailto:68attendees-request@ietf.org?subject=subscribe>
Errors-To: 68attendees-bounces@ietf.org

On Fri, Mar 23, 2007 at 11:26:49AM +0100, Bob Hinden wrote:
> 
> On Mar 23, 2007, at 11:13 AM, ext Jeffrey Hutzelman wrote:
> 
> >On Fri, 23 Mar 2007, Henning Schulzrinne wrote:
> >
> >>It would be very useful to have one AP up until Friday afternoon.
> >
> >Let's avoid micromanaging the details, specifying number of AP's etc.
> >Instead, perhaps we can just ask that the meeting network remain
> >somehow accessible to attendees for a longer period.
> 
> Keeping one AP up is easy, keeping the network up behind it is  
> harder.  Normally, the network team has a fixed deadline to be out of  
> the hotel space.  For example, in Dallas we had to be out of the NOC  
> and other spaces by about 6pm, and had arranged for shippers to pick  
> up the equipment late Friday afternoon.  Delaying the tear down later  
> in the day makes this all a lot harder.

So maybe it's just easier to negotiate free hotel wireless for the day
before/after IETF, assuming the hotel wlan is provisioned for those
who would be around.

-- 
Tim



_______________________________________________
68ATTENDEES mailing list
68ATTENDEES@ietf.org
https://www1.ietf.org/mailman/listinfo/68attendees

v2.23.0 | Report a Bug | By Email