Home / Blogs

A Quick Primer on Internet Peering and Settlements

The business world today features many complex global service activities which involve multiple interconnected service providers. Customers normally expect to execute a single paid transaction with one service provider, but many service providers may assist in the delivery of the service. These contributory service providers seek compensation for their efforts from the initial provider. However, within a system of interdependent providers a service provider may undertake both roles of primary and contributory provider, depending on the context of each individual customer transaction. In a system where there are many mutual service provision transactions it is common to see the use of a balance of services used in place of individual transaction payments between providers, and the use of inter-provider financial settlements as a means of reconciling residual imbalances in the accounting of such mutual service provision tasks. In this article I’d like to describe how this has been applied to the Internet, and look at the Internet’s approach to interconnection and financial settlements.

For example, airlines these days have codeshare agreements where a customer may purchase a ticket from one airline where the flight is operated by another airline. Given that one provider has received the revenue for the service and another provider has incurred the costs of providing the service, there is a need to pass some form of payment from one provider to the other. Rather than undertaking a separate inter-provider financial transaction for each codeshare journey, airlines can use a more efficient arrangement that uses inter-provider settlements. Each airline retains the original ticket sales revenue, and accumulates amounts in credit and debit from the execution of the codeshare flights between providers. They then settle any residual imbalance in the mutual service account with single financial transaction at the end of each settlement period.

The Internet operates in a similar fashion: its services are provided by some 40,000 constituent network service providers that must not only interconnect with one another, but also execute a set of inter-provider arrangements that ensures that each service provider is duly compensated for their respective efforts in providing end-to-end services to the network’s clients.

The Telephony Model

To look at the Internet interconnection and settlement structure, it is useful to look at its immediate predecessor, the inter-provider financial settlements within the telephony domain.

The retail model for telephony is, for the most part, a model that appears to have been borrowed from the postal service, where the caller pays its local carrier for the entire cost of the call, while the called party pays nothing to receive the call. When both the caller and the called party are connected to the same carrier then this is quite straight forward: the carrier charges the caller for the entire cost of the call. When we take the same model and apply it to international phone calls, then the common intent is to preserve the same simple retail model: the caller pays the cost of the call. Given that this now involves the telephone carriers undertaking mutual service provision activities, the arrangement that the telephone industry came up to redress any residual imbalances in mutual service provision with was the concept of inter-carrier call accounting financial settlements.

Within the framework of this interconnection model, two national carriers interconnect at an agreed handover point, and, as part of this interconnection, they establish a call minute settlement rate, which is the rate one carrier bills the other for the residual imbalance of terminated calls that originate from the other carrier’s network and are passed to the terminating carrier at the handover point for termination in the other carrier’s network.

The calling provider receives a payment from the caller for the entire call, and accumulates a debit to the terminating provider for the termination costs of the call. The terminating provider receives no payment from the called party, and accumulates a credit from the calling provider for the same call termination cost. A periodic financial payment from one provider to the other allows the two providers to “settle” the net of these debit and credit accounts, and thereby providing a form of equity of cost distribution in meeting the costs of the calls made between the two providers.

Calls are measured in units of call minutes in the interconnection domain, and the debit and credit accounts are measured in units of call minutes. Where there is equity of call accounting rates between the two providers, the bilateral inter-provider financial settlements are used in accordance with originating call-minute imbalance, in which the provider hosting the greater number of originating call-minutes pays the other party according to a bilaterally negotiated rate per residual call minute imbalance as the mechanism of cost distribution between the two providers.

It’s notable that the general bilateral telephony settlement model does not admit multi-party transit arrangements. Such arrangements are handled using further forms of inter-carrier agreements where a carrier may hand-off call requests to a third party carrier at some mutually agreed call minute rate, and similarly a carrier may engage another carrier to act as its call terminating carrier for an agreed share of the call termination settlement fees.

Because the telephony model includes local monopolies there is no inherent market-based capability that prevents a carrier setting its call termination settlement rates to a level that is in excess of its actual call termination costs. The resultant distortions and economic inefficiencies in the inter-carrier domain have acted as a powerful driver behind the increasing interest from some high volume calling party carriers in voice-over-IP (VoIP) solutions that bypass these call accounting settlements. In such situations the originating carrier uses VoIP trunking instead of call handover at the inter carrier interconnection point, and terminates the call request within the terminating carrier’s network as a regular internal call. This allows the origination carrier to avoid the call termination settlement rates. The end customer of these VoIP trunk services benefit from a lower priced service offering, with an associated commercial pressure on the terminating carrier to remove the monopoly rental component from its call termination settlement rates. It would be a highly retrograde step to see a new wave of international regulation that entrenches these inefficient distortions of monopoly rentals in the telephone sector by attempting to prevent, by regulation, the use of alternate voice trunking solutions, such as VoIP, in the international telephony domain.

Another by product of this monopoly-based distortion in the inter-carrier settlement rates is the emergence of a lobby group who are current beneficiaries of these arrangements who, perhaps understandably, are highly motivated to see the continuance of these arrangements and the potential extension of these arrangements to encompass the Internet. This contemplated extension of interconnection regulations from telephony into the Internet environment again represents a retrograde step in terms of introducing regulatory distortions and significant inefficiencies into what is at present a functional and efficient Internet interconnection market, as we’ll examine in the next section.

Internet Considerations

There are a number of important technical differences that exist between the telephony and Internet models of carrier interconnection. These differences are fundamental, and have confounded all attempts to cleanly map telephony interconnection models into the Internet environment. The most critical of these differences are described as follows:

There is no “call”

Unlike a telephony call, there is no concept of state initiation in an IP network to pass a call request through a network and lock down a network transit path in response to a call response. The network undergoes no state change in response to a packet being passed through the network, and therefore, no means is readily available to the carriage service operator to identify that a call has been initiated, and by which party.

Packets may be dropped

When a packet is passed across an interconnection from one carriage service provider to another, no firm guarantee is given by the second provider that the packet will definitely be delivered to the destination. The second provider, or subsequent providers in the packet’s transit path, may drop the packet for quite legitimate reasons, and will remain within the Internet Protocol specification in so doing. Indeed, the TCP protocol uses packet drop as a rate-control signal, necessary for its efficient operation. The broader implication here is that the quality of the packet transit service that one carrier may anticipate from it’s adjacent carrier peer when passing packets across an interconnection is inherently undefined.

Packet paths are not necessarily symmetric

The inter-carrier path a packet takes from one client to another is not necessarily the same path that a packet takes in the reverse direction. This path asymmetry means that there is no direct analogy to the virtual circuit model used in telephony. When two clients, A and B, exchange traffic a carrier may only see traffic flowing in the direction from B to A and not see any traffic from A to B. It’s not that there is no such traffic, but that the traffic in the opposite direction uses a different inter-carrier transit path through the network. One outcome from this observation is that in a hypothetical case of traffic flow-based inter-carrier service accounting, when a carrier sees just one half of a traffic flow, it’s unclear how a carrier can reliably determine whether it should claim a service debit or a credit from its adjacent carriers in passing the traffic towards its intended destination.

There is no network-based resource management regime

In the telephone world the establishment of a virtual circuit to support a voice call can be viewed as an exclusive claim on a unit of capacity in the network that excludes all other potential users of that capacity. However, in the Internet, there is no concept of resource exclusion, in other words, the Internet does not use a network-based management regime to allocate its resources to support individual transactions. The end-to-end architecture of the Internet places the onus of responsibility for resource management and allocation on the collection of end systems that generate traffic at any point in time. In this architecture its conventional to see traffic flows across the network being regulated by the Internet’s transport protocol, TCP. Each traffic session is adaptive in such a manner that it will attempt to make the most efficient use of the entire set of network resources, while at the same time attempting to sustain a stable state were each individual traffic flow claims an equal volume of network resources for itself.

Internet Interconnection Arrangements

The retail model used by the Internet is not one of “sender pays,” nor one of “receiver pays”. The retail service is not one where either the sender or the receiver funds the entire end-to-end transit of a packet through the Internet as part of the retail tariff structure for Internet services. Indeed, given that the end-to-end transmission of a packet is not even an assured outcome in the Internet architecture, such a tariff model would be a mismatch to the nature of the service provided by the underlying IP network. The Internet retail model is one where a customer contracts with a carriage service provider for an access service. This is a customer/provider relationship, where the customer funds its carriage service provider for all packets that are sent or received by the customer.

The translation of this retail service model into the inter-carrier interconnection environment is one that preserves this particular form of customer/provider relationship at the retail edge of the network, translating in into the context of two interconnecting carriers. A carrier that is a customer of another carrier pays for an access service, where the customer carrier funds all traffic to and from its provider (or upstream transit) carrier.

Who is the provider and who is the customer in such an arrangement is not pre-determined by any objective or regulatory determination. It is based on a self-assessment by each carrier as to their own value and the value that the other carrier is bringing to the proposed interconnection.

If one carrier believes that it is bringing greater value to the interconnection then it would naturally only contemplate the interconnection if it were to be the provider and the other carrier to be its customer. If the other carrier reaches a similar conclusion that the other party is providing a greater value to the interconnection than the interconnection would most likely proceed to the next step of negotiation of service terms and conditions between provider and customer that recognizes the extent of the difference in relative value. Sometimes this takes the form of a conventional wholesale relationship, while at other times more creative labels are used for much the same form of customer relationship, such as “paid peering”.

If the other carrier reaches the conclusion that it too was bringing a greater value to the interconnection, and it should assume the role of provider in an interconnection, then the mismatch in relative value perceptions would imply that any attempt to execute an interconnection between the two carriers would not be stable. The typical outcome of such a failure to directly interconnect is not necessary one that results in partitioning of the network. A more typical outcome in such a case is that any traffic that is exchanged between customers of the two carriers would be passed through indirect transit arrangements.

There is another possible outcome of this self-assessment of perception of value in an interconnection, where both parties see approximately equal mutual benefit in interconnecting. Here a “Sender Keep All” (SKA) relationship is appropriate, where the parties exchange traffic in both directions but do not exchange any funds in either direction. These SKA arrangements are typically referred to as “peer” relationships.

In all of these relationships, the parties themselves do not have to agree on what that measured value or scope may be in absolute terms. Each party makes an independent assessment of the value of the interconnection, in terms of the perceived size and value it brings to the interconnection and the value of the assets that the other party brings to the interconnection. If both parties reach the conclusion that, in their respective terms, a net balance of value is achieved, then the SKA interconnection is a stable one. If one party believes that it is bringing a greater value to the interconnection than the other then any SKA interconnection would result in leverage of its investment by the smaller party, and an SKA interconnection would be unstable.

These two forms of interconnection, namely a customer/provider relationship and a SKA peer relationship, form the basis of the entire set of connections that collectively support a coherent and fully connected Internet.

An outcome of this interconnection model is that the service providers’ options for business optimization includes a strong incentive of increasing the size, scope and efficiency of its service provider operation within the consumer and wholesale market space, so that non-financially settled SKA peering can be negotiated with larger providers, thereby reducing the additional outlays required to purchase upstream transit services to complement these peering connections. This in tern results in an internet which is highly interconnected, which, in turn improves both the performance and operational costs of the service offering, both of which translate to improved consumer offerings in a highly competitive service industry.

A Market-based Approach to Interconnection

In many ways interconnection in the Internet can be seen as the operation of an open market within the broader framework of a generally deregulated industry, where each party brings assets to the interconnection market place and attempts to reach mutually satisfactory arrangements with other actors in the same market. Each party is attempting to reach precisely the same outcome, namely comprehensive connectivity, and to do so in a maximally efficient manner such that it minimizes its expenditure while meeting its requirements for connectivity and capacity.

Over twenty years of experience in operating this market-based framework for Internet connectivity has shown that it is capable of scaling from a few dozen service providers to currently over 40,000 component networks, and at the same time it has proved to be capable of sustaining its objective, namely that of universal connectivity across the entire Internet’s interconnection domain. It is also the case that the Internet has been able to achieve this outcome without the imposition of overriding regulatory impost, and with ever increasing price performance service offerings for the end consumer. The evidence from this experience points to a conclusion that this market operates in an efficient manner, and this efficiency directly translates into cost efficiencies in the retail market for Internet services.

The ultimate beneficiary of this form of market-based Internet connection in the Internet is the end consumer, who, for the price of a local access service across the last mile, gains access to the entire world of the Internet.

By Geoff Huston, Author & Chief Scientist at APNIC

(The above views do not necessarily represent the views of the Asia Pacific Network Information Centre.)

Visit Page

Filed Under


Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

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.

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



New TLDs

Sponsored byRadix


Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

Brand Protection

Sponsored byCSC

Domain Names

Sponsored byVerisign

IPv4 Markets

Sponsored byIPv4.Global