Ten years ago, the most effective branding exercise the internet registry market has ever seen began. And to celebrate the anniversary, its owner is going to strangle it. At the ICANN meeting in Montreal this month, the Government of Colombia booked a meeting room, prepared a Powerpoint presentation and invited representatives of the world's largest registry operators to attend. Once there, they were offered a rare and valuable opportunity: to take over running of the .co registry.
Our goal was to announce Usenet at the January, 1980 Usenix meeting. In those days, Usenix met at universities; it was a small, comaparatively informal organization, and didn't require hotel meeting rooms and the like. (I don't know just when Usenix started being a formal academic-style conference; I do know that it was no later than 1984, since I was on the program committee that year for what would later be called the Annual Technical Conference.)
SpaceNews recently reported that Elon Musk and his low-orbit space venture Starlink have filed with the International Telecommunications Union (ITU) to launch an additional 30,000 broadband satellites in addition to the 11,927 now in the planning stages. This looks like a land grab and Musk is hoping to grab valuable orbital satellite paths to keep them away from competitors.
A year ago, under the leadership of the Internet Corporation for Assigned Names and Numbers (ICANN), the internet naming community completed the first-ever rollover of the cryptographic key that plays a critical role in securing internet traffic worldwide. The ultimate success of that endeavor was due in large part to outreach efforts by ICANN and Verisign which, when coupled with the tireless efforts of the global internet measurement community, ensured that this significant event did not disrupt internet name resolution functions for billions of end users.
I run a business. For years I've been in the ICANN Business Constituency, holding a series of different positions including Chair. Suffice it to say, I'm absolutely ok with making money and generally speaking, letting markets work. I also care about NGOs. For years our firm worked with PIR on the .NGO project. We got to see up close the role PIR has played as a supporter of NGOs online -- encouraging best practice, helping push out DNSSEC to a global audience, working on DNS abuse issues, supporting the sector.
We knew that Usenet needed some sort of management system, and we knew that that would require some sort of authentication, for users, sites, and perhaps posts. We didn't add any, though -- and why we didn't is an interesting story. The obvious solution was something involving public key cryptography, which we (the original developers of the protocol: Tom Truscott, the late Jim Ellis, and myself) knew about: all good geeks at the time had seen Martin Gardner's "Mathematical Games" column...
I recently stepped into a new role as Chief Purpose Officer of Ethos Capital, a specialized investment firm focused on helping companies drive growth and transformation through technology. In doing so, we are committed to operating ethically, responsibly, and in the best interests of all stakeholders, including employees, customers, vendors and the broader community.
The past week in the 5G world was notable because of some major events in Reno in the 5G race to roll out the full 5G specifications known as Release 16. A set of seven major concurrent industry standards meetings were hosted there over five days last week. The metrics are indicative of who really participates in and shapes the rapidly emerging 5G platforms.
The Paris Peace Forum (PPF), established by the French president Emanual Macron, was picked by the Global Commission for Stability in Cyberspace (GCSC) to launch its final report "Advancing Cyberstability" for good reasons: The Internet isn't just a purely technical issue with some political implications anymore. On the eve of the 2020s, the management of cyberspace is a global problem, a matter of international security, a question of war or peace.
To understand some of our implementation choices, it's important to remember two things. First, the computers of that era were slow. The Unix machine at UNC's CS department was slower than most timesharing machines even for 1979 – we had a small, slow disk, a slow CPU, and – most critically – not nearly enough RAM. Duke CS had a faster computer – they had an 11/70; we had an 11/45 -- but since I was doing the first implementation, I had to use what UNC had. (Log in remotely?