Internet Protocol

Happy Birthday BGP

The first RFC describing Border Gateway Protocol (BGP), RFC 1105, was published in June 1989, thirty years ago. By any metric that makes BGP a venerable protocol in the Internet context and considering that it holds the Internet together, it's still a central piece of the Internet's infrastructure. How has this critically important routing protocol fared over these thirty years, and what are its prospects? Is BGP approaching its dotage or will it be a feature of the Internet for decades to come? more

Leaving it to the Last Second - The Leap Seconds Conundrum

Thanks to the moon, the earth's rate of rotation is slowing down. It's a subtle interaction and the modeling of planetary dynamics predicts that the earth's rotation should be slowing down by an average of 2.3 milliseconds per century. But this is not quite so uniform... So what? Maybe we can start by looking at how we've defined time over history... It's only been in recent decades that we've turned our attention to timekeeping with an obsessive level of detail that rivals, and maybe even surpasses, train spotting. more

Failed Expectations: A Deep Dive Into the Internet’s 40 Years of Evolution

In a recent workshop, I attended, reflecting on the evolution of the Internet over the past 40 years, one of the takeaways for me is how we've managed to surprise ourselves in both the unanticipated successes we've encountered and in the instances of failure when technology has stubbornly resisted to be deployed despite our confident expectations to the contrary! What have we learned from these lessons about our inability to predict technology outcomes? more

The Internet And Its Governance: Where Should We Look For Models?

The US Department of Commerce (DOC) has recently signed a new contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for one more year. ICANN and the DOC are to continue to work together to design an organizational form that is suitable to administer and control the infrastructure of the Internet. That infrastructure includes the IP numbers, which are critical to the functioning of the Internet protocol TCP/IP. These numbers must be unique for the Internet to continue to function. The infrastructure also includes the protocols that make the Internet possible. Protocols involve the conventions or agreements that each network that is part of the Internet accepts in order to make communication possible across the boundaries of the different technical and political and administrative entities that comprise the networks of the Internet. Another component of the Internet's infrastructure is the domain name system (DNS). This system includes the names that identify various sites on the Internet and the translation of those names into IP numbers via the system of computers that make the one to one mapping between names and numbers. more

Fifty Years On – What to Expect in the Next 50 Years of the Internet

When did the Internet begin? It all gets a bit hazy after so many years, but by the early 1970s, research work in packet-switched networks was well underway, and while it wasn't running TCP at the time (the flag day when the ARPANET switched over to use TCP was not until 1 January 1983) but there was the base datagram internet protocol running in the early research ARPA network in the US. Given that this is now around 50 years ago, and given that so much has happened in the last 50 years, what does the next 50 years have in store? more

Human Network, Human Challenges

It has now been about eight months since I joined the Internet Society as the Director of Deployment & Operationalization and I still get asked on a fairly regular basis "what do you do?" Well, with ISOC's Chief Internet Technology Officer Leslie Daigle's recent departure, and with my time here having exceeded both my first 120 days and my first 6 months, this seems like the right moment to reflect on my brief tenure here so far and perhaps pontificate a bit on where we're going - and why. more

Watch Live - What Does “Success” For IPv6 Look Like? (Briefing Panel on Nov 5)

Now that IPv6 deployment is happening in major networks around the world, the question becomes -- what does "success" look like for IPv6? How much IPv6 traffic is "enough"? What are major milestones we should be tracking in IPv6 deployment? What is next for IPv6? more

NFV Orchestration Without Network Visibility: OS MANO Needs Operational Improvements

Open Source (OS) Management and Orchestrations (MANO) is a European Telecommunications Standards Institute (ETSI) initiative that aims to develop a Network Function Virtualization (NFV) MANO software stack, aligned with ETSI NFV. The main goal of MANO is to simplify the onboarding of virtual network components in telco cloud data centers. The initiative has gained impressive momentum among leading Communication Service Providers (CSPs) around the world as part of their NFV programs. more

House of Cards

Time flies. Although it was over 18 months ago, it seems just like yesterday that a small Czech provider, SuproNet, caused global Internet mayhem by making a perfectly valid (but extremely long) routing announcement. Since Internet routing is trust-based, within seconds every router in the world saw this announcement and tried to pass it on. Unfortunately, due to the size of this single message, quite a few routers choked -- resulting in widespread Internet instability. Today, over a year later, we were treated to a somewhat different version of the exact same story. more

Notes from the DNS Privacy Workshop at NDSS 2021

For many years the consuming topic in DNS circles was that of the names themselves. If you wind the clock back twenty years or so, you will find much discussion about the nature of the Internet's namespace. Why were there both generic top-level labels and two-letter country codes? If we were going to persist with these extra-territorial generic country codes in the namespace, then how many should there be? Who could or should manage them? And so on. more

Who Says You Can’t Have Fun at The IETF?

A new IETF draft has been published that specifies a new HTTP status code for legally restricted resources. That is, if the government restricts your access to the web page, return this code (similar to how something not found is a 404). The error code: 451. From the Internet Draft, if the user tries to access a page, but access to the page is restricted by the government, display the following... more

Network Design: If You Haven’t Found the Tradeoff…

This week, I ran into an interesting article over at Free Code Camp about design tradeoffs... If you think you've found a design with no tradeoffs, well... Guess what? You've not looked hard enough. This is something I say often enough, of course, so what's the point? The point is this: We still don't really think about this in network design. This shows up in many different places; it's worth taking a look at just a few. more

Thinking Outside The ICANN Box: Creating A Prototype Based On Internet Experience - Part I

In research, one of the important steps is to identify the problem that needs exploration. Another step is to identify how to find a solution. Once it is possible to agree on the nature of the problem, then it begins to be a matter of how to approach the problem. more

Filtering Spam at the Transport Level

An interesting new paper from the Naval Postgraduate School describes what appears to be an interesting new twist on spam filtering, looking at the characteristics of the TCP session through which the mail is delivered. They observe that bots typically live on cable or DSL connections with slow congested upstreams. ... This paper tries to see whether it would be practical to use that info to manage spam in real time. more

Communities of Things

When I want to go to a website, I just type in the URL, and I'm there. Sure, we had to get a subscription from a service provider and set up our devices, but that was a one-time thing. As we move into a world of many connected devices, it's no longer a one-time thing. Today, creating connected devices and services requires thinking about all the mechanics and networking and onboarding and providers. more