We would like to provide you with a better user experience. Please re-enable Javascript in your web browser.
This article is based on a presentation I made to the ARIN 56 meeting in October 2025. Here I’d like to elevate the typical Regional Internet Registry policy conversations above the day-to-day mundanities of address allocation policies with its vocabulary of address block sizes and needs-based justifications, fairness and efficiency…
The 91st meeting of the RIPE community was held in Bucharest in October this year. It was a busy week and, as usual, there were presentations on a wide variety of topics, including routing, the DNS, network operations, security, measurement and address policies. The following are some notes on presentations…
“Where are you?” is not an easy question to answer on the Internet. The telephone system’s address plan embedded a certain amount of physical location information in the fixed line network, and a full E.164 telephone number indicated your location in terms of your country, and your area within that…
The Australian Network Operators’ Group, AUSNOG, just held its 19th meeting. Rather than simply relate the content of the presentations I’d like to take a few presentations and place them into a broader context to show how such topics fit today’s networked environment. Network Operations and Data Centres Perhaps unsurprisingly…
Most of today’s transport on the public Internet still uses TCP (and in this admittedly sweeping generalization I’ll include QUIC, as QUIC can be seen as an updated form of TCP that happens to use UDP as an encapsulation protocol). TCP does not operate at a fixed transmission rate and…
Background The arrangements regarding the composition and organisation of the provision and operation of authoritative root servers are one of the more long-lasting aspects of the public Internet. In the late 1980’s, Jon Postel, as the IANA, worked with a small set of interested organisations to provide this service. It…
Early models of packet networking used a hop-by-hop paradigm of control. Each intermediate device (a “router” in Internet parlance) would use a control loop with its adjacent neighbour and retransmit any frame that was not explicitly acknowledged as received by the neighbour. Such models were used by the X.25 protocol,…
The Internet Engineering Task Force (IETF) meets three times a year to work on Internet Standards and related operational practice documents. In July of 2025 the IETF met in Madrid (finally, and only after a number of thwarted mis-starts!) with more than a thousand folk in attendance through the week.…
The Internet Engineering Task Force (IETF) meets three times a year to work on Internet Standards and related operational practice documents. In July of 2025 the IETF met in Madrid (finally, and after a number of thwarted mis-starts!) with more than a thousand folk in attendance through the week. The…
Last month, in June 2025, I reported on our progress with the adoption of the QUIC transport protocol. Here I would like to look at the mechanisms used to trigger a client application (typically a browser) to connect to the server using the QUIC transport protocol. A conventional way to…
