Archive for August, 2013
Posted August 30th, 2013
At its meeting on 13 August 2013, the ICANN Board New gTLD Program Committee (NGPC) adopted a resolution affirming that “dotless domain names” are prohibited. Dotless domain names are those that consist of a single label (e.g., http://example, or mail@example). Dotless names would require the inclusion of, for example, an A, AAAA, or MX, record in the apex of a TLD zone in the DNS (i.e., the record relates to the TLD-string itself).
In addition to public comments on dotless domain names, the NGPC considered the security and stability risks associated with dotless domain names highlighted in the following papers:
- On 23 February 2012, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 053: SSAC Report on Dotless Domains [PDF, 183 KB]. In this report, the SSAC stated that dotless domains would not be universally reachable and recommended strongly against their use. As a result, the SSAC recommended that the use of DNS resource records such as A, AAAA, and MX in the apex of a Top-Level Domain (TLD) should be contractually prohibited where appropriate, and strongly discouraged in all cases.
- On 10 July 2013 the Internet Architecture Board (IAB) released a statement on dotless domain names, recommending against the use of dotless domain names for TLDs.
- On 29 July 2013 Carve Systems delivered a report on dotless domain names, which was commissioned by ICANN. Consistent with the SSAC report, Carve’s report on dotless domain names [PDF, 1.02 MB] identifies security and stability issues.
When adopting its resolution, the NGPC considered the security and stability risks identified in these papers, as well as the impracticality of mitigating these risks. Based on the NGPC resolution, ICANN does not plan to pursue any additional studies on the subject.
Posted in Domain Names, gTLDS, ICANN by Ken Taylor
Posted August 28th, 2013
As ICANN previously announced, we commissioned a study to consider the likelihood and impact of name space collisions between applied-for new gTLD strings and non-delegated TLDs. In light of that study, ICANN proposed to the community several possible mitigation measures, including:
- Proceeding with contracting and delegation of those strings categorized as “low risk” (80%) but recommending additional mitigation measures which should not materially impact their timeline for delegation.
- Conducting further study on those strings categorized as “uncalculated risk” (20%) anticipated to take 3-6 months to complete.
- Delaying contracting and delegation of the two “high risk” strings until mitigation efforts can place them in the “low risk” category.
ICANN has solicited community comment on the mitigation steps outlined in the staff recommendation paper, with a comment close date of 27 August 2013 23:59 UTC. Pending receipt of community feedback on the staff mitigation proposals, ICANN intends to proceed with New gTLD applications as follows:
- Low Risk – Eligible applicants will be invited to begin contracting and may proceed through contract execution of a Registry Agreement. Delegation of Low Risk strings will be held until we have evaluated community comments and settled on appropriate mitigation measures.
- Uncalculated Risk – Eligible applicants will be invited to begin contracting. Execution of registry Agreements will be held until we have evaluated community comments and settled on appropriate mitigation measures.
- High Risk – Applicants will not be invited to begin contracting until we have evaluated community comments and settled on appropriate mitigation measures.
We encourage the community to submit comments on name space collision and appropriate mitigation measures to assist ICANN in considering these matters.
For further information from ICANN on Name Space Collision, go HERE.
Posted in DNS, gTLDS, ICANN by Ken Taylor
Posted August 23rd, 2013
From The Domains
85 new gTLD applications passed ICANN Initial Evaluation today, including the Dot Brands: .Netflix, .Ping, .Lamborghini, .Tiffany, .Dish, .BBT, .HITACHI, .Gallo, .Symantec and .Intuit.
See the full skinny HERE.
Posted in gTLDS, ICANN by Ken Taylor
Posted August 19th, 2013
From Harvard Business Review
How IT Professionals Can Embrace the Serendipity Economy
With Frederick’s Taylor invention of scientific management in the 1880s, and its subsequent assimilation into what we now consider modern management, organizations have used logic and rationality to the eliminate waste, to seek efficiency, and to transfer human knowledge to tools and processes. This perspective created the industrial economy lens through which most managers perceive their operations.
The industrial age economy does not exist in a vacuum. Running alongside it is the Serendipity Economy, an economic space where often random, always unanticipated interactions occur that may lead to value. Industrial age measures can’t evaluate Serendipity Economy results, leaving its outcomes like invention and innovation, process improvements, and new businesses relegated to the evidence of anecdote.
IT professionals need to recognize and embrace the Serendipity Economy in order to better understand the impact of technology investments, improve employee engagement and drive business transformation.
Get the full skinny HERE.
Posted in Cool Ideas by Ken Taylor
Posted August 8th, 2013
ICANN has embarked on an effort to reinvent today’s WHOIS system. Be part of the solution and join the discussion…online and at ICANN‘s Durban meeting.
At the request of ICANN Community Members, the Expert Working Group on gTLD Directory Services has extended its open consultation period until 6 September 2013 – 23:59 UTC in order to provide the Community with additional time to comment on the proposed model and recommendations.
Please note that the EWG is meeting in late August to begin revising the initial report . Comments received by 23 August 2013 – 23:59 UTC will be most useful.
See the full skinny HERE.
Posted in gTLDS, ICANN, Whois by Ken Taylor
Posted August 7th, 2013
Marshall McLuhan’s profound observation that “the medium is the message” is often misunderstood. It is assumed the 20th-century communications theorist meant that channels of mass media eventually take precedence over the content they deliver, but that’s not the case.
McLuhan’s notion of a medium was “any extension of ourselves,” which could easily be a wheel or a Walkman®. The message the medium conveys is found in “the change of scale or pace or pattern” that it introduces into human affairs—in other words, how the medium transforms people.
In the mid-1800s, for example, the telegraph transformed the world. By accelerating the pace at which business was conducted, the telegraph (medium) resulted in a populace that came to expect instant gratification in matters of discourse, regardless of distance (message).
What today’s Internet is telling us is still unclear, even if we know its message is vastly more complex than the telegraph’s. Indeed, that message will likely be at least as far-reaching as the medium itself. And social media are increasingly a part of whatever story is unfolding—as Corporate America is about to discover in ways it probably could have never imagined.
See the full skinny HERE.
Posted in Social Networks by Ken Taylor
Posted August 6th, 2013
As directed by the ICANN Board of Directors on 18 May 2013, ICANN commissioned and today releases the results of a study that considers the likelihood and impact of name space collisions between applied-for new gTLD strings and non-delegated TLDs. Additionally, the study also reviewed the possibility of collisions arising from the use of X.509 digital certificates.
Background: In a study published in January 2013, ICANN’s Security and Stability Advisory Committee (SSAC) identified fact that some certificate authorities issue X.509 certificates for domain names that are not resolvable in the public DNS. Such issues identified in SAC 057, as well as in SAC 045, are symptoms of entities that have local environments that include strong assumptions about the number of top-level domains and/or have introduced local top-level domains in private namespaces that may conflict with names yet to be allocated. These private namespaces sometimes “leak” into the public DNS (either through misconfiguration or the use of old software), meaning that requests for resources on private networks could end up querying the public-facing DNS Root Servers and hence “colliding” with the delegated new gTLD.
See the full skinny including the resulting study and ICANN staff recommendations HERE.
Posted in Compliance, DNS, gTLDS, ICANN by Ken Taylor
Posted August 1st, 2013
The massive summer music festivals are a great way to catch short sets from your four favorite bands while tolerating 25 mediocre acts you’ve never heard of. But like anything that involves leaving the house for an extended period of time, you need to be prepared. And when we say prepared, we mean it’s time to get your smartphone ready for the crowded, lonely grasslands.
See the full skinny HERE.
Posted in Cool Ideas, Gadgets by Ken Taylor