[98all] IETF98 Network Information (and an update on hotel wireless)

Jim Martin <jim@daedelus.com> Sat, 25 March 2017 19:18 UTC

Return-Path: <jim@daedelus.com>
X-Original-To: 98all@ietfa.amsl.com
Delivered-To: 98all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5FF9126DEE for <98all@ietfa.amsl.com>; Sat, 25 Mar 2017 12:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3ROKS9ymG7DF for <98all@ietfa.amsl.com>; Sat, 25 Mar 2017 12:18:05 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D370127876 for <98all@ietf.org>; Sat, 25 Mar 2017 12:18:05 -0700 (PDT)
Received: from imladris.daedelus.com (imladris.daedelus.com [206.197.161.143]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 7B2D7880F4 for <98all@ietf.org>; Sat, 25 Mar 2017 12:18:05 -0700 (PDT)
Received: from t2001067c037000007cb1b4242ac70429.v6.meeting.ietf.org (t2001067c037000007cb1b4242ac70429.v6.meeting.ietf.org [IPv6:2001:67c:370:0:7cb1:b424:2ac7:429]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by imladris.daedelus.com (Postfix) with ESMTP id 38F3F13083E9 for <98all@ietf.org>; Sat, 25 Mar 2017 12:18:05 -0700 (PDT)
From: Jim Martin <jim@daedelus.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <1B47D71C-3DCD-4B63-BE42-3083CC87A04C@daedelus.com>
Date: Sat, 25 Mar 2017 14:18:03 -0500
To: 98all@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/98all/VmUXjta8_uSKbYC4M-hd5GANXXg>
Subject: [98all] IETF98 Network Information (and an update on hotel wireless)
X-BeenThere: 98all@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of all 98 attendees for official communication <98all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/98all>, <mailto:98all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/98all/>
List-Post: <mailto:98all@ietf.org>
List-Help: <mailto:98all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/98all>, <mailto:98all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Mar 2017 19:18:07 -0000

Gentlepeople,
	Welcome to IETF98 in Chicago! You will find the usual IETF Network information document at:

	https://tickets.meeting.ietf.org/wiki/IETF98network

	We’re having some extraordinary issues with the Guestroom and Public networks in the Swissôtel that are requiring some further work on the NOC team’s part. 

	While we continue to work to have the usual IETF network in the public and guest room areas, the Swissôtel has kindly offered the use of the “swissotel” wireless network for everyone, using the code “SWISSOTEL0317”. 

	Also, if you happen to be in the Fairmont Hotel, you’ll find the “ietf-fairmont” SSID to be active and available for all. 

	We hope to have the IETF network available in the Swissôtel guest rooms and public space available soon, but there’s currently no estimate on exactly when. I’ll update both the network document linked above as well as send out an update when the issues are resolved.

	Have a good meeting!

	- Jim & the IETF NOC Team