The story of computing and communications over the past eighty years has been a story of quite astounding improvements in the capability, cost and efficiency of computers and communications. If the same efficiency improvements had been made in the automobile industry cars would cost a couple of dollars, would cost fractions of a cent to use for trips, and be capable of travelling at speeds probably approaching the speed of light!
Dave Taht died on April 1st. I met him only recently, and never in person, but his passing saddens me. His technical work and evangelism have improved the Internet, and I will give some examples of his contributions to the Internet community and users, but I am sad because he was a good person -- idealistic, unselfish, open, and funny. I'll miss him. First, his contributions, then his values.
At the Internet Governance Forum (IGF) 2024 in Riyadh, the Internet Standards, Security and Safety Coalition (IS3C) released a new tool: 'To deploy or not to deploy, that's the question. How to convince your boss to deploy DNSSEC and RPKI'. In this report, IS3C advocates mass deployment of these two newer generation, security-related internet standards, as their deployment contributes significantly to the safety and security of all internet users.
At first glance, this book looks like another history of the Internet, but it is much, much more. The authors use their engineering and scholarly understanding of what constitutes Internet history to identify forks in the digital road and key past decisions that shaped the Internet's path. The first part of the book maps out the core technical and policy decisions that created the Internet.
If you operate an Internet Exchange Point (IXP) or are interested in creating one, the Internet Society has a “Sustainable Peering Infrastructure” funding program that is open for applications until this Friday, September 6, 2024... Grant funds from USD $5,000 up to $50,000 are open to all regions and are available to assist in equipment purchases (switches, optic modules, servers, and routers), training, capacity building, and community development.
Digital communications systems always represent a collection of design trade-offs. Maximizing one characteristic of a system may impair others, and various communications services may choose to optimize different performance parameters based on the intersection of these design decisions with the physical characteristics of the communications medium.
There have been a number of occasions when the Internet Engineering Task Force (IETF) has made a principled decision upholding users' expectations of privacy in their use of IETF-standardised technologies. (Either that, or they were applying their own somewhat liberal collective bias and to the technologies they were working on!) The first major such incident that I can recall is the IETF's response to the US CALEA measures.
There have been a number of occasions when the Internet Engineering Task Force (IETF) has made a principled decision upholding users' expectations of privacy in their use of IETF-standardised technologies. (Either that, or they were applying their own somewhat liberal collective bias to the technologies they were working on!) The first major such incident that I can recall is the IETF's response to the US CALEA measures.
From the creation of DNSAI Compass ("Compass"), we knew that measuring DNS Abuse1 would be difficult and that it would be beneficial to anticipate the challenges we would encounter. With more than a year of published reports, we are sharing insights into one of the obstacles we have faced. One of our core principles is transparency and we've worked hard to provide this with our methodology.
Project Liberty's Institute sat down with Wendy Seltzer, an advisor to the Decentralized Social Networking Protocol (DSNP). Wendy was counsel to the World Wide Web Consortium (W3C), and has served on the boards of The Tor Project, Open Source Hardware Association and ICANN.
Interested in learning more about routing security? How it can affect your connectivity supply chain? What are best practices for enterprises and organizations? What is the role of CSIRTs in securing routing? What are governments doing now, and planning to do in the future around routing security?
ome 50 years ago, at the Palo Alto Research Centre of that renowned photocopier company Xerox, a revolutionary approach to local digital networks was born. On the 22nd of May 1973, Bob Metcalf authored a memo that described "X-Wire," a 3Mbps common bus office network system developed at Xerox's Palo Alto Research Center (PARC).
Project Liberty's Institute sat down with Dave Clark, an early contributor to the TCP/IP protocols that built and run the Internet, and one of the expert advisors on DSNP, the Decentralized Social Networking Protocol. Dave Clark is Senior Research Scientist at MIT's Computer Science and Artificial Intelligence Laboratory (CSAIL) and Fellow of the National Academy of Engineering and the American Academy of Arts and Sciences.
The idea for Ethernet was born fifty years ago in May 1973 when Robert Metcalf coined the word Ethernet. He had been studying ALOHAnet, developed at the University of Hawaii in 1971 and was the first public demonstration of a wireless packet data network. Metcalf used the work Ethernet as a reference to luminiferous aether, a concept postulated in the 17th century to explain how light could be transmitted through a vacuum.
At Verisign, we believe that continuous improvements to the safety and security of the global routing system are critical for the reliability of the internet. As such, we've recently embarked on a path to implement Resource Public Key Infrastructure (RPKI) within our technology ecosystem as a step toward building a more secure routing system. In this blog, we share our ongoing journey toward RPKI adoption and the lessons we've learned as an operator of critical internet infrastructure.