<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<small>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style></style> </small>
<table class="backgroundTable" cellpadding="0" cellspacing="0"
bgcolor="#ffffff" width="100%">
<tbody>
<tr>
<td align="left" valign="top">
<table cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="border-top: 0px solid rgb(0, 0, 0);
border-bottom: 1px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255); text-align:
center;" align="center"><span style="font-size:
10px; color: rgb(96, 96, 96); line-height: 200%;
font-family: verdana; text-decoration: none;">Email
not
displaying correctly? <a
href="http://www.oplin.org/4cast/"
style="font-size: 10px; color: rgb(0, 0, 255);
line-height: 200%; font-family: verdana;
text-decoration: none;">View
it in your browser.</a></span></td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(51, 51, 51);
border-bottom: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255);">
<center><a href=""><img id="editableImg1"
src="cid:part2.06040406.04030506@oplin.org"
title="OPLIN" alt="OPLIN 4Cast" border="0"
align="middle"></a></center>
</td>
</tr>
</tbody>
</table>
<table style="width: 763px; height: 877px;" cellpadding="20"
cellspacing="0" bgcolor="#ffffff">
<tbody>
<tr>
<td style="font-size: 12px; color: rgb(0, 0, 0);
line-height: 150%; font-family: trebuchet ms;"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
bgcolor="#ffffff" valign="top">
<p><!-- Make sure you modify the 4Cast title in this section -->
<span style="font-size: 20px; font-weight: bold;
color: rgb(0, 0, 0); font-family: arial;
line-height: 110%;">OPLIN 4cast #407: Jamming
hotspots</span><br>
<!-- Make sure you modify the date of the 4Cast in this section -->
<span style="font-size: 11px; font-weight: normal;
color: rgb(102, 102, 102); font-style: italic;
font-family: arial;">October 15th, 2014</span></p>
<!-- Begin copy of Web Source here -->
<p style="text-align: justify;font-size: 16px;
font-family: arial; line-height: 110%;"><img
src="cid:part4.04090504.06030309@oplin.org"
alt="Wi-Fi hotspot" align="left" height="90"
width="110">A couple of weeks ago, the Federal
Communications Commission <a
href="http://www.fcc.gov/document/marriott-pay-600k-resolve-wifi-blocking-investigation">fined</a>
the Marriott hotel chain $600,000, charging that
they "…intentionally interfered with and disabled
Wi-Fi networks established by consumers in the
conference facilities of the Gaylord Opryland
Hotel and Convention Center in Nashville,
Tennessee, in violation of Section 333 of the
Communications Act." In plainer English, Marriott
was sending signals that disabled the cellular
mobile hotspots that people at the conference
facility were trying to set up for use by their
group, thus getting around paying steep fees
charged by Marriott for using their in-house
Wi-Fi. (If you're curious about how steep these
fees can be, OPLIN just paid the Greater Columbus
Convention Center $10,000 for Wi-Fi access for OLC
Convention attendees last week.) While most media
reported this <a
href="http://www.forbes.com/sites/quickerbettertech/2014/10/13/how-marriott-bumrushed-opryland-guests-to-pay-for-wifi/">story</a>
as an example of a hotel getting caught being
greedy, the FCC's action raised ticklish questions
for some technicians responsible for maintaining
Wi-Fi networks.
</p>
<div> </div>
<ul style="text-align: left;">
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://www.cnn.com/2014/10/03/travel/marriott-fcc-wi-fi-fine/index.html">Marriott
fined $600,000 by FCC for blocking guests'
Wi-Fi</a> (CNN | Katia Hetter) "Marriott
issued the following statement Friday afternoon
defending its actions: 'Marriott has a strong
interest in ensuring that when our guests use
our Wi-Fi service, they will be protected from
rogue wireless hot spots that can cause degraded
service, insidious cyber-attacks and identity
theft,' the statement said. 'Like many other
institutions and companies in a wide variety of
industries, including hospitals and
universities, the Gaylord Opryland protected its
Wi-Fi network by using FCC-authorized equipment
provided by well-known, reputable
manufacturers.'"</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://blog.airtightnetworks.com/fcc-wi-fi-rogue-containment/">Understanding
FCC decision regarding Wi-Fi containment at
Marriott</a> (Mojo Wireless | Hemant Chaskar)
"In this case, it seems FCC reached the
conclusion that rogue containment was used in a
manner to disrupt rightful communications of
users even though they did not pose security
threat to the Marriott network. I think everyone
would agree with the FCC position here. Some may
bring up the hotel Wi-Fi performance degradation
issue due to personal hot spots, but Wi-Fi
operates in the public spectrum and does not
guarantee performance in the first place."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://itcblogs.currentanalysis.com/2014/10/08/prudence-in-the-wake-of-the-fccs-ruling-on-marriott-jamming-wifi/">Prudence
in the wake of the FCC's ruling on Marriott
jamming WiFi</a> (IT Connection | Mike Fratto)
"On the other hand, Marriott - and any
organization running a WiFi network - has good
reason to monitor its airspace in order to
provide good service. If you look at the
airspace at any public venue, it is a mess of
access points overlapping channels and degrading
WiFi access for everyone, and there is no way
for a venue owner to provide good service in
that environment. However, protecting unwitting
guests from 'insidious cyber-attacks and
identity theft' is a specious argument and not
one you should make unless you have tangible
proof."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://www.networkcomputing.com/wireless-infrastructure/fcc-marriott-wifi-blocking-fine-opens-pandoras-box/a/d-id/1316449">FCC-Marriott
WiFi blocking fine opens Pandora's box</a>
(Network Computing | Lee Badman) "Many of us
have bought into the fact that WLAN can be as
good and secure as Ethernet, and the WLAN
industry says we shouldn't hesitate to include
WiFi in our critical infrastructures. But we
need the FCC to provide some clarity. Even if
it's not OK to 'jam' in whatever form that may
take, it ought to be OK to have 'Thou shalt not
use' policies for our own spaces. The FCC didn't
say that's acceptable, but it really needs to at
this point."</li>
</ul>
<div style="text-align: left;"> </div>
<p style="text-align: left; font-size: 20px;
font-family: arial; line-height: 110%;"><small><strong><em>Articles
from <a href="http://ohioweblibrary.org">Ohio
Web Library</a>:</em></strong></small><br>
</p>
<div style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;">
<ul>
<li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=fdea8fdb-0950-4ba3-8c73-a360cb588108%40sessionmgr111&vid=0&hid=115&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=94346367">Hotspot:
Share your phone's mobile data with other
devices.</a> (<em>Time.com</em>, 2/6/2014,
p1 | Jared Newman)</li>
<li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=941ee432-18f4-4e7e-834c-14a679ad8c9e%40sessionmgr198&vid=2&hid=115&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=59565401">It
that a hot spot in your pocket?</a> (<em>Entrepreneur</em>,
April 2011, p42 | Rich Karpinski)</li>
<li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=bbf8287c-b441-42e2-8b07-15c635635991%40sessionmgr112&vid=2&hid=115&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=59669538">Managing
mobile hotspots.</a> (<em>eWeek</em>,
3/21/2011, p26 | Cameron Sturdevant)</li>
</ul>
</div>
<div style="text-align: left;"> </div>
<!-- End paste of web source here --> </td>
</tr>
<tr>
<td style="" solid="" background-color:="" rgb(255,=""
255,="" 255);="" >=""
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
valign="top" width="760"><span style="font-size:
10px; color: rgb(96, 96, 96); line-height: 100%;
font-family: verdana;">
<hr><!-- Begin standard subscription verbiage -->
<div style="text-align: justify;">The <strong><em>OPLIN
4cast</em></strong>
is a weekly compilation of
recent headlines, topics, and trends that could
impact public
libraries. You can subscribe to it in a variety
of ways, such as: <br>
</div>
<div style="text-align: left;"> </div>
<ul>
<li style="text-align: justify;"><strong>RSS
feed.</strong>
You
can receive the OPLIN 4cast
via RSS feed by subscribing to the following
URL:
<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/index.php/?feed=rss2">http://www.oplin.org/4cast/index.php/?feed=rss2</a>.
</li>
<li style="text-align: justify;"><strong>Live
Bookmark.</strong>
If you're using the Firefox
web browser, you can go to the 4cast website
(<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/">http://www.oplin.org/4cast/</a>) and click on the
orange "radio wave" icon
on the right side of the address bar. In
Internet Explorer 7, click on
the same icon to view or subscribe to the
4cast RSS feed. </li>
<li style="text-align: justify;"><strong>E-mail.</strong>
You
can have the OPLIN 4cast
delivered via e-mail (a'la OPLINlist and
OPLINtech) by subscribing to
the 4cast mailing list at
<a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/OPLIN4cast">http://mail.oplin.org/mailman/listinfo/OPLIN4cast</a>.
</li>
</ul>
</span> </td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 204);"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg"
valign="top" width="760"> <br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<small>
<title>OPLIN 4Cast</title>
<style>
.headerTop { background-color:#FFFFFF; border-top:0px solid #000000; border-bottom:1px solid #FFFFFF; text-align:center; }
.adminText { font-size:16px; color:#0000FF; line-height:200%; font-family:verdana; text-decoration:none; }
.headerBar { background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:0px solid #FFFFFF; }
.title { font-size:20px; font-weight:bold; color:#000000; font-family:arial; line-height:110%; }
.subTitle { font-size:11px; font-weight:normal; color:#000000; font-style:italic; font-family:arial; }
.defaultText { font-size:12px; color:#000000; line-height:150%; font-family:trebuchet ms; }
.footerRow { background-color:#FFFFCC; border-top:0px solid #FFFFFF; }
.footerText { font-size:10px; color:#996600; line-height:100%; font-family:verdana; }
a { color:#0000FF; color:#0000FF; color:#0000FF; }
</style>
</small>
</body>
</html>