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

"Dave Oran (oran)" <oran@cisco.com> Mon, 03 March 2014 00:05 UTC

Return-Path: <oran@cisco.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 830A31A0B59 for <89attendees@ietfa.amsl.com>; Sun, 2 Mar 2014 16:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.047
X-Spam-Level:
X-Spam-Status: No, score=-115.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 lII_T7eOqKQy for <89attendees@ietfa.amsl.com>; Sun, 2 Mar 2014 16:05:00 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 85C811A0B4C for <89attendees@ietf.org>; Sun, 2 Mar 2014 16:04:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9511; q=dns/txt; s=iport; t=1393805096; x=1395014696; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=H0b4/afRZjSa+oCsMh9zTtxzi/12zWcNFGQIhj3AEuk=; b=HwJzsraKuXp7zuDs7ggAPGsdKMBBdqk5Lu2OaCeqe5OjuxdGB02cBArs Fltl3QpyEssViiCgqnOUoAbLIk5u0rIBj0e35EcTQOEaZ0uo1X2guAkBJ GMArEj17Zuva3S7UX91HBsGkVTNmhBs1BLsTuX4nm4TikSaAJ9P1vm35T M=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFAILGE1OtJV2d/2dsb2JhbABagkJEO1e/fU+BGBZ0giUBAQEDAQEBAWUGCxACAQgOCi4hBgslAgQOBQ6HVwMJCA3EUg2HHRMEjEOBUUUHgySBFASQSIE0hFOBbYxjhUiDLYIq
X-IronPort-AV: E=Sophos; i="4.97,574,1389744000"; d="asc'?scan'208,217"; a="307571645"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 03 Mar 2014 00:04:55 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s2304ta0019470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Mar 2014 00:04:55 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.150]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Sun, 2 Mar 2014 18:04:55 -0600
From: "Dave Oran (oran)" <oran@cisco.com>
To: Jim Spring <jmspring@gmail.com>
Thread-Topic: [89attendees] When does the IETF network officially come up?
Thread-Index: AQHPNm6vboKJn/oZwEqefpJZHoR8kJrO4DCA
Date: Mon, 3 Mar 2014 00:04:54 +0000
Message-ID: <793587FD-24DB-48A8-B4EB-A2134F0716AD@cisco.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>
In-Reply-To: <95EA75A4-77C6-4C57-B260-104725FC1816@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.78.39]
Content-Type: multipart/signed; boundary="Apple-Mail=_CB9DC75F-8500-49AE-BF84-7691AB7A3BEE"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/89attendees/ArsFGQ-2yCbqMWnfhuhKTRYT7uU
Cc: David Misell <david.misell@icloud.com>, Randy Bush <randy@psg.com>, "CCEO@bt.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 00:05:06 -0000

Did somebody do something for the Tower, specifically the 4th floor? When I got back to my room tonight, the wireless had dramatically improved, to under 200ms ping times (through a vpn tunnel as well) and very low packet loss.

Or is it random, weather, somebody moved changing the multipath…or whatever.

First time I have a solid enough connection to do work in the room.

If the BOC or some angel is responsible, thank you!

DaveO.

On Mar 2, 2014, at 11:25 PM, Jim Spring <jmspring@gmail.com> wrote:

> 
> On Mar 2, 2014, at 12:02 PM, Jim Martin <jrmii@isc.org> wrote:
> 
>> 	Finally, there's the public space and guest room areas. It's not practical for us to build out a network that reaches everywhere in the building, so we work with the hotel to either take over or ride their infrastructure. In the case of the wired networks to the guest rooms, we continue to use their cabling and switches, but take the hand off into the IETF infrastructure at layer 2. We provide all IP services, which means we can provide real public IPv4 and native IPv6. In the case of wireless, we've worked with the normal wireless provider (BT Wireless) to add an additional SSID that they're handing off to us at layer 2 as well, so we can provide the IP services there.  If there are IP layer issues, please do let us know at tickets@meeting.ietf.org, or by coming by the help desk in the terminal room. 
>> 
>> 	The one thing we really can't control is whether the ethernet running to your room is working, or if you can get the BT wireless signal (the ietf-hotel SSID) wherever you're situated. That's where we ask folks to contact the normal BT tech support. If they're unable to help, please let us know, as we can advocate for you a bit deeper inside the organization. 
> 
> Jim, 
> 
> 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.
> 
> Also, since 2001, most devices are wireless instead of wired.  I was here in 2001 and, yes, things were different then.  BT should have either beefed up AP coverage (included into the rooms) or there should have been some sort of distribution APs that could plug into the rooms wired connection to provide wireless coverage.  Unlike 2001, more devices are wireless than not.
> 
> -jim
> _______________________________________________
> 89attendees mailing list
> 89attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/89attendees