Telephone numbers — global numbering, NANP, toll-free, and the lifecycle of a number

A telephone number is not a name and it is not a serial number. It is a routing identifier with regulatory weight, a jurisdictional structure, a lifecycle, and a set of governance bodies that maintain it. Most discussions of caller authentication skip past all of that and treat the number as an opaque token — but the number is the thing being authenticated, and what STIR/SHAKEN can honestly assert about a call depends entirely on how the underlying number is structured, assigned, and governed. This section is that grounding.

The through-line worth holding onto is that a number’s meaning is not intrinsic; it is administered. Whether a number is geographic or toll-free, who is authorized to use it, whether it has been ported, and whether it was recently reassigned to a new subscriber are all facts maintained in registries and databases, not encoded in the digits themselves. The trust framework is, in large part, the project of making those administrative facts cryptographically checkable at call time.

Global numbering: E.164

At the global level, telephone numbers are governed by E.164, the ITU-T recommendation that defines the international public numbering plan. An E.164 number is at most fifteen digits and begins with a country code — one to three digits that the ITU assigns to nations and to special “global” services. The country code determines which national authority governs the rest of the number: the ITU hands a country its code, and the country’s own regulator and numbering administrator decide how the digits beneath it are structured and assigned. This is why “whose rules apply to this number” is answered first by the leading digits, and why cross-border trust frameworks have to reason about country codes before anything else — a fact that matters directly when a foreign-originated call arrives using a North American number.

E.164 is also the canonical form the rest of the stack builds on. When a number is written as +1 202 555 0143, the + and the full country-code form is the E.164 representation, and it is this form that ENUM maps into DNS, that a PASSporT carries, and that a certificate’s authorization list is expressed in. Getting the canonical form right is unglamorous and load-bearing.

North American numbering: the NANP

North America — the US, Canada, and a set of Caribbean nations — shares a single country code, +1, under the North American Numbering Plan (NANP). A NANP number has the familiar ten-digit NPA-NXX-XXXX structure: the NPA is the three-digit area code, the NXX is the central-office code (historically tied to a physical switch), and the final four digits are the line number. This structure is the reason a number used to imply a location — the NPA-NXX pointed at a rate center, a geographic exchange — and it is also why that implication has steadily broken down as numbers became portable and nomadic.

The plan is maintained through defined administrative roles rather than by any one company in perpetuity. The North American Numbering Plan Administrator (NANPA) assigns area codes and central-office codes; the Pooling Administrator manages the finer-grained allocation of numbers in thousands-blocks so that carriers draw only the inventory they need; and the whole apparatus operates under FCC oversight in the US, with the North American Numbering Council (NANC) advising on policy. I served across a decade of NANC’s Call Authentication Trust Anchor working-group reports, which is where much of the numbering-and-authentication policy was worked out; the NANC CATA page covers that history. As geographic assignment gives way to number pooling and portability, the plan’s scarcity pressures — area-code exhaust, overlays, and conservation measures — become ongoing administrative work rather than one-time events.

Toll-free: a different set of rails

Toll-free numbers — the 8YY codes (800, 888, 877, 866, 855, 844, 833) — look like ordinary NANP numbers but run on entirely different infrastructure and governance. A geographic number routes on its digits; a toll-free number does not route on its own, it is looked up. Each toll-free number is associated in a central registry with a Responsible Organization (RespOrg) — the entity that manages the number on behalf of the subscriber — and a routing record that says where calls to it should actually terminate. Dialing a toll-free number triggers a query against that registry to find the routing, which is why toll-free numbers can point anywhere and change instantly.

This separate world has its own identifiers and its own administration. A RespOrg is identified by a RespOrgID, which — like a carrier’s OCN — serves as a valid authorization value in a STIR certificate for signing toll-free traffic; the carrier-identity page ties those identifiers together. The registry itself (long known by its legacy name, the SMS/800 system, now the Toll-Free Number Registry) is a distinct administrative function from geographic numbering. The reason this matters for trust is that toll-free is a Rights-to-Use model rather than an assignment-to-a-carrier model: the subscriber holds the number and directs a RespOrg to manage it, so “who is authorized to use this number” has a different shape than it does for geographic numbers, and the attestation logic has to account for that.

Portability

Local Number Portability (LNP) is the mechanism that lets a subscriber keep a number when changing carriers, and it is the single change that did the most to sever a number from its geographic and carrier meaning. It works through a Location Routing Number (LRN): when a number is ported, the network no longer routes on the number’s own NPA-NXX but on a separate LRN that points at the subscriber’s current carrier, resolved through a number-portability database. The number the caller sees stays the same; the routing identifier underneath it changes.

The consequence for trust is direct. Once a number can be ported, the digits no longer tell you which carrier is authoritative for it — that fact has to be looked up, and it changes over time. Any framework that wants to assert “this carrier is authorized to originate calls from this number” is really asserting something about the current state of the portability and assignment records, not about the number’s face value. Portability is why authorization has to be a live, checkable fact rather than an inference from the NPA-NXX.

The lifecycle of a number

A number moves through defined stages, and each one has trust implications. It starts as available inventory administered by the numbering authorities, is allocated to a carrier (in blocks, or increasingly in thousands-blocks through pooling), and the carrier then assigns an individual number to a subscriber. When a subscriber gives it up, the number is disconnected and enters an aging period — held out of circulation for a stretch of time so that calls and messages meant for the previous holder taper off — before it is reclaimed and eventually reassigned to someone new. The exact status vocabulary differs by domain — geographic pooling tracks numbers as available, assigned, reserved, aging, and administrative, while the toll-free registry uses its own set including spare, reserved, and working — but the shape of the lifecycle is the same.

That reassignment step is a live problem the trust framework has had to address directly. A number that legitimately belonged to one person last month can belong to a different person today, which breaks any system that treated the number as a durable identifier for an individual — from two-factor authentication to autodialer consent. The FCC’s Reassigned Numbers Database exists precisely so a caller can check whether a number has been reassigned since consent was obtained. The lifecycle, in other words, is not administrative trivia: it is the reason a number is a rotating identifier, and any trust claim attached to one has to be anchored in time.

Why this matters for the framework

Every stage above feeds the authentication story. What STIR/SHAKEN attestation can honestly claim depends on the number’s type and state: an A-level attestation means the originating provider knows the customer and confirms their right to use the number, which is a claim about assignment and portability records, not about the digits. Toll-free, geographic, and international numbers each carry different authorization models. Enforcement levers like Do Not Originate and the Robocall Mitigation Database operate on number- and provider-level facts that only make sense against this structure. And ENUM is one attempt to make the number-to-routing mapping queryable in the first place.

Where this fits

This section is foundational context for the trust work throughout the library. The carrier-identity page ties the OCN/RespOrgID/Filer-ID identifier stack together; trust governance covers the policy and enforcement layered on top; ENUM covers the DNS-based mapping of numbers to routing; and the attestation levels page shows how a number’s structure determines what an attestation can mean. The planned sub-pages will take global numbering, the NANP, toll-free, portability, and the lifecycle each to the depth a working engineer or policy reader needs.