Part Two: What the FCC Is Proposing for Numbering — and Why the Details Matter

While telephone numbers have become a cornerstone of digital identity, the reseller ecosystems through which many of them flow are under growing scrutiny. The FCC has issued a Notice of Proposed Rulemaking that could fundamentally change how telephone numbers are tracked through reseller networks, with real implications for fraud prevention, law enforcement, and consumer protection. In this three-part series, iconectiv — the nation's Local Number Portability Administrator for the past eight years — examines what's being proposed and what it will take to make it work.

The FCC's NPRM on numbering policy addresses a range of robocall and fraud concerns, but one proposed section stands out for its technical implications: requiring that reseller relationships be identified within the NPAC's data fields for ported telephone numbers. As the LNPA, iconectiv filed formal comments  — not to oppose the goal, but rather to ensure the Commission understands the operational realities that will determine whether this rule succeeds.

To understand the challenge, it helps to know how the NPAC identifies service providers. Every carrier with access to telephone numbers is assigned a Service Provider Identifier (SPID) within the NPAC. When a number is ported, the NPAC uses the SPID to track which provider controls it. Resellers, however, typically don't hold their own numbering resources; they operate under a sponsoring service provider, who can create a SPID on the reseller's behalf. There is currently no standardized process for this — meaning the same reseller could carry different SPIDs from different sponsoring service providers, making consistent identification across the system unreliable.

That consistency problem is at the heart of iconectiv's concern with the NPRM. The NPAC supports two optional fields — Alternative SPID (AltSPID) and LastAltSPID — that can be used to associate reseller identifiers with a telephone number. The FCC proposes to make populating the AltSPID field mandatory when a reseller relationship exists. Without a uniform reseller identification standard, however, mandatory reporting could produce fragmented, conflicting data that undermines the Commission's objectives rather than advancing them.

There is also a field-use conflict to resolve. The AltSPID field already serves another purpose: identifying default providers for Internet-based Telecommunications Relay Service (iTRS), which enables individuals with hearing or speech disabilities to communicate over voice networks. Overloading it for two different unrelated purposes not only risks operational confusion, it also can reduce accuracy for both. iconectiv recommends that the industry, through the Number Portability Industry Forum (NPIF), determine the appropriate field or fields to use for reseller identification — and that the FCC incorporate that determination into any potential rule changes.

iconectiv also believes that two additional implementation issues need attention. First, requiring NPAC records for reseller identification on non-ported numbers could significantly increase record volume distributed to service providers’ network systems, which are already operating under capacity pressure. The NPAC's existing pseudo-Location Routing Number (LRN) capability may offer an effective mitigation approach and should be considered. Second, the NPRM suggests the LNPA enforce mandatory field population, but the LNPA has no visibility into which numbers carry reseller relationships. That responsibility must rest clearly with the service providers creating the records. 

These are not objections — rather, they are the informed observations of an organization that has operated this infrastructure for eight years and wants any rule changes to achieve the FCC’s objectives. 

In the third and final installment of this series, we'll lay out what we believe is the right path forward — and what it will take to turn the FCC's proposal into a framework that truly delivers on reseller accountability.