[103attendees] Four Points Sheraton WiFi sub-par

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 05 November 2018 00:50 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 103attendees@ietfa.amsl.com
Delivered-To: 103attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D816C1294D0 for <103attendees@ietfa.amsl.com>; Sun, 4 Nov 2018 16:50:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 nB-izgbKmSvn for <103attendees@ietfa.amsl.com>; Sun, 4 Nov 2018 16:50:07 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1414F128766 for <103attendees@ietf.org>; Sun, 4 Nov 2018 16:50:07 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:1232:144:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id B90321F8BD for <103attendees@ietf.org>; Mon, 5 Nov 2018 00:50:05 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D3F09185F; Mon, 5 Nov 2018 06:19:37 +0530 (IST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 103attendees@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 05 Nov 2018 07:49:37 +0700
Message-ID: <27164.1541378977@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/103attendees/t1NkQWgEWoRp7q57BWVPbewZVuw>
Subject: [103attendees] Four Points Sheraton WiFi sub-par
X-BeenThere: 103attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of IETF 103 attendees that have opted in on this list <103attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/103attendees>, <mailto:103attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/103attendees/>
List-Post: <mailto:103attendees@ietf.org>
List-Help: <mailto:103attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/103attendees>, <mailto:103attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 00:50:09 -0000

While the WiFi seemed okay when I checked on Friday to the Four Points
Sheraton, I did not really use it that much.  Last night, in my room, after
seven WiFi drops (requiring me to Disconnect from the AP, reconnect), I
dialed 0, and they reset something.  I had to login again, and then dropped a
few more times, and then I went to sleep to get up early to come to the
Marriot early.  It's clearly a layer-2 issue.  I will search the desk for a
wired jack when I return tonight.

I thought we more often wired the overflow hotels, but as I read
venue-selection I see that it's clearly stated that we usually don't.
I usually wind up in an AirBnb or something cheaper than the overflow, but
decided to "splurge" on the overflow, I guess with the mis-apprehension that
network would be good.  But, I guess mostly because it would more guarantee an
english speaking front-desk.
When I realized it was 1.5km away, of course, it is unlikely to be wired.

iaoc-venue-selection-process-16 does say:

   o  It is desirable for Overflow Hotels to provide reasonable,
      reliable, unfiltered Internet service for the public areas and
      guest rooms, and that this service be included in the cost of the
      room.

and I believe that the Four Points is not, at this point, satisfying the
"reliable" point.  (The bathroom is rather nice though)

I wonder if the selection process is asking hotels if they have IPv6.
I sadly know what the answer is.

I'd also like them to ask some questions about the technology of the captive
portal, but we don't really have a good captive portal "list of things not do
to" document yet.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-