Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.

Where is the domain industry with the adoption of DNSSEC? After a burst of well publicized activity from 2009-2011 — .org, .com, .net, and .gov adopting DNSSEC, roots signed, other Top-Level Domains (TLDs) signed — the pace of adoption appears to have slowed in recent years.

As many CircleID readers know, DNSSEC requires multiple steps in the chain of trust to be in place to improve online security. Those are:

The TLD Must Be Signed – Major TLDs such as .org, .info, .com, and .net have been signed, as have a good number of ccTLDs. All new gTLDs must sign the TLD zone and must accept public key material from registrars, but they are not required to enforce signed second level delegations.

The Registrar Must Support DNSSEC – The registrar where the domain is registered must support DNSSEC. ICANN requires that a registrar must be able to add, remove, or change public key material (DNSKEY or DS resource records) on behalf of registrants for those registries that require it (see point 1).

The DNS Hosting Provider Must Support DNSSEC – Very often a registrar may also provide DNS Hosting services — where they will host the domain name's DNS records, allow management of those records, and publish them to the global DNS. Regardless of whether DNS hosting is provided by the registrar or by another company DNSSEC support is required.

Of course, for DNSSEC to be useful, both the server side and validation on the client side must support signed domains. Client-side validation is moving in a positive direction. In late 2013, APNIC Labs produced research that demonstrated that roughly 8 percent of global DNS queries involved some kind of DNSSEC validation. Last month APNIC unveiled a global validation graph that showed DNSSEC validations increasing to 12 percent.

In the United States Comcast (the country's largest ISP) has adopted client-side validation. Some countries like Sweden and Estonia see a majority of queries using DNSSEC validation. DNSSEC technology standards have been stable and mature since 2007, with only updates, clarifications, and new functionality added since then. "Waiting until the standards are final" is no longer a valid reason to delay deployment.

Authoritative DNS is very mature, and it's easy to get access to DNSSEC information once it is deployed. DNSSEC has been included in every major name server implementation for a few years now. Second level domains can now be signed, but adoption at that level has been frustratingly slow, due to the lack of service provider support (see point 2 above).

The final step in the deployment of DNSSEC is the use of validated information by services and applications to provide enhanced and innovative security services to users, with browsers obviously being first in line. Businesses need to see better online security as a market advantage — especially financial services firms.

More signed domains are needed to demonstrate full viability, and that's currently a huge gap in the DNSSEC chain of trust. New TLDs will help to some degree, but more needs to be done. There are two obstacles standing in the way of more secure domains, one related to policy and one technical.

On the policy side, the new ICANN policy for gTLDs mandates signed TLD zones, but not signed second level delegation. In addition, the 2013 Registrar Accreditation Agreement (RAA) requires registrars to offer "DNSSEC services," but only for those registries that require it.

On the technical side, it is not possible for a gTLD domain name registration with active DNSSEC to be transferred from one registrar to another without breaking the security chain of trust.

Part Two of this series will address impediments to greater DNSSEC adoption.

By Dr. James Galvin, Director, Technical Standards at Afilias Dr. Galvin is a key leader of the Afilias technical team with over 25 years of Internet standards and policies development experience. Visit Page

If you are pressed for time ...

... this is for you. More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Vinton Cerf, Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

WHOIS access and development of an interim GDPR compliance model remains THE hot topic within the ICANN community. Developments are occurring at a break-neck pace, as ICANN and contracted parties push for an implementable solution ahead of the May 25, 2018 effective date of the GDPR... ICANN is now poised to formally publish the convergence model, although the community continues to discuss and seek a solution that is acceptable for all stakeholders. more

The European Commission recently released technical input on ICANN's proposed GDPR-compliant WHOIS models that underscores the GDPR's "Accuracy" principle - making clear that reasonable steps should be taken to ensure the accuracy of any personal data obtained for WHOIS databases and that ICANN should be sure to incorporate this requirement in whatever model it adopts. Contracted parties concerned with GDPR compliance should take note. more

There is an urgent need to clarify the GDPR's territorial scope. Of the many changes the GDPR will usher in this May, the expansion of EU privacy law's territorial scope is one of the most important. The GDPR provides for broad application of its provisions both within the EU and globally. But the fact that the GDPR has a broad territorial scope does not mean that every company, or all data processing activities, are subject to it. more

When you've been around the domain industry for as long as I have, you start to lose track of time. I was reminded late last year that the 6-year agreement Verisign struck with ICANN in 2012 to operate .com will be up for expiration in November of this year. Now, I don't for a second believe that .com will be operated by any other party, as Verisign's contract does give them the presumptive right of renewal. But what will be interesting to watch is what happens to Verisign's ability to increase the wholesale cost of .com names. more

One of the chronic features of the Bitcoin landscape is that Bitcoin exchanges screw up and fail, starting with Mt. Gox. There's nothing conceptually very hard about running an exchange, so what's the problem? The first problem is that Bitcoin and other blockchains are by design completely unforgiving. If there is a bug in your software which lets people steal coins, too bad, nothing to be done. more

Panels appointed to hear and decide disputes under the Uniform Domain Name Dispute Resolution Policy (UDRP) have long recognized that three letter domains are valuable assets. How investors value their domains depends in part on market conditions. Ordinarily (and for good reason) Panels do not wade into pricing because it is not a factor on its own in determining bad faith. more

These days in Washington, even the most absurd proposals become the new normal. The announcement yesterday of a new U.S. State Department Cyberspace Bureau is yet another example of setting the nation up as an isolated, belligerent actor on the world stage. In some ways, the reorganization almost seems like a companion to last week's proposal to take over the nation's 5G infrastructure. Most disturbingly, it transforms U.S. diplomacy assets from multilateral cooperation to becoming the world's bilateral cyber-bully nation. more

Cryptocurrencies (such as Bitcoin) are all the rage -- so, naturally, related domain name disputes are, too. The wild fluctuations in cryptocurrency prices (Bitcoin hit a low of close to $6,000 this week, after reaching an all-time high of more than $19,000 only two months ago, and less than $1,000 a year ago) have attracted speculators, regulators and now even cybersquatters. more

With GDPR coming into effect this May, it is almost a forgone conclusion that WHOIS as we know it today, will change. Without knowing the full details, how can companies begin to prepare? First and foremost, ensuring that brand protection, security and compliance departments are aware that a change to WHOIS access is on the horizon is an important first step. Just knowing that the ability to uncover domain ownership information is likely to change in the future will help to relieve some of the angst that is likely to occur. more

The defining of rights in the UDRP process is precisely what WIPO and ICANN contemplated, but it is unlikely they foresaw the destination of the jurisprudence. Since its inception, UDRP Panels have adjudicated over 75,000 disputes, some involving multiple domain names. (These numbers, incidentally, are a tiny fraction of the number of registered domain names in legacy and new top-level domains, which exceeded 320 million in the first quarter 2017). more

The way the Internet operates drove a wedge between strings of lexical and numeric characters used as marks and alphanumeric strings used as addresses. Domain names were described by Steve Forbes in a 2007 press release as virtual real estate. It is, he said, analogous to the market in real property: "Internet traffic and domains are the prime real estate of the 21st century." more

Unicode's goal, which it meets quite well, is that whatever text you want to represent in whatever language, dead or alive, Unicode can represent the characters or symbols it uses. Any computer with a set of Unicode typefaces and suitable layout software can display that text. In effect, Unicode is primarily a typesetting language. Over in the domain name system, we also use Unicode to represent non-ASCII identifiers. That turns out to be a problem because an identifier needs a unique form, something that doesn't matter for typesetting. more

Before the Internet, the sole competition for strings of characters employable as marks was other businesses vying to use the same strings for their own products and services. National registries solved this competition by allowing businesses in different channels of commerce to register the same strings but prohibiting competitors in the same industries from using identical or confusingly similar marks on the grounds that they were likely (at best) to create confusion and (at worst) to deceive the public. more

On January 24, 2018, ICANN's Business Constituency (BC) and Intellectual Property Constituency (IPC) co-hosted an event to discuss the EU's General Data Protection Regulation (GDPR) and its implications on access to the WHOIS database. ICANN's CEO and General Counsel joined the discussion, as did stakeholders from across the ICANN community. The event was timely and well attended with over 200 participants attending in-person or virtually. more

I am a student of life, learning one hard lesson at a time. In fact, I actually dropped out of my last year of college to start a tech company in a new space called the internet. I was an entrepreneur running an online service prior to the advent of the world wide web in 1992, back when Pine, Usenet, and Gopher ruled the information superhighway. Over the last 25 years, I have learned a great deal about technology adoption cycles by launching six internet companies, each at the forefront of a new technology wave. more

Promoted Post

Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.

Avenue4 LLCRead4635

A World-Renowned Source for Internet Developments. Serving Since 2002.