IETF Logo Mail Archive

Re: [89attendees] When does the IETF network officially come up?

Ted Lemon <mellon@fugue.com> Mon, 03 March 2014 09:43 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: 89attendees@ietfa.amsl.com
Delivered-To: 89attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E83D31A0D98 for <89attendees@ietfa.amsl.com>; Mon, 3 Mar 2014 01:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXnVllXejq5V for <89attendees@ietfa.amsl.com>; Mon, 3 Mar 2014 01:43:24 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id CC8C51A0D97 for <89attendees@ietf.org>; Mon, 3 Mar 2014 01:43:24 -0800 (PST)
Received: from wireless-v6.meeting.ietf.org (unknown [IPv6:2001:67c:370:160:995e:9533:2945:668d]) by toccata.fugue.com (Postfix) with ESMTPSA id 192CD2380067; Mon, 3 Mar 2014 04:43:11 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <95EA75A4-77C6-4C57-B260-104725FC1816@gmail.com>
Date: Mon, 3 Mar 2014 09:43:09 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C547F33-84C7-41E8-AAB7-705B38CB22D9@fugue.com>
References: <97BB5D24-4559-4640-A56B-3ADEBAEBDAF0@juniper.net> <69A9E91B-B466-4558-AB18-FC63F7A246D7@icloud.com> <171DD9F8-8B95-4212-BF6C-E7D5108F04F3@isc.org> <95EA75A4-77C6-4C57-B260-104725FC1816@gmail.com>
To: Jim Spring <jmspring@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/89attendees/DCfB6cPDr58V5gQEMjn0LgXooUA
Cc: David Misell <david.misell@icloud.com>, Randy Bush <randy@psg.com>, CCEO@bt.com, Jim Martin <jrmii@isc.org>, "89attendees@ietf.org" <89attendees@ietf.org>
Subject: Re: [89attendees] When does the IETF network officially come up?
X-BeenThere: 89attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 89 attendees that have opted in to the list." <89attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/89attendees>, <mailto:89attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/89attendees/>
List-Post: <mailto:89attendees@ietf.org>
List-Help: <mailto:89attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/89attendees>, <mailto:89attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 09:43:26 -0000

On Mar 2, 2014, at 11:25 PM, Jim Spring <jmspring@gmail.com> wrote:
> I understand the efforts, but the fact is that thet BT installation of APs covering guest rooms is woefully inadequate and I suspect would have the same behavior if the IETF was ongoing or not -- multiple people have pointed out "good" coverage outside the room, "adequate" near the door, and "inadequate" within the room itself.  I suspect this pattern would be maintained whether the conference was here or not -- I've seen this at 3-4 properties while traveling in the last several months.  Specifically for me, there is some interference (metal door, machinery in the hallway, who knows) that is causing interference

FWIW, before the massive influx, the network was actually working pretty well.   The IETF is known for testing hotel networks to failure and meltdown.

v2.8.7 | Report a Bug | By Email