A Proposal for Long-Term Expansion of the North American Numbering Plan (NANP) to 11 Digits

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 22 December 2026.¶

Copyright Notice

Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶

Table of Contents

1. Executive Summary

The North American Numbering Plan (NANP), which governs the 10-digit telephone numbers used across the US, Canada, and partner nations, faces eventual exhaustion of its numbering capacity. Current stopgap measures — area code overlays and number pooling — extend the system's lifespan but compound routing complexity and degrade user experience.¶

2. Introduction

The NANP currently utilizes a fixed-length 10-digit numbering format (NPA-NXX-XXXX). Growth in telecommunications services, device proliferation, and number portability has steadily increased demand for numbering resources.¶

Mitigation strategies such as overlays and thousands-block number pooling have delayed exhaustion but introduce increasing complexity in routing, administration, and user experience.¶

This document explores a uniform expansion of NANP numbers to 11 digits as a long-term solution.¶

This proposal preserves fixed-position digit parsing, avoiding variable-length interpretation and timing-based ambiguity. This property is a primary design objective, as it minimizes required changes to existing switching and routing infrastructure.¶

3. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

4. Definitions

CP:

is Cellular Provider, the service provider for a caller using cellular telephony.¶

IXC:

Interexchange Carrier - the organization that carries a call between the caller's service provider and the called party's service provider where the caller's service provider does not serve the area of the called party.¶

Jeopardy: 

Jeopardy is the condition where an NPA is in danger of running out of available NXXs to use for new telephone subscribers, requiring a freeze on the issuance of further subscriber numbers in that NPA until more NXXs become available.¶

LEC:

Local Exchange Carrier, the service provider for a caller using a landline or VoIP service, the organization that provides dial tone and carries a call to the called party where they are within the service area of the LEC, or transfers the call to an IXC when the called party is outside its service area.¶

N versus X:

In the context of a telephone number, N is used to indicate a digit that is restricted to values of 2 through 9, while X indicates an unrestricted digit with values 0 through 9.¶

NPA:

The area code, or first three digits of the 10-digit telephone number. This document will use both 'area code' and 'NPA' interchangeably, generally with NPA used when discussing technical and implementation issues, and area code being used when discussing issues faced by subscribers and the public.¶

NPAX:

The new area code, or first four digits of the new 11-digit telephone number. This proposal recommends expansion of the NPA field by 1 digit and provides an expansion of the entire telephone number to 11 digits.¶

NXX:

The prefix, or digits four through six of the 10-digit telephone number, or first three digits of the subscriber number. This field is to remain unchanged, but is moved to digits five through seven of the new 11-digit telephone number.¶

SIT tone:

A Special Information Tone (SIT) is a standardized, three-beep audio signal (typically 950/1400/1800 Hz) played before a recorded announcement to indicate a telephone call has failed.¶

Subscriber number:

The portion of the telephone number following the NPA or NPAX. It remains unchanged at seven digits, but is moved from positions four through ten of the telephone number, to positions five through eleven.¶

Telephone number:

The entire number of the party to be called, consisting of either¶

• On 10-digit systems, the three-digit NPA, three-digit NXX, and four-digit XXXX.¶

• On 11-digit systems, the four-digit NPAX, three-digit NXX, and four-digit XXXX.¶

VoIP:

Voice Over IP, or telephone service where the call initiates from or terminates via the Internet.¶

XXXX:

The last four digits of the subscriber number, or line number, digits seven through ten of the 10-digit telephone number. This field is also to remain unchanged, but is moved to digits eight through eleven of the new 11-digit telephone number.¶

5. Problem Statement

The finite capacity of the current NANP is not a hypothetical concern but an eventual certainty. According to [NANPA-OCT2025] NANPA's October 2025 NANP Exhaust Analysis [NANPA-2025-10], the NANP is projected to exhaust available numbering resources between 2052 and 2060, depending on demand growth rates. The baseline projection, using an average annual CO code demand of 5,213 codes, places exhaustion in 2060. A sensitivity analysis using demand 20% above baseline projects exhaustion as early as 2052. These projections assume a pool of 680 usable NPAs; the remainder of the 800-NPA address space is reserved or unavailable, including 80 NPAs explicitly held in reserve for future NANP expansion — an implicit acknowledgment by the standards community that structural expansion will eventually be required.
This is an even shorter timeline than estimated in [NANPA-APR2025], only six months earlier.¶

The current NANP faces several challenges:¶

• Finite NPA capacity under existing numbering rules¶

• Fragmentation of numbering resources due to allocation practices¶

• Growing operational complexity in routing and database systems¶

• Long lead times required for major numbering plan changes¶

A long-term solution should address these challenges while preserving fixed-length numbering. Variable-length telephone number schemes are explicitly rejected: they introduce timing-based ambiguity, complicate digit analysis at every layer of the switching and routing stack, increase validation burden across interconnected systems, and create inconsistent user experiences across regions and carriers. Fixed-length numbering is a foundational property of the NANP and must be preserved in any expansion.¶

All feasible approaches to expanding NANP numbering capacity introduce some degree of disruption. The proposed expansion of the NPA is considered the least disruptive option, as it preserves the existing hierarchical structure of the numbering plan and minimizes changes to subscriber numbering and routing semantics.¶

6. Design Goals

The proposed solution is guided by the following goals:¶

• Maintain fixed-length numbering¶

• Minimize changes to existing routing logic¶

• Preserve compatibility with existing numbering structures¶

7. Non-Goals

The following approaches are explicitly not considered desirable:¶

• Variable-length telephone numbers¶

• Region-specific numbering formats¶

• Frequent or repeated structural changes to the numbering plan¶

• Solutions requiring rapid or "flash cut" transitions¶

8. Proposed Expansion Model

This document is a proposal to expand NANP numbers from 10 to 11 digits by extending the NPA from three digits to four digits. This ensures that existing fixed-position digit parsing logic can be extended with minimal modification, avoiding the need for timing-based or variable-length interpretation.¶

Existing numbers:¶

  NPA-NXX-XXXX

Expanded format:¶

  NPAX-NXX-XXXX

During initial deployment, the fourth digit added to the NPA to form the NPAX MUST be selected such that it does not conflict with existing digit patterns used to identify the first digit of NXX codes. Under current NANP rules, the first digit of an NXX is restricted to values 2 through 9.¶

By selecting 0 or 1 for the additional NPA digit, the boundary between the expanded NPAX and the following NXX remains unambiguous. This allows existing digit analysis algorithms to distinguish between legacy 10-digit and expanded 11-digit numbers using a simple examination of the fourth digit.¶

Restricting the fourth digit initially to a single value minimizes required changes to routing logic and reduces deployment cost.¶

This property allows existing fixed-position digit analysis logic to be extended with minimal modification, avoiding the need for timing- based disambiguation, interdigit timeout adjustments, or variable- length parsing mechanisms.¶

A single value (0 or 1) SHALL be used consistently across all NPAs during the initial deployment phase to ensure uniform behavior across networks. Uniformity avoids user confusion, simplifies parsing, and prevents mixed national behavior during migration.¶

Example:¶

  213-555-1234  (legacy)

  2130-555-1234 (expanded)

Or:¶

  303-555-1234  (legacy)

  3031-555-1234 (expanded)

A telephone switching system processes a telephone number using the following logic:¶

1. Scan fourth digit of number.¶

2. If 0 or 1, process as NPAX.¶

3. Else, process as NXX.¶

This proposal preserves the semantic structure of the number.¶

• The NPAX field preserves the existing role of the NPA field, whether geographic, overlay, toll-free, or service-specific.¶

• NXX is still used as the routing block.¶

• XXXX is still the subscriber line number.¶

The widespread adoption of overlay area codes has fundamentally altered the NANP environment. A return to strictly geographic, non-overlapping area codes is no longer practical. The proposed approach assumes the continued existence of overlays and does not attempt to reverse this trend.¶

The designation of 988 as a nationwide service code required the elimination of 7-digit dialing in affected areas, accelerating the transition to uniform 10-digit dialing across the NANP. As a result, this proposal does not impact legacy 7-digit dialing, as that capability has already been largely eliminated.¶

This approach ensures that numbering expansion occurs at the highest level of the NANP hierarchy, avoiding disruption to lower-level components such as routing prefixes and subscriber numbers.¶

This method preserves fixed-field positional parsing, avoiding the need for timing-based digit collection or variable-length interpretation, which are known sources of complexity and error in telephony systems.¶

9. Human Factors

During and after transition, published numbers SHOULD be displayed in hyphenated 4-3-4 form (e.g., 2130-555-1234). Users will find this format similar to the existing 3-3-4 format, and are expected to adapt to the new format following the patterns observed during the transition to mandatory 10-digit dialing. Contact storage systems, dialing interfaces, and automated dialing features are expected to adapt with minimal modification due to the preserved fixed-length structure.¶

10. Routing Considerations

Existing routing systems rely on fixed field positions within the NANP number. The proposed expansion preserves the relative position of the NXX and subscriber line number fields, allowing for minimal modification to routing logic.¶

Systems that perform digit analysis MUST be updated to recognize the NPAX format. This includes SS7-based switching systems (the signaling protocols used to route calls across telephone networks), SIP routing platforms, and number portability databases.¶

These updates are limited to recognition of the fourth digit as a format discriminator and do not require changes to downstream routing logic based on NXX or subscriber number.¶

11. Potential Misunderstandings

Historically, the leading domestic prefix "1" served a toll-alert or toll-access function. It warned the caller, and the network, that the call was being placed outside the local calling area and might incur higher charges. This distinction mattered when local calls were flat-rate or inexpensive while toll calls could be substantially more expensive.¶

That function has diminished in modern wireless, VoIP, and bundled calling environments, where calls are often rated independently of whether the caller dialed a leading "1". Accordingly, this proposal treats the leading "1" as an optional domestic dialing prefix or legacy access convention, not as part of the NANP telephone number.¶

Under this proposal, the NANP subscriber number expands from 10 digits to 11 digits:¶

NPAX-NXX-XXXX¶

Some legacy systems or carrier arrangements may continue to accept or require a leading domestic prefix, commonly "1", before the NANP number. In that case, the dialed digit sequence may contain 12 digits:¶

1-NPAX-NXX-XXXX¶

However, the leading "1" is not part of the NANP telephone number itself. Many wireless and VoIP systems already accept calls with or without this prefix, and this proposal does not require any change to that behavior.¶

12. Transition Strategy

A phased transition is recommended:¶

13. Alternatives Considered

The following alternatives were evaluated:¶

14. Operational Considerations

The proposed expansion is designed to minimize impact on:¶

• Call routing systems¶

• Number portability databases¶

• Inter-carrier signaling¶

However, significant updates would be required in:¶

• Customer-facing systems¶

• Validation logic¶

• Legacy equipment and embedded systems¶

A question that may arise is "Why not allow the full number range of 0-9 in the fourth digit of the telephone number to be activated immediately, rather than the current proposal to initially only permit a single digit?"¶

The rationale is cost and complexity. Initial deployment using a single digit minimizes required routing changes. This proposal acknowledges that significant costs would be involved in moving to an 11-digit telephone number. Eventually, the change must happen. The fact remains, initially implementing only one digit generates the least amount of cost increase, as only the routing logic of the fourth digit of the telephone number is required to be changed. Later, when digits 2-9 are enabled, the code required to check the fourth digit can then be eliminated. Thus, this also reduces the complexity involved in making this change.¶

15. Backwards Compatibility Risks

There will need to be lead time to account for, and attention placed on informing owners of systems that may need to be replaced because of incapacity to update them to use the new format telephone number, such as systems using:¶

• Hard-coded 10-digit fields¶

• Regular expression validation failure¶

• Embedded devices¶

Emergency equipment that sends "final warnings" or notifications need to be considered:¶

• Elevator telephones¶

• Audible Burglar alarms¶

• Silent alarms¶

• Credit/debit card processing terminals in places where Internet connections are unavailable¶

• Roadside motorist assistance telephones¶

Civil emergency response centers will have critical need to make certain proper expansion and adjustment is done for:¶

• 911/E-911 routing¶

• PSAP systems¶

• ALI/ANI databases¶

Number portability and carrier identification databases must be adjusted to compensate for this change:¶

• LNP databases are massive, and may require updates to database schemas and query logic in both SQL and NoSQL implementations¶

• Key lookup structures are dependent on current NPA-NXX format¶

One advantage this proposal provides is it requires no change to NXX format, preserving existing LNP granularity.¶

16. Benefits

The current NPA format allows a maximum of 800 NPAs to be implemented (200-999). However, practical considerations reduce this in several ways:¶

• X11 codes (211, 311, 911 etc.) are unavailable¶

• 988 as an additional N11-style number (and possibly others in the future) will reduce the supply further¶

• N9X was reserved for future expansion.¶

Given these constraints, the maximum number of NPAs is probably more like 700. While this is a large number, it eventually will be exhausted, possibly within the foreseeable future.¶

Expansion of area codes to add an extra digit, and later full expansion to 11-digits expands the numbering range by a full factor of magnitude, to 8000 possible NPAXs. Assuming similar carve-outs are used:¶

• N11X is reserved to prevent confusion¶

• 988X is also reserved¶

• Other similar service codes to 988 (200, 766, 322, 433 etc) are created, and those code ranges are restricted, e.g. 200X, 322X, 433X¶

• N9XX is reserved for future expansion¶

It still leaves a huge pool of available NPAXs. If the X11X, 988X, and 10 additional service code code blocks are reserved, in addition to N9XX, we have¶

• 72 NPAXs restricted for N11X protection¶

• 110 NPAXs restricted for 988X protection and 10 additional service code blocks¶

• 800 NPAXs reserved for N9XX expansion¶

Leaves more than 7,000 potential NPAXs available for assignment. This represents an approximate order-of-magnitude increase in addressable numbering capacity compared to the current NANP structure.¶

17. Economic Considerations

I am not ignoring that the change is going to be massive, and expensive. This is why it is important to start thinking about the issue well in advance of when action becomes mandatory, and to begin planning this change long before it is necessary. An orderly transition on a long timetable with reachable milestones and progress goals will be easier and less costly than an "under the gun" rushed change because the deadline is approaching and we can't wait.¶

The history of infrastructure transitions is littered with examples of "we'll deal with it later" becoming "we're dealing with it in crisis mode at enormous cost." The two closest analogies in the tech world are instructive:¶

• The Internet address space IPv4 exhaustion is the cautionary tale. The internet community knew for decades that 32-bit addresses would run out. IPv6 was standardized in 1998. Here we are in 2026 and the transition is still incomplete — largely because nobody acted until addresses were actually scarce, by which point the installed base was so enormous that migration became enormously painful and expensive. The NANP is in a similar position today: there's still time to plan, but that window won't stay open forever.¶

• The problem caused by the near-universal use of six-digit date fields in computer systems resulted in the "Y2K" crisis when people realized date calculations were going to fail when the year 2000 arrived, possibly in a catastrophic fashion. While extreme effort prevented a disaster scenario, it still came at enormous cost, because the work had to be done under severe time constraints. This would not have been necessary if it was started earlier. Articles in trade magazines as far back as 1985 were warning about the upcoming problem, which was mostly ignored. Until it couldn't be.¶

The 20- to 40-year timeframe for the upcoming exhaustion is the sweet spot for this kind of change: long enough that a careful, phased transition is feasible, short enough that "we'll get to it" is genuinely dangerous. The 20–40 year estimate is not a reason to wait, but the reason to start now.¶

18. Security Considerations

Changes to numbering formats may impact fraud detection systems, call validation mechanisms, and authentication processes. These impacts SHOULD be evaluated during implementation planning.¶

Number spoofing detection systems, including but not limited to STIR/SHAKEN authentication to take into account both the current, and replacement numbers.¶

Call authentication frameworks, robocall enforcement tools, and carrier reputation systems all embed assumptions about 10-digit number formats.¶

Call authentication assumptions MUST be reviewed and updated to ensure compatibility with both legacy and expanded numbering formats. This represents an approximate order-of-magnitude increase in addressable numbering capacity compared to the current NANP structure.¶

19. Transition Governance

Governance is arguably the hardest part of any NANP change. Prior transitions (e.g., the 1995 area code relief plan, the 988 rollout) would be instructive in preparation, management, and implementation of any solution to this issue.¶

One or more coordinating authorities MUST be designated to manage key aspects of the transition. These include:¶

• Whether the NPAX flag digit in position 4 of the telephone number is 0 or 1¶

• Timeline for start and implementation of each phase and segment of the upgrade plan¶

• Who will be responsible for enforcing compliance with all mandates?¶

This could be a single organization, or a cooperative arrangement of regulatory and operating companies (Carriers, Canada's CRTC, NANPA, Regulatory authorities in other jurisdictions, U.S. FCC, etc.)¶

20. Transition Difficulties

Not all parties involved in the transition will necessarily act as expeditiously as possible. Concerns over depreciation or amortization of existing equipment and/or  software will be a serious concern to various organizations and responsible  individuals. This may result in compatibility problems with respect to¶

• "Long tail" legacy systems¶

• Private Branch Exchange (PBX) systems¶

• International interoperability lag¶

As a result, partial deployment conditions may persist long after others are fully ready for the changes as a result of the implementation of 11-digit telephone numbers.¶

21. International Considerations

The proposed 11-digit format remains compatible with the E.164 [ITU] maximum length of 15 digits. Coordination with international carriers and regulatory bodies is required.¶

• This change poses no impact to global numbering compatibility¶

• It fits into the existing +1 country code model¶

No changes to the E.164 country code (+1) are required.¶

Coordination among over 25 international jurisdictions, state and provincial regulators, and the ITU will need to be taken into account.¶

22. IANA Considerations

This document has no IANA actions.¶

23. Conclusion

Expansion of the NANP to 11 digits represents a viable long-term solution to numbering exhaustion. Early commitment to a transition plan is essential to enable a controlled and gradual transition, and
avoid time-constrained or emergency implementation.¶

Expansion of the NANP to 11 digits is not an immediate necessity — but it is an eventual certainty. The question is not whether this transition will happen, but whether it will be managed or improvised.¶

With a projected exhaustion window of 2052 to 2060, the NANP community is in a position that infrastructure planners rarely enjoy: enough lead time to do this properly. A carefully designed, phased transition executed over 10 to 20 years allows vendors to absorb changes into normal product refresh cycles, carriers to plan capital expenditure in advance, embedded systems to be replaced through natural attrition, and the public to adapt gradually rather than abruptly. Regulatory processes can proceed at a measured pace. Standards can be refined. Mistakes can be caught and corrected before they propagate.¶

That window is not permanent. The history of infrastructure transitions offers two instructive examples. Y2K was resolved successfully — but only because the industry mobilized with sufficient lead time, and it was still extraordinarily expensive and stressful with years to spare. IPv4 address exhaustion is the alternative outcome: a problem understood for decades, deferred until it became acute, and still incompletely resolved thirty years after IPv6 was standardized.¶

The NANP does not have to follow either path exactly. The lead time available today makes a third outcome possible: a transition that is planned deliberately, implemented gradually, and completed before urgency drives the agenda. Early evaluation and commitment to a structural solution — of which this proposal is one candidate — is the prerequisite for that outcome.¶

Given the long lead times required for numbering plan changes, the time to begin is now, while beginning is still a choice.¶

24. References

Appendix A. Changelog

draft-00:¶

• Initial Release¶

draft-01:¶

• correct misspelling: allowsexisting -> allows existing¶

• Explain drawbacks of some alternative strategies¶

• Adjust line lengths to improve ease if editing, to take advantage of kramdown-rfc and xml2rfc automatic reformatting¶

draft-02:¶

• add executive summary¶

• clarify that some actions are temporary in nature ("bridge logic") while the transition from 10-to 11-digits is in progress.¶

• give examples of inaction and why it should be avoided¶

Author's Address