01.07.2014 Views

name-collision-02aug13-en

name-collision-02aug13-en

name-collision-02aug13-en

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Proposed TLD usage 2012 2013<br />

_sip… 0% 0%<br />

_xmpp… 0% 0%<br />

mail at other than TLD 0% 0%<br />

.proposedTLD. only 0% 0%<br />

total 71% 70%<br />

Table 12—Proposed TLD usage as perc<strong>en</strong>tages across all roots<br />

5.4.1 SLD is an existing TLD<br />

Common examples of domain <strong>name</strong>s in this category are:<br />

<br />

<br />

.com.home.<br />

..home.<br />

in which is a two-letter country code (for example .uk. or .sg.).<br />

These appear to be examples of a valid domain <strong>name</strong> that has had a TLD app<strong>en</strong>ded<br />

(incorrectly)—for example, by a commercial off-the-shelf (COTS) router or cable modem used<br />

at home or in a small office.<br />

5.4.2 SLD is also a proposed TLD<br />

Common examples of domain <strong>name</strong>s in this category are:<br />

<br />

..corp.<br />

in which is the <strong>name</strong> of a company that matches a proposed TLD.<br />

These appear to be examples of an internal domain <strong>name</strong> being used (incorrectly) outside the<br />

administrative boundary of the company in which it is defined.<br />

5.4.3 SLD is a random 10-alphabetic-character string<br />

Oft<strong>en</strong> spotted near each other in the traces, examples of domain <strong>name</strong>s in this category are<br />

<br />

<br />

<br />

lfbviakqaw.home.<br />

mdqrerrefm.home.<br />

uprxbvqnxa.home.<br />

These domain <strong>name</strong>s comprise t<strong>en</strong> appar<strong>en</strong>tly random alphabetic characters for the SLD and a<br />

proposed TLD (oft<strong>en</strong>, but not only, .home.).<br />

Name Collision Study Report Page 48<br />

Version 1.5 2013.08.02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!