<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<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>
<table class="backgroundTable" width="100%" bgcolor="#ffffff"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top" align="left">
<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.01080109.07010005@oplin.org"
title="OPLIN" alt="OPLIN 4Cast" align="middle"
border="0"></a></center>
</td>
</tr>
</tbody>
</table>
<table style="width: 763px; height: 877px;"
bgcolor="#ffffff" cellpadding="20" cellspacing="0">
<tbody>
<tr>
<td style="font-size: 12px; color: rgb(0, 0, 0);
line-height: 150%; font-family: trebuchet ms;"
valign="top"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
bgcolor="#ffffff">
<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 #333: Domains
without dots</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;">May 8th, 2013</span></p>
<!-- Begin copy of Web Source here -->
<p style="text-align: justify;font-size: 16px;
font-family: arial; line-height: 110%;"><img
alt="ICANN logo"
src="cid:part4.08090702.03080600@oplin.org"
height="88" width="110" align="left">Over a year
ago, the Internet Corporation for Assigned Names
and Numbers (ICANN), the organization that is
responsible for coordinating Internet domain names
and IP addresses, announced that it would accept
applications for new generic top-level domains
(gTLDs). [See <a
href="http://www.oplin.org/4cast/?p=1985">4cast
#235</a>.] Current gTLDs include .com and .org,
but now companies and organizations have submitted
applications for a wide range of proposed new
gTLDs - such as .book. Google has gone one step
further and proposed a "dotless" domain that would
consist of only one word: "search"
(<a class="moz-txt-link-freetext" href="http://search/">http://search/</a>). And that proposal has stirred up
the debate about the wisdom of allowing dotless
domains on the Internet and Google's motives.
</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://techcrunch.com/2013/04/10/google-wants-to-operate-search-as-a-dotless-domain/">Google
wants to operate .search as a "dotless"
domain, plans to open .cloud, .blog and .app
to others</a> (TechCrunch/Frederic Lardinois)
"Google plans to run <a class="moz-txt-link-freetext" href="http://search/">http://search/</a> as a
redirect service that 'allows for registration
by any search website providing a simple query
interface.' 'The mission of the proposed gTLD,
.search, is to provide a domain name space that
makes it easier for Internet users to locate and
make use of the search functionality of their
choice,' Google writes in its amended
application."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="https://medium.com/the-rolled-up-newspaper/56c13f710359">On
dotless domains and domainless TLD's</a> (The
Rolled-Up Newspaper/Andrew Johnson) "So why
would Google want to promote a way to search
elsewhere when there's no real threat to their
position as top dog in search? [...] ICANN is
probably much more amenable to allowing a
dotless TLD-a risky and huge departure from
standard practice-knowing its operator is tied
to a promise to include others. In this case,
Google would just be investing in familiarizing
people with the concept of a domain-less TLD,
dotted or not, and they plan to do this to
additional TLD's down the road: first
proprietary TLD's ('google,' 'android') and
maybe later generic TLD's in a proprietary
manner, if they could swing it ('maps' being
exclusive to Google Maps, or 'translate' from
Google Translate, for instance)."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://www.icann.org/en/groups/ssac/documents/sac-053-en.pdf">SSAC
report on dotless domains</a> [pdf] (ICANN
Security and Stability Advisory Committee)
"Other security issues may arise if dotless
domains are permitted to host content directly.
The advent of such hosting will violate a
longstanding (more than 20 year) assumption that
a dotless hostname is within an organization's
trust sphere. In Windows, for instance, this
means that a dotless host may be considered to
be in the Intranet zone, and is accorded the
security privileges conveyed to sites in that
zone. These privileges are significant and may,
depending on the user's configuration, permit
code execution."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://blogs.msdn.com/b/mthree/archive/2013/04/15/gtld-041513.aspx">ICANN,
the GAC, SSAC and gTLDs: Challenges with
dotless domains and closed generics</a> (MSDN
Blogs/M3 Sweatt) "As we summarized in <a
href="http://forum.icann.org/lists/sac053-dotless-domains/pdfjobOOzS93n.pdf">our
comments</a> [pdf], Microsoft supports and
endorses the report's recommendations against
use of dotless domains. There are significant
security considerations around the use of
dotless domains with new gTLDs, generally a bad
idea that would create significant security
risks for people using the Internet. Dotless
domain names are often resolved by operating
systems, browsers and other products to
addresses on the local network / intranet. Our
recommendation is to use Fully Qualified Domain
Names (FQDNs) - sometimes referred to an
absolute domain name - to ensure that people get
where they are expecting when they type in an
address on the Internet URL."</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>Technical
fact:</em></strong></small><br>
</p>
<div style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;">At the
very least, handling dotless domains would require
extensive revisions to current web browsers and
Internet apps. Such software typically interprets
and completes shortened domain names and does not
insist on use of fully qualified domain names.
</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);="" >="" valign="top" width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"><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);" valign="top"
width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg">
<br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<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>
</body>
</html>