Tuesday, November 17, 2026

The Mobile Communications Paradox: Portable Devices, Fragmented Communications

 

The evolution of personal computing has fundamentally changed how people communicate. Desktop computers and laptops, once the primary tools for written electronic communication, have increasingly given way to smartphones and tablets. People now carry their communications devices with them, remain continuously connected, and increasingly rely on short, conversational exchanges rather than traditional email correspondence.

Yet the telecommunications industry has not fully adapted its messaging infrastructure to this transformation. Instead, the migration to mobile computing has exposed and, in some respects, amplified the fragmentation of electronic communications. We have made computing increasingly portable without making communications equally portable. 

The shift from email to conversational messaging

Email remains an essential communications tool, particularly for business correspondence, formal communications, document exchange, and longer written exchanges. But the growth of mobile computing has changed everyday communication patterns. Smartphones have made messaging immediate and persistent. Notifications, contact lists, conversational interfaces, and always-available connectivity encourage shorter, more frequent exchanges.

For many people, messaging has become the default method of personal communication. It is also increasingly used for business transactions, customer service, appointment reminders, authentication, and interactions with organizations. This is not simply a generational preference or a change in application design. It reflects a broader transition in how people use computing devices. The mobile device has become the primary communications interface for a substantial portion of the population. Consequently, the ability to exchange written messages across devices and networks has become more important, not less. Yet the underlying communications architecture remains divided. 

The Apple versus Android divide

The competition between Apple and Android illustrates the problem. Both ecosystems have developed sophisticated messaging capabilities, but their users have historically experienced different levels of functionality depending on which platform they use and which platform the recipient uses. Apple's iMessage is integrated into its hardware and software ecosystem. Android has its own messaging applications and the broader RCS standard. Although the introduction of RCS support on iPhones has improved interoperability, the experience is still not equivalent to having one universal messaging system.

This resembles the VHS versus Betamax competition of the 1980s, when competing video recording formats created compatibility problems for consumers. There is an important difference: Apple and Android are not simply competing technical formats. They are extensive commercial ecosystems with different hardware, software, applications, and business models. Both are likely to remain important competitors. But the consumer consequence is familiar. The choice of technology can determine how easily people communicate with one another.

The irony is that email solved much of this problem decades ago. A person using Gmail can communicate with someone using Outlook, an independent business email server, or virtually any other email provider. Neither party needs to know what computer, operating system, or email application the other is using. There is no comparable universal framework for mobile messaging.

The desktop computing analogy

Consider how extraordinary it would be if desktop email worked the way mobile messaging sometimes does. Imagine purchasing a Windows computer and discovering that you could only send messages to people using computers manufactured by the same company. Or imagine being unable to send an email to someone using a different email provider unless you maintained a second computer or account. Such restrictions would be commercially unacceptable. Yet similar limitations have become normalized in mobile communications.

An iPad provides Internet connectivity, email, web browsing, and access to numerous communications applications. Nevertheless, Apple's native Messages application cannot independently send conventional SMS messages without an iPhone acting as a relay. The device is capable of accessing the Internet, but its conventional text messaging capability remains dependent on another device and a separate cellular service relationship.

From the user's perspective, this is an artificial distinction. Why should sending a text message from a tablet require ownership of a particular smartphone? The problem is not a lack of computing capability. It is the way the industry has organized messaging identities and delivery systems. Separate networks, separate identities

The historical separation between email and SMS helps explain the current situation.

Email developed as an Internet-based communications service. Its addressing system is independent of the device and network used to access it. The email address identifies the recipient, while Internet infrastructure handles message routing and delivery. SMS developed within mobile carrier networks. Its addressing system is based primarily on telephone numbers, with delivery historically controlled by mobile network operators. More recently, proprietary messaging applications have introduced additional identities and communications environments. Apple iMessage, WhatsApp, Facebook Messenger, and other services each have their own methods of identifying users and delivering messages.

The result is a fragmented landscape in which the user must navigate different applications, identities, and networks to accomplish essentially the same task: exchanging written information. This fragmentation was less conspicuous when desktop computers and email dominated electronic communication. It becomes increasingly problematic when smartphones and tablets become the primary devices people use to communicate.

The telecommunications industry has recognized parts of this problem.

The telecommunications industry has effectively moved the user toward mobile computing without establishing a correspondingly universal mobile messaging architecture. Interoperability is the next logical stepRCS, developed through the GSMA, is intended to modernize traditional SMS and provide richer messaging capabilities. Its adoption by Apple has improved communication between Android and iPhone users.

The Internet Engineering Task Force has also established the MIMI (More Instant Messaging Interoperability) working group to develop standards for interoperability between independent messaging providers. The Matrix protocol provides another example of an open, federated messaging architecture in which independent servers and applications can communicate.

These are meaningful developments. But they primarily address interoperability between messaging services. They do not yet establish a universal messaging identity that integrates email, SMS, RCS, and other Internet-based messaging systems. That distinction is important. Making separate messaging applications communicate with one another is useful. Establishing a common identity and addressing framework that makes the underlying differences largely irrelevant would be a more fundamental improvement. 

Moving from device-centric to identity-centric communications.

 The next evolution in messaging should separate three things that have become unnecessarily intertwined:
  • Personal identity: How an individual is identified and addressed for communications.
  • Messaging transport: The network or protocol used to deliver the message.
  • Device and application: The hardware and software used to compose and receive it.
A universal messaging framework would allow an individual to maintain a persistent communications identity independent of any particular device manufacturer, mobile carrier, or messaging application. That identity could support multiple delivery addresses and methods, including email, telephone numbers, and Internet-based messaging services. A common interoperability layer would determine how to route messages to recipients using different systems.

For example, someone composing a message on an iPad could send it to an Android user without needing an iPhone as an intermediary. If the recipient were reachable only through SMS, the system could use an appropriate carrier gateway. If the recipient used an IP-based messaging service, the message could be delivered through that service. The sender would not need to know or select the underlying transport mechanism. The same identity could be used from a smartphone, tablet, desktop computer, or other connected device. This would not require eliminating email, SMS, or existing messaging applications. They could continue serving different purposes and user preferences while operating within a more interoperable communications environment.

The commercial challenge

The technical requirements for such a system are substantial, but the commercial obstacles may be even greater. Apple benefits from the integration of iMessage with its hardware ecosystem. Google has its own messaging interests. Mobile carriers have historically controlled SMS delivery and telephone-number-based messaging. Independent messaging platforms benefit from keeping users within their respective environments. A universal messaging identity would reduce the ability of individual companies to use messaging access as a source of customer lock-in.

That does not mean eliminating competition. It means changing what companies compete over. Device manufacturers could continue competing on hardware and user experience. Application developers could compete on messaging features, security, and convenience. Carriers could compete on connectivity and network services.But consumers would no longer have to sacrifice basic communications interoperability to participate in those competing ecosystems.

An open framework would also need to address authentication, spam, fraud, privacy, encryption, identity portability, and the governance of the addressing infrastructure. A universal identity should remain under user control rather than becoming another proprietary asset controlled by a single technology company.

The larger telecommunications paradox

The Internet was built around the principle that independent networks could communicate using common protocols. Email demonstrated that electronic communications could operate across different providers, devices, and operating systems without requiring users to belong to the same commercial ecosystem. Yet mobile messaging has developed in a different direction. The industry is investing in 5G, 6G, satellite connectivity, cloud infrastructure, and increasingly sophisticated mobile devices. Computing power and connectivity are becoming more portable and ubiquitous. But one of the most fundamental forms of digital communication remains divided by proprietary applications, separate addressing systems, and carrier-dependent infrastructure.

As mobile devices replace traditional computers as the primary communications interface, this fragmentation becomes increasingly difficult to justify. The future of messaging should not be determined by whether someone owns an Apple or Android device, subscribes to a particular carrier, or prefers email over a particular messaging application. The individual should own the communications identity. Applications should compete to serve the individual. Networks should deliver the message. We have achieved device portability without achieving communications portability. It is time for the telecommunications industry to address that disconnect.

Monday, November 16, 2026

Beyond Messaging Interoperability: The Case for a Universal Messaging Identity

The fragmentation of text messaging is more than an inconvenience caused by competing applications and incompatible devices. It reflects a deeper architectural problem in telecommunications: the absence of a universal messaging identity and addressing framework that works independently of the device, application, or network used to communicate.

As discussed in my previous post, The Fragmentation of Text Messaging, email and text messaging evolved along separate paths. Email became an Internet-based communications service built around persistent addresses and relatively open standards. SMS evolved as a mobile carrier service tied to telephone numbers and carrier-controlled delivery infrastructure. More recently, technology companies have introduced proprietary messaging platforms that create additional divisions.

The result is a communications environment in which users must navigate multiple identities, applications, and networks simply to exchange text messages. This is not an inherent limitation of digital communications. It is an architectural and institutional choice. The fundamental problem is identity, not messaging applications

Consider how email works. An individual can send an email from a desktop computer, tablet, or smartphone using virtually any compatible email application. The recipient's email address remains the same regardless of the device or service used by either party. The Internet handles the routing and delivery. The user does not need to know which network carries the message or what device the recipient is using.

Mobile text messaging works differently. A telephone number serves as the messaging address, but the ability to send and receive conventional SMS messages is generally tied to a mobile carrier subscription and its network infrastructure.

Apple's Messages ecosystem illustrates the problem. An iPad can exchange iMessages with other Apple devices, but sending conventional SMS messages requires an iPhone to relay them. An Android user has a different set of messaging options. A person using a desktop computer may have yet another experience.

The user is left dealing with distinctions that should be largely invisible. Why should sending a text message from a tablet require ownership of a separate smartphone? Why should changing devices or messaging applications potentially change how someone can communicate with the people they know?
The underlying problem is that the industry has not established a truly universal messaging identity that is independent of the device and service provider. Interoperability is necessary, but it is not enough

The telecommunications industry has made progress toward messaging interoperability. RCS (Rich Communication Services) is intended to modernize SMS with features such as read receipts, typing indicators, group messaging, and richer media exchange. Apple's adoption of RCS is an important development in improving communication between iPhone and Android users.

But interoperability between messaging systems does not necessarily solve the underlying identity problem. RCS still relies heavily on telephone-number-based addressing and mobile ecosystem integration. Email remains a separate addressing and delivery system. Proprietary messaging platforms continue to maintain their own identities and user communities. Making these systems communicate better is worthwhile, but it does not establish a common identity that users can carry across devices, applications, and networks. That should be the larger objective.

A universal messaging identity and addressing framework

What is needed is an open, standardized messaging identity and addressing framework that operates above individual messaging networks. Such a framework would separate four functions that are currently intertwined:

1. Personal identity and addressing
Individuals would have a persistent messaging identity that is not dependent on a particular telephone number, email provider, device manufacturer, or messaging application. An individual could retain that identity when changing mobile carriers, replacing a smartphone, purchasing a tablet, or moving to another messaging application. Telephone numbers and email addresses could continue to function as familiar addresses and discovery mechanisms, but neither would have to define the individual's entire messaging identity.

2. A common messaging protocol
A standardized protocol would support the exchange of text, attachments, images, and other content, along with delivery notifications, security, and other messaging functions. The objective would not necessarily be to replace SMTP, SMS, or RCS immediately. Rather, it would establish a common framework through which these existing protocols could interoperate.

3. An interoperability and routing layer
A network-level routing and translation system would determine how messages reach their intended recipients. If a recipient uses an IP-based messaging application, the message could be delivered directly through that system. If the recipient is reachable only through SMS, the infrastructure could route the message through an appropriate carrier gateway. Email could remain another supported delivery mechanism. The sender would not need to select the transport mechanism manually.
 
4. Device- and application-independent access
Any compatible device or application could access the messaging service. A user could compose and receive messages on a smartphone, tablet, desktop computer, or other connected device without having to maintain separate messaging accounts for each. This is fundamentally how email already works. There is no compelling reason why the same principle cannot be extended to mobile messaging.

What this would mean for consumers

The practical implications are substantial. Imagine having a single messaging identity that works across all your devices and communication applications. You could send a message from an iPad to someone using an Android phone without needing an iPhone as an intermediary. You could switch from Apple to Android without losing your messaging identity or access to your contacts. You could use a desktop messaging application without depending on a smartphone being powered on and connected to a carrier network.

You could also choose among competing messaging applications without losing the ability to communicate with people using other applications. The distinction between sending a text message and sending an email would become less important from the user's perspective. The recipient's preferred application and available network would determine how the message is delivered.

This would not mean that email and text messaging must become identical. They serve different purposes and have different conventions. Email is particularly useful for longer communications, formal correspondence, and document exchange. Text messaging is optimized for immediate, conversational communication. But there is no reason these different experiences must depend on entirely separate identity and addressing infrastructures.

The commercial and institutional obstacles

The technical challenge is significant, but perhaps not the greatest obstacle. The existing messaging environment creates commercial advantages for companies that control identities, applications, and delivery networks. Apple benefits from the integration of iMessage with its hardware ecosystem. Google has its own messaging interests. Mobile carriers historically controlled SMS delivery and telephone-number-based messaging. Other messaging platforms benefit from keeping users within their respective ecosystems.

A universal messaging identity would reduce the ability of any one provider to use messaging access as a source of customer lock-in. That does not mean eliminating competition or requiring every provider to offer the same application. Quite the opposite. Competition could shift toward the quality of applications, security, reliability, features, customer support, and network services rather than the ability to restrict communication to users of a particular platform. Carriers could continue competing on connectivity and transport. Device manufacturers could compete on hardware and user experience. Application developers could compete on messaging features. The difference is that users would no longer have to surrender interoperability to participate in those competing ecosystems.

This would require industry cooperation, open standards, governance, and perhaps regulatory encouragement. It would also require careful attention to authentication, spam, fraud, privacy, encryption, and the security implications of translating messages between different systems.

A universal identity should not become a universal surveillance mechanism or a centralized database controlled by one commercial provider. Portability, user control, decentralized administration where practical, and strong security would be essential design principles.

The Internet already demonstrated the model

There is an important historical precedent. Email became a universal communications medium because its addressing and transport standards were sufficiently open to permit different providers and applications to communicate. A Gmail user can communicate with someone using Outlook, a business email server, or an independently hosted domain. The Internet itself was built around a similar principle: different networks could interconnect using common protocols without requiring every participant to use the same equipment or service provider.

Mobile messaging has not achieved that same degree of openness. The industry has spent years improving individual messaging platforms and negotiating interoperability between competing systems. It has devoted considerably less attention to establishing a persistent, portable messaging identity that belongs to the user rather than the provider.

That is the opportunity. Moving beyond the device-centric communications model

The broader telecommunications industry is increasingly defined by Internet Protocol networks, cloud services, connected devices, and software-based communications. Yet text messaging remains constrained by architectural decisions made when mobile networks were primarily designed around voice calls and carrier-controlled services. The continued separation of email and mobile messaging is an example of how legacy network structures and commercial interests can constrain the evolution of communications. The next step should not simply be another messaging application or another proprietary messaging standard. It should be a universal messaging identity and interoperability framework that allows people to communicate independently of the devices, applications, and networks they choose to use.

The individual should own the communications identity. The applications should compete to serve the individual. The networks should deliver the message. That is a more logical foundation for the future of digital communications than the fragmented environment we have today.

Tuesday, November 10, 2026

The Fragmentation of Text Messaging: Have We Traded Email's Universality for Smartphone Convenience?

 

The migration from email to mobile messaging has made everyday communication faster and more immediate. But it has also created a fragmented communications environment that many users don't fully understand and encounter difficulty navigating. As smartphones become the primary computing and communications devices for an increasing share of the population, people are becoming more dependent on text-based messaging while becoming less familiar with email. Yet the messaging environment replacing email is considerably more fragmented and, in many respects, less intuitive.

Consider a simple example: an iPhone user wants to send a message to someone using an iPad. They ask for the iPad's telephone number, assuming that every device receiving messages must have one. But an iPad can receive Apple's iMessages through an Apple Account email address without having a cellular telephone number at all.

Or consider someone entering a recipient's telephone number into Apple's Messages application and encountering an unexpected indication that the number isn't available as an iMessage destination. The user may conclude that the number is incorrect or that something is wrong with the recipient's phone. They may not understand that iMessage is Apple's proprietary messaging service and that communicating with someone outside the Apple ecosystem involves a different messaging protocol.

These aren't isolated technical curiosities. They illustrate a growing problem with the way digital communication is evolving, and they share a common cause: messaging identity and addressing have become bound to particular ecosystems rather than to the people trying to communicate.

Email: A relatively universal communications standard

Email established an important principle of Internet communications: users could communicate across different hardware, software, service providers, and operating systems using a common addressing system.

A Gmail user could send a message to someone using Outlook, Yahoo, or an organizational email server. The applications might look different, but the underlying communications standards were interoperable. Users didn't need to know which email client the recipient used, what operating system they owned, or which manufacturer produced their computer. The email address was the essential identifier. The communications infrastructure largely operated behind the scenes. That relative universality was one of email's greatest strengths.

Mobile messaging: A fragmented ecosystem

Text messaging has evolved along a very different path. Today, users encounter multiple applications, messaging identities, and communications protocols:

·        Apple Messages/iMessage: Apple's messaging application and proprietary messaging service, integrated into iOS, iPadOS, and macOS.

·        Google Messages: Google's Android messaging application, supporting SMS/MMS and RCS.

·        SMS/MMS: Traditional carrier-based messaging standards that provide basic interoperability across mobile networks.

·        RCS: A more modern messaging protocol intended to provide richer messaging capabilities across networks and devices.

·        Third-party messaging services: WhatsApp, Facebook Messenger, Signal, Telegram, and others, each with its own application, identity system, and ecosystem.

The distinction between an application, a messaging protocol, and a communications service is largely invisible to ordinary users. iMessage, for example, is at once an application (Apple Messages), a proprietary service (Apple's messaging servers), and a protocol of Apple's own design. RCS is different again: a protocol carried by whichever application a device happens to include. WhatsApp bundles its own application, service, and identity system into a single product.

The iPhone owner who calls all of this “texting” and the Android owner who means Google Messages can exchange messages without using the same application, service, or underlying protocol. The problem becomes more pronounced when users encounter capabilities that work within one ecosystem but not another.

The disappearance of a common mental model

A major consequence of this fragmentation is that users increasingly misunderstand how to address and reach other people. Traditional telephone numbers are still widely used, but they are no longer the only way to identify a messaging destination; the iPad from the opening example needs none at all to participate in Apple's messaging ecosystem. Yet many users continue to assume that messaging is fundamentally an extension of traditional telephone service.

Others assume that a messaging application on one operating system has an equivalent application on another, without recognizing that Apple Messages and Google Messages are separate applications with different platform integrations and capabilities. The confusion becomes visible in small failures: the group chat that behaves differently once one participant switches to an Android phone and the conversation silently falls back to SMS.

The resulting confusion is familiar:

“It won't let me.”

“I can't open it.”

“It won’t go through.”

Smartphone dependence doesn't necessarily mean digital literacy

Many people who are highly dependent on smartphones are remarkably proficient at using familiar applications but have relatively little understanding of the systems supporting them. They know how to navigate their messaging application, share photographs, and participate in group conversations. But when something falls outside the expected workflow, they may have difficulty diagnosing the problem.

Modern smartphone interfaces deliberately conceal technical complexity. That is generally good design. Users shouldn't need to understand network protocols to send a message. However, the combination of proprietary ecosystems, multiple messaging applications, different addressing systems, and increasingly invisible technical boundaries creates a situation in which users may not even understand why communication sometimes fails or behaves differently.

RCS helps, but doesn't solve the larger problem

The introduction of RCS support across Apple and Android devices is a welcome development. Where carriers and devices support it, cross-platform conversations gain typing indicators, read receipts, and higher-quality media sharing. But encrypted cross-platform RCS has lagged behind what proprietary services already offer, and rollout still varies by carrier.

RCS addresses only part of the problem. It doesn't make Apple Messages and Google Messages the same application. It doesn't eliminate third-party messaging services or their separate account requirements. Nor does it establish a universal identity and addressing system for all forms of mobile messaging. The distinction between application, protocol, and platform remains.

A case for universal messaging identity and addressing

Perhaps the larger question is whether the telecommunications industry should revisit the concept of a universal messaging identity and addressing framework. Email provides a useful precedent. A person doesn't need to know whether the recipient uses Gmail, Outlook, or another email application. A common addressing convention allows the message to reach its destination regardless of the recipient's device or service provider. Why shouldn't mobile messaging aspire to a similar degree of interoperability?

Imagine a system in which an individual or organization has a persistent, universally recognized messaging address. That address could be associated with a telephone number, email address, or another verified identity, but would not be dependent on a particular device manufacturer, operating system, or messaging application. A sender could initiate a conversation without first determining whether the recipient uses an iPhone, Android phone, tablet, or desktop computer. The underlying infrastructure would negotiate the appropriate delivery method and supported features.

Such a framework would need several foundational elements:

·        Universal addressing: A consistent way to identify messaging recipients independent of their device or application.

·        Interoperability: The ability to exchange messages across platforms and service providers without requiring users to understand the underlying protocols.

·        Identity portability: Messaging identities that remain with the individual when changing devices, operating systems, or service providers.

·        Protocol negotiation: Automatic selection of supported messaging capabilities, including encryption, media, and delivery features.

·        Security and privacy: Strong authentication, protection against impersonation, spam prevention, and user control over who can initiate contact.

This wouldn't necessarily require replacing Apple Messages, Google Messages, WhatsApp, or other existing applications. The proposal is not another messaging application; it is a common identity and interoperability layer that existing applications can use. They could continue competing on interface design, features, security, and user experience while supporting that common framework. The objective would be to separate the identity of the person being contacted from the particular technology used to contact them.

There are significant implementation and governance challenges. Apple, Google, telecommunications providers, and third-party messaging services would need to agree on common standards, identity management, security requirements, and interoperability rules. Commercial incentives and proprietary ecosystems would also have to be addressed. Nevertheless, these are challenges worth examining.

The telecom industry's interoperability challenge

For telecommunications providers, this raises a broader question about the direction of consumer communications. The industry has spent decades building interoperable networks, and mobile voice, SMS, and Internet connectivity demonstrate the value of common standards across competing providers. Messaging should not be excluded from that conversation.

The consumer experience, however, is increasingly determined not by network connectivity but by the messaging ecosystem a user happens to occupy. The commercial obstacle is equally clear: identity lock-in is an asset for the platforms that own it, which is precisely why a neutral addressing layer will not emerge on its own.

There is a lesson here from email. A successful communications environment doesn't necessarily require everyone to use the same application. It requires common standards, interoperable addressing, and the ability to communicate without having to understand the technical preferences of the recipient. Mobile messaging has made substantial progress, particularly through RCS. But the broader experience remains divided among proprietary services and platform-specific applications.

As more people abandon or minimize their use of email, this fragmentation becomes increasingly consequential. Text messaging is no longer just a convenient supplement to traditional communications. For many people, it is becoming their primary communications channel. The question is whether the telecommunications industry will continue to accept fragmentation as the inevitable consequence of competing ecosystems, or treat universal messaging identity as the next standard worth building. We have made communication faster, more immediate, and more convenient. But have we actually made it simpler?

Monday, September 28, 2026

Building for the Future Instead of Catching Up: A Proposal for a National Connectivity Trust

For decades, U.S. telecommunications policy has struggled to keep pace with the transition from analog voice telephone service to digital, Internet Protocol-based advanced telecommunications.

Ideally, better policy would have been put in place in the early 1990s to build what then Vice President Al Gore envisioned as an "information superhighway," reaching nearly every American home, school and business just as Plain Old Telephone Service (POTS) did for the latter half of the 20th century.

Over the past three decades, policymakers and regulators have implemented various subsidy programs to support the transition from POTS copper networks to fiber optic connections. Instead of building for the future, they have tried to catch up, and they have come up short and late.

I've drafted a framework for a different approach, a single institution I'm calling the National Connectivity Trust. The full discussion draft is available here [link to PDF]. What follows is a summary.

Why the current approach isn't working

The main mechanism, the Universal Service Fund (USF), is funded by a charge on interstate voice revenue, a market in long decline. In the fourth quarter of 2026, that charge will reach a record 42 percent, the second record quarter in a row. Loading ever more of the cost of future networks onto a shrinking base of voice calls can't last.

Meanwhile, federal support is spread across more than 133 programs administered by 15 agencies. GAO describes the result as "fragmented and overlapping". States run their own programs on top of that.

Even after BEAD, the largest construction program yet, about 1.1 million locations remain unfunded. The figure rises to 1.6 million if satellite awards aren't counted as service.

Construction grants also leave a gap: they pay for building networks, not for running them. NTIA now requires BEAD recipients to certify that they won't seek future operating subsidies. In high-cost rural areas, operating costs can exceed subscriber revenue even when construction was fully paid for.

Costs keep rising. In 2025, median fiber construction costs reached $18 per foot underground and $8 per foot aerial, and 88 percent of builders expect further increases in 2026.

Then there is affordability. The Affordable Connectivity Program was serving 23 million households when its one-time funding ran out. Doug Dawson of CCG Consulting reports a rise in customer losses ISPs now see comes from households that can't afford the monthly bill. Smartphone-only households grew from 7.5 percent in 2017 to 11.5 percent in 2024.

A different approach: finance and operate for the long term

The National Connectivity Trust would be a congressionally chartered nonprofit federal corporation, tax-exempt under IRC § 501(c)(1) and administered through nine regional offices plus a national Tribal Office. It would take over every federal program that pays for networks or service, ending the grant and subsidy administration roles of the FCC, NTIA and USDA's Rural Utilities Service. The FCC would keep its regulatory work: pole attachments, spectrum, numbering and consumer protection.

The Trust would do four things.

1. Lend rather than grant. Its core is a long-term, low-interest loan facility for middle-mile and last-mile fiber, with priority for consumer cooperatives, electric cooperatives, and municipal and Tribal sponsors. Nonprofit and cooperative operators need no return on equity and pay no income tax. A 2 percent, 30-year loan to such a sponsor supports roughly twice the construction cost that a private operator's 9 percent return target would. Replacing aging poles, a major obstacle to aerial fiber in rural and exurban areas, is an eligible cost.

Where a project can't repay all its costs, part of the loan is forgivable. The share forgiven is set by a published national cost model, and sponsors who request less get priority. Forgiveness is earned in stages:

  • 25 percent at construction completion.
  • 25 percent once service is established.
  • 50 percent spread over ten years of compliant operation.

Sponsors who fail to perform owe the balance. This keeps the focus on building and operating networks at affordable rates, not on competing for free money.

2. Use satellite where fiber can't pay for itself. In very-low-density and remote areas, the Trust would buy satellite service competitively, reviewing every five years whether those areas can move to fiber. Satellite has limits. As Blair Levin, former policy advisor to New Street Research, put it, satellite "can provide an important connection where better options are not available" but is not "interchangeable with fiber for the long-term demands of an AI-driven economy". The five-year review keeps satellite a bridge to fiber rather than a permanent substitute.

3. Make service affordable everywhere. Trust-financed fiber networks would offer one residential rate, $65 a month for symmetrical 1 Gbps service, with no speed tiers. Business service would have speed tiers. Customers could pause and restart service without penalty.

A permanent Affordability Credit of about $30 a month would replace the ACP, with no separate application. Every household in a high-poverty census tract would qualify automatically, as would households enrolled in SNAP, Medicaid and similar programs. The credit would apply to fixed service from any provider, including in urban areas where mobile-only use is growing.

4. Drop the map and the challenge process. There would be no national availability map, no "served/underserved/unserved" categories and no process for incumbents to challenge eligibility. Sponsors define their own service areas and must serve every location in them. Eligibility rests on financial viability, not on the speed of existing service. Some overlap with existing fiber, which incumbents often build only in their most profitable neighborhoods, is expected, but no forgivable money goes to duplicate fiber.

Who pays

The Trust would be funded by a Universal Connectivity Excise Tax on large edge providers and AI hyperscalers, the companies whose business depends most on these networks. The USF charge on voice revenue would phase out over three years.

U.S. digital advertising revenue alone was $294.6 billion in 2025. By my estimates:

  • Building the networks would take less than 1 percent of that revenue.
  • Adding the existing USF programs would raise the rate to about 3.4 percent.
  • Adding the Affordability Credit would bring it to about 6.1 percent.

Does it pencil out?

Financial modeling suggests it can:

  • Fully repayable loans work in exurban and rural aerial areas for cooperative-cost operators at the $65 rate.
  • Mixed projects that combine cheaper and costlier areas can often repay in full.
  • Lower-density areas need a forgivable share of roughly a quarter to two-thirds of construction cost.

Because satellite serves the most remote locations, the federal government would not need to own networks. It would take one over only as a remedy when a sponsor fails.

Federal law already says advanced telecommunications should reach "all regions of the Nation" at "reasonably comparable" rates. What's missing is an institution built to deliver that: sustainable funding, finance that doesn't depend on subsidy forever, and affordability built in rather than added as an afterthought. The National Connectivity Trust is my proposal for that institution. I welcome your comments.

Full discussion draft: National Connectivity Trust: A Framework for the Universal Connectivity Act (September 2026) [link to PDF].

Sunday, April 12, 2026

The magical economic thinking at the center of the 1996 Telecom Act: Why Al Gore’s Information Superhighway wasn’t built

The Telecommunications Act of 1996 is now 30 years old, and there has been a lot of events, hearings and webinars, including a congressional hearing, an FCC series of panels, Public Knowledge, Benton Foundation, TPI, Brookings, Broadband Breakfast, and a few others, all easily findable on the web.

The Act was supposed to open the wired networks to direct competition, that would lower prices and bring in new and innovative services that would be available via a new fiber optic wire to the home and business. And it would be delivered to everyone, equally, as this Act was an update of the original Communications Act of 1934.

https://kushnickbruce.medium.com/telecom-act-is-30-500-billion-overcharging-the-digital-divide-and-delete3-by-fcc-chairman-carr-e50d0ab5940f

With these words, Bruce Kushnick, a longtime critic of U.S. telecom policy, sums up the flawed magical thinking that made the envisioned future state immediately preceding this regulatory overhaul impossible to attain. As Kushnick describes it:

Starting in the 1990’s, a few years before the Telecom Act, America was promised a new shiny fiber optic future. Seven holding companies had been created in 1984 and given control over the existing state telecommunications public utilities, which were based on copper wire.

And in 1992, Vice President Al Gore laid out the ‘Information Superhighway’, a fiber replacement of this existing copper wires.
The root cause is negligent policymaking. A dispassionate economic assessment would have determined advanced telecommunications like basic telecommunications before it that ran on copper networks providing analog voice telephone service functions as a natural monopoly like other utilities.

As such, facilities-based market competition would be highly unlikely to appear since the barriers to competitor entry against established incumbents would be too high and the future return on investment too distant.

As AT&T explained, the cost of modernizing the copper cable distribution network to fiber to the premise infrastructure is enormous. Its shareholders or investors and creditors and those of any other privately held company would be unable to bear them. Consequently, as Kushnick’s analysis alludes, multiple state level plans by the RBOCs to replace the copper with fiber were abandoned. The economics would not pencil out.

That reality would have been reasonably if not painfully obvious for any serious policymaking effort in the early 1990s, calling for a different approach: the one not chosen.

The seven holding companies to which Kushnick refers are the Regional Bell Operating Companies (RBOCs) formed out of the 1984 settlement of the federal government’s antitrust prosecution of AT&T in the 1970s. Had the proper policy been put in place, they could have formed the structural framework for Al Gore’s Information Superhighway that could have reached most every American doorstep by 2010.

How would it work? By creating a federal-private partnership with the RBOCs. The federal government would form a telecom authority that would take a majority stake in each of the RBOCs with an option for the RBOCs to negotiate a purchase of those stakes once universal fiber is built out in their respective regions as determined by a federal review.

This could have fostered a mindset of bandwidth abundance rather than scarcity, thus avoiding decades of “broadband” battles at all levels of government over a constantly changing definition of broadband, where is available and at what price. And decades of unproductive protectionist lobbying by incumbent telephone and cable companies to stymie publicly owned and operated fiber delivery infrastructure despite its lower cost structure.