tag:blogger.com,1999:blog-39407261797639625012024-03-13T05:39:53.716-07:00DOMINIO .TEL ------ Diseñando el futuro ------Toda información que se vaya publicando sobre la evolución de los dominios .tel , creados para liderar el futuro, se irá poniendo en este blog. Web patrocinada por TELrural.comUnknownnoreply@blogger.comBlogger1784125tag:blogger.com,1999:blog-3940726179763962501.post-80818691581579637142017-03-14T02:13:00.001-07:002017-03-14T02:13:28.709-07:00What's the future for the .tel domain name?<header class="entry-header">
<h1 class="entry-title">
What's the future for the .tel domain name?</h1>
<div class="entry-meta">
<span class="posted-on"><time class="entry-date published" datetime="2017-02-02">2nd February 2017</time></span><span class="sep"> | </span>
<span class="tags-links">#<a href="https://shkspr.mobi/blog/tag/tel/" rel="tag">.tel</a> #<a href="https://shkspr.mobi/blog/tag/dns/" rel="tag">dns</a></span><span class="sep"> | </span>Read ~121 times. </div>
</header>
<hr class="hr-top" />
Good news! <img src="https://shkspr.mobi/blog/wp-content/uploads/2011/01/tel-icon1.png" /> is being relaunched with a slew of new features which frees it up from its previous shackles.<br />
<h2>
What is .tel</h2>
Your address book is probably a mausoleum - stuffed with the rotting
corpses of long dead phone numbers. Perhaps you took my business card
back in 2002, duly entered it on your Palm Pilot, and never spoke to me
again. That address book entry has a phone number I've not used for a
decade, an email address provided by a defunct start-up, and a postal
address for a country I no longer live in.<br />
Isn't there a better way?<br />
That's what .tel was supposed to be.<br />
<ul>
<li>I register a .tel domain - <a href="http://edent.tel/"><code>http://edent.tel</code></a></li>
<li>I fill it with my contact details.</li>
<li>You store my .tel in your address book.</li>
<li>When I change my phone number, I update my .tel and your phonebook receives the changes.</li>
</ul>
The magic of .tel is that everything is stored in the DNS. It
shouldn't matter if the website goes down - or even if you've got low
connectivity. All you need to do to get my details is:<br />
<pre><code>dig @8.8.8.8 edent.tel naptr
</code></pre>
Or, to get <em>everything</em> in the DNS records:<br />
<pre><code>dig +nocmd edent.tel any +multiline +noall +answer
</code></pre>
The tragedy of .tel is that there was almost no UI customisation
available. Every site looked close to identical, corporate colour
schemes couldn't be easily integrated, and the design was limited.<br />
This is what it looked like back in 2009:<br />
<img alt="A plain looking website" class="aligncenter size-full" height="480" src="https://shkspr.mobi/blog/uploaded_images/IMG_0011-711880.png" width="320" /><br />
Which, thankfully, had improved by 2013:<br />
<img alt="A screenshot of the original .tel platform" class="aligncenter size-full wp-image-16500" height="878" src="https://shkspr.mobi/blog/wp-content/uploads/2013/03/edent.tel-screenshot.jpg" width="512" /><br />
No further improvements were made.<br />
So, how well did it work in practice?<br />
<h2>
Lack of critical mass</h2>
Back in 2012, there were <a href="https://icannwiki.com/.tel">256k .tel domains</a>. In 2016, it's a mere <a href="http://www.statdns.com/">105k domains</a>. Those numbers need to be in the multi-millions in order to get the traction needed for success. In their original proposal, <a href="http://www.tel.community/t423-comparision-of-the-five-year-financial-projections-for-tel-before-after">they were expecting 20 million registrations</a> five years after launch.<br />
As registrations fell, so did income. <a href="http://www.tel.community/t1730-interesting-quotes-from-telnic-s-telnames-former-cto">Senior staff left</a> the .tel organisation, and the infrastructure was left to rot. There were <a href="http://www.tel.community/t434-request-for-all-tel-owners-please-tell-us-your-suggestions-to-improve-tel">no updates</a>, and it looked like <a href="http://www.tel.community/t4491-telnic-ltd-officially-declares-negative-net-worth">.tel might collapse</a> - an unprecedented event in DNS history.<br />
I worked in the mobile industry for a decade. I don't think I <em>ever</em> met anyone else with a .tel. I got mine <a href="https://shkspr.mobi/blog/2009/03/some-thoughts-on-tel/">when they first launched in 2009</a> - and have been lonely ever since.<br />
As far as I can tell, no mobile phones were ever released which had .tel capable address books.<br />
<h2>
Relaunch!</h2>
Late last year, .tel owners were sent emails describing the upcoming relaunch and reinvigoration of the service.<br />
✓ Lifting of usage restrictions.<br />
✓ A new Telhosting platform.<br />
✓ Android and iPhone apps.<br />
✘ No porting of data!<br />
✘ No sub-pages.<br />
✘ No search.<br />
✘ No advertising.<br />
✘ Limited foreign language support.<br />
It's a bit of a mixed bag. But, hopefully, there's enough to sustain numbers - if not increase them.<br />
The most important is the lifting of hosting and design restrictions.
Users will be able to point their .tel at any site they like. The idea
of it <em>just</em> being an address book is disappearing.<br />
For those people who do want to keep it as their virtual contact card
- a new platform is being launched with an improved interface and fewer
design restrictions. It will still be free of charge for domain owners.<br />
As far as I can tell, this also means that sites can be secured with https - something which was <a href="http://www.networksolutions.com/support/compatibility-with-other-services/">unavailable on the old system</a>.<br />
Apps will be available for <em>editing</em> your site - but it would be a lot more useful to integrate with native address books.<br />
It is downright <strong>odd</strong> that they're not automatically
porting over peoples' data. There's going to be a one month grace period
before launch in mid-March, but that isn't a huge amount of time.<br />
The lack of sub-pages and search probably reflects how little those
features were used. Removing Ad-Sense seems weird - but people can
always add their own advertising.<br />
They're also dropping support for "Arabic, Czech, Japanese, Korean,
Portuguese and Russian" - I have no idea what those languages have in
common! I assume they just mean that their hosting platform won't
contain translations for those languages.<br />
<h2>
Is it enough?</h2>
I doubt it. Sorry to be so pessimistic - there are now literally <a href="https://www.iana.org/domains/root/db"><em>hundreds</em> of available top level domains</a>. Including .mobi, .mobile, .phone, .call, .me - all of which could serve the same purpose.<br />
If .tel had built on their early momentum - and perhaps done some
deals with mobile networks or manufacturers - then perhaps .tel would be
in a better position.<br />
It is pretty neat that they can store data like this in the DNS, and it is more discoverable than <a href="http://microformats.org/wiki/hcard">.hcard or other microformats</a> - but I fear that the idea of placing one's address details in DNS is doomed to failure.<br />
Because they aren't porting existing data to the new system, I expect that a lot of existing .tel sites are going to be empty.<br />
<h2>
Bonus Retro Video</h2>
This is how .tel launched itself back in the day.<br />
<div class="jetpack-video-wrapper">
<span class="embed-youtube" style="display: block; text-align: center;"></span></div>
Bless!Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-3940726179763962501.post-80236677950412004282016-12-14T07:30:00.002-08:002016-12-14T07:30:18.681-08:00<h1 itemprop="headline">
10 domain name secrets to repair your online reputation</h1>
<h2 class="subhead" itemprop="alternativeHeadline">
If you're
trying to fix your personal reputation online, looking toward your
domain name is a valuable first step. Columnist Chris Silver Smith
explains some options beyond setting up YourName.com.</h2>
<section class="sharing_controls mode_sticky" data-abbreviated-title="10 domain name secrets to repair your online reputation" data-content-endpoint-selector=".sharing_controls_endpoint_content" data-content-startpoint-selector=".sharing_controls_startpoint_content" data-email-body="Hi,[newline][newline]I've shared a link from Marketing Land.[newline][newline][title]:[newline][shortlink][newline]" data-email-subject="A link from Marketing Land" data-featured-image="#insert-image-url" data-full-title="10 domain name secrets to repair your online reputation" data-linkedin-source="Marketing Land" data-permalink="http://marketingland.com/10-domain-name-secrets-repair-online-reputation-199079" data-shortlink="" data-sticky-endpoint-selector="footer" data-sticky-startpoint-selector=".sharing_controls_startpoint_fixed" data-twitter-handle="@marketingland" style="display: block;"><ul style="left: 99px; top: -86.8px;">
<li class="more" data-id="more" style="opacity: 1;"><span>More</span></li>
</ul>
</section>
<div class="sharing_content_channel">
</div>
<img alt="Online Reputation Domain Names" class="aligncenter size-full wp-image-199080" height="360" src="http://marketingland.com/wp-content/ml-loads/2016/11/Reputation-Domains.jpg" width="640" />
If you’re trying to repair your personal reputation online, chances
are you have already figured out that you might need one or more
websites devoted to your name to help displace something negative in the
search results. Beyond setting up YourName.com, what other options are
there? Here are a few secrets that may help you get the search results
all shiny again with less effort!<br />
As part of good, proactive online reputation management and personal
branding, I advise that everyone should own the basic “YourName.com”
domain, particularly if one’s name is unique. If your name is common,
like “John Smith,” it may not require as much proactive concern, but it
would still be useful and recommended to set yourself up with a domain
that features your proper name.<br />
Some use this as a place to park their resumes online, and I’ve seen
people simply redirect their proper name domains to their LinkedIn
profiles or Facebook pages. If you ever run into a hater or a crazy
person, you ought to own your name just as a defensive measure to keep
it from being obtained to trash you.<br />
<h2>
It happened to me</h2>
I’m speaking about this from personal experience, unfortunately,
since I once had someone register my professional name as a sort of
threat to try to tarnish my name online. It was a very unusual
situation. I had long operated my personal domain as “<a href="http://silvery.com/">silvery.com</a>,” which was intended to be clever and is closely similar to my nickname, Silver.<br />
Simpler domains like “silver.com” and “silver.net” were already
unavailable, of course, because they were snapped up by domainer
speculators and then resold to jewelers and precious metal commodity
companies. I had thought the domain was just fine for my personal
branding; it didn’t occur to me that I might need other domain assets to
protect myself from attacks.<br />
Apparently, an individual who I had encountered at a company that I
had previously consulted for felt threatened by my SEO knowledge and,
perhaps due to professional jealousy, decided to start setting up
“ChrisSilverSmith.com” to take me down a few notches. (Truly, I had
never done anything to harm nor demean this individual, and I had gone
out of my way to be polite to them despite some aggressive moves on
their part.)<br />
Out of the blue one day, I discovered ChrisSilverSmith.com to be
ranking in Google a page or two back in the results. There was one page
on the site, with an animated GIF or video on it of a humorous sequence
from a popular online multiplayer game. But the Meta Description made
clear it was aimed at me; it was similar or identical to the Meta
Description on my personal site.<br />
I didn’t know at first if it was intended to be a joke or if it was
the first move in a hostile reputation attack campaign. The registration
details were proxied, of course, to hide them. After a little digging,
however, I was able to learn who was behind the registration. I
considered what to do — such as legal options — but, I was initially
determined not to allow the individual the satisfaction of attention,
and I knew that I could use my experience and resources to keep the
domain from affecting my professional work, if necessary.<br />
<h2>
How it turned out</h2>
Ultimately, I gently approached the people involved, diffused the
situation and persuaded them to relinquish the domain, turning ownership
over to me. No threats, no legal action. But many people in such a
situation are not that lucky, and I realized how foolish I had been not
to have already registered my full name as a domain name.<br />
If you have any public persona whatsoever, you ought to proactively
register your name as .COM, if it is available. I’ve known a lot of
colleagues who’ve also faced brief, unwarranted attacks online, and I’ve
dealt with a number of reputation clients who really should have
already been operating a website paired up with a domain name optimized
to be relevant for their personal name.<br />
If you’re doing this proactively, perhaps you only need one domain
name. But if you’re working to mitigate an attack on yourself, you may
find setting up a small handful of domain names is more beneficial than
setting up just your main one.<br />
<h2>
What to do if it happens to you</h2>
Either way, one question that often comes up is, “What should I do if
MyName.com is unavailable?” Here are some of my secret tactics to help
you maximize how effective your efforts will be.<br />
The first, most basic principle is that a domain name that is an
exact match for your name will be the most beneficial. Google and other
search engines look at the keywords found in domain names when
evaluating how relevant a website is to a user’s search query, and the
closer the match, the easier it is for the site to rank higher in search
results.<br />
Google has worked to try to be sure that “official” websites for
brands and individuals may rank highest for name searches, so the bar
for achieving rankings is lower if you get an exact match domain.
Negative materials are often just a page on another site, such as on
RipoffReport.com, or perhaps Yelp, or horrific people-trashing sites
like MyEx.com. Since those sites don’t have your name as a domain name,
you can get an immediate advantage over them in ranking factors with
your personalized domain.<br />
I’ve run into many situations where people have used cute domain
names for their personal websites, as I did for myself. Don’t make that
mistake, because it won’t help in a reputation attack situation.<br />
If your name is “John Smith,” then “JohnsHappyFunPlayhouse.com” is
not going to be helpful. Yes, you can get a website with a different
domain name to rank for your name searches, but it can require more
effort in other areas.<br />
Once you start searching on a domain registrar site, like
GoDaddy.com, they will often suggest many top-level domain (TLD)
alternatives to the “.COM” one. Some of these work better than others,
depending on your situation. If you have a common name, the .COM option
may be unavailable to you — so my tips for these options will be
necessary for you.<br />
By the way, people often ask if they should use their full name
versus the more casual variations they use in personal life. It’s common
to use your full name on your resume while asking people to use a
shortened, familiar version in daily interactions. For instance, should I
use “ChristopherSmith.com” or “ChrisSmith.com”?<br />
The answer to this is: Use the variation that people will be most
frequently searching upon and the name that has been used in any
reputation attack online. If you go by both, you may need to be
conducting reputation-strengthening campaigns for each name variation.<br />
It is also possible to optimize a single website for both name
variations by incorporating both names in the site’s text content and
multiple SEO signals. But mostly, you just need to focus on the name
that people are searching for.<br />
<h2>
10 online reputation domain name secrets</h2>
<b>1. First, start with the grand-daddy standard domain of them all: .COM</b>
— The dot-com TLD is highly effective and preferable to register first
as your primary website if it’s available. There are multiple reasons
it’s effective: It’s one of the longest-established TLDs; it is the
most-recognized top-level domain of all by both humans and machines; and
it functions great from a marketing/branding standpoint, as well as
from a technical standpoint.<br />
If “YourName.com” is already taken, though, don’t despair. In some instances, slight name variations may work just as well.<br />
For instance, dashes are allowed characters in domain names, and they
can be used to delimit between first and last names, as in
“Your-Name.com.” Many optimization experts avoid this out of fear that
search engines may evaluate it to be a suspect domain and lower in
quality and trustworthiness. But these fears may be largely unjustified,
since dashed domains can function well. Admittedly, dashed domains are
undesirable if you’d like to print your URL on your business cards and
in other offline media.<br />
Adding just a few letters near the end of the name can function well,
too, in certain circumstances. Example: ChrisSmithCEO.com or
JamesSmithBanker.com. Mostly, avoid tacking on additional words or
letters, though, or you start eroding your exact-match domain advantage.
Longer domains/URLs function correspondingly worse in search engines,
so only adding very few letters should be considered if your options are
limited.<br />
<b>2. .NET, .BIZ, .US, .ORG</b> — If you search for your name with
most registrars, they are likely to list these TLDs as options for you.
In general, each one of these can function fairly well, closely similar
to .COM.<br />
I would say that in general, none of these confer any specialized
advantages, but they can work quite well as simple, solid TLD extensions
on a proper name domain. (One of my close friends has operated
“John.org” since 1998, but I think he mainly maintains it just for his
email address. It does indeed rank very well for a few queries, which is
mildly surprising, since there’s no optimization put into it, and it’s
not at all focused on his full name.)<br />
<b>3. Treat yourself to a .ME domain</b> — While this is technically
the TLD for the country of Montenegro, the government there decided to
operate it as a Generic Top-Level Domain (gTLD), because they recognized
that it held a wide commercial appeal worldwide, since “Me” is the
English self-referencing pronoun. Domains with the .ME extension can
function very well in search results, and the extension has a decent
degree of recognizability. It’s short; it makes sense; it seems to
convey that it’s operated by the person bearing the name used in the
domain — it’s simply elegant!<br />
A related alternative with differing advantages is to use the <a href="http://about.me/">About.me</a>
service to set up a profile page for yourself at About.me/Your.Name;
this service has inbuilt website design/publishing capabilities and
likely has some degree of ranking capabilities, fresh out of the box. I
probably wouldn’t recommend having both YourName.me and
About.me/Your.Name simultaneously, though — use one or the other.<br />
<b>4. Geographic TLDs</b> — Examples of Geographic TLDs:
YourName.NYC, YourName.Miami, YourName.Paris. In a lot of reputation
management cases, an individual’s name is closely associated with their
local geographic areas in search results, rather than being prominent
nationwide. A common case for this is when well-known proprietors of
local businesses may be searched for with higher frequency in their
cities than elsewhere, and Google will present different search result
rankings according to geography for this reason.<br />
For instance, in most places in the US, if you search for “Chris
Silver Smith,” my site is likely to come up at the top of search results
(since I speak nationwide at conferences and work professionally
nationwide). However, if you search in the Miami area, Google is more
likely to present web pages about an attorney, Chris Silversmith, who
lives and works there.<br />
If you are best-known in your local area, one great option for you
would be to set up a personal website using a GeoTLD that is in sync
with your geography. So Chris Silversmith could leverage his location
associatively by setting up a personal web page on
“ChrisSilversmith.miami,” and it would likely rank quite favorably in
search results. My research indicates that these GeoTLDs perform quite
advantageously in local search results, and SEO strategist <a href="http://www.donuts.domains/donuts-media/donuts-in-the-news/early-data-suggests-new-gtlds-perform-well-in-search-environment">Bill Hartzer</a> has had similar findings.<br />
<b>5. Combine a subdomain with a domain</b> — If you can’t obtain
“FirstnameLastname.com,” which is likely if it’s at all common, then
there’s a possibility you could obtain “Lastname.com.” And if you do
that, you can set up a customized subdomain using your First Name:
http://Firstname.lastname.com — wonderfully, this can accomplish very
good optimization.<br />
To obtain full benefit, be sure to 301 redirect the .www and non-.www
versions of the site domain URLs over to the first/last name subdomain
combination.<br />
<b>6. Use keyworded gTLDs</b> — Honestly, this is a great tactic to
use for many professionals online as their overall commercial
optimization. Attorneys could use .LAWYER, .ATTORNEY or .LEGAL domain
names. For doctors, .CARE, .HEALTHCARE, .SURGERY may be great options.
Indeed, quite a few professions are covered, such as: .ACCOUNTANT,
.ACTOR, .CONTRACTORS, .DENTIST, .BANK, .REALTOR and many others.<br />
Considering that the reputations of many small businesses are as
associated with the names of their founders/owners as they are with the
company brand names, this is an overall good search marketing tactic.
(It’s not as hot when performing offline marketing, such as in print or
radio ads, because people still don’t recognize these newer top-level
domains as much as the .COM/.NET standbys. But you could still use a
more recognizable domain name variation in your offline marketing which
just redirects to the keyworded gTLD.) I find that the shorter gTLDs
function best for optimization, in part simply because shorter URLs
function better in search.<br />
<b>7. Add a misspelling domain</b> — If your ideal, exact-match
domain name isn’t available, you may be able to use a misspelling to
obtain virtually the same level of advantage. If “JohnSmith.com” isn’t
available, “JohnSmiths.com” may work just as well. Google and other
search engines have worked very hard to handle plurals/singulars and
stemming variations of words, often treating them nearly identically.<br />
In addition, using slight, common variations in the spelling of names
may also work. Of course, the rest of the SEO of the site needs to
focus still on the proper, exact-match spelling of the name in most
cases. But a closely similar domain name will be an advantage when you
cannot obtain exact matches. (In fact, even performing a complete
optimization campaign more fully around a misspelling may provide
additional assets to rank for the target name, since Google tries to
incorporate a lot of variation in search results.)<br />
<b>8. Add a .TEL domain</b> — Many marketers are seemingly unaware of
this unique domain; it was set up as an internet directory service,
with all types of contact information stored directly within the domain
name system (DNS) information about each domain. So, the information you
put on your .TEL domain will be republished on many of the sites that
publish domain WHOIS information.<br />
Naturally, you could include all sorts of things — your street
address, city, state, ZIP and phone number — but, you could also include
a biographic description of yourself, links to Facebook, Twitter and
other social media, photos and more! .TEL automatically displays your
domain’s information on the domain URL, marked up in HTML and Card
Microformat. (Can you say, “<a href="http://agsearchblog.com/local-seo-what-are-local-citations/">citations for local SEO?</a>”)<br />
Telnic, the organization that administers the .TEL domain names, has also set up a <a href="http://d0.telpages.com/search.action">directory of links</a>
to help ensure that all of the many .TELs become indexed in Google and
Bing. I have found that by also adding some independent links pointing
into a .TEL domain, one may further help it achieve good rankings.Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-3940726179763962501.post-79449055057832521762016-12-12T03:12:00.002-08:002016-12-12T03:12:47.208-08:00Nuevas caracteristicas de los dominios .telDear valued .tel community member,<br /><br />As 2016 draws to a close, we
would like to take this opportunity to thank you for your continued
support and being part of the .tel community. It is with great pleasure
that we are also able to share with you some exciting news for 2017
which we believe will provide you with a new and enhanced product
experience, greater flexibility and choice with respect to the
application and use of your .tel domains and facilitate innovation in
our namespace.<br /><br /><br /><span style="font-size: 16px; line-height: normal;"><strong>2016 – A Milestone year for Telnic and its community</strong></span><br /><br />2016
has been a milestone year for Telnic and one which we believe provides
us with a firm platform to deliver on the feedback and requests of our
community members and thus increase the value and usage potential of
your .tel domain.<br /><br /><strong>Lifting of usage restrictions</strong><br /><br />As
a direct result of your feedback, Telnic has successfully negotiated
the lifting of usage restrictions from your .tel domain. This means that
you will now be able to use your .tel to design and host your own
website and other digital services of your choosing. This freedom of
choice has been a recurring request from community members and we are
delighted to now offer you this option.<br /><br /><strong>A new Telhosting platform</strong><br /><br />We
are also marking this giant milestone in .tel’s history by providing
our community with an optional, new and modernised Telhosting platform.
The new platform has been designed based on extensive community feedback
and usage patterns observed with the current system.<br /><br />Staying
true to our sponsored status, .tel is the universally recognised web
address for publishing contact details online and is still primarily
intended to serve the needs of individuals and businesses that wish to
store their contact information using the DNS. On this basis, the new
Telhosting platform offers you a compact, feature rich, single page
solution to hosting and publishing your very own digital profile. Your
new site can be totally managed using our new and free iPhone and
Android smartphone apps or using our new desktop control panel and all
for the same competitively low annual subscription fee.<br /><br />We have set up an example digital profile page at <a class="vglnk" href="http://telpage.tel/" rel="nofollow"><span>http</span><span>://</span><span>telpage</span><span>.</span><span>tel</span></a>
for you to get a better feel for how you can leverage the functionality
of the new platform to create a great looking .tel. With lots of new
features such as more advanced custom design capability, PayPal
integration, voucher and offers, PDF publishing and image library, we
know you are going to enjoy and benefit from the new product experience
to create a richer more customized and contemporary digital profile.<br /><br /><img alt="" height="492" src="https://ci6.googleusercontent.com/proxy/0nEAkDE8imfRb0T6xs2BjXCLufNGM4HDuLEi1le96nAzWp1vZ0MPZc4lY2urDcpdsGuuW2J3jSXFyUGmUK-cA05btutOu8w3cDQ5HjHu1kA_89-DTco=s0-d-e1-ft#https://hello.neustar.biz/rs/401-EDD-684/images/tel-image001.png" width="640" /><br /><br />
<div align="center">
Some
examples of great looking .tel domains created on the new platform
using our desktop control panel or iOS and Android smartphone apps</div>
<br /><br /><strong>Retiring the current Telhosting platform</strong><br /><br />As
a result of launching our new Telhosting platform, we will be retiring
the current Telhosting platform and there will be certain features such
as sub domains, search and data privacy which will not be available in
the new platform. Our attached FAQ provides a more detailed list of the
differences between the current and new platforms.<br /><br />We feel that
our new platform offers you incredible value for money and is a great
entry level hosting solution for establishing and managing your own
digital identity and being found in search. If however, you feel that
this new product is not for you then that is fine too and you will soon
be able to utilize your .tel domain for other purposes of your choosing.<br /><br /><strong>What is happening and when?</strong><br /><ul><br />
<li>From
the 13th February 2017, Telnic will issue you (by email) with account
details to the new Telhosting platform. Once you receive your new
details, you can access your new account and start adding content.</li>
<li>From
13th March 2017, any content that you have added to the new platform
will be published to the internet from the new platform. From this date,
content on the current platform will stop being published to the
internet.</li>
<li>It is important to note that Telnic will not be
performing any Data Migration from the current to new platform. Your new
account will be empty and it will be your responsibility to populate
your domain on the new platform before 13th March 2017.</li>
<li>From 13th March 2017, all usage restrictions will be lifted from .tel and you get to choose how you use your .tel domain.</li>
</ul>
<br /><strong>Important information for directory builders and sub domain users</strong><br /><br />Telnic
is very conscious and appreciative of the hard work and effort expended
by many .tel owners who have developed directory sites using the sub
domain functionality. Unfortunately, Telnic is unable to dual run the
current and new platform and will not be offering sub domain
functionality in the new platform. You are advised to back up your
domain data from the current platform using the BACKUP function as soon
as possible and by 12th March 2017 at the latest. This will produce an
XML file containing all of your data which can then be used as a data
source for populating your very own, independent database and service
offering outside of Telhosting.<br /><br />This data will not be accessible
to after the 13th March 2017 therefore it is extremely important to make
this backup copy if you wish to keep and use this data in future
endeavours.<br /><br />Should you wish to continue to host your domain on a
version to the current Telhosting platform which incorporates sub
domains, please contact us at cservice@telnic.org and we will discuss
options available to you.<br /><br /><strong>Customer support for the new platform</strong><br /><br />Up
until now, your registrar or reseller has provided you with access to
and support for the Telhosting platform. Starting on the 13th of March
2017, Telnic will assume this responsibility. For all new platform .tel
hosting product support requests from 13th March 2017 onwards, please
contact cservice@telnic.org. Questions relating to domain lifecycle
activities such as registration, renewal, WHOIS updates etc should
continue to be directed to your registrar or reseller.<br /><br /><strong>Next steps</strong><br /><br />An
FAQ is provided below to help you further understand the nature of the
forthcoming changes and how they may impact you. These changes present
new and exciting opportunities for the .tel community. Over the next few
months, we will be sending out further communications to keep you fully
updated with developments and timescales to ensure a smooth transition.<br /><br />I
hope that you are as excited as we are by this news and we look forward
to working with you to grow the .tel community. If you have any
questions, please contact us at cservice@telnic.org<br /><br />Kindest Regards,<br /><br />Khashayar Mahdavi<br />CEO<br />Telnic Ltd<br /><br /><br /><span style="font-size: 16px; line-height: normal;"><div align="center">
<strong>FAQ</strong></div>
</span><br /><br /><strong>1. When will the restrictions be lifted from .tel and what will be my options then be for using my domain?</strong><br /><br />All
restrictions will be lifted from .tel on 13th March 2017. From this
date, and subject to your registrar or reseller support, you will be
able to use your .tel domain as a normal website, continue to take
advantage of our free, new Telhosting platform or opt for a paid for
Telhosting service which incorporates sub domains with a 3rd party
hosting provider.<br /><br /><strong>2. When will I be able access my new Telhosting account?</strong><br /><br />From
13th February 2017, Telnic will issue (by email) new Telhosting account
details to all .tel owners. From this date, .tel owners will be able to
log in and manage content on the new platform. Please note that this
content will not display on the internet until the current Telhosting
platform is retired on 13th March 2017.<br /><br /><strong>3. What happens if I do not receive my new account details by end of February 2017?</strong><br /><br />If
you have not received account details for your new Telhosting account
by the end of February 2017, you should contact Telnic by sending an
email to cservice@telnic.org confirming the domain name(s) in question.
We will be using the email address that you have stored in your old
Telhosting account profile for your new TelHosting account. Additionally
we will use the email address that is associated with the domain
registrant in our WHOIS to contact you. To ensure that you receive our
communications, you are advised to ensure that these email addresses are
current and accurate.<br /><br /><strong>4. When will the current Telhosting platform be retired?</strong><br /><br />The
current Telhosting platform will be retired and taken offline on 13th
March 2017. You can continue to use the current Telhosting platform up
to 12th March 2017 but not after this date.<br /><br /><strong>5. What happens to my data on the current Telhosting platform after 13th March 2017?</strong><br /><br />.tel
domain owner data that resides on the current Telhosting system will
not be accessible after 13th March 2017. Any .tel domain owner that
wishes to extract a copy of their data from the current system should
run the BACKUP function from their current Telhosting account before
13th March 2017. This will produce an XML file containing all of their
data which can be used either as a reference for populating their new
account or as a data source for populating an independent and separate
3rd party hosting solution.<br /><br /><strong>6. What happens if I do not make a copy of my data before the 13th March 2017?</strong><br /><br />If
you do not make a copy of your data before 13th March 2017, the data
will be deleted and not recoverable as the current Telhosting platform
is being retired.<br /><br /><strong>7. Why is Telnic not migrating my data from the current Telhosting platform to the new?</strong><br /><br />The
current Telhosting platform is being retired and the new platform is
not designed as a like for like replacement in terms of functionality or
data structure. As such, there is no direct data migration path from
old to new so you will need to log in and republish your contact records
in order to take advantage of new functionality that does not exist in
the curent platform. The vast majority of .tel owners only publish a
single page of contacts and content and re-publishing will be a very
quick exercise.<br /><br /><strong>8. What if I wish to continue to host my .tel domain on a platform that supports sub domains?</strong><br /><br />The
current Telhosting platform will be shutdown on 13th March 2017. If you
would like to continue to host your .tel domain on a similar Telhosting
platform that supports sub domains please contact cservice@telnic.org
and we will help you to review hosting options<br /><br /><strong>9. What happens to any new .tel domains that I register before 13th March 2017?</strong><br /><br />Up to 13th March 2017, you will continue to manage your .tel for live internet publishing purposes on the current platform.<br /><br /><strong>10. What happens to any new .tel domains that I buy after 13th March 2017?</strong><br /><br />After
13th March 2017, you will receive information from your registrar and
Telnic informing you of the process to claim your free hosting account
for your new .tel domain. Telnic’s web site (<a class="vglnk" href="http://www.telnic.org/" rel="nofollow"><span>www</span><span>.</span><span>telnic</span><span>.</span><span>org</span></a>)
will have a page dedicated to Telhosting management. On this page, .tel
owners will be able to set up a new telhosting account, add .tel
domains to an existing account as well as manage their domain(s) and
request support.<br /><br />Alternatively, you may opt to use your .tel for a purpose of your own choosing.<br /><br /><strong>11. What happens if I do not access my new Telhosting account and add some contacts or content?</strong><br /><br />The
content from your current Telhosting account will disappear on 13th
March 2017. If you have not populated your new Telhosting account with
any data by this date, your .tel domain will show a standard template
page. Any content that you add after 13th March will automatically be
published.<br /><br /><strong>12. What happens if I take no action before 13th March 2017?</strong><br /><br />If
you do not take any action before 13th March 2017, an account will be
automatically created for you and your domains on the new Telhosting
platform and we will send you the access details by email. Your new
account and domains will remain empty and inactive until you login and
add content. Your account and data on the current Telhosting system will
not be accessible after 12th March 2017 so it is important that you
backup any data you wish to keep before this date.<br /><br /><strong>13. Is there a smartphone app to help manage my .tel domain content on the new Telhosting platform?</strong><br /><br />Yes.
Telnic will have a new iOS and Android app that will enable .tel owners
using Telhosting to fully manage their domain content using their
smartphone. Free downloads will be available from our web site or from
the Apple and Google Play stores. These apps will be available for
download in March 2017.<br /><br /><strong>14. What are the functional differences between the current and new Telhosting platforms?</strong><br /><br />The new Telhosting platform will be a single page product. You can see an example of the new product in use at: <a class="vglnk" href="http://telpage.tel/" rel="nofollow"><span>http</span><span>://</span><span>telpage</span><span>.</span><span>tel</span></a>. It provides a more modern interface that allows the user to:<br /><ul><br />
<li>Publish contact and content records</li>
<li>Add PDF documents</li>
<li>Add Promotional product/service offers</li>
<li>Add Images and Video</li>
<li>Sell Products and services via a PayPal interface</li>
<li>Add custom design</li>
<li>Add an image advert</li>
</ul>
<br />The
new platform does not support a number of features from the current
platform detailed in the list below. The decision to exclude these
features was based on customer feedback and usage statistics.<br /><ul><br />
<li>Multiple pages or sub-domains</li>
<li>Telfriends and private data support</li>
<li>.tel search functionality</li>
<li>Multiple profile support</li>
<li>Telhosting product language support for Arabic, Czech, Japanese, Korean, Portuguese and Russian.</li>
<li>SOAP API access for registrars and domain owners</li>
<li>Google Ad sense integration</li>
</ul>
<br /><strong>15. How will Telnic support the new Telhosting platform?</strong><br /><br />From
13th March 2017, all support requests from domain owners that use the
new Telhosting platform should be sent to cservice@telnic.org . Telnic
will handle these requests directly.<br /><br /><strong>16. If I am not using the Telhosting platform, who do I contact for .tel domain support?</strong><br /><br />Starting
13th March 2017, if you have questions about your domain name and are
not using the Telhosting platform, you should contact your registrar or
reseller for support or the 3rd party hosting provider if you have opted
to use this service.<br /><br /><strong>17. Will domain owners be charged for the new Telhosting platform?</strong><br /><br />No. Telnic will continue to provide a free and optional Telhosting service to all .tel community members.<br /><br /><strong>18. Will my domain registration and ownership status be affected by the Telhosting changes?</strong><br /><br />No.
You will continue to be the owner of your .tel domain and there is no
change to the contractual relationship you have with your registrar or
reseller with respect to domain renewal and other domain specific
activities such as transfers and WHOIS updates. Your registrar will
still be your point of contact with respect to these key domain
lifecycle activities.Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-3940726179763962501.post-52870562707846266082016-11-08T13:50:00.002-08:002016-11-08T13:50:10.523-08:00El futuro de los 10 próximos años de los dominios .tel (2016-2026)<h1>
Adopted Board Resolutions | Regular Meeting of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h1>
<time datetime="2016-11-08T00:15:00-08:00">08 Nov 2016</time><br />
<ol>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1">Consent Agenda:</a>
<ol class="lower-alpha">
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.a">Approval of Board Meeting Minutes</a></li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.b"><abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr class="" title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>) Member Appointments</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.b.rationale">Rationale for Resolution 2016.11.08.02</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.c"><abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr class="" title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>) Member Reappointments</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.c.rationale">Rationale for Resolution 2016.11.08.03</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.d">Appointment of D-, E-, G-, and H-Root Server Operator Representatives to the Root Server System <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Root Server System Advisory Committee">RSSAC</abbr>)</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.d.rationale">Rationale for Resolution 2016.11.08.04</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.e">Investment of Auction Proceeds</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.e.rationale">Rationale for Resolution 2016.11.08.05</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.f"><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Delegation of Authority Guidelines</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.f.rationale">Rationale for Resolution 2016.11.08.06</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.g">Renewal of .TEL Registry Agreement</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.g.rationale">Rationale for Resolution 2016.11.08.07</a></em></li>
</ul>
</li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.h">Thank You to Community Members</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.i">Thank You to Local Host of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.j">Thank You to Sponsors of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#1.k">Thank You to Interpreters, Staff, Event and Hotel Teams of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</a></li>
</ol>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2">Main Agenda:</a>
<ol class="lower-alpha">
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.a">Two-Character Domain Names in the New <abbr title="generic Top Level Domain">gTLD</abbr> Namespace</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.a.rationale">Rationale for Resolution 2016.11.08.15</a></em></li>
</ul>
</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.b">Consideration of the <em>Corn Lake, LLC v. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr></em> Independent Review Process Final Declaration</a>
<ul class="none">
<li><em><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.b.rationale">Rationale for Resolutions 2016.11.08.16 – 2016.11.08.18</a></em></li>
</ul>
</li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.c">Thank You to the Global Multistakeholder Community</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.d">Thank You to Bruno Lanvin for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.e">Thank You to Erika Mann for her service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.f">Thank You to Kuo-Wei Wu for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.g">Thank You to Suzanne Woolf for her service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</a></li>
<li><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#2.h">Thank You to Bruce Tonkin for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</a></li>
</ol>
</li>
</ol>
<ol><a href="https://www.blogger.com/null" id="1" name="1"></a>
<li>
<h3>
Consent Agenda:</h3>
<ol class="lower-alpha"><a href="https://www.blogger.com/null" id="1.a" name="1.a"></a>
<li>
<h4>
Approval of Board Meeting Minutes</h4>
Resolved (2016.11.08.01), the Board approves the minutes of
the 9 August, 15 August, 17 September and 30 September 2016 meetings of
the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board.<br />
</li>
<a href="https://www.blogger.com/null" id="1.b" name="1.b"></a>
<li>
<h4>
<abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>) Member Appointments</h4>
Whereas, the <abbr title="Security – Security, Stability and Resiliency (SSR)">Security </abbr>and <abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>) reviews its membership and makes adjustments from time-to-time.<br />
Whereas, the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> Membership Committee, on behalf of the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>, requests that the Board should appoint Jacques Latour and Tara Whalen to the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> for three-year terms beginning immediately upon approval of the Board and ending on 31 December 2019.<br />
Resolved (2016.11.08.02), that the Board appoints Jacques Latour and Tara Whalen to the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> for three-year terms beginning immediately upon approval of the Board and ending on 31 December 2019.<br />
<a href="https://www.blogger.com/null" id="1.b.rationale" name="1.b.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.02</em></h4>
The <abbr title="Security and Stability Advisory Committee">SSAC</abbr> is a diverse group of individuals whose expertise in specific subject matters enables the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> to fulfill its charter and execute its mission. Since its inception, the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
has invited individuals with deep knowledge and experience in technical
and security areas that are critical to the security and stability of
the Internet’s naming and address allocation systems.<br />
The <abbr title="Security and Stability Advisory Committee">SSAC</abbr>’s
continued operation as a competent body is dependent on the accrual of
talented subject matter experts who have consented to volunteer their
time and energies to the execution of the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
mission. Jacques Latour is currently the CTO at CIRA, the Canadian
Internet Registry Authority for .CA, a position he has held for the past
6 years. He also is an active member of the <abbr title="Country Code Names Supporting Organization">ccNSO</abbr> community and the <abbr title="Internet Engineering Task Force">IETF</abbr> <abbr title="Domain Name System">DNS</abbr>
community. Jacques has extensive country code registry experience and
all of the related technologies. He has been an active member of the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>’s <abbr title="DNS Security Extensions">DNSSEC</abbr> Workshop Program Committee for several years.<br />
Tara Whalen has a PhD in Computer Science followed by a
Masters in Law with a concentration in Law and Technology. She has over
20 years of experience in security and privacy, including working in
the Office of the Privacy Commissioner of Canada, as a Privacy and <abbr title="Security – Security, Stability and Resiliency (SSR)">Security </abbr>Standards Engineer at Apple, and is currently a Staff Privacy Analyst at Google. She has been active in the <abbr title="Internet Engineering Task Force">IETF</abbr> (intrusion detection working group) and is currently active in the <abbr title="World Wide Web Consortium">W3C</abbr> (Privacy Interest Group). She is generally engaged in an operational role around the nexus of security and privacy.<br />
The <abbr title="Security and Stability Advisory Committee">SSAC</abbr> believes Jacques Latour and Tara Whalen would be significant contributing members of the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>.<br />
</li>
<a href="https://www.blogger.com/null" id="1.c" name="1.c"></a>
<li>
<h4>
<abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>) Member Reappointments</h4>
Whereas, Article 12, Section 12.2(b) of the Bylaws governs the <abbr title="Security – Security, Stability and Resiliency (SSR)">Security </abbr>and <abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Security and Stability Advisory Committee">SSAC</abbr>).<br />
Whereas, the Board, at Resolution 2010.08.05.07 approved Bylaws revisions that created three-year terms for <abbr title="Security and Stability Advisory Committee">SSAC</abbr> members, required staggering of terms, and obligated the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> Chair to recommend the reappointment of all current <abbr title="Security and Stability Advisory Committee">SSAC</abbr> members to full or partial terms to implement the Bylaws revisions.<br />
Whereas, the Board, at Resolution 2010.08.05.08 appointed <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
members to terms of one, two, and three years beginning on 01 January
2011 and ending on 31 December 2011, 31 December 2012, and 31 December
2013.<br />
Whereas, in January 2016 the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> Membership Committee initiated an annual review of <abbr title="Security and Stability Advisory Committee">SSAC</abbr> members whose terms are ending 31 December 2016 and submitted to the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> its recommendations for reappointments in September 2016.<br />
Whereas, on 21 September 2016, the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> members approved the reappointments.<br />
Whereas, the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> recommends that the Board reappoint the following <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
members to three-year terms: Jeff Bedser, Ben Butler, Merike Kaeo,
Warren Kumari, Xiaodong Lee, Carlos Martinez, and Danny McPherson.<br />
Resolved (2016.11.08.03), the Board accepts the recommendation of the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> and reappoints the following <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
members to three-year terms beginning 01 January 2017 and ending 31
December 2019: Jeff Bedser, Ben Butler, Merike Kaeo, Warren Kumari,
Xiaodong Lee, Carlos Martinez, and Danny McPherson.<br />
<a href="https://www.blogger.com/null" id="1.c.rationale" name="1.c.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.03</em></h4>
The <abbr title="Security and Stability Advisory Committee">SSAC</abbr> is a diverse group of individuals whose expertise in specific subject matters enables the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> to fulfill its charter and execute its mission. Since its inception, the <abbr title="Security and Stability Advisory Committee">SSAC</abbr>
has invited individuals with deep knowledge and experience in technical
and security areas that are critical to the security and stability of
the Internet’s naming and address allocation systems. The
above-mentioned individuals provide the <abbr title="Security and Stability Advisory Committee">SSAC</abbr> with the expertise and experience required for the Committee to fulfill its charter and execute its mission.<br />
</li>
<a href="https://www.blogger.com/null" id="1.d" name="1.d"></a>
<li>
<h4>
Appointment of D-, E-, G-, and H-Root Server Operator Representatives to the Root Server System <abbr class="" title="Advisory Committee">Advisory Committee</abbr> (<abbr class="" title="Root Server System Advisory Committee">RSSAC</abbr>)</h4>
Whereas, the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws call for the establishment of a Root Server System <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Root Server System Advisory Committee">RSSAC</abbr>) with the role to advise the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
Board of Directors on matters relating to the operation,
administration, security, and integrity of the Internet’s Root Server
System.<br />
Whereas, the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws call for the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors to appoint one <abbr title="Root Server System Advisory Committee">RSSAC</abbr> member from each Root Server operator organization, based on recommendations from the <abbr title="Root Server System Advisory Committee">RSSAC</abbr> Co-Chairs.<br />
Whereas, the <abbr title="Root Server System Advisory Committee">RSSAC</abbr> Co-Chairs have recommended for <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors consideration the appointment of representatives from the D-, E-, G, and H-root server operators to the <abbr title="Root Server System Advisory Committee">RSSAC</abbr>.<br />
Resolved (2016.11.08.04), the Board appoints to the <abbr title="Root Server System Advisory Committee">RSSAC</abbr>
the following representatives from the D-, E-, G-, and H-root server
operators: Tripti Sinha, Kevin Jones, Kevin Wright, and Howard Kash,
respectively, through 31 December 2019.<br />
<a href="https://www.blogger.com/null" id="1.d.rationale" name="1.d.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.04</em></h4>
In May 2013, the root server operators (RSO) agreed to an initial membership of RSO representatives for <abbr title="Root Server System Advisory Committee">RSSAC</abbr>, and each RSO nominated an individual. The <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors approved the initial membership of <abbr title="Root Server System Advisory Committee">RSSAC</abbr> in July 2013 with staggered terms.<br />
The representatives from the D-, E-, G-, and H-root server
operators were appointed to an initial three-year term, which expires on
31 December 2016. These appointments are for full, three-year terms.<br />
The appointment of these <abbr title="Root Server System Advisory Committee">RSSAC</abbr> members is not anticipated to have any fiscal impact on <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>, though there are budgeted resources necessary for ongoing support of the <abbr class="" title="Root Server System Advisory Committee">RSSAC</abbr>.<br />
This resolution is an organizational administrative function for which no public comment is required. The appointment of <abbr title="Root Server System Advisory Committee">RSSAC</abbr> members contributes to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s commitment to strengthening the security, stability, and resiliency of the <abbr title="Domain Name System">DNS</abbr>.<br />
</li>
<a href="https://www.blogger.com/null" id="1.e" name="1.e"></a>
<li>
<h4>
Investment of Auction Proceeds</h4>
Whereas, to date <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> has collected US$233 million of auction proceeds.<br />
Whereas, the Board Finance Committee has determined that
auction proceeds need to be invested in a manner that preserves capital
and keeps these funds readily available.<br />
Whereas, the Board Finance Committee recommends that auction
proceeds be distributed across three different investment managers, and
invested in safe and liquid financial instruments.<br />
Resolved (2016.11.08.05), the<a href="https://www.blogger.com/null" name="4.rationale"></a> Board
authorizes the President and CEO, or his designee(s), to take all
actions necessary to distribute the auction proceeds across three
different investment managers, which will be tasked with investing those
proceeds in safe and liquid financial instruments.<br />
<a href="https://www.blogger.com/null" id="1.e.rationale" name="1.e.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.05</em></h4>
To date <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> has collected auction proceeds totaling US$233 million. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
continuously mitigates the risk of custody by distributing investments
across more than one investment management firm. Considering the amount
of auction proceeds collected to date, the number of firms used to
manage these funds need to be increased from the one firm currently
used, to three firms. Through an RFP conducted in 2013 for the New <abbr title="generic Top Level Domain">gTLD</abbr> Program, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
has already qualified three investment management firms. The auction
funds will be distributed across these three firms, in separate and
distinct accounts holding exclusively auction proceeds. In addition,
considering the intended usage of these funds in the near future, as per
the ongoing community process, the BFC has recommended that the
managers hold these funds in safe and liquid financial instruments.<br />
As a result, the organization recommends that the auction
proceeds be invested at three different investment managers to reduce
the risk of custody, and be invested in safe and liquid financial
instruments.<br />
This action is not expected to have any fiscal impact, or any
impact on the security, stability and resiliency of the domain name
system.<br />
This is an Organizational Administrative Function that does not require public comment.<br />
</li>
<a href="https://www.blogger.com/null" id="1.f" name="1.f"></a>
<li>
<h4>
<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Delegation of Authority Guidelines</h4>
Whereas, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws <a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article2">Article 2</a> establishes that with certain exceptions, the powers of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
shall be exercised by, and its property controlled and its business and
affairs conducted by or under the direction of, the Board.<br />
Whereas, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws <a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article15" title="⽠叽翿">Article 15</a> establishes officers of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>, and designates the President to be the Chief Executive Officer (CEO) of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
in charge of all of its activities and business. All other officers and
staff shall report to the President or his or her delegate, unless
stated otherwise in the Bylaws.<br />
Whereas, the Board desires to set out a clear line of
delegation of authority between the role of the Board and the roles of
CEO and management.<br />
Resolved (2016.11.08.06), the Board hereby adopts the “<a href="https://www.icann.org/en/system/files/files/delegation-of-authority-guidelines-08nov16-en.pdf"><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Delegation of Authority Guidelines</a>” to provide clear guidance and clarification of roles between the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
CEO/Management (“Guidelines”). The Guidelines shall be reviewed
regularly and amended from time to time by resolution of the Board.<br />
<a href="https://www.blogger.com/null" id="1.f.rationale" name="1.f.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.06</em></h4>
The Board is taking action at this time to adopt a set of
guidelines to provide greater clarity of roles between the Board and
CEO/Management. These guidelines, titled “<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
Delegation of Authority Guidelines,” identify the respective key roles
of the Board, key roles of CEO/Management, and the key interdependencies
in those relationships. As outlined in the Guidelines, a primary source
of the Board’s powers come directly from the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
Bylaws, as well as internal policies. Among others, these key powers
include: (1) acting collectively by voting at meetings to authorize and
direct management to take action on behalf of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> organization, (2) interacting with the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community to ensure that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is serving the global public interest within <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s mission, and (3) considering policy recommendations arising out of <abbr title="Supporting Organizations">Supporting Organizations</abbr>, including participating in consultation processes if necessary.<br />
The <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
CEO is authorized to act within the authority delegated by the Board.
The CEO may designate key management to assist in carrying out these
responsibilities. The CEO’s responsibilities, include, but are not
limited to: (1) interacting with the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community to ensure that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is serving the global public interest within <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s mission, (2) maintaining open lines of communication with the Board, (3) interacting with governments within the scope of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s mission and Board’s directives, and (4) leading and overseeing <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s day-to-day operations.<br />
By adopting these Guidelines, the Board intends to ensure
that the Board and CEO/Management continue to operate within the scope
of its mission. The Board’s approval of the Guidelines will have
positive impact on the community as provides additional transparency and
clarity about the roles and responsibilities of key members in the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
organization. Additionally, it provides additional accountability to
the community by clearly defining the roles and responsibilities.<br />
There is no anticipated fiscal impact of the Board taking
this action, and there are no expected security, stability, or
resiliency issues related to the <abbr title="Domain Name System">DNS</abbr> associated with the Board’s approval of the Guidelines.<br />
This decision is an Organizational Administrative Function that does not require public comment.<br />
</li>
<a href="https://www.blogger.com/null" id="1.g" name="1.g."></a>
<li>
<h4>
Renewal of .TEL Registry Agreement</h4>
Whereas, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
commenced a public comment period from 04 August 2016 to 13 September
2016 on a proposed Renewal Registry Agreement for the .TEL <abbr title="Top Level Domain">TLD</abbr>.<br />
Whereas, the proposed .TEL Renewal Registry Agreement
includes modified provisions to bring the .TEL Registry Agreement into
line with the form of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement.<br />
Whereas, the public comment forum on the proposed Renewal Registry Agreement closed on 13 September 2016, with <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
receiving twenty-seven (27) comments, both by individuals and
organizations/groups. A summary and analysis of the comments were
provided to the Board. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
modified the proposed Renewal Registry Agreement to correct
typographical errors and to incorporate additional clarifying language
in response to the public comments related to the <abbr title="Rights Protection Mechanism">RPM</abbr>
language proposed in Section 1 of Specification 7 regarding
applicability and implementation of applicable rights protection
mechanisms.<br />
Whereas, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
conducted a review of Telnic’s recent performance under the current
.TEL Registry Agreement and found that Telnic substantially met its
contractual requirements.<br />
Resolved (2016.11.08.07), the .TEL Renewal Registry
Agreement, as revised, is approved and the President and CEO, or his
designee(s), is authorized to take such actions as appropriate to
finalize and execute the Agreement.<br />
<a href="https://www.blogger.com/null" id="1.g.rationale" name="1.g.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.07</em></h4>
<strong>Why the Board is addressing the issue now?</strong><br />
<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> and Telnic Limited (the “Registry Operator”) entered into a <a href="https://www.icann.org/resources/unthemed-pages/tel-2012-02-25-en">Registry Agreement</a>
on 30 May 2006 for operation of the .TEL top-level domain. The current
.TEL Registry Agreement expires on 01 March 2017. The proposed Renewal
Registry Agreement was posted for public comment between 04 August 2016
and 13 September 2016. At this time, the Board is approving the Renewal
Registry Agreement for the continued operation of the .TEL <abbr title="Top Level Domain">TLD</abbr> by the Registry Operator.<br />
<strong>What is the proposal being considered?</strong><br />
The revised Renewal Registry Agreement approved by the Board
includes modified provisions to bring the Agreement into line with the
form of the New <abbr title="generic Top Level Domain">gTLD</abbr>
Registry Agreement. The modifications include: updating technical
specifications; adding Public Interest Commitments including the
obligation to only use registrars under the 2013 Registrar Accreditation
Agreement; and requiring the implementation of additional Rights
Protection Mechanisms, namely the Uniform Rapid Suspension and the
Post-Delegation Dispute Resolution Procedure.<br />
Specifically, all approved registry services in the current
.TEL Registry Agreement carry over to the revised Renewal Registry
Agreement. Such services include Bulk Transfer After Partial Portfolio
Acquisition, Registry Controlled <abbr title="Domain Name System">DNS</abbr>
Records Service, Domain data change notifications, Whois private
contact information opt-out for Individuals, Special Access Service,
Additional RDDS Data Fields and Internationalized Domain Names.<br />
With regard to the Schedule of Reserved Names, the revised
Renewal Registry Agreement includes existing provisions permitting the
Registry Operator to allocate previously reserved one and two-character
names through <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>-accredited
registrars via a Phased Allocation Program. However, all
single-character numerical labels continue to be reserved at the second
level.<br />
As part of the adaptation needed to carry over the Sponsored <abbr title="Top Level Domain">TLD</abbr> Charter of .TEL to the revised Renewal Registry Agreement, Specification 12 incorporates the language of the original <a href="https://www.icann.org/resources/unthemed-pages/appendix-s-2011-02-02-en">Sponsorship Charter - Appendix S</a> in the current .TEL <abbr title="Top Level Domain">TLD</abbr>
Agreement, with modifications to remove the requirement that the
Registry control the name servers of delegated domain names, and the
restriction that registrants cannot define the contents of the zone for
their domain names. As .TEL was originally approved under this premise,
the change will transform the .TEL <abbr title="Top Level Domain">TLD</abbr> into a <abbr title="generic Top Level Domain">gTLD</abbr> with a limited set of community parameters. These parameters will become optional rather than required.<br />
<strong>Which stakeholders or others were consulted?</strong><br />
<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
conducted a public comment period on the proposed .TEL Renewal Registry
Agreement from 04 August 2016 through 13 September 2016, following
which time the comments were summarized and analyzed. Additionally, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
engaged in bilateral negotiations with the Registry Operator to agree
to the package of terms to be included in the proposed Renewal Registry
Agreement that was posted for public comment.<br />
<strong>What concerns or issues were raised by the community?</strong><br />
The proposed Renewal Registry Agreement was posted for public
comment. Commenters expressed their views in three key areas during the
public comment period:<br />
<ul>
<li>
<u>Extension of .TEL Registry Agreement</u>: Some of the commenters
expressed support for the extension of .TEL Registry Agreement, while
others suggested that improvements should be implemented for .TEL domain
names if the .TEL Registry Agreement is to be extended.</li>
<li>
<u>Proposed Renewal Registry Agreement for .TEL</u>: Three key issue areas were raised on the specific text of the renewal:</li>
<li>General Views – Some commenters positively noted there are technical and operational advantages to the New <abbr title="generic Top Level Domain">gTLD</abbr>
Registry Agreement form that serve as a benefit to registrants and the
Internet community over earlier versions of the legacy Agreement.
Additionally, there was support for <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s efforts at bilateral negotiations with legacy <abbr title="Top Level Domain">TLD</abbr> registries in order to transition to the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement and the procedural benefit of consistency that will come with <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s bilaterally negotiating for transition to provisions of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement not only with .TEL but with other legacy TLDs like .JOBS, .CAT, .PRO, and .TRAVEL.</li>
<li>Rights Protection Mechanisms – One commenter sought
clarity over the language proposed in Section 1 of Specification 7
regarding applicability and implementation of rights protection
mechanisms. </li>
<ul>
<li>Registration Data Directory Service (Whois) – Some
commenters raised concerns with continuing the unique Registration Data
Directory Service that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s Board approved in 2007 for the .TEL <abbr title="Top Level Domain">TLD</abbr>. </li>
</ul>
<li>The continued operation of .TEL by Telnic Limited:
Concerns were expressed over Telnic Limited continuing to be the
Registry Operator of .TEL, claiming, among other things that Telnic has
violated <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s requirements several times and Telnic no longer has stable financials to continue the operation of .TEL. </li>
</ul>
<strong>What significant materials did the Board review?</strong><br />
As part of its deliberations, the Board reviewed various
materials, including, but not limited to, the following materials and
documents:<br />
<ul>
<li>.TEL form of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement: <<a href="https://www.icann.org/sites/default/files/tlds/tel/tel-proposed-renewal-04aug16-en.pdf">https://www.icann.org/sites/default/files/tlds/tel/tel-proposed-renewal-04aug16-en.pdf</a>> </li>
<li>.TEL Addendum to form of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement: <<a href="https://www.icann.org/sites/default/files/tlds/tel/tel-proposed-renewal-addendum-04aug16-en.pdf">https://www.icann.org/sites/default/files/tlds/tel/tel-proposed-renewal-addendum-04aug16-en.pdf</a>>. At this time, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is proposing to implement the incorporation of terms unique to a legacy <abbr title="Top Level Domain">TLD</abbr>,
such as .TEL, through an "Addendum" to the Registry Agreement. The
Addendum will show the terms of the .TEL Registry Agreement that are
unique from the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement that are incorporated into the renewal. </li>
<li>Public comments: <<a href="https://forum.icann.org/lists/comments-tel-renewal-04aug16/">https://forum.icann.org/lists/comments-tel-renewal-04aug16/</a>></li>
<li>Summary and analysis of public comments: <<a href="https://www.icann.org/en/system/files/files/report-comments-tel-renewal-07oct16-en.pdf">https://www.icann.org/en/system/files/files/report-comments-tel-renewal-07oct16-en.pdf</a>></li>
<li>27 September 2016 letter from Telnic CEO to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board: <a href="https://www.icann.org/en/system/files/correspondence/mahdavi-to-icann-board-27sep16-en.pdf">https://www.icann.org/en/system/files/correspondence/mahdavi-to-icann-board-27sep16-en.pdf</a>. Telnic's observations on past achievements and opportunities for .TEL.</li>
<li>Current .TEL Registry Agreement and Appendices: <<a href="https://www.icann.org/resources/unthemed-pages/tel-2012-02-25-en">https://www.icann.org/resources/unthemed-pages/tel-2012-02-25-en</a>></li>
<li>New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement – Updated 09 January 2014 <<a href="http://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.pdf">http://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.pdf</a> ></li>
<li>
<a href="https://www.icann.org/resources/board-material/minutes-2007-12-18-en">18 December 2007 Board Resolution</a> that approved changes to .TEL’s Registration Data Directory Service (Whois) requirements </li>
</ul>
<strong>What factors has the Board found to be significant?</strong><br />
The Board carefully considered the public comments received
for the Renewal Registry Agreement, along with the summary and analysis
of those comments. The Board also considered the terms agreed to by the
Registry Operator as part of the bilateral negotiations with <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>.
The Board acknowledges the concerns expressed by some community members
regarding suggested improvements that should be implemented for .TEL
domain names if the .TEL Registry Agreement is to be extended. However,
the terms of the .TEL Registry Agreement set forth the contractual
obligations that must be fulfilled by Telnic Limited in its operation of
the .TEL registry but do not prescribe or proscribe the Registry
Operators’ business model. Additionally, the <a href="https://www.icann.org/en/system/files/files/report-comments-tel-renewal-07oct16-en.pdf">Staff Report of Public Comment Proceeding</a>
encouraged those commenters that desire to see changes in the business
model of the .TEL registry to contact Telnic Limited to discuss these
matters.<br />
The Board acknowledges the request for clarity over the <abbr title="Rights Protection Mechanism">RPM</abbr>
language proposed in Section 1 of Specification 7 regarding
applicability and implementation of applicable rights protection
mechanisms. While the revisions to Specification 7 were consistent with
prior legacies, a modification was made to the language of the Renewal
Registry Agreement for .TEL to address the comment. The revision is now
reflected in Section 1 of Specification 7 of the revised Renewal
Registry Agreement to read “Registry Operator will include all RPMs
required by this Specification and any additional RPMs developed and
implemented by Registry Operator in the registry-registrar agreement
entered into by <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>-accredited registrars authorized to register names in the <abbr title="Top Level Domain">TLD</abbr>.”<br />
The Board acknowledges the concerns raised with continuing
the unique Registration Data Directory Service that the Board approved
in 2007 for the .TEL <abbr title="Top Level Domain">TLD</abbr>. The Board notes the <a href="https://www.icann.org/resources/board-material/minutes-2007-12-18-en">18 December 2007 Board Resolution</a>
that approved changes to .TEL’s Registration Data Directory Service
(Whois) requirements was based on unique business and legal
circumstances stating, “…the Board concludes that the requested
modifications are justified by the unique business and legal
circumstances of the .TEL top-level domain…” After conferring with
Telnic Limited, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
has confirmed that, to the knowledge of the Registry Operator, the
legal circumstances related to Registration Data Directory Service
(Whois) have not changed. Therefore, the Registration Data Directory
Service (Whois) requirements which were ultimately replicated from the
prior agreement between <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> and Telnic Limited will be retained in the Renewal Registry Agreement.<br />
Additionally, the Board has considered comments regarding the
continued operation of .TEL by Telnic Limited, including concerns that
Telnic has violated <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s
requirements several times and Telnic no longer has stable financials
to continue the operation of .TEL. As part of the renewal process <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
conducts a review of contractual compliance under the .TEL Registry
Agreement. Telnic Limited was found to be in substantial compliance with
their contractual requirements. Also, during the past 10 years of
operation, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
has no knowledge of Telnic Limited experiencing financial or other
operational impediments that have caused a failure of registry
operations or security and stability concerns. If Telnic Limited were to
experience financial problems that resulted in the Registry Operator
failing to comply with its obligations under the Registry Agreement, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> can take action to protect registrants and ensure continuity of registry operations.<br />
Finally, the Board notes that existing Registry Agreement
calls for presumptive renewal of the Agreement at its expiration so long
as certain requirements are met. These provisions are intended to
promote stability and security of the registry by encouraging long-term
investment in <abbr title="Top Level Domain">TLD</abbr> operations,
which benefits the community in the form of reliable operation of
registry infrastructure. The Renewal Registry Agreement is subject to
the negotiation of renewal terms reasonably acceptable to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
and the Registry Operator. The renewal terms approved by the Board are
the result of the bilateral negotiations called for in the current
Registry Agreement.<br />
<strong>Are there positive or negative community impacts?</strong><br />
The Board’s approval of the Renewal Registry Agreement also
offers positive technical and operational benefits. Pursuant to the
Renewal Registry Agreement, in the event that any of the emergency
thresholds for registry functions is reached, Registry Operator agrees
that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> may designate an emergency interim Registry Operator of the registry for the <abbr title="Top Level Domain">TLD</abbr>, which would mitigate the risks to the stability and security of the <abbr title="Domain Name">Domain Name</abbr> System. Also, technical onboarding of the Registry Operator to comply with the provisions in the New <abbr title="generic Top Level Domain">gTLD</abbr> Agreement will allow the registry to use uniform and automated processes, which will facilitate operation of the <abbr title="Top Level Domain">TLD</abbr>.<br />
There will also be positive impacts on registrars and registrants. The transition to the New <abbr title="generic Top Level Domain">gTLD</abbr>
Registry Agreement will provide consistency across all registries
leading to a more predictable environment for end-users and also the
fact that the proposed Renewal Registry Agreement requires that the
Registry Operator uses <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> accredited registrars that are party to the 2013 Registrar Accreditation Agreement (<abbr title="Registrar Accreditation Agreement">RAA</abbr>) only will provide more benefits to registrars and registrants.<br />
<strong>Are there fiscal impacts or ramifications on <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> (strategic plan, operating plan, budget); the community; and/or the public?</strong><br />
There is no significant fiscal impact expected if <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
approves the proposed .TEL Renewal Registry Agreement. It should be
noted however that as a result of approval of the Renewal Registry
Agreement, projected annual registry fees to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> will result in a minimal negative fiscal impact. This change has been considered in <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s budget.<br />
<strong>Are there any security, stability or resiliency issues relating to the <abbr title="Domain Name System">DNS</abbr>?</strong><br />
There are no expected security, stability, or resiliency issues related to the <abbr title="Domain Name System">DNS</abbr> if <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
approves the proposed .TEL Renewal Registry Agreement. The proposed
Renewal Registry Agreement in fact includes terms intended to allow for
swifter action in the event of certain threats to the security or
stability of the <abbr title="Domain Name System">DNS</abbr>. As part of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s organizational administrative function, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> posted the draft Renewal Registry Agreement for public comment on 04 August 2016.<br />
</li>
<a href="https://www.blogger.com/null" id="1.h" name="1.h"></a>
<li>
<h4>
Thank You to Community Members</h4>
Whereas, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> wishes to acknowledge the considerable effort, skills, and time that members of the stakeholder community contribute to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>.<br />
Whereas, in recognition of these contributions, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> wishes to acknowledge and thank members of the community when their terms of service end on the <abbr title="Supporting Organizations">Supporting Organizations</abbr>, <abbr title="Advisory Committees">Advisory Committees</abbr> and Nominating Committee. <br />
Whereas, the following members of the Address <abbr title="Supporting Organization">Supporting Organization</abbr> are concluding their terms of service:<br />
<ul>
<li>Dmitry Kohmanyuk, Address <abbr title="Supporting Organization">Supporting Organization</abbr> Address Council Member</li>
<li>John Sweeting, Address <abbr title="Supporting Organization">Supporting Organization</abbr> Address Council Member</li>
</ul>
Resolved (2016.11.08.08), Dmitry Kohmanyuk and John Sweeting have earned the deep appreciation of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following members of the County Code Names <abbr title="Supporting Organization">Supporting Organization</abbr> are concluding their terms of service:<br />
<ul>
<li>Becky Burr, County Code Names <abbr title="Supporting Organization">Supporting Organization</abbr> Council Member</li>
<li>Celia Lerman Friedman, County Code Names <abbr title="Supporting Organization">Supporting Organization</abbr> Council Member</li>
<li>Vika Mpisane, County Code Names <abbr title="Supporting Organization">Supporting Organization</abbr> Council Member </li>
<li>Ron Sherwood, County Code Names <abbr title="Supporting Organization">Supporting Organization</abbr> Liaison to the At-Large <abbr title="Advisory Committee">Advisory Committee</abbr></li>
</ul>
Resolved (2016.11.08.09), Becky Burr, Celia Lerman Friedman,
Vika Mpisane, and Ron Sherwood have earned the deep appreciation of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following members of the Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> are concluding their terms of service:<br />
<ul>
<li>David Cake, Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> Councilor </li>
<li>Mason Cole, Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> Liaison to the Governmental <abbr title="Advisory Committee">Advisory Committee</abbr> </li>
<li>Jennifer Gore, Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> Councilor </li>
<li>Volker Greimann, Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> Councilor</li>
<li>Carlos <abbr title="Registrar">Ra</abbr>úl Gutiérrez, Councilor</li>
<li>Michele Neylon, Registrar Stakeholder Group Chair</li>
<li>Darcy Southwell, Registrar Stakeholder Group Vice Chair</li>
<li>Rudi Vansnick, Not-for-Profit Operational Concerns Constituency Chair</li>
</ul>
Resolved (2016.11.08.10), David Cake, Mason Cole, Jennifer Gore, Volker Greimann, Carlos <abbr title="Registrar">Ra</abbr>úl Gutiérrez, Michele Neylon, Darcy Southwell, and Rudi Vansnick have earned the deep appreciation of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following members of the At-Large community are concluding their terms of service:<br />
<ul>
<li>Satish Babu, Asian, Australasian and Pacific Islands Regional At-Large Organization Vice Chair</li>
<li>Humberto Carrasco, Latin American and Caribbean Islands Regional At-Large Organization Secretariat</li>
<li>Olivier Crépin-Leblond, At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> Liaison to the Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr></li>
<li>Timothy Denton, At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> Member</li>
<li>Sandra Hoferichter, At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> Member</li>
<li>Barrack Otieno, African Regional At-Large Organization Secretariat</li>
<li>Vanda Scartezini, At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> Member</li>
<li>Jimmy Schulz, At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> Member</li>
<li>Alberto Soto, Latin American and Caribbean Islands Regional At-Large Organization Chair</li>
<li>Siranush Vardanyan, Asian, Australasian and Pacific Islands Regional At-Large Organization Chair</li>
</ul>
Resolved (2016.11.08.11), Satish Babu, Humberto Carrasco,
Olivier Crépin-Leblond, Timothy Denton, Sandra Hoferichter, Barrack
Otieno, Vanda Scartezini, Jimmy Schulz, Alberto Soto, and Siranush
Vardanyan have earned the deep appreciation of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following members of the Root Server System <abbr title="Advisory Committee">Advisory Committee</abbr> are concluding their terms of service:<br />
<ul>
<li>Jim Cassell, Member </li>
<li>Ashley Heineman, National Telecommunications and Information Administration Liaison to the Root Server System <abbr title="Advisory Committee">Advisory Committee</abbr> </li>
<li>Lars-Johan Liman, Co-Chair</li>
<li>Jim Martin, Member</li>
</ul>
Resolved (2016.11.08.12), Jim Cassell, Ashley Heineman,
Lars-Johan Liman, and Jim Martin have earned the deep appreciation of
the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following member of the <abbr title="Security – Security, Stability and Resiliency (SSR)">Security </abbr>and <abbr title="Security, Stability and Resiliency">Stability</abbr> <abbr title="Advisory Committee">Advisory Committee</abbr> is concluding his term of service:<br />
<ul>
<li>Shinta Sato, Member </li>
</ul>
Resolved (2016.11.08.13), Shinta Sato has earned the deep appreciation of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for his terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes him well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
Whereas, the following members of the Nominating Committee are concluding their terms of service:<br />
<ul>
<li>Stephen Coates, Member</li>
<li>Sylvia Herlein Leite, Member </li>
<li>Hans Petter Holen, Chair-Elect</li>
<li>Zahid Jamil, Member</li>
<li>Wolfgang Kleinwächter, Associate Chair</li>
<li>Yrjö Länsipuro, Member </li>
<li>Stéphane Van Gelder, Chair</li>
</ul>
Resolved (2016.11.08.14), Stephen Coates, Sylvia Herlein
Leite, Hans Petter Holen, Zahid Jamil, Wolfgang Kleinwächter, Yrjö
Länsipuro, and Stéphane Van Gelder have earned the deep appreciation of
the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors for their terms of service, and the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board of Directors wishes them well in their future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
<a href="https://www.blogger.com/null" id="1.i" name="1.i"></a>
<li>
<h4>
Thank You to Local Host of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</h4>
The Board wishes to extend its thanks to the local host
organizer, Minister Ravi Shankar Prasad and the Government of India
including Ministry of Electronics and Information Technology, Ministry
of External Affairs, National <abbr title="Security – Security, Stability and Resiliency (SSR)">Security </abbr>Council Secretariat, Ministry of Home Affairs, Government of Telangana and National Internet Exchange of India (NIXI).<br />
</li>
<a href="https://www.blogger.com/null" id="1.j" name="1.j"></a>
<li>
<h4>
Thank You to Sponsors of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</h4>
The Board wishes to thank the following sponsors:
CentralNic, Knipp Median und Communication GmbH, Afilias plc, Public
Interest Registry, China Internet Network Information Center, Nominet,
Web Werks India Pvt. Ltd., Radix FZC, Verisign, .blog, Directi Web
Technology Private Limited, BNSL, Tata Tele Services, Atria Convergence
Technologies Pvt. Ltd. (ACT) and GMR.<br />
</li>
<a href="https://www.blogger.com/null" id="1.k" name="1.k"></a>
<li>
<h4>
Thank You to Interpreters, Staff, Event and Hotel Teams of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> 57 Meeting</h4>
The Board expresses its deepest appreciation to the scribes, interpreters, audiovisual team, technical teams, and the entire <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> staff for their efforts in facilitating the smooth operation of the meeting.<br />
The Board would also like to thank the management and staff
of the Hyderabad International Convention Center for providing a
wonderful facility to hold this event. Special thanks are extended to
Vijay Ramnath Ugale, Event Manager; Varun Mehrotra, Director of Sales -
Meetings & Events; Gorav Arora, Director of Sales and Marketing;
Shyam Sunder, Director of Convention; Ravindra Reddy, Assistant Manager
of Client Services; Johnet Pereira, Manager of Client Services; Rambabu
Talluri, IT Manager; Anand Prakash Ravi, Operational Manager; Ramu
Dasari, Asst. Manager of Client Services; Mr. Ranjan Alu, Asst. Manager
F&B; Executive Chef Amanaraju; and Gilbert Yeo from Pryde Live.<br />
</li>
</ol>
</li>
<a href="https://www.blogger.com/null" id="2" name="2"></a>
<li>
<h3>
Main Agenda:</h3>
<ol class="lower-alpha"><a href="https://www.blogger.com/null" id="2.a" name="2.a"></a>
<li>
<h4>
Two-Character Domain Names in the New <abbr title="generic Top Level Domain">gTLD</abbr> Namespace</h4>
Whereas, Specification 5, Section 2 of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement requires registry operators to reserve two-character ASCII labels within the <abbr title="Top Level Domain">TLD</abbr>
at the second level. The reserved two-character labels “may be released
to the extent that Registry Operator reaches agreement with the related
government and country-code manager of the string as specified in the <abbr title="International Organization for Standardization">ISO</abbr>
3166-1 alpha-2 standard. The Registry Operator may also propose the
release of these reservations based on its implementation of measures to
avoid confusion with the corresponding country codes, subject to
approval by <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>.”<br />
Whereas, the <abbr title="Governmental Advisory Committee">GAC</abbr> has issued advice to the Board in various communiqués on two-character domains. The <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-15oct14-en.pdf">Los Angeles Communiqué</a> (15 October 2014) stated, “The <abbr title="Governmental Advisory Committee">GAC</abbr>
recognized that two-character second level domain names are in wide use
across existing TLDs, and have not been the cause of any security,
stability, technical or competition concerns. The <abbr title="Governmental Advisory Committee">GAC</abbr> is not in a position to offer consensus advice on the use of two-character second level domains names in new <abbr title="generic Top Level Domain">gTLD</abbr> registry operations, including those combinations of letters that are also on the <abbr title="International Organization for Standardization">ISO</abbr> 3166-1 alpha 2 list.” The <abbr title="Governmental Advisory Committee">GAC</abbr> also issued advice in the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-11feb15-en.pdf">Singapore Communiqué</a> (11 February 2015) and the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-21oct15-en.pdf">Dublin Communiqué</a> (21 October 2015).<br />
Whereas, on 16 October 2014, the Board directed <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
to develop and implement an efficient procedure for the release of
two-character domains currently required to be reserved in the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement, taking into account the <abbr title="Governmental Advisory Committee">GAC</abbr>’s advice in the Los Angeles Communiqué on the matter. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> launched this procedure (the “Authorization Process”) on 1 December 2014.<br />
Whereas, as part of the Authorization Process, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
launched a community consultation process to help develop a standard
set of proposed measures to avoid confusion with country codes. The
measures were intended to be mandatory for new <abbr title="generic Top Level Domain">gTLD</abbr> registries seeking to release reserved letter/letter two-character labels.<br />
Whereas, in the <abbr title="Governmental Advisory Committee">GAC</abbr>’s <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-30jun16-en.pdf">Helsinki Communiqué</a> (30 June 2016), the <abbr title="Governmental Advisory Committee">GAC</abbr> advised the Board to “urge the relevant Registry or the Registrar to engage with the relevant <abbr title="Governmental Advisory Committee">GAC</abbr>
members when a risk is identified in order to come to an agreement on
how to manage it or to have a third-party assessment of the situation if
the name is already registered.” The advice was incorporated in the
proposed measures to avoid confusion.<br />
Whereas, on 8 July 2016, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> published for public comment the <a href="https://www.icann.org/en/system/files/files/proposed-measures-two-char-08jul16-en.pdf">Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes</a>,
which listed measures registry operators could adopt to avoid confusion
with corresponding country codes. The measures incorporated the <abbr title="Governmental Advisory Committee">GAC</abbr>’s advice issued in the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-30jun16-en.pdf">Helsinki Communiqué</a>. Forty-three comments were submitted by individuals, governments and groups/organizations.<br />
Whereas, the Board considered the public comments, the staff summary and analysis report of public comments, and <abbr title="Governmental Advisory Committee">GAC</abbr> advice. The proposed measures were updated to take into account the public comments and <abbr title="Governmental Advisory Committee">GAC</abbr> advice relating to the proposed measures and two-character labels.<br />
Resolved (2016.11.08.15), the <a href="https://www.icann.org/en/system/files/files/revised-measures-ltr-ltr-two-char-ascii-labels-country-codes-08nov16-en.pdf">Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes</a>
as revised are approved, and the President and CEO, or his designee(s),
is authorized to take such actions as appropriate to authorize registry
operators to release at the second level the reserved letter/letter
two-character ASCII labels not otherwise reserved pursuant to
Specification 5, Section 6 of the Registry Agreement, subject to these
measures.<br />
<a href="https://www.blogger.com/null" id="2.a.rationale" name="2.a.rationale"></a>
<h4>
<em>Rationale for Resolution 2016.11.08.15</em></h4>
<strong>Why the Board is addressing the issue?</strong><br />
On 16 October 2014, the Board adopted a resolution directing
staff to develop and implement an efficient procedure for the release of
two-character domains currently required to be reserved in the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement, taking into account the <abbr title="Governmental Advisory Committee">GAC</abbr>’s advice in the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-15oct14-en.pdf">Los Angeles Communiqué</a> on the matter.<br />
For nearly two and a half years, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> has been developing and implementing a procedure as directed by the Board. On 1 December 2014, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> launched the first phase of the procedure, an <a href="https://www.icann.org/resources/two-character-labels">Authorization Process for Release of Two-Character ASCII Labels</a>.
The finalization of this procedure is the implementation of a framework
containing standardized measures registry operators can implement to
avoid confusion, in accordance with the Registry Agreement, and allow
for the release of all letter/letter two-character ASCII labels
corresponding with country codes not otherwise reserved pursuant to
Specification 5, Section 6 of the Registry Agreement.<br />
The <abbr title="Governmental Advisory Committee">GAC</abbr> has issued advice on this topic in various communiqués over the past two years including, most recently, the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-30jun16-en.pdf">Helsinki Communiqué</a>. Per <a href="http://www.icann.org/en/about/governance/bylaws#XI">Article XI, Section 2.1 of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws</a>, the <abbr title="Governmental Advisory Committee">GAC</abbr>
may "put issues to the Board directly, either by way of comment or
prior advice, or by way of specifically recommending action or new
policy development or revision to existing policies." The <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws require the Board to take into account the <abbr title="Governmental Advisory Committee">GAC</abbr>'s advice on public policy matters in the formulation and adoption of the policies.<br />
<strong>What is the proposal being considered?</strong><br />
The proposal is to address requests from registry operators
to release reserved letter/letter two-character ASCII labels and the
advice from the <abbr title="Governmental Advisory Committee">GAC</abbr>
on reserved letter/letter labels. The Board is taking action to approve
the Measures for Letter/Letter Two-Character ASCII Labels to Avoid
Confusion with Corresponding Country Codes, as revised. By approving the
revised measures, the Board is authorizing <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> to issue a blanket authorization that allows new <abbr title="generic Top Level Domain">gTLD</abbr>
registry operators who implement the required measures to release all
reserved letter/letter two-character ASCII labels not otherwise reserved
pursuant to Specification 5, Section 6 of the New <abbr title="generic Top Level Domain">gTLD</abbr>
Registry Agreement. The current authorization process, whereby a
registry operator submits an individual request subject to 60-day
comment period and <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s review of comments, will be retired.<br />
<strong>Which stakeholders or others were consulted?</strong><br />
<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
initiated multiple public comment periods and consulted with various
stakeholders on this matter over a period of nearly two and a half
years.<br />
From June through September 2014, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
staff initiated five public comment forums to obtain feedback from the
community on the amendments that resulted from various RSEPs to
implement the proposed new registry service of releasing from
reservation two-character ASCII labels<sup><a href="https://www.icann.org/resources/board-material/resolutions-2016-11-08-en#foot1" id="note1" name="note1">1</a></sup> for 203 TLDs. Various members of the community submitted comments, including the At-Large <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="At-Large Advisory Committee">ALAC</abbr>), <abbr title="generic Top Level Domain">gTLD</abbr> registry operators, the Brand Registry Group (BRG), <abbr title="International Trademark Association">INTA</abbr> Internet Committee (<abbr title="International Trademark Association">INTA</abbr>), the Business Constituency (<abbr title="Business Constituency">BC</abbr>), the Intellectual Property Constituency (<abbr title="Intellectual Property Constituency">IPC</abbr>) and a registrar.<br />
Since 1 December 2014 at the launch of the <a href="https://www.icann.org/resources/two-character-labels">Authorization Process for Release from Two-Character ASCII Labels</a>,
all authorization requests for letter/letter two-character ACII labels
were subject to a comment period. Over 646 requests have been received
under this process.<br />
Throughout the nearly two and a half years, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> notified 1) the <abbr title="Governmental Advisory Committee">GAC</abbr>
for amendments posted from June through September 2014 and 2)
governments for requests under the Authorization Process since December
2014, when two-character requests from registry operators were posted
for comment. The <abbr title="Governmental Advisory Committee">GAC</abbr>
had not submitted comments under the Public Comment Periods for the
amendments to release two-character labels. Under the Authorization
Process, the <abbr title="Governmental Advisory Committee">GAC</abbr> had not submitted comments, but various individual governments submitted comments on requests.<br />
On 6 October 2015, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
corresponded with governments who previously submitted comments
requesting that clarification of their comments be provided via a new
comment form within 60 days; new comments were required to be submitted
via the new comment form.<br />
On 25 February 2016, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
corresponded with registry operators requesting they provide proposed
measures to avoid confusion with corresponding country codes in order to
respond to governments’ confusion concerns within 60 days.<br />
On 8 July 2016, taking into consideration the inputs from governments and registry operators, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> published for public comment the <a href="https://www.icann.org/en/system/files/files/proposed-measures-two-char-08jul16-en.pdf">Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes</a>,
which listed measures registry operators could adopt to avoid confusion
with corresponding country codes and which incorporated the <abbr title="Governmental Advisory Committee">GAC</abbr>’s advice issued in its <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-30jun16-en.pdf">Helsinki Communiqué</a>.
As part of the proposal, registry operators who adopt the measures
would be authorized to release all letter/letter two-character ASCII
labels not otherwise reserved in other sections of the Registry
Agreement, and the current process would be retired. Forty-three
comments were received, including comments from the <abbr title="Registries Stakeholder Group">RySG</abbr>, the BRG, the <abbr title="Intellectual Property Constituency">IPC</abbr>, the <abbr title="Non-Commercial Stakeholders Group">NCSG</abbr>, <abbr title="Latin American and Caribbean ccTLDs">LACTLD</abbr>, various governments, <abbr title="Country Code Top Level Domain">ccTLD</abbr> registry operators and <abbr title="generic Top Level Domain">gTLD</abbr> registry operators.<br />
<strong>What concerns or issues were raised by the community?</strong><br />
From the five public comment periods from 2014 on registry
agreement amendments that resulted from RSEPs, the majority of the
comments received were in favor of the release of two-character domain
names.<br />
The arguments made in favor of the release of the two-character domain names included:<br />
<ul>
<li>The introduction of two-character domain names would
increase competition since the current restrictions hinder competition,
in particular for the new gTLDs, which are competing with legacy TLDs
that are allowed to offer such registrations. The current restrictions
to the new <abbr title="generic Top Level Domain">gTLD</abbr> registry operators create a discriminatory situation, which is contrary to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws Article II, Section 3 that provide for Non-Discriminatory Treatment of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> stakeholders.</li>
<li>The introduction of two-character domain names poses a
limited risk of confusion, or no risk at all, as demonstrated by prior
use of two-character domain names in existing TLDs.</li>
<li>The release of two-character domain names would provide
opportunities for companies and brands to have tailored segmented domain
names to connect with the public as well as provide localized content,
thus expanding consumer choice and driving economic growth, in
particular in developing countries.</li>
<li>There is uniform precedent regarding the release of two-character domain names in the history of relevant <abbr title="Registry Services Evaluation Policy">RSEP</abbr> requests.</li>
<li>The release of country codes and names is allowed by the Applicant Guidebook. </li>
</ul>
The arguments made in opposition to the release of the
two-character domain names expressed two general concerns: the first
concern is related to the general recognition and associated use of the
two character domain names leading to user confusion or abuse; the
second concern is how to specifically protect ccTLDs when country and
territory names are newly formed.<br />
From the public comment forum for the <a href="https://www.icann.org/en/system/files/files/proposed-measures-two-char-08jul16-en.pdf">Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes</a>,
which established a standard set of registry operator requirements to
avoid confusion, comments indicated support for the release of
two-character labels reserved pursuant to Specification 5, Section 2 of
the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement overall, including comments of support from the <abbr title="Non-Commercial Stakeholders Group">NCSG</abbr>, <abbr title="Intellectual Property Constituency">IPC</abbr> and <abbr title="Registries Stakeholder Group">RySG</abbr>
among others. Comments noted that the Registry Agreement allows for two
paths by which registry operators may release two-character labels: one
path of agreement with the government and country-code manager, and a
second path of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> approval.<br />
There was moderate support for the Proposed Measures to the
extent the Proposed Measures allows for the release of two-character
labels, including comments of support from the <abbr title="Registries Stakeholder Group">RySG</abbr>
and BRG among others. Comments that seem to generally support the
Proposed Measures made specific suggestions about how the framework
could be improved, such as noting that two of the three proposed
measures (registration policy and post-registration investigation)
pertained to confusion and suggesting one measure (exclusive
availability pre-registration period) be made voluntary.<br />
Some commenters took the position that governments do not
have special rights to two-character labels that correspond with country
codes, and that the labels should be released as soon as possible.
Conversely, some governments and <abbr title="Country Code Top Level Domain">ccTLD</abbr>
operators commented with objections to the release of two-character
labels that correspond with country codes and took the position that
government and/or <abbr title="Country Code Top Level Domain">ccTLD</abbr> operator approval is required.<br />
Over the past two years, the <abbr title="Governmental Advisory Committee">GAC</abbr> has issued advice through various communiqués and formal correspondence to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>. Members of the <abbr title="Governmental Advisory Committee">GAC</abbr> have varying views on the topic. In the <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-15oct14-en.pdf">Los Angeles Communiqué</a> (15 October 2014), the <abbr title="Governmental Advisory Committee">GAC</abbr> stated, “The <abbr title="Governmental Advisory Committee">GAC</abbr>
recognized that two-character second level domain names are in wide use
across existing TLDs, and have not been the cause of any security,
stability, technical or competition concerns. The <abbr title="Governmental Advisory Committee">GAC</abbr> is not in a position to offer consensus advice on the use of two-character second level domains names in new <abbr title="generic Top Level Domain">gTLD</abbr> registry operations, including those combinations of letters that are also on the <abbr title="International Organization for Standardization">ISO</abbr> 3166-1 alpha 2 list.” In the <a href="https://gacweb.icann.org/download/attachments/27132037/20160630_GAC%20ICANN%2056%20Communique_FINAL%20%5B1%5D.pdf?version=1&modificationDate=1469016353728&api=v2">Helsinki Communiqué</a> (30 June 2016), the <abbr title="Governmental Advisory Committee">GAC</abbr>
stated, “Some countries and territories have stated they require no
notification for the release of their 2 letter codes for use at the
second level. The <abbr title="Governmental Advisory Committee">GAC</abbr>
considers that, in the event that no preference has been stated, a lack
of response should not be considered consent. Some other countries and
territories require that an applicant obtains explicit agreement of the
country/territory whose 2-letter code is to be used at the second
level.”<br />
The <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-11feb15-en.pdf">Singapore Communiqué</a> (11 February 2015) and <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-21oct15-en.pdf">Dublin Communiqué</a>
(21 October 2015) advised improvements to the process such as extending
the comment period from 30 days to 60 days and working with the <abbr title="Governmental Advisory Committee">GAC</abbr> Secretariat to address technical issues on the comment form. In both communiqués, the <abbr title="Governmental Advisory Committee">GAC</abbr> advised that comments from relevant governments should be fully considered. In its <a href="https://gacweb.icann.org/download/attachments/27132037/20160630_GAC%20ICANN%2056%20Communique_FINAL%20%5B1%5D.pdf?version=1&modificationDate=1469016353728&api=v2">Helsinki Communiqué</a>, the <abbr title="Governmental Advisory Committee">GAC</abbr> also advised the Board to “urge the relevant Registry or the Registrar to engage with the relevant <abbr title="Governmental Advisory Committee">GAC</abbr>
members when a risk is identified in order to come to an agreement on
how to manage it or to have a third-party assessment of the situation if
the name is already registered.”<br />
<strong>What significant materials did the Board review? What factors did the Board find to be significant?</strong><br />
The Board reviewed several materials and also considered
several significant factors during its deliberations about whether or
not to approve the request. The significant materials and factors that
the Board considered as part of its deliberations, included, but not
limited to the following:<br />
<ul>
<li>
<a href="https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm">Specification 5, Section 2 of the New <abbr title="generic Top Level Domain">gTLD</abbr> Registry Agreement</a> (updated 9 January 2014) </li>
<li>
<a href="https://www.icann.org/en/system/files/files/rstep-gnr-proposal-review-team-report-04dec06-en.pdf"><abbr title="Registry Services Technical Evaluation Panel">RSTEP</abbr> Report on the Proposal for the Limited Release of Initially Reserved Two-Character Names</a> (4 December 2006)</li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/crocker-to-dryden-2-02sep14-en.pdf">Correspondence from the Board to the <abbr title="Governmental Advisory Committee">GAC</abbr> regarding requests for release of two-character labels as second-level domains in New gTLDs</a> (2 September 2014)</li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/dryden-to-crocker-10sep14-en.pdf">Correspondence from the <abbr title="Governmental Advisory Committee">GAC</abbr> to the Board regarding requests for release of two-character labels as second-level domains in New gTLDs</a> (10 September 2014)</li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-15oct14-en.pdf"><abbr title="Governmental Advisory Committee">GAC</abbr> Los Angeles Communiqué</a> (15 October 2014)</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2014-10-16-en#2.b"><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board Resolution 2014.10.16.14: Introduction of Two-character Domain Names in the New <abbr title="generic Top Level Domain">gTLD</abbr> Namespace</a> (16 October 2014) </li>
<li>
<a href="https://www.icann.org/resources/two-character-labels">Authorization Process for Release of Two-Character ASCII Labels</a> (launched 1 December 2014, last updated 14 April 2016) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-11feb15-en.pdf"><abbr title="Governmental Advisory Committee">GAC</abbr> Singapore Communiqué</a> (11 February 2015)</li>
<li>
<a href="https://www.icann.org/resources/board-material/resolutions-2015-02-12-en#2.a"><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board Resolution 2015.02.12.2016: Release of Two-Letter Codes at the Second Level in gTLDs</a> (12 February 2015)</li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/rysg-to-atallah-13mar15-en.pdf">Correspondence from <abbr title="Registries Stakeholder Group">RySG</abbr>
to the President of the Global Domains Division regarding the treatment
of government comments on requests to release two-character ASCII
labels</a> (13 March 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/atallah-to-rysg-23mar15-en.pdf">Response from the President of the Global Domains Division to the <abbr title="Registries Stakeholder Group">RySG</abbr> regarding the treatment of government comments on requests to release two-character ASCII labels</a> (23 March 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/sutton-cooper-shatan-to-crocker-14apr15-en.pdf">Joint Correspondence from the BRG, the <abbr title="Business Constituency">BC</abbr> and the <abbr title="Intellectual Property Constituency">IPC</abbr> to the Board regarding the release of 2-letter labels and country names for Specification 13 registries</a> (14 April 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/atallah-to-sutton-et-al-15jun15-en.pdf">Response from the President of the Global Domains Division to the BRG, the <abbr title="Business Constituency">BC</abbr> and the <abbr title="Intellectual Property Constituency">IPC</abbr> regarding the release of 2-letter labels and country names for Specification 13 registries</a> (15 June 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/schneider-to-atallah-16jul15-en.pdf">Correspondence from <abbr title="Governmental Advisory Committee">GAC</abbr> to the President of the Global Domains Division regarding two-character codes as Second Level Domains</a> (16 July 2015)</li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/atallah-to-schneider-1-06aug15-en.pdf">Response from the President of the Global Domains Division to the <abbr title="Governmental Advisory Committee">GAC</abbr> regarding two-character codes as Second Level Domains</a> (6 August 2015)</li>
<li>
<a href="https://www.icann.org/resources/pages/two-character-comments-consideration-2015-10-06-en">Two-Character Letter/Letter Labels Comments Consideration Process</a> (launched 8 October 2015, last updated 25 February 2016) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-21oct15-en.pdf"><abbr title="Governmental Advisory Committee">GAC</abbr> Dublin Communiqué</a> (21 October 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/diaz-to-crocker-09nov15-en.pdf">Correspondence from <abbr title="Registries Stakeholder Group">RySG</abbr> to the Board regarding advice contained in the <abbr title="Governmental Advisory Committee">GAC</abbr>’s Dublin communiqué regarding the use of two-letter country codes</a> (9 November 2015) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/chalaby-to-diaz-30mar16-en.pdf">Response from the Board to the <abbr title="Registries Stakeholder Group">RySG</abbr> regarding advice contained in the <abbr title="Governmental Advisory Committee">GAC</abbr>’s Dublin communiqué regarding the use of two-letter country codes</a> (30 March 2016) </li>
<li>
<a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-30jun16-en.pdf"><abbr title="Governmental Advisory Committee">GAC</abbr> Helsinki Communiqué</a> (30 June 2016)</li>
<li>
<a href="https://www.icann.org/en/system/files/files/proposed-measures-two-char-08jul16-en.pdf">Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes</a> (8 July 2016) </li>
<li>
<a href="https://www.icann.org/en/system/files/files/report-comments-proposed-measures-two-char-ascii-23sep16-en.pdf">Public Comment Summary and Analysis Report on Proposed Measures</a> (23 September 2016) </li>
<li>Correspondence from the Secretariat General of the Cooperation Council for the Arab States of the Gulf to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> President and CEO regarding the proposed measures for letter/letter two-character ASCII labels (3 October 2016) </li>
<li>Correspondence from the Communication and Information Technology Regulatory Authority of Kuwait to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> President and CEO regarding the proposed measures for letter/letter two-character ASCII labels (12 October 2016) </li>
</ul>
<strong>Are there positive or negative community impacts? Are there fiscal impacts or ramifications on <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
(strategic plan, operating plan, budget); the community; and/or the
public? Are there any security, stability or resiliency issues relating
to the <abbr title="Domain Name System">DNS</abbr>?</strong><br />
The overall impact on the community is anticipated to be
positive as new opportunities for diversification, competition and
targeted content creation in the <abbr title="generic Top Level Domain">gTLD</abbr> namespace are created, while minimal risk of user confusion has been identified.<br />
It is not expected that there will be any significant fiscal impact on <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>.<br />
In December 2006, the Registry Services Technical Evaluation Panel (<abbr title="Registry Services Technical Evaluation Panel">RSTEP</abbr>) issued a <a href="https://www.icann.org/en/system/files/files/rstep-gnr-proposal-review-team-report-04dec06-en.pdf">report</a>
regarding the release of two-character labels and found that “taken in
the context of our overall understanding, none of the observations point
to the proposed release of two-character Second Level Domain having a
material security or stability impact on the Internet.” Additionally,
these names are not reserved in many legacy TLDs, which have not caused
apparent security, stability or resiliency issues in relation to the <abbr title="Domain Name System">DNS</abbr>.<br />
It is expected that the release of these names in new gTLDs will not cause security, stability or resiliency issues.<br />
<strong>Is this either a defined policy process within <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s <abbr title="Supporting Organizations">Supporting Organizations</abbr> or <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s Organizational Administrative Function decision requiring public comment or not requiring public comment?</strong><br />
This is an Organizational Administrative Function for which public comments were received.<br />
</li>
<a href="https://www.blogger.com/null" id="2.b" name="2.b"></a>
<li>
<h4>
Consideration of the <em>Corn Lake, LLC v. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr></em> Independent Review Process Final Declaration</h4>
Whereas, on 19 October 2016, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> received the Independent Review Process (IRP) Final Declaration in the IRP filed by Corn Lake, LLC (Corn Lake) against <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> (Final Declaration).<br />
Whereas, the IRP Panel declared that: (i) Corn Lake’s
challenges to the determination rendered by an expert panelist
sustaining the Independent Objector’s (IO’s) Community Objection against
Corn Lake’s application for .CHARITY (Expert Determination) and the
Board Governance Committee’s (BGC’s) denial of Corn Lake’s
Reconsideration Request 14-3 challenging the Expert Determination were
time-barred; (ii) “the Board acted without conflict [of interest]”; and
(iii) “the Board members exercised independent judgment, believed to be
in the best interests of the community.” (See Final Declaration, ¶¶
7.14, 8.70, 8.74, <a href="https://www.icann.org/en/system/files/files/irp-corn-lake-final-declaration-17oct16-en.pdf">https://www.icann.org/en/system/files/files/irp-corn-lake-final-declaration-17oct16-en.pdf</a>.)<br />
Whereas, the Panel further declared that “the [Board] action
of omitting .CHARITY from the [the review mechanism to address perceived
inconsistent or unreasonable string confusion objection determinations
(Final Review Procedure)] was inconsistent with the Articles of
Incorporation and Bylaws.” (Final Declaration at ¶ 11.1(b).)<br />
Whereas, the Panel further declared that “Claimant, Corn
Lake, is the prevailing party” and that “no costs shall be allocated to
the prevailing party.” (Final Declaration at ¶¶ 11.1(a), (e).)<br />
Whereas, the Panel recommended that: (1) “the Board extend
the [Final Review Procedure] to include review of Corn Lake’s .CHARITY
Expert Determination”; and (2) “the Board continue to stay any action or
decision in relation to [Spring Registry Limited’s] .CHARITY
application until such time as the Board reviews and acts upon the
opinion of the IRP Panel.” (Final Declaration at ¶¶ 11.1(c)-(d).)<br />
Whereas, in accordance with Article IV, section 3.21 of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s Bylaws, the Board has considered the Final Declaration.<br />
Resolved (2016.11.08.16), the Board accepts the following
findings of the Final Declaration: (i) Corn Lake is the prevailing
party in the Corn Lake, LLC v. <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
IRP; (ii) Corn Lake’s challenges to the Expert Determination and the
BGC’s denial of Corn Lake’s Reconsideration Request 14-3 were
time-barred; (iii) the Board acted without conflict of interest; (iv)
“the Board members exercised independent judgment, believed to be in the
best interests of the community”; (v) “the [Board] action of omitting
.CHARITY from the [Final Review Procedure] was inconsistent with the
Articles of Incorporation and Bylaws”; and (vi) the parties shall each
bear their own costs.<br />
Resolved (2016.11.08.17), the Board directs the President and
CEO, or his designee(s), to take all steps necessary to implement the
Panel’s recommendation that “the Board extend the [Final Review
Procedure] to include review of Corn Lake’s .CHARITY Expert
Determination.”<br />
Resolved (2016.11.08.18), the Board directs the President and
CEO, or his designee(s), to refrain from taking any further action or
decision in relation to Spring Registry Limited’s .CHARITY application
until after the results of the Final Review Procedure are known, and
then to proceed pursuant to established processes with the processing of
both Corn Lake’s and Spring Registry Limited’s applications in
accordance with the results of Final Review Procedure.<br />
<a href="https://www.blogger.com/null" id="2.b.rationale" name="2.b.rationale"></a>
<h4>
<em>Rationale for Resolutions 2016.11.08.16 – 2016.11.08.18</em></h4>
Corn Lake, LLC (Corn Lake) initiated Independent Review
Process (IRP) proceedings challenging: (1) the determination rendered
by an expert panelist sustaining the Independent Objector’s (IO’s)
community objection against Corn Lake’s application for .CHARITY (Expert
Determination); (2) the Board Governance Committee’s (BGC’s) denial of
Corn Lake’s Reconsideration Request 14-3 challenging the Expert
Determination; and (3) the Board’s decision to not include the Expert
Determination in the review mechanism to address perceived inconsistent
or unreasonable string confusion objection determinations (Final Review
Procedure).<br />
Corn Lake applied to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> for the opportunity to operate the .CHARITY new <abbr title="generic Top Level Domain">gTLD</abbr>.
Spring Registry Limited (“SRL”) also submitted an application for
.CHARITY, and Excellent First Limited (Excellent First) submitted an
application for .慈善 (the Chinese translation of “charity”). <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s
Independent Objector (IO) filed Community Objections against the two
.CHARITY applications, as well as the application for .慈善, meaning
charity. The IO was concerned that, among other things, the lack of any
policy restricting registrations in these gTLDs to charitable or
not-for-profit organizations created a likelihood of detriment to the
rights or legitimate interests of the charity community, to users, and
to the general public. (See IO’s Community Objection at Para. 46, pgs.
16-17, <a href="http://www.independent-objector-newgtlds.org/home/the-independent-objector-s-objections/charity-cty-corn-lake-llc/">http://www.independent-objector-newgtlds.org/home/the-independent-objector-s-objections/charity-cty-corn-lake-llc/</a>).<br />
The International Centre for Expertise of the International Chamber of Commerce (<abbr title="International Chamber of Commerce">ICC</abbr>)
expert panel evaluating the IO’s Community Objection to Corn Lake’s
application rendered a determination (Expert Determination) in favor of
the IO, finding that, because Corn Lake’s .CHARITY application did not
include registration restrictions to charitable organizations, “there is
a likelihood of material detriment to the charity sector community were
the Application to proceed.” The same <abbr title="International Chamber of Commerce">ICC</abbr>
expert panel also evaluated the IO’s Community Objections to SRL’s
application and Excellent First’s application, rendering determinations
in favor of SRL and Excellent First Limited. Specifically, the expert
panel found that SRL’s and Excellent First’s commitments set out in
their applications to restrict registrations in the applied-for string
to charitable organizations was sufficient to negate any concern of
material detriment to the targeted community.<br />
On 24 January 2014, Corn Lake filed Reconsideration Request
14-3 (Request 14-3) seeking reversal of the Expert Determination. On 27
February 2014, the Board Governance Committee (BGC) denied Request
14-3, finding no evidence that the expert panel violated any process or
policy in reaching its determination.<br />
Separately, in April 2013, the Governmental <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Governmental Advisory Committee">GAC</abbr>)
recommended in the Beijing Communiqué that the Board adopt eligibility
restrictions for “sensitive strings,” including .CHARITY. (See Beijing
Communiqué at <a href="https://www.icann.org/en/system/files/correspondence/gac-to-board-11apr13-en.pdf">https://www.icann.org/en/system/files/correspondence/gac-to-board-11apr13-en.pdf</a>.) The New <abbr title="generic Top Level Domain">gTLD</abbr> Program Committee (NGPC) adopted the <abbr title="Governmental Advisory Committee">GAC</abbr>’s recommendation by a 5 February 2014 resolution (see <a href="https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-02-05-en">https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-02-05-en</a>), which, according to the Panel, effectively required that whichever applicant ultimately operated the .CHARITY <abbr title="generic Top Level Domain">gTLD</abbr>
would need to restrict registrations to charitable organizations. Also
at that 5 February 2014 meeting, the NGPC adopted a resolution that
authorized the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
President and CEO to initiate a public comment period with respect to a
proposed review mechanism to address perceived inconsistent string
confusion objection determinations (Final Review Procedure). At its
creation, the Final Review Procedure was limited to the review of
certain string confusion expert determinations for .CAR/.CARS,
.CAM/.COM, and .SHOP/.ONLINESHOPPING (in Japanese characters). In March
2014, via the public comment process, Corn Lake’s parent company
(Donuts, Inc.) asked the Board to extend the Final Review Procedure to
perceived inconsistent determinations of community objection, such as
that concerning .CHARITY. The Board did not do so when the procedure
was implemented in a 12 October 2014 Board resolution (“12 October 2014
Resolution”). (See <a href="https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-10-12-en">https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-10-12-en</a>.)<br />
Corn Lake’s IRP Request, submitted on 24 March 2015, sought a declaration that the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board’s decision not to include the .CHARITY determination in the 12 October 2014 Resolution violates <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s Articles and Bylaws, and also asked the Panel to review the Expert Determination and the BGC’s denial of Request 14-3.<br />
On 17 October 2016, the three-member IRP Panel (Panel) issued
its Final Declaration, which was circulated to the parties on 19
October 2016. After consideration and discussion, pursuant to Article
IV, Section 3.21 of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws, the Board adopts the findings of the Panel, which are summarized below, and can be found in full at <a href="https://www.icann.org/en/system/files/files/irp-corn-lake-final-declaration-17oct16-en.pdf">https://www.icann.org/en/system/files/files/irp-corn-lake-final-declaration-17oct16-en.pdf</a>.<br />
The Panel held that the IRP request was denied in part and
granted in part, and determined Corn Lake to be the prevailing party.
(Final Declaration at ¶¶ 7.14, 8.96, 11.1(a).) As a threshold issue,
the Panel declared that Corn Lake’s challenges to the Expert
Determination and the BGC’s denial of Request 14-3 were “out of time”
and therefore time-barred from consideration in this IRP. (Final
Declaration at ¶¶ 7.14, 8.34.)<br />
The Panel also declared that: (i) with respect to setting filing deadlines, “<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
is entitled and indeed required to establish reasonable procedural
rules in its Bylaws, including in respect of filing deadline, in order
to provide for orderly management of its review processes” (id. at ¶
7.9); (ii) “it is now well established that: ‘…the IRP Panel is charged
with ‘objectively’ determining whether or not the Board’s actions are in
fact consistent with the Articles, Bylaws and Guidebook, which the
Panel understands as requiring that the Board’s conduct be appraised
independently, and without any presumption of correctness’” (id. at ¶
8.18); (iii) “[t]here is no suggestion that the Board had a conflict of
interest, and the IRP Panel finds that the Board acted without
conflict.” (id. at ¶ 8.70); and (iv) “[t]here is no indication that the
Board members were acting in any way other than in good faith and
exercising independent judgment, with the subjective belief that they
were acting in the best interests of the community. The IRP Panel finds
that the Board members exercised independent judgment, believed to be
in the best interests of the community” (id. at ¶ 8.74). The Panel
further stated: “[t]his IRP Panel does not suggest that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
lacks discretion to make decisions regarding its review processes as
set out in the Applicant Guidebook, which may well require it to draw
nuanced distinctions between different applications or categories of
applications. Its ability to do so must be preserved as being in the
best interest of the Internet community as a whole.” (Id. at ¶ 8.98).<br />
The Panel stated that “[t]he sole issue before this Panel is
whether the Board properly or improperly excluded the .Charity Expert
Determinations from the [Final Review Procedure] in the first place.”
(Final Declaration at ¶ 8.97, fn. 246.) In considering this issue, the
Panel noted that the Expert Determination was largely based on the fact
that Corn Lake’s application originally had not made clear that it would
restrict registrations to charitable organizations. The Panel felt
that the NGPC’s acceptance of the Beijing Communiqué created a “leveling
effect,” effectively requiring that whichever .CHARITY applicant
prevailed, it would be required to implement restricted registration
policies. The Panel noted: “We make no finding that the Board’s
failure to consider the impact of its adoption of the Beijing Communiqué
recommendations was malicious or intentional. We find simply that the
leveling effect on the eligibility requirements in the pending
applications of the new PIC requirement was a material fact that should
have been considered, and apparently it was not.” (Final Declaration at
¶ 8.73.) The Panel therefore declared that that “the action of
omitting .CHARITY from the [Final Review Procedure] was inconsistent
with the Articles of Incorporation and Bylaws.” (Final Declaration at ¶
11.1(b).) The Panel noted that its finding “is further supported by
the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
Board’s [later] decision to include the .HOSPITAL Expert Determinations
[in the Final Review Procedure], despite those Determinations appearing
to have been less clearly within the criteria tha[n] the .CHARITY
Determinations.” (Final Declaration at ¶ 8.101.) The Panel further
noted that “this is a unique situation and peculiar to its own unique
and unprecedented facts[; and t]his unique set of circumstances created
what was doubtless a difficult situation for <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> to consider in establishing the scope of the new review process[.]” (Final Declaration at ¶ 8.97.)<br />
The Panel further declared that “these IRP proceedings
involve extraordinary circumstances,” and therefore “no costs shall be
allocated to the Claimant as the prevailing party,” “each Party shall
bear its own costs in respect of this IRP Panel proceeding.” (Final
Declaration at ¶¶ 9.3-9.5.)<br />
In addition, the Panel recommended that: (1) “the Board
extend the [Final Review Procedure] to include review of Corn Lake’s
.CHARITY Expert Determination”; and (2) “the Board continue to stay any
action or decision in relation to [Spring Registry’s] .CHARITY
application until such time as the Board reviews and acts upon the
opinion of the IRP Panel.” (Final Declaration at ¶¶ 11.1(c)-(d).)
Subsequent to the issuance of the Final Declaration, the Board received a
letter on 28 October 2016 (dated 27 October) from Corn Lake’s counsel
“urg[ing] the Board to reinstate its .CHARITY application without”
“[g]oing through the motions of such review[, which] will cost money to <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
and Corn Lake, and unnecessary time for all .CHARITY applicants.” Corn
Lake requests that the Board “reinstat[e] Corn Lake’s .CHARITY
application and allow[] it to compete for the domain without going
through the additional time and expense [of the Final Review
Procedure].” (See <a href="https://www.icann.org/en/system/files/correspondence/genga-to-icann-board-27oct16-en.pdf">https://www.icann.org/en/system/files/correspondence/genga-to-icann-board-27oct16-en.pdf</a>.)
The Board had the opportunity to review Corn Lake’s correspondence and
has taken it into consideration in reaching its Resolution regarding the
Panel’s recommendation.<br />
As required, the Board has considered the Final Declaration.
As this Board has previously indicated, the Board takes very seriously
the results of one of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>’s
long-standing accountability mechanisms. Accordingly, and for the
reasons set forth in this Resolution and Rationale, the Board has
accepted the Panel’s Final Declaration as indicated above.<br />
Adopting the Panel’s Final Declaration and implementing the
Panel’s recommendation will have a direct financial impact on the
organization, but that impact will not impact the underlying budget for
FY17. Adopting the Panel’s Final Declaration will not have any direct
impact on the security, stability or resiliency of the domain name
system.<br />
This is an Organizational Administrative function that does not require public comment.<br />
</li>
<a href="https://www.blogger.com/null" id="2.c" name="2.c"></a>
<li>
<h4>
Thank You to the Global Multistakeholder Community</h4>
Whereas, on 14 March 2014, the National Telecommunications and Information Administration (<abbr title="US National Telecommunications and Information Agency">NTIA</abbr>) of the United States Department of Commerce announced its intention to transition the stewardship of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions to the global multistakeholder community.<br />
Whereas, <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> asked <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> to convene global stakeholders to develop a proposal to transition the current role, played by <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>, in the coordination of the Internet's domain name system (<abbr title="Domain Name System">DNS</abbr>). <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> required that the proposal for transition must have broad community support and uphold the following principles:<br />
<ul>
<li>Support and enhance the multistakeholder model;</li>
<li>Maintain the security, stability, and resiliency of the Internet <abbr title="Domain Name System">DNS</abbr>;</li>
<li>Meet the needs and expectation of the global customers and partners of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> services; and,</li>
<li>Maintain the openness of the Internet.</li>
</ul>
<abbr title="US National Telecommunications and Information Agency">NTIA</abbr> also stated it would not accept a proposal that replaces the <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> role with a government-led or an inter-governmental organization solution.<br />
Whereas, in the Board resolutions 2016.03.10.12-15 the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board resolved to accept the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Transition Coordination Group’s (<abbr title="IANA Stewardship Transition Coordination Group">ICG</abbr>) <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Transition Proposal, reflecting he proposals developed by CRISP, <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Plan and the CWG-Stewardship, and approve the transmittal of the Proposal to <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> of the United States Department of Commerce in response to <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>'s 14 March 2014 announcement.<br />
Whereas, the Board further resolved that the President and
CEO, or his designee, was directed to plan for the implementation of the
Proposal so that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is operationally ready to implement in the event <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> approves of the Proposal and the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions Contract expires.<br />
Whereas, in its Board resolutions 2016.03.10.16-19, the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board resolved to accept the Cross Community Working Group on Enhancing <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Accountability (CCWG-Accountability) Work Stream 1 Report ("Report"), and approve the transmittal of the Report to <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> to accompany the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Transition Proposal developed by the <abbr title="IANA Stewardship Transition Coordination Group">ICG</abbr>.<br />
Whereas, the Board further resolved that the President and
CEO, or his designee, is directed to plan for the implementation of the
Report so that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is operationally ready to implement in the event <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> approves of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Transition Proposal and the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions Contract expires.<br />
Whereas, on 27 May, the Board adopted resolution <em>2016.05.27.01-04, resolving that the </em><a href="https://www.icann.org/en/system/files/files/adopted-bylaws-27may16-en.pdf">New <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Bylaws</a> will be deemed effective upon the expiration the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions Contract between <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> and <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>, and directed the President and CEO, or his designee, to plan for the implementation of the Bylaws so that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> is operationally ready to meet its obligations in the event <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> approves of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Transition Proposal and the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions Contract expires.<br />
Whereas, on 9 June <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> <a href="https://www.icann.org/en/system/files/correspondence/strickling-to-crocker-09jun16-en.pdf">informed</a> <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> that <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> had completed its review of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Stewardship Proposal along with the other US agencies, and determined that the proposal meets the criteria set out by <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> in March 2014 when it announced its intent to transition <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>”s stewardship of key Internet domain name functions to the global multistakeholder community. <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> noted and outlined in their report that there was still some work to be done before the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> functions stewardship transition could occur, and requested that <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> provide <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> with an implementation planning status report by August 12, 2016.<br />
Whereas, on 12 August, <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> provided <abbr title="US National Telecommunications and Information Agency">NTIA</abbr> with the <a href="https://www.icann.org/en/system/files/correspondence/marby-to-strickling-12aug16-en.pdf">implementation planning status report</a> noting that: “<abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>, working with the multistakeholder community, confirms that all required <abbr title="Internet Assigned Numbers Authority">IANA</abbr> functions stewardship transition tasks specified in <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>’s June 9, 2016 letter are complete, and all other tasks in support of the <abbr title="Internet Assigned Numbers Authority">IANA</abbr>
stewardship transition are either in a final review stage or
awaiting approval, which will be complete in advance of September
30, 2016 to allow the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> functions contract to expire.”<br />
Whereas, on 1 October, the <a href="https://www.ntia.doc.gov/press-release/2016/statement-assistant-secretary-strickling-iana-functions-contract"><abbr title="US National Telecommunications and Information Agency">NTIA</abbr> advised <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr></a> and the global multistakeholder community that the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions contract had expired.<br />
Resolved (2016.11.08.19), the Board expresses its deep
appreciation for the tireless efforts of the global multistakeholder
community, including the leadership of the various community-led groups
contributing to the Proposals. The development of the coordinated
Proposals across the global community, that met the criteria set out
by <abbr title="US National Telecommunications and Information Agency">NTIA</abbr>,
and the work to achieve implementation to allow for the contract to
lapse on 30 September 2016, is unprecedented and serves as an
historical record of the success of the work of the community to
achieve a longstanding goal.<br />
Resolved (2016.11.08.20), the Board expresses its deep
appreciation to the US Department of Commerce, for standing by the
long-standing commitment to end the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Functions contract, and for its dedication, and tireless efforts as a partner with <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> and the community to achieving this historic goal.<br />
</li>
<a href="https://www.blogger.com/null" id="2.d" name="2.d"></a>
<li>
<h4>
Thank You to Bruno Lanvin for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h4>
Whereas, Bruno Lanvin was appointed by the Nominating Committee to serve as a member of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 21 November 2013.<br />
Whereas, Bruno Lanvin concluded his term on the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 8 November 2016.<br />
Whereas, Bruno served as a member of the following Committees:<br />
<ul>
<li>Audit Committee</li>
<li>Finance Committee</li>
<li>New <abbr title="generic Top Level Domain">gTLD</abbr> Program Committee</li>
<li>Organizational Effectiveness Committee [formerly the Structural Improvements Committee]</li>
</ul>
Resolved (2016.11.08.21), Bruno Lanvin has earned the deep
appreciation of the Board for his term of service, and the Board wishes
him well in his future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
<a href="https://www.blogger.com/null" id="2.e" name="2.e"></a>
<li>
<h4>
Thank You to Erika Mann for her service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h4>
Whereas, Erika Mann was appointed to serve by the Nominating Committee as a member of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 10 December 2010.<br />
Whereas, Erika concludes her term on the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 8 November 2016.<br />
Whereas, Erika has served as a member of the following Committees and Working Groups:<br />
<ul>
<li>Audit Committee</li>
<li>Compensation Committee</li>
<li>Global Relationships Committee</li>
<li>Governance Committee</li>
<li>New <abbr title="generic Top Level Domain">gTLD</abbr> Program Committee</li>
<li>Board-<abbr title="Governmental Advisory Committee">GAC</abbr> Recommendation Implementation Working Group</li>
<li>Board Working Group on Internet Governance (BWG-IG)</li>
<li>Board Working Group on Registration Data Directory Services (BWG-RDS)</li>
<li><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board Liaison to the Charter Drafting Team for the Cross Community Working Group on New <abbr title="generic Top Level Domain">gTLD</abbr> Auction Proceeds</li>
</ul>
Resolved (2016.11.08.22), Erika Mann has earned the deep
appreciation of the Board for her term of service, and the Board wishes
her well in her future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
<a href="https://www.blogger.com/null" id="2.f" name="2.f"></a>
<li>
<h4>
Thank You to Kuo-Wei Wu for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h4>
Whereas, Kuo-Wei Wu was appointed by the Address <abbr title="Supporting Organization">Supporting Organization</abbr> (AS0) to serve as a member of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 22 April 2010.<br />
Whereas, Kuo-Wei concluded his term on the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 8 November 2016.<br />
Whereas, Kuo-Wei served as a member of the following <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board Committees and Working Groups:<br />
<ul>
<li>Global Relationships Committee</li>
<li><abbr title="Internet Assigned Numbers Authority">IANA</abbr> Committee</li>
<li>New <abbr title="generic Top Level Domain">gTLD</abbr> Program Committee</li>
<li>Organizational Effectiveness Committee [formerly the Structural Improvements Committee]</li>
<li>Public Participation Committee</li>
<li>Risk Committee </li>
<li>IDN Variants Working Group</li>
</ul>
Resolved (2016.11.08.23), Kuo-Wei Wu has earned the deep
appreciation of the Board for his term of service, and the Board wishes
him well in his future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
<a href="https://www.blogger.com/null" id="2.g" name="2.g"></a>
<li>
<h4>
Thank You to Suzanne Woolf for her service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h4>
Whereas, Suzanne Woolf was appointed to serve by the Root Server System <abbr title="Advisory Committee">Advisory Committee</abbr> (<abbr title="Root Server System Advisory Committee">RSSAC</abbr>) as a member of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 5 December 2004.<br />
Whereas, Suzanne concludes her term on the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 8 November 2016.<br />
Whereas, Suzanne has served as a member of the following Committees and Working Groups:<br />
<ul>
<li>Governance Committee</li>
<li>Risk Committee</li>
<li><abbr title="Internet Assigned Numbers Authority">IANA</abbr> Committee </li>
<li>IDN Variants Working Group</li>
</ul>
Resolved (2016.11.08.24), Suzanne Woolf has earned the deep
appreciation of the Board for her term of service, and the Board wishes
her well in her future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
<a href="https://www.blogger.com/null" id="2.h" name="2.h"></a>
<li>
<h4>
Thank You to Bruce Tonkin for his service to the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board</h4>
Whereas, Bruce Tonkin was appointed by the Generic Names <abbr title="Supporting Organization">Supporting Organization</abbr> (<abbr title="Generic Names Supporting Organization">GNSO</abbr>) to serve as a member of the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 29 June 2007.<br />
Whereas, Bruce Tonkin concluded his term on the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board on 8 November 2016.<br />
Whereas, Bruce served as a member of the following Committees:<br />
<ul>
<li>Governance Committee</li>
<li>Compensation Committee</li>
<li>Executive Committee</li>
<li>Risk Committee</li>
<li>Board Working Group on Registration Data Directory Services (BWG-RDS)</li>
<li><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Board Liaison to the Cross Community Working Group (CCWG) on Enhancing <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> Accountability</li>
</ul>
Resolved (2016.11.08.25), Bruce Tonkin has earned the deep
appreciation of the Board for his term of service, and the Board wishes
him well in his future endeavors within the <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> community and beyond.<br />
</li>
</ol>
</li>
</ol>
Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-3940726179763962501.post-23728414395380191572016-09-14T13:29:00.003-07:002016-09-14T13:29:15.431-07:00<br />
<header class="post-header">
<h1 class="entry-title">
La esencia de los dominios .tel</h1>
</header><br /><div style="text-align: justify;">
Todos cuantos hemos sido
contemporáneos del nacimiento de los dominios .tel, debemos recordar dos
aspectos muy sencillos y básicos: Que éstos iban a diferenciarse de los
dominios .mobi en el aspecto de que deberían servir para
mostrar/representar informaciones de contacto, y que dichos datos de
contacto deberían almacenarse en los DNS. La compatibilidad para los
dispositivos móviles (ojo, y no sólo para éstos, sino para todo tipo de
dispositivos comunicacionales ;-)) es un complemento natural, armónico,
para esas mencionadas propiedades.</div>
<div style="text-align: justify;">
La carga de datos desde los DNS, para
quienes se pusiesen a reflexionar sobre sus implicaciones y sus
posibilidades, representaba (representa) uno de sus aspectos más
interesantes y emocionantes. No sólo hace a los sitios webs
independientes de un hosting, tanto para su configuración como para su
mantenimiento en línea, sino que además favorece una inmejorable
velocidad de carga, en una red global cada vez más compleja (y en honor a
las tecnologías de punta, pasamos de decir, congestionada).</div>
<div style="text-align: justify;">
La comprobación de la velocidad de carga
de las informaciones consignadas en dominios .tel, la hicimos al
manejar un amplio directorio durante más de cuatro años, y la obtuvimos
directamente de los clientes anunciantes, y de los usuarios navegantes
de la red, sin siquiera preguntarlo. De cientos y miles de clientes no
obtuvimos sino satisfacción y reconocimiento.</div>
<div style="text-align: justify;">
Los dominios .tel para la conformación de directorios de contacto, son una opción de éxito.</div>
<div style="text-align: justify;">
No falta quienes digan que el
almacenamiento de datos en los DNS se ha vuelto poco útil en el momento
presente, mas es poco probable que pueda sostenerse tal afirmación. Por
el contrario: En cualquier caso, son un recurso básico de todo sitio
web.</div>
<div style="text-align: justify;">
Lo que sucede con el almacenamiento de
datos en los DNS, no es que se haya quedado como algo obsoleto y
primitivo (junto con los dominios .tel), sino que sus inmensas
posibilidades no se han mostrado… quienes tienen la sartén por el mango,
no han querido sacarlas a la luz…</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-82084207481730250552016-09-14T13:28:00.003-07:002016-09-14T13:28:53.241-07:00<br />
<header class="post-header">
<h1 class="entry-title">
¿Cómo deberían funcionar los dominios .tel?</h1>
<div class="meta post-meta">
Posted on <span class="updated">25/08/2016</span> por <span class="vcard author"><span class="fn"><a href="http://www.blogdominios.com/author/londres/" rel="author" title="Entradas de Domain Report">Domain Report</a></span></span> en <a href="http://www.blogdominios.com/category/gtlds/" rel="category tag">gTLD's</a> // 0 Comentarios</div>
</header>
<br />
<div class="post-thumbnail">
<img alt="" src="https://www.blogdominios.com/wp-content/uploads/2016/08/login-tel-620x264.png" title="login-tel" />
</div>
<div style="text-align: justify;">
Después de un largo y casi
ininterrumpido período de silencio, comienza a moverse de nuevo en los
medios relacionados con dominios, el tema de los dominios .tel. Todo a
la luz del proceso de renovación del convenio entre la ICANN y Telnic,
entidad a la que corresponde el manejo de esta extensión en el presente,
y hasta el mes de Marzo del 2017.</div>
<div style="text-align: justify;">
El tema es del interés no sólo para el
domainer puro y duro, sino en especial para un puñado de emprendedores,
de diversos perfiles, interesados en la utilización de los .tel y su
especialísima configuración, para la conformación de directorios.
Directorios con palabras claves orientadas geográficamente, directorios
que definen áreas más o menos extensas o nichos del mundo laboral, de
los negocios. Dirigidos a funcionar como páginas amarillas de internet.</div>
<div style="text-align: justify;">
En la siguiente URL, pueden leerse (en
inglés) los comentarios de participantes que la ICANN ha dispuesto al
efecto de este evento contractual:</div>
<div style="text-align: justify;">
http://forum.icann.org/lists/comments-tel-renewal-04aug16/index.html#00000</div>
<div style="text-align: justify;">
El concepto de almacenamiento,
distribución y presentación de datos en los dominios .tel, es
comprendido por pocos, desestimado por muchos e ignorado por casi todos.
Quizás no corresponda, al menos hoy, ahondar en su sentido profundo.</div>
<div style="text-align: justify;">
Podría decirse, sin embargo, y
utilizando un estilo críptico, que la clave del sentido de los dominios
.tel se puede encontrar en estas dos palabras: síntesis y sinergia. Todo
ello, por cierto, en relación muy estrecha con lo que últimamente
llamamos “el internet de las cosas”, y con el concepto de comunicación
en todas sus facetas.</div>
<div style="text-align: justify;">
En este contexto, no falta quien diga
que la extensión de dominio que nos ocupa, debería “beneficiarse” de la
posibilidad de funcionar como “el resto de los TLDs”, lo que le daría
una supuesta vitalidad en el mercado.</div>
<div style="text-align: justify;">
Sin embargo, cambiar su actual sistema
de configuración y funcionamiento, por algo que es común al resto de las
innumerables extensiones de dominios disponibles en la actualidad,
colocaría a los singulares dominios .tel en un nivel común y con un
perfil bajo o mediano. En tal caso, ventas se generarían de forma
moderada, quizás durante un largo tiempo, sin que estos dominios
llegasen a representar un suceso notable (tanto en el mundo del usuario
final como en el mundo de la compra-venta de dominios), es decir, la
condena a no ser relevantes jamás.</div>
<div style="text-align: justify;">
La posibilidad de que un .tel pueda ser
usado como un dominio “normal”, de manera opcional por parte del
cliente, resulta mucho más razonable, y mantener el concepto inicial de
almacenamiento y articulación de las informaciones consignadas en cada
dominio, sí que sería positivo, y multiplicaría sus posibilidades de
acción y de inversión.</div>
<div style="text-align: justify;">
¿Deseas compartir tu opinión con nosotros?</div>
<div style="text-align: justify;">
¿Qué piensas tú, Cómo crees que deberían funcionar los dominios .tel?</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-29176047205547505682015-11-23T06:03:00.001-08:002015-11-23T06:03:30.519-08:00telchina.orgThe website telchina.org got a redesign and a new template for .tel domains:<br /><br />telchina.orgUnknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-20070108713744743002015-09-14T06:55:00.001-07:002015-09-14T06:55:23.601-07:00Telmail<div class="author">
<br /></div>
<div class="post-entry">
<div>
<img alt="" height="564" src="http://i21.servimg.com/u/f21/18/85/77/90/telmai10.jpg" width="640" /><br /><img alt="" height="484" src="http://i21.servimg.com/u/f21/18/85/77/90/telmai14.jpg" width="640" /><br /><br /><img alt="" height="546" src="http://i21.servimg.com/u/f21/18/85/77/90/telmai12.jpg" width="640" /><br /><img alt="" height="266" src="http://i21.servimg.com/u/f21/18/85/77/90/telmai13.jpg" width="640" /></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-13543541174097792612015-07-22T10:29:00.000-07:002015-07-22T10:29:08.204-07:00Internet de las cosas y los dominios .tel<div style="border: 0; margin-top: 0;">
The IOT opens new possibilities for .TEL. For instance, we've partnered with the <a href="http://www.thewirelessregistry.com/" rel="nofollow" style="color: #006699; font-weight: bold; text-decoration: none;" target="_blank">www.TheWirelessRegistry.com</a> to promote a free wireless profile for each .TEL site, eg<br /><a href="http://www.thewirelessregistry.com/tel%7Emark" rel="nofollow" style="color: #006699; font-weight: bold; text-decoration: none;" target="_blank">www.thewirelessregistry.com/<wbr></wbr>tel~mark</a> and <a href="http://www.ubi.me/tel%7Emark" rel="nofollow" style="color: #006699; font-weight: bold; text-decoration: none;" target="_blank">www.ubi.me/tel~mark</a> (both in BETA)</div>
<div style="border: 0; margin-top: 0;">
Eddystone, Google Nearby and physical
web beacons are another way TELNIC can partner to provide instant mobile
solutions for advertisers in the wireless (IOT) space.</div>
<div style="border: 0; margin-top: 0;">
But as you say, we need to have control over templates to some extent. With <a href="http://ubi.me/" target="_blank">ubi.me</a>
(UbiNames) we plan to introduce a whole suit of contextually-sensitive
templates later this year that can tie in wireless (IOT) signal content
nicely with .TEL content. That way <a href="http://ubi.me/" rel="nofollow" style="color: #006699; font-weight: bold; text-decoration: none;" target="_blank">UbiNames</a> owners can control the look and feel of disseminated content, lessons learned from Telnic. </div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-82608644158589147012015-05-29T04:26:00.001-07:002015-05-29T04:26:03.074-07:00Telnic Partners With NeuStar for New .TEL Domain <h1 id="h1Headline">
</h1>
<div class="newsreldettrans width894px">
<br /></div>
<a href="https://www.blogger.com/null" name="linktopagetop"></a>
<div class="featured">
</div>
LONDON and STERLING, Virginia, January 29 /PRNewswire/ --
<br />
Telnic Limited, the UK-based operator of the .TEL top-level domain (TLD),
announced today that it has selected NeuStar, Inc. (NYSE: NSR), a provider of
essential clearinghouse and directory services to the global communications
and Internet industry, to operate the domain name registry and DNS resolution
systems for .TEL.
<br />
.TEL uses innovative technology to enable businesses and individuals to
safely publish and manage their contact information in real time directly in
the domain name system (DNS). Anyone will be able to use a .TEL domain name
(i.e., JohnSmith.tel or CompanyName.tel) to initiate communication using
telephony, Voice over IP (VoIP), Instant Messaging, email, SMS and other new
forms of Internet communication. The .TEL domain will seamlessly integrate
traditional means of communications with emerging technologies, making it an
essential tool for businesses and individuals worldwide.
<br />
"We selected NeuStar because of its reputation for operational
excellence, its global reach and its expertise in the convergence of Internet
and telephony technologies," commented Khashayar Mahdavi, CEO of Telnic.
"NeuStar has a deep understanding of -- and broad experience with -- domain
name services, and the company has proven itself to be eminently capable of
scaling to the very large transaction volumes expected in .TEL."
<br />
"NeuStar is excited to be working with Telnic to launch the new .TEL
domain," said Mark Foster, CTO of NeuStar. "We believe that .TEL will help to
enable new services like VoIP for individuals and businesses that need to
publish and control, in real time, how they can be reached."
<br />
About Telnic Limited
<br />
Founded in 1998, Telnic Limited is a UK-based technology company that
develops and delivers cutting-edge technology and solutions for the emerging
Internet communications industry. For more information regarding the .TEL
domain or Telnic Limited, please visit http://www.telnic.org.
<br />
About NeuStar
<br />
NeuStar (NYSE: NSR) is a provider of essential clearinghouse and
directory services to the global communications and Internet industry. Visit
NeuStar online at http://www.NeuStar.biz.
<br />
<pre>
Web site: http://www.neustar.biz
http://www.telnic.org
</pre>
<br />
SOURCE NeuStar, Inc. Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-58406741686681211672015-04-25T00:36:00.002-07:002015-04-25T00:37:26.807-07:00<span style="color: #0486ff; font-family: georgia;">
</span>
<center>
<span style="color: #0486ff; font-family: georgia;">
<h1>
<img alt="TelName and Passbooks" src="http://www.telshops.com/logo.jpg" /></h1>
<span style="font-size: 20px;">
<img src="http://www.telshops.com/mainstreet.jpg" />
<table>
<tbody>
<tr><td style="font-size: 20px;">Connect your store ...
<img src="http://www.telshops.com/business.jpg" height="134" width="200" />
</td><td align="center" style="font-size: 20px;">... with local customers ...
<img src="http://www.telshops.com/customers.jpg" height="134" width="200" />
</td><td align="right" style="font-size: 20px;">through a mobile-friendly TelNames website.
<img src="http://www.telshops.com/telnames.jpg" height="134" width="200" />
</td></tr>
</tbody></table>
Let us show you how you can market your local business on the internet
sign up for a free seminar or call us today!
<br />
For less than <b>$100</b>
<img src="http://www.telshops.com/info.jpg" style="margin: -2px;" title="$100 first year one-time fee, $25 each year afterwards" />
, TelNames™ gives your business a mobile presence in minutes.
<br />.TEL sites' rankings are actually boosted by Google's "<b>Mobilegeddon</b>" algorithmic search update.
<br />Boost your local awareness by pushing coupons and offers to your customers in real-time.
<br />Our .TEL Network builds affinity within your community through a vast set of local citations.
<br />
<div style="background-color: yellow; color: blue; font-size: 16px; padding: 5px; width: 610px;">
<a href="http://www.telshops.com/telshops-network.jpg" style="text-decoration: none;" target="_blank">
The power of the TelShops Network comes from myriad links between master
TelShops directory sites, associated business web sites and their
citations.
<br /><img src="http://www.telshops.com/telshops-network600.jpg" /></a>
<br />
Substantial power also comes from the inherent SEO matching built into
descriptive keyword "subdomains" like Construction.905.tel,
Newmarket.Spas.tel
<br />
Kitchen-Cabinets-Barrie-Muskoka-Rockwood-Kitchens.Cabinets.tel
<br />
Residential-Cleaner.King-City.MaidCleaningServices.Tel
</div>
<div style="background-color: yellow; color: blue; font-size: 16px; padding: 5px; width: 610px;">
<a href="http://www.telshops.com/telshops-network-geo.jpg" style="text-decoration: none;" target="_blank">
TelShops sites are linked locally by town or city. The GTA network has extensive directories.
Business owners may choose multiple regions for greater online exposure.
<br /><img src="http://www.telshops.com/telshops-network-geo600.jpg" /></a>
<br />
Citations to local business websites come from these master TelShops sites.</div>
<div style="background-color: yellow; color: blue; font-size: 16px; padding: 5px; width: 610px;">
<a href="http://www.telshops.com/telshops-network-categories.jpg" style="text-decoration: none;" target="_blank">
Each TelShops site can have over 20 industry categories to group citations.
Business owners are linked from these categories as best suited to their industry.
<br /><img src="http://www.telshops.com/telshops-network-categories600.jpg" /></a>
<br />
Citations to local business websites also emanate from these sites.</div>
<div style="background-color: yellow; color: blue; font-size: 16px; padding: 5px; width: 610px;">
Each of the 20+ subcategories includes more specific domains for citation links.
Business owners may choose multiple categories for greater online exposure.
<br />
<a href="http://www.telshops.com/telshops-network-home-garden.jpg" style="text-decoration: none;" target="_blank">
<img src="http://www.telshops.com/telshops-network-home-garden300.jpg" /></a>
<a href="http://www.telshops.com/telshops-network-health.jpg" style="text-decoration: none;" target="_blank">
<img src="http://www.telshops.com/telshops-network-health300.jpg" /></a>
<a href="http://www.telshops.com/telshops-network-shopping.jpg" style="text-decoration: none;" target="_blank">
<img src="http://www.telshops.com/telshops-network-shopping300.jpg" /></a>
<a href="http://www.telshops.com/telshops-network-personal-care.jpg" style="text-decoration: none;" target="_blank">
<img src="http://www.telshops.com/telshops-network-personal-care300.jpg" /></a>
</div>
<div style="background-color: yellow; color: blue; font-size: 16px; padding: 5px; width: 610px;">
<a href="http://www.telshops.com/telshops-nmkt-network.jpg" style="text-decoration: none;" target="_blank">
We manage the complexities of an automated network such as one for Newmarket, Ontario.
Once your TelNames .tel site is created, it is added to the network.
<br /><img src="http://www.telshops.com/telshops-nmkt-network600.jpg" /></a></div>
<div href="http://www.pinterest.com/telnames/discover-aurora/" style="background-color: yellow; color: blue; padding: 5px; width: 440px;" target="_blank">
Check our Pinterest page for examples.
<br />
Click to visit our 70+ customer sites.
<br />
<img src="http://www.telshops.com/pinterest.jpg" /></div>
<img src="http://www.telshops.com/coupons.jpg" />
<br />
<div style="background-color: yellow; color: red; padding: 10px; width: 400px;">
<a href="http://marketingland.com/survey-online-6-percent-smbs-mobile-sites-45-percent-dont-site-73937">
<b>READ THE FACTS:</b><br />40% of small businesses don't yet a website!
<br />24% of small businesses that do, don't yet a mobile website!</a></div>
<div href="http://www.pinterest.com/telnames/discover-aurora/" style="background-color: orange; color: blue; padding: 5px; width: 500px;" target="_blank">
Order your Telnames from
<br />
<a href="http://solutions.tel/">SOLUTIONS.TEL
<br /><img src="https://img.telnames.com/img/ggae98cis7a8mg6147be0l4jbffk0ira.jpg" /></a>
</div>
See how we can help your local<br />Business Improvement Area (BIA/BID)<br />through <a href="http://shoplocalgames.com/">Local Shopping Games</a>
<br />
Check for our <a href="http://teloffers.com/">local coupon offers</a>.
<br />
<span style="color: #cc0022;">VIDEO:</span> [ <a href="https://www.blogger.com/null">Why You Need A Mobile Site</a> ]
<br />
<div id="video" style="display: block;">
<br />
<div style="text-align: right; width: 640px;">
<a href="http://www.solutions.tel/">www.Solutions.tel</a> </div>
</div>
<br />
<span style="color: red;">To register your domain for local shopping, please contact Mark Kolb via <br /><a href="http://www.solutions.tel/">www.Solutions.tel</a>.
</span><br />
<img src="http://www.telshops.com/mainstreet.jpg" />
<br />
<span style="font-size: x-small;">Image attribution: <a href="http://www.freedigitalphotos.net/">FreeDigitalPhotos.net</a> |
Copyright © 2015 <a href="http://telmasters.tel/">TelMasters.tel</a> |
<a href="http://telwebs.com/">TelWebs</a> |
<a href="http://twitter.com/telshops">TelShops on Twitter</a>
<iframe allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/wo1xLYX60zc" width="560"></iframe>
</span></span></span></center>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-48921698644317885132015-04-20T22:42:00.001-07:002015-04-20T22:42:49.602-07:00Dominio .tel visto en un móvil<img alt="http://img.pen.io/55341c7e110796.75741398.undefined" class="decoded" src="http://img.pen.io/55341c7e110796.75741398.undefined" />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-6604166514533555332015-03-30T02:24:00.001-07:002015-03-30T02:24:38.248-07:00How to redirect a .tel to another .tel?<strong>Procedure:</strong><br /><br />1. Delete all contacts and all other entries like header, location, folders, pictures, videos and keywords.<br />2. Delete Google AdSense.<br />3. Enter one contact type "Go to a .tel" with the .tel destination address.<br /><br /><strong>You don't need to delete:</strong><br />
<ul><br />
<li>E-Mail settings</li>
<li>Google Analytics</li>
<li>Design settings</li>
</ul>
<br /><strong>Remarks:</strong><br /><ul><br />
<li>The redirection won't work if the .tel destination address is redirected itself.</li>
<li>You can redirect a .tel only to another .tel, but not to other domain extensions like .com, .net etc.</li>
<li>You can also redirect a. tel to a sub-page of another .tel.</li>
<li>You can also redirect a. tel from Telnic to a .tel from Telnames (and vice versa).</li>
</ul>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-934509020765438592015-03-17T05:36:00.002-07:002015-03-17T05:41:28.530-07:00Telnic cambia de direcciónStarting this month Calder & Co., a firm of accountants, has taken over the business of Telnic & Telnames:<br />
<blockquote>
<div>
Calder & Co<br />
Chartered Accountants<br />
16 Charles II Street<br />
London<br />
SW1Y 4NW<br />
<br />
Telephone: 020 7839 6655<br />
Fax: 020 7839 6016<br />
Email: <a href="mailto:info@calders.net">info@calders.net</a><br />
<a href="http://www.calders.net/" rel="nofollow" target="_blank">www.calders.net</a></div>
</blockquote>
<br />
<header class="entry-header"><h1 class="entry-title" itemprop="headline">
Google Mobile deadline approaching, but you don’t want to use .Mobi</h1>
<div class="entry-meta">
<span class="entry-comments-link"><a href="http://domainnamewire.com/2015/03/12/google-mobile-deadline-approaching-but-you-dont-want-to-use-mobi/#comments"></a></span></div>
</header><strong>Responsive design, not a separate website, is key to going mobile.</strong><br />
On April 21, Google’s search rankings will undergo a <a href="https://domainnamewire.com/2015/02/26/google-make-your-website-mobile-friendly-by-april-21-or-suffer/">“significant” change on mobile devices</a>. Websites that are mobile friendly will get a big leg up on those that aren’t.<br />
The .Mobi domain name wants to take advantage of this, and tweeted this today:<br />
<span id="more-45314"></span><br />
Let me be frank: using a .mobi domain name is a bad idea.<br />
.Mobi was an interesting idea, almost prescient when it originally
came out in 2006. Mobile web browsing was about to take off with the
iPhone coming out a year later. But the mobile web has change
dramatically, primarily thanks to <a href="https://domainnamewire.com/2013/05/14/responsive-design-is-another-blow-to-mobi/">responsive design</a>.<br />
The need for a separate domain name to host mobile content has
passed. Using a separate domain name, such as .mobi, is a really bad
idea. Instead, your existing website — which already has search rankings
— should be made responsive.<br />
One site, not two. One site to optimize for search, one site to publish all content. <br />
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-2811424198515531352014-11-24T07:22:00.000-08:002014-11-24T07:22:21.620-08:00Como ver si tu dominio .tel es amigable para google en los móviles<h3 class="content_posts_title">
Para hacer el text: <a href="https://www.google.com/webmasters/tools/mobile-friendly/">https://www.google.com/webmasters/tools/mobile-friendly/</a></h3>
<h3 class="content_posts_title">
Google upgrades mobile-friendly sites in search results</h3>
<ol class="content_posts_meta clearfix">
<li class="meta_author">BY <span class="content_post_author">Andrew Allemann</span> - Nov 18, 2014</li>
<li class="meta_category"><a href="http://domainnamewire.com/category/uncategorized/" rel="category tag">Uncategorized</a></li>
<li class="meta_comments"><a href="http://domainnamewire.com/2014/11/18/google-upgrades-mobile-friendly-sites-in-search-results/#comments">4 Comments</a></li>
</ol>
<strong>Sites will get label, and might get a search benefit in the future.</strong><br />
<img align="right" alt="Mobile-Friendly Google" src="http://domainnamewire.com/wp-content/mobile-friendly.jpg" />Google
announced today that it is adding a “mobile-friendly” label to sites in
search results, and is experimenting with using mobile-friendliness as a
ranking signal.<br />
Over the next few weeks, Google will start adding the
“mobile-friendly” identifier next to qualified sites for mobile searches
(see picture). <br />
In a <a href="http://googlewebmastercentral.blogspot.com/2014/11/helping-users-find-mobile-friendly-pages.html">blog post</a> about the move, Google suggested that how mobile-friendly a site is might also affect its rankings in the future.<br />
<blockquote>
We see these labels as a first step in helping mobile
users to have a better mobile web experience. We are also experimenting
with using the mobile-friendly criteria as a ranking signal.</blockquote>
It seems intuitive that Google will demote sites in mobile search if they don’t render well on a mobile browser.<br />
You can see if your site is eligible for the mobile-friendly label on this <a href="https://www.google.com/webmasters/tools/mobile-friendly/">test page</a>.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-52782989142477762402014-11-24T07:16:00.001-08:002014-11-24T07:16:51.781-08:00Como reducir el back up en los dominios .telAll backup files contain multiple versions of your .tel to ensure
backward compatibility, but you actually only need the latest version,
which is version 8.1. If you delete some of the other versions it could
as much as halve the file size.<br />
<br />
• Open the backup XML file<br />
<br />
• On line 2 you should see the 1st version in the <export> tag:<br />
<br />
<export xmlns="http://xmlns.telnic.org/nsp/exchange-6.0"><br />
<br />
• The bold number above shows you that it is version 6.<br />
<br />
• You can delete this whole section, so find the end of the
<export> tag which is </export> and delete everything
between the two tags. NOTE, you are looking for export and NOT exports<br />
<br />
• You will see that the next export tag contains version 7. This can
also be deleted as above if you wish, so that your xml only contains
versions 8 and<br />
8.1<br />
<br />
• Save the file as an xml file and restore this new, smaller version
</export></export>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-56680894057683844752014-10-28T04:16:00.001-07:002014-10-28T04:16:24.306-07:00Imagenes de fondo, desde el panel de controlWe have today updated the .tel control panel (CTH) so that a background
image can be added. As with the logo, the image does need to be stored
on the web, but for background images we have integrated Dropbox
functionality, so any images hosted at Dropbox can quickly and easily be
added as a background to your .tel domain.<br />
<br />
Please note that background images are not possible with all templates
(e.g. some templates fill the entire width of the page). A definitive
list of which templates can be used and lots of other information
regarding background images can be found in our guide at <a href="http://telnic.org/downloads/backgroundimage.pdf" target="_blank">http://telnic.org/downloads/backgroundimage.pdf</a>.<br />
<br />
We have noticed this morning that as Domain Monster have significantly
customised their CTH, there is a minor layout issue which affects the
display of the help question mark in their control panel. This has no
impact on the functionality and we will be advising Domain Monster on
how this can be corrected.<br />
<br />
If you do have any other questions regarding this, please let me know.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-35759178729673525662014-10-23T01:46:00.003-07:002014-10-23T01:46:19.941-07:00How to use a video as full wallpaper in a .tel domain<h2 class="topic-title">
<a href="http://www.whatsyourtel.com/t110-how-to-use-a-video-as-full-wallpaper-in-a-tel-domain#312">How to use a video as full wallpaper in a .tel domain</a></h2>
<div class="author">
<img alt="Post" class="sprite-icon_post_target" src="http://illiweb.com/fa/empty.gif" title="Post" /> by <a href="http://www.whatsyourtel.com/u27">Jens</a> </div>
<div class="content clearfix">
<div>
<ol type="1"><br />
<li>Transform a short video with a converter software into a picture with the format GIF</li>
<li>Save the picture somewhere in the cloud</li>
<li>Use the picture URL as background image for your .tel domain</li>
<li>Use the option "Stretch" for the background settings</li>
<li>View the result: <a href="http://sexchat.tel/" rel="nofollow" target="_blank">http://SexChat.tel</a></li>
</ol>
</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-91321479227931405892014-10-23T01:43:00.002-07:002014-10-23T01:43:33.507-07:00<h1 class="article-title entry-title" itemprop="headline">
The problem with designing for smart homes? You don’t have any users</h1>
<div class="article-featured-image">
</div>
<br /><em>Henrik Holen is the CEO and co-founder of <a href="http://meetviva.com/" rel="nofollow" target="_blank">Viva Labs</a>, a next-generation <span class="il">smart</span> <span class="il">home</span> platform for ISPs, cable companies and utilities.</em><br />
<hr />
<div class="p1">
Want to make a bazillion dollars? Build a dishwasher that empties itself.</div>
<div class="p1">
These days, it’s easy to mock many of the <a href="http://thenextweb.com/dd/2014/07/19/internet-things-narrative-change/" target="_blank">smart products</a>
that appear on the market, but a really good one – one that solves a
real problem for consumers – is something that people will beat down
your door to get.</div>
<div class="p2">
A smart home that can reduce its carbon footprint and make
people feel more secure and more comfortable without demanding too much
has the potential to be such a product.</div>
<div class="p2">
Unfortunately, with a few notable exceptions, this has not
been the approach of smart home products. Instead, companies assume
that the user wants a platform to build on, not a product that improves
their lives. The solutions have been built by engineers, for engineers,
and require enthusiastic and highly skilled users. Regular users will
think they’ve been magically transported back to Windows 95.</div>
<div class="p2">
At Viva Labs, we’ve spent the last couple of years
figuring out how to design something that’s easy enough for the mass
market to use. Through testing with real families and countless
iterations, we’ve learnt a lot about how mass market smart homes should
be designed, and how the consumer expects them to work. These are our
four lessons.</div>
<h3 class="p3">
1. Don’t think in terms of users</h3>
<div class="p2">
If you come from a Web or app background, you’re used to
users who actively engage with your product. They’ve made a choice to
use what you offer, and there is an active interaction happening.</div>
<div class="p2">
When you move beyond the browser, this engagement becomes less clear.</div>
<div class="p2">
When do you use a lamp? Is it when you flip the light
switch or is it when you read by that light? Active interaction is only a
small part of how we use the devices that surround us in the home.
Instead, they work in the background, helping us and keeping us
comfortable, without engaging us.</div>
<div class="p2">
Even those who installed the technology seldom engage in a
meaningful way with it. Beyond them, many of the people who use your
solution don’t even know it exists. Children, visitors, and even family
pets will engage with your product without ever knowing it is there. It
still needs to work like expected.</div>
<h3 class="p3">
2. It’s their world, not yours</h3>
<div class="p2">
Because your users aren’t consciously using your product,
you can’t expect them to follow the rules you set. In an app, the
boundaries are defined by you. In the home, the customer makes the
rules. They won’t change habits built up over years to fit your idea of
how things are supposed to work.</div>
<div class="p2">
Take that approach and your product will appear broken, unable to deal with the way the world works.</div>
<div class="p2">
As an example, people think thermostats are taps. The
higher you set it, the more heat comes out. In fact, most thermostats
are switches, with an even level of heat output. But I can’t even
convince my wife of this, so you’ll never get a non-user to understand
it. Instead, you have to design around these and other user quirks.</div>
<h3 class="p3">
3. Improve and rethink, don’t replace</h3>
<div class="p2">
A key reason why smart homes haven’t succeeded so far is
that they’ve been built for people who love technology. Because they are
early adopters and keen to try new things, they are more accepting of
flaws and willing to tinker. They are a tempting group to focus on, but
doing this will make it impossible to cross the chasm from early adopter
to mass market.</div>
<div class="p2">
Just because it’s analog doesn’t mean its broken, and not
everything needs an internet connection. Light switches, for instance,
work well, and you won’t change how people use them.</div>
<div class="p2">
To reach the mass market you have to improve and rethink
the product, not replace it. To win users over, you need to focus on
building services and products that offer clear value, not potential for
tinkering.</div>
<div class="p2">
Nest, the popular learning thermostat <a href="http://thenextweb.com/google/2014/01/13/google-acquires-nest-3-2-billion/" target="_blank">recently bought by Google</a>,
has done improving and rethinking well. Traditional “smart” thermostats
added lots of functionality. You could program them, set schedules and
modes, but they didn’t improve the actual thermostat experience.</div>
<div class="p2">
What Nest did was find a way to improve on the existing
thermostat experience, letting the user continue their regular habits
while still saving them money and making them more comfortable.</div>
<h3 class="p3">
4. Clear a path: Find the irritants and remove them</h3>
<div class="p2">
People want to do less and think less. Helping them do
that is the secret to success. Your product, especially in the smart
home, should clear a path through daily life, removing the small
irritants, the things you have to remember to do and the repetitive
tasks.</div>
<div class="p2">
For us at Viva Labs, that’s meant intelligent automation.
When I leave the house, the heating gets turned down, the lights off,
and the burglar alarm on. All these are things that I used to have to
remember, but now just happen by themselves. In a busy life, these
little things help, and we believe that is the future of the smart home.</div>
<div class="p2">
Within the next year or two, most of us will have the
opportunity to make our homes considerably smarter and more connected.
Apple, Google, Samsung and your local cable company will fight to be the
platform that supports more and more of your daily life. Whether or not
they succeed will depend on how well they understand how we live our
daily lives.</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-41054579726971826952014-10-23T01:40:00.004-07:002014-10-23T01:40:57.744-07:00finally, a great solution to clicking on a .tel website phone number. ah-hoo!!<br />
<br />
<a href="http://appleinsider.com/articles/14/10/17/how-to-make-and-answer-iphone-calls-on-your-mac-with-os-x-yosemite" target="_blank">http://appleinsider.com/articles/14/...-os-x-yosemite</a><br />
<br />
and, the call-centre directory idea yet again comes to mind.<br />
I'm sure there will be an app in the near future, siri taking the calls.<br />
apple adding function to .tel, yeah-hey<br />
<h1 class="art-head">
How to place and answer iPhone calls on your Mac with OS X Yosemite</h1>
<div class="gray small byline">
By <a href="mailto:neil@appleinsider.com">Neil Hughes</a> </div>
<span class="article-leader">With Apple's newly released OS X Yosemite
and iOS 8, users can be alerted to incoming calls to their iPhone on
their Mac, and even answer a call and carry a conversation through their
Mac in a simple, seamless process.</span><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3233-HT6337_mac_and_ios_mac_phone-l.png" height="266" src="http://cdn1.appleinsider.com/gallery/10752-3233-HT6337_mac_and_ios_mac_phone-l.png" style="display: inline;" width="640" /></div>
<br /><span class="minor2 small gray"></span></div>
<br /><br />
Phone calling in Yosemite requires an iPhone with iOS 8 and an activated
carrier plan. Both the Mac and the iPhone must use the same Apple ID
for the system to automatically work.<br /><br />
Phone calls in Yosemite actually work through the FaceTime application.
As a result, users must ensure they are signed in to their Apple ID for
FaceTime calls on both their iPhone and their Mac, and both devices must
also be connected to the same Wi-Fi network.<br /><br />
Placing phone calls in Yosemite works systemwide. That means users can
initiate a call through the Contacts app, through the FaceTime app, or
even by selecting a phone number in plain text or on a website.<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3228-Screen-Shot-2014-10-17-at-92046-AM-l.png" height="394" src="http://cdn1.appleinsider.com/gallery/10752-3228-Screen-Shot-2014-10-17-at-92046-AM-l.png" style="display: inline;" width="640" /></div>
</div>
<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3232-Screen-Shot-2014-10-17-at-123721-PM-m.png" src="http://cdn1.appleinsider.com/gallery/10752-3232-Screen-Shot-2014-10-17-at-123721-PM-m.png" style="display: inline;" /></div>
</div>
<br /><br />
Instructing Yosemite to dial the chosen number will automatically
initiate the call. The user has no need to do anything with their
iPhone, and the call itself will be routed through their Mac, including
audio output and microphone input.<br /><br />
The call is handled by default in speakerphone mode, but if a user has
headphones and a mic inserted into their Mac, those will work as well.<br /><br />
Answering a call on your Mac running Yosemite is even easier. A ringtone
will play and an accompanying notification appears in the upper right
side of the screen.<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3224-Screen-Shot-2014-10-17-at-95045-AM-m.png" src="http://cdn1.appleinsider.com/gallery/10752-3224-Screen-Shot-2014-10-17-at-95045-AM-m.png" style="display: inline;" /></div>
</div>
<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3225-Screen-Shot-2014-10-17-at-95036-AM-m.png" src="http://cdn1.appleinsider.com/gallery/10752-3225-Screen-Shot-2014-10-17-at-95036-AM-m.png" style="display: inline;" /></div>
</div>
<br /><br />
From here users can choose to accept the call, which automatically
routes it through the Mac, or they can decline it with the usual options
of replying with a message or setting reminders.<br /><br />
When a user is in a call, the iPhone displays a green bar at the top of
the display showing the current call time. The bar can be tapped to pull
up detailed call information or control the call directly from the
iPhone.<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3226-Screen-Shot-2014-10-17-at-95017-AM-m.png" src="http://cdn1.appleinsider.com/gallery/10752-3226-Screen-Shot-2014-10-17-at-95017-AM-m.png" style="display: inline;" /></div>
</div>
<br /><br /><div align="center">
<div class="article-img">
<img alt="" class="lazy" data-original="http://cdn1.appleinsider.com/gallery/10752-3229-Screen-Shot-2014-10-17-at-92009-AM-m.png" src="http://cdn1.appleinsider.com/gallery/10752-3229-Screen-Shot-2014-10-17-at-92009-AM-m.png" style="display: inline;" /></div>
</div>
<br /><br />
Missed call alerts are also displayed accordingly through Notification Center in Yosemite.<br /><br />
Phone calls through Yosemite will not work if the iPhone has Wi-Fi
Calling enabled. And the Cellular Calls option can be disabled on
Yosemite through the settings of the Mac FaceTime application.<br /><br />
Phone call routing isn't restricted to Yosemite, as both the iPad and
iPod touch can also be used to answer calls. Here the process works the
same as on the Mac, automatically handling the call in speaker mode and
routing audio output and mic input through the connected device on which
the call was answered. Missed call alerts are also displayed across
devices.<br /><br />
iPad and iPod touch calling can be disabled by going into the iOS
Settings application, choosing FaceTime, and turning off the option for
iPhone Cellular Calls.
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-61377935496416820132014-09-15T07:52:00.001-07:002014-10-23T01:41:43.707-07:00<h1 itemprop="headline">
Post-Pigeon Best Practice: How To Optimize For Internet Yellow Pages & Directories</h1>
<h2 class="subhead">
While many marketers have written off Internet
Yellow Pages as dead, the recent Google Pigeon update may have made
them relevant once more.</h2>
<br />
<div class="sharing_content_channel">
</div>
<img alt="Yellow Pages SEO" class="aligncenter wp-image-202415 size-full" src="http://searchengineland.com/figz/wp-content/seloads/2014/09/IYP-seo.jpg" height="360" width="640" /><br />
The recent <a href="http://searchengineland.com/google-makes-significant-changes-local-search-ranking-algorithm-197778">Google Pigeon</a>
update appears to have provided a bit of a traffic upswing for Internet
Yellow Pages (IYPs) and other online business directories, at the cost
of individual local businesses’ site rankings in many cases.<br />
In order to cash in on this new paradigm, businesses must once again
return to the yellow pages as a source of customer referrals. Here’s how
to optimize your presence in IYPs and other directories.<br />
Now, if you’ve been watching the course of local online business
trends over the past decade and noted how the internet has impacted both
traditional media and their online equivalents, you may be thinking
I’ve completely lost the plot by recommending to shift back to Internet
Yellow Pages promotional efforts (since many businesses have moved their
advertising budgets away from yellow pages).<br />
Search engines and the internet have put some serious dents in old
local media powerhouses like yellow pages, newspapers, classifieds, etc.
I’ve frequently <a href="http://searchengineland.com/are-yellow-pages-toast-four-years-later-we-review-ad-value-116199">mentioned</a>
in the past how Google and other local search engines were edging out
IYPs as the local business information provider-of-choice for consumers.
However, the pendulum may be swinging back somewhat now.<br />
As a number of us <a href="http://searchengineland.com/googles-pigeon-update-solves-yelp-problem-boosts-local-directories-197949">noted</a>,
the recent Pigeon update improved the ranking and visibility of IYPs
and directories, and SEMrush and other competitive analytics services
are already showing a real upswing in those sites’ visits as a result.<br />
Some of the sites that appear to be showing increases in search
referral traffic include Yellowpages.com, Superpages.com,
Yellowbook.com, Insiderpages.com, Smartpages.com and Manta.com:<br />
<div class="wp-caption aligncenter" id="attachment_202416" style="width: 810px;">
<img alt="IYP Search Referral Traffic Increased In 2014" class="wp-image-202416 size-full" src="http://searchengineland.com/figz/wp-content/seloads/2014/09/IYPgraphs.jpg" height="376" width="640" /><br />
<div class="wp-caption-text">
Source: <a href="http://www.semrush.com/" target="_blank">SEMrush</a></div>
</div>
Top Internet Yellow Pages sites, and even some of the second-tier
yellow pages sites, have seen increases in traffic over the past year,
particularly after late spring and going into the summer.<br />
Other business review sites also seem to have enjoyed bumps up in
rankings in various market/category combinations. Local business reviews
sites seem to have benefited in many cases, including Angie’s List, the
Better Business Bureau (BBB), HomeAdvisor and probably Yelp (even
though SEMrush shows a slight dip downwards for Yelp after June).<br />
<img alt="Business Reviews Graphs" class="aligncenter wp-image-202417 size-full" src="http://searchengineland.com/figz/wp-content/seloads/2014/09/Reviews-Graphs.jpg" height="250" width="640" /><br />
Some vertical business directories (these are directories that are
devoted to specific business categories) have apparently also benefited
from the changes, including ones like Restaurants.com, FindLaw.com,
Avvo.com, and Doctoroogle.com.<br />
<img alt="Vertical Directories Graphs" class="aligncenter wp-image-202428 size-full" src="http://searchengineland.com/figz/wp-content/seloads/2014/09/VerticalDirectories-graphs1.jpg" height="256" width="640" /><br />
It’s pretty simple math to figure out that in many business
categories, if the local directory sites have risen some in rankings,
then other stuff was equally displaced. It’s likely that some local
businesses’ websites are not as visible in each of the search markets
where this occurred.<br />
If you’re a business that lost its visibility when the tide shifted,
then you need to seriously consider beefing up your presence and
visibility within the directory sites where the consumers are now going.<br />
Even if your website or local pack listing did not lose its
first-page-of-search-results placement, you should still consider
strengthening your directory game in order to increase your visibility
and maximize your presence where consumers are looking.<br />
<h2>
<b>Optimizing Your Business In IYP & Business Directories</b></h2>
Below are a handful of tips for optimizing your business in Internet Yellow Pages and Business Directories:<br />
<h2>
Search</h2>
First, do a few searches for your type of business in your area and
then see which directory sites are ranking well in search results. For
instance, when searching for [auto repair Nashville], I can see
Yellowpages.com and the BBB.org sites showing up on Page 1, and
Angieslist.com near the top of Page 2 (which could easily pop up a notch
onto Page 1).<br />
So, I would then focus my efforts for an auto repair business there in Yelp.com, Yellowpages.com, the BBB and Angie’s List.<br />
When you do this, you likely will need to conduct a few different
searches with logical variations, such as [car repair Nashville],
[transmission repair Nashville], etc – this would add Superpages.com and
MapQuest.com to my list.<br />
<h2>
Research</h2>
Once you have your list of local directory sites, visit the pages
from them that are showing up for your keyword searches in order to
assess what you may need to do with each. Determine whether you merely
wish to optimize your business profiles there at their free levels, or
whether you’ll wish to purchase advertising.<br />
Questions you should ask are: Does my business listing appear on the
first page of results from the directory webpage that is ranking for my
local business keyword searches? And, if your listing is already on Page
1 there, is it ranking higher on the page – such as in the first half
to first third of the page?<br />
In some cases, adjusting your listing might help it pop up onto Page 1
for free, but in many cases you may want to seriously consider
advertising since ads are typically going to be in the upper portion of a
directory page.<br />
For some sites like Angie’s List and the BBB, you can’t advertise,
but you may be able to apply for membership and that can help you to
address any customer reviews or questions (and, don’t forget about
adding/correcting any information about your business that you can!).<br />
Above all, for the directory page to benefit you, your business must
appear on Page 1 of that directory site. It helps further for it to rank
near the top, but that’s not as important as simply being there.<br />
<h2>
To Advertise Or Not?</h2>
For those sites that allow businesses to advertise, this can be a
complex assessment. I’ll say that in general, it may not be worthwhile
to advertise in the print yellow pages books in many cases, but IYP and
online directory sites often have much more cost-effective advertising
options compared with the heyday of print.<br />
With many of these sites, simply purchasing the least-expensive ad
option might be the minimum necessary to enable you to appear in the ad
section of their first page of listings – so, that might be all you
would need.<br />
IYPs may offer bundled advertising deals that would combine print
with internet and mobile advertising – I think that in most cases you
don’t need the print (there are undoubtedly exceptions to this – small
towns and locations in the Midwest of the U.S. may still have sufficient
print book usage to rationalize value for the print ad costs).<br />
I think the main goal for you will be to get on Page 1 of the
directory page in question, and closer to the top of it. There can be
other value-add options that you may want to consider, such as add-ons
that would make the listing more visible and more attention-getting for
consumers.<br />
In the past, there was some anecdotal evidence that IYP ads might
provide actual SEO benefits – but, most of these links will be
identified and discounted as ad links by search engines, or they’re
nofollowed on those sites – so, this probably should not be considered
to be an SEO stratagem.<br />
<h2>
Your Phone Number</h2>
Keep your standard local phone number. If you choose to advertise, I recommend that you continue to <a href="http://searchengineland.com/be-wary-of-call-tracking-numbers-in-local-search-26895">avoid using call-tracking numbers</a> for the sake of your overall local SEO healthiness.<br />
A number of directory sites employ call tracking so that they can
show more of their sites’ value to advertisers, but these numbers can be
detrimental to the rankings of your business in local search, and if
the tracking number displays a nonlocal area code, it might have an
impact on your conversion rates when consumers are choosing a business.<br />
So use your main local phone number and not an 800 number nor tracking number.<br />
<h2>
Your Location</h2>
Leverage geographic placement with directory sites. Some directory
sites will allow you to select multiple cities where your listings may
appear – to maximize your visibility in major metro areas, be sure to go
to the effort of associated your business listing with as many
geographic/city names as applicable.<br />
<h2>
Directory Site SEO?</h2>
Business listings pages from online directory sites are often a type
of local search results pages. As such, there are optimization
techniques that can enable your business to rise up in their rankings,
just as with the local results in the major search engines! So, there is
potential you could apply these in order to pop up into the first page
of the directory site without incurring advertising or membership fees,
if you’re not already there.<br />
Starting with the name – some directories will display businesses
according to alphabetical order, so you might be able to reorder or
modify your business name in order to pop up onto Page 1 (the BBB.org
website is one example).<br />
In most cases, you would likely have to file for a name change or
apply for a “Doing Business As” name, and then supply the government
approved paperwork to the directory to ask them to change how they list
you. (Disclaimer: I do not know the business rules for these sites –
they likely differ from organization to organization.)<br />
In yet other cases, the businesses are displayed in order of
proximity to the center of the search area – in order to optimize for
this, you’d have to alter your address, which might not be worth it for
the potential added exposure benefit.<br />
Don’t laugh! Businesses have actually done this to attempt to improve
their rankings in search engines, so why not in directory sites, too?
(See: <a href="http://searchengineland.com/relocation-relocation-relocation-a-new-local-ranking-tactic-135325">Relocation, Relocation, Relocation – A “New” Local Ranking Tactic?</a>)<br />
<h2>
Optimize</h2>
Optimize your business directory profile. There are frequently a
number of elements of business directory profiles that may be optimized
beyond merely checking to see if your name, address and phone number are
correct: <a href="http://searchengineland.com/double-your-traffic-using-optimal-category-names-44559">business categories</a>,
lists of products and services, written descriptions, hours of
operations, website link, photos, logos, social media links, and more.<br />
I’ve written about those <a href="http://searchengineland.com/anatomy-optimization-of-a-local-business-profile-12943">before</a>,
although I was focusing more on search optimization benefits then. Your
optimization in this instance should be more focused upon making you as
visible and attractive within the directory site as possible.<br />
<h2>
Review Sites</h2>
Improve your presence in reviews sites. For business reviews sites,
your promotional value is naturally going to be heavily affected by your
overall reviews and ratings.<br />
Obviously, your overall customer service needs to be excellent
already – if it is less than what it could be, beef it up by studying
companies at the top of the customer service game, like Zappos.<br />
But, there are also things you can do to improve your presence in
reviews sites online, such as encouraging happy customers to post
reviews, responding capably to feedback, and more. See <a href="http://searchengineland.com/5-go-tos-to-make-online-reviews-work-for-your-business-181490">4 Go-Tos To Make Online Reviews Work For Your Business</a>.<br />
<h2>
Social Media</h2>
Be sure to connect your directory listings with your social media
accounts wherever possible! I’m seeing many instances where a business’s
Facebook page is ranking well in the new search results, and consumers
may like businesses that appear more open to interacting with them
online, so enhance the chances of this happening.<br />
I’ve also seen a lot of instances where businesses have made errors
when adding their social media URLs to directory sites, so be sure to
check all your links when you look at your listings and directory
profile pages.<br />
<h2>
Analyze</h2>
Watch your directory listing over time. Revisit the page where your
listing appears at least monthly so you may see if conditions have
changed since the last time you viewed your listing. It’s possible that
new listings (or new advertisers) could have appeared in the meantime,
affecting your business’s directory listing.<br />
Did you know you can see how many visitors were referred from
directory sites to your site’s pages in web analytics systems like
Google Analytics? I recommend that you compare these referrals before
and after you’ve performed optimizations on your listings – if you were
successful in your efforts, I would imagine you’ll likely see the
referral numbers rise!<br />
<h2>
<b>Further Increasing Sales</b></h2>
Many businesses have hyper-focused on how they rank and appear in
Google and Bing search results, and your presence in that top tier of
search is definitely valuable and important. However, using these tips
can further optimize your presence in the second tier of search,
thereby increasing your potential customer referrals and associated
sales. And, increasing sales is what we’re all after, anyway.<br />
<hr />
<i>Some opinions expressed in this article may be those of a
guest author and not necessarily Search Engine Land. Staff authors are
listed <a href="http://searchengineland.com/staff">here</a>.</i>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-18770380487371510172014-09-15T07:39:00.001-07:002014-09-15T07:39:40.514-07:00Background Images for .TEL Domains<div class="post-headline">
<h2>
<a href="http://www.telmasters.com/Blog/?p=463" rel="bookmark" title="Permanent Link to Background Images for .TEL Domains">Background Images for .TEL Domains</a></h2>
</div>
<div class="post-bodycopy clearfix">
Telnic recently allowed images to be used as backgrounds on .TEL domains. They make the web pages “pop”. <br />
Currently, the only way to insert a background image is via a third party tool such as <a href="http://telmasters.com/">Telmasters </a>or <a href="http://telvision.co/">TelVision</a>. Once inserted, the background is used for all subdomains. Backgrounds must be hosted on an external server.<br />
To insert a background with Telmasters free Quick Update tool, supply its URL in the Background URL field.<br />
To insert a background with TelVision, click [Template] and supply its URL in the B/G Image URL.<br />
We recommend you use the “Stretch” option to ensure best fit for your
image. An image size of approximately 1500 pixels wide by 1000 high or
4:3 ratio is recommended.<br />
Note that backgrounds are not supported for all template styles. We like the narrow news style templates.<br />
<a href="http://shoplocal.tel/"><img alt="" class="alignnone size-medium wp-image-464" src="http://www.telmasters.com/Blog/wp-content/uploads/2014/09/shoplocal555-500x366.jpg" height="366" title="shoplocal555" width="500" /></a><br />
If you have a large number of domains, you can use Telmaster’s Bulk
Insert Tool to insert an image across all domains. Optimal tool
performance if all your domains are grouped into one or a few CTH
accounts.<br />
<a href="http://newmarketontario.tel/"><img alt="" class="alignnone size-medium wp-image-466" src="http://www.telmasters.com/Blog/wp-content/uploads/2014/09/nmkt555-500x388.jpg" height="388" title="nmkt555" width="500" /></a></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-75539900294411145842014-09-03T12:21:00.000-07:002014-09-03T12:39:30.370-07:00Video in the CTHWe have today added video functionality to the .tel control panel (CTH).
This will automatically appear when you log in (If not, please try
refreshing the page) and is located between the “Contact Information”
and “Keywords” sections.<br />
<br />
You can show a video that is hosted on YouTube, Vimeo or Daily Motion. To do so:<br />
<br />
- Click Add in the Video section<br />
- Select the Source of the video from the dropdown (YouTube, Vimeo or Daily Motion)<br />
- Add the link to the video hosting service. For example, with
YouTube click the “Share” button just below the video to see the link
that needs to be added<br />
<br />
I have held back on making this announcement as registrars do need to
activate the functionality. The Video section will still appear even if
it isn't activated, but you would get an error if you tried to save. I
believe the majority are now activated but if anyone has an issue please
let us know and we can follow up with the registrar. Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-66860816328478889892014-09-03T11:49:00.002-07:002014-09-03T12:42:58.699-07:00 Background images -->for example 1440 x 1080 pixels-->stretch<br />
Ejemplos:<br />
http://criptomonedas.tel/<br />
http://libros.tel/ <br />
We have this week launched background image functionality for .tel
domains. Currently this is only available to be activated through the
API, although it will also be added to the .tel control panel (CTH) at a
later date. Full details of this new functionality can be found in this
document - <a href="http://www.telnic.org/downloads/TelHostingClientSOAPAPI-BGImage.pdf" target="_blank">http://www.telnic.org/downloads/TelH...PI-BGImage.pdf</a>.<br />
<br />
As mentioned in the document, some of the designs mean that not all
templates are suitable for a background image (i.e. some don’t have a
background). Unfortunately the API commands have different IDs to those
used in the CTH, For clarity, therefore, the templates which can have a
background image are the ones with the following IDs in the CTH:<br />
<br />
• Option 2<br />
• Option 3<br />
• Option 5<br />
• Option 6<br />
<br />
Also, as with all design aspects, background images are set for the .tel as a whole, rather than a folder by folder basis.<br />
<br />
As mentioned in the document, there are three ways in which an image can be added. These are set by the "bip" value in the API:<br />
<br />
0 (default) - image is aligned top left and constrained (if applicable) to the width of the page<br />
<br />
1 – image is stretched to width and height of page<br />
<br />
2 – image is repeatedly tiled (works best with smaller images)<br />
<br />
For the default (0) as this will be displayed on a variety of different
monitor and tablet screen sizes, it is impossible to create an ideal
dimension for all. With the majority of screens having a 4:3 aspect
ratio, however, this is the ratio we recommend (for example 1440 x 1080
pixels).<br />
<br />
For the other two as the image is either stretched or tiled, it's
completely up to you. As mentioned above, the tiled setting is best with
smaller images to get the full effect of the tiling.<br />
<br />
Telmasters tools were updated to support background image management:<br />
Quick Update<br />
Directory Populate new BG directive <br />
Bulk Insert/Delete<br />
<br />
Telvision.co support is under the Template option.<br />
<br />
Examples of sites with backgrounds: <br />
<a href="http://www.905.tel/" target="_blank">www.905.tel</a><br />
<a href="http://www.mark.tel/" target="_blank">www.mark.tel</a><br />
<a href="http://www.617.tel/" target="_blank">www.617.tel</a><br />
<a href="http://www.lcbo.tel/" target="_blank">www.lcbo.tel</a><br />
<br />
Un sitio para experimentar con el tamaño de las fotos:<br />
http://www.smushit.com/ysmush.it/<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-3940726179763962501.post-5616651248610186612014-07-23T10:38:00.000-07:002014-07-23T10:38:10.016-07:00Hidden Cash craze<h1 title="multifirma.criptografia.criptomonedas.tel">
If you want to see how .TEL is applied to the Hidden Cash craze<br />
read the blogs and visit the site.<br />
<a href="http://www.hiddencash.tel/" target="_blank">www.HiddenCash.tel</a> <br />
Just had game #3 for $60 with some media attention finally.<br />
BTW, this can be applied to any town with a good .TEL merchant base, eg UK communities.<br />
Mark </h1>
<h3 class="post-title entry-title" itemprop="name">
<a href="http://hiddencashtoday.blogspot.ca/2014/07/the-hidden-cash-game-comes-to-aurora.html">The Hidden Cash Game Comes to Aurora, Ontario!</a>
</h3>
<div class="post-header">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-VnXTWvVL4N4/U8mjlKb9M9I/AAAAAAAAAQk/9TAL17-HLws/s1600/hiddencash555.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="160" src="http://1.bp.blogspot.com/-VnXTWvVL4N4/U8mjlKb9M9I/AAAAAAAAAQk/9TAL17-HLws/s1600/hiddencash555.jpg" width="200" /></a></div>
<br />
The <b>Hidden Cash</b> craze started in San Francisco in May (2014) and
has progressed to towns and communities worldwide. Hiding cash and
tweeting clues has been quite entertaining and finding cash is even more
rewarding for the lucky few. Selfies are taken of their discovery to
spread the word. Some people even share their good fortune within their
community by giving back to others less fortunate.<br />
<br />
<br />
<a href="http://3.bp.blogspot.com/-LW5086CNb44/U8mdqEv4F6I/AAAAAAAAAQM/PbW8kGQl9ek/s1600/map-4.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="http://3.bp.blogspot.com/-LW5086CNb44/U8mdqEv4F6I/AAAAAAAAAQM/PbW8kGQl9ek/s1600/map-4.jpg" width="129" /></a>In
creating a Hidden Cash Game for Aurora, we decided to engage the
combined community of both merchants and residents and are using Hidden
Cash as a <b>shop local initiative</b>. Players have a map revealed
while they visit merchant websites. Played weekly, the first part of the
map is available Monday through Saturday, while the remaining parts are
revealed on Sunday.<br />
<br />
Once completed, players visit the secret location to hunt for the cash.
At that time, a final clue in a tweet or online location pinpoints the
"stash".<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://4.bp.blogspot.com/-8A9F7e01BKc/U8meZmGx8fI/AAAAAAAAAQU/kMFjhgSRTtY/s1600/examplelogos.jpg" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="81" src="http://4.bp.blogspot.com/-8A9F7e01BKc/U8meZmGx8fI/AAAAAAAAAQU/kMFjhgSRTtY/s1600/examplelogos.jpg" width="200" /></a></div>
With a large group of merchants already participating in the <a href="http://www.discoveraurora.ca/" target="_blank">Discover Aurora</a> game, we had an instant base to begin a new<b> </b>shop
local initiative. Our form of hidden cash game effectively promotes
local merchants to local residents. We do this by getting players to
answer questions, whose answers are found only on mobile-friendly
merchant (.TEL) websites. With each correct answer, more of a player's
map is revealed.<br />
<br />
Questions and answers usually focus on a deal or coupon each merchant has to offer.<br />
<br />
As a shop local marketing initiative, Hidden Cash Today is a <b>win-win</b>
for players and merchants alike. Players get a chance to win cash while
discovering new things about local merchants' products, services and
deals.<br />
<br />
If you are local to Aurora, Ontario join the game at <a href="http://www.hiddencash.today/">www.HiddenCash.today</a>.<h1 title="multifirma.criptografia.criptomonedas.tel">
</h1>
Unknownnoreply@blogger.com0