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.

Saturday, September 06, 2025

Futurist Alvin Toffler foresaw ubiquitous fiber to the home -- in 1990

Like phones and VCRs, faxes will begin to appear in even the humblest homes, driven by the Law of Ubiquity. And so will fiber optic cables and other advanced technologies, whether paid for by the individual, the public, or by other users whose fees will subsidize service to those who can’t afford it.

The widest diffusion of communication capabilities is an inseparable part of the new system of wealth creation. The direction is almost inevitably toward what the old Bell phone company called “universal service”—i.e., ubiquity—combined with interactivity, mobility, convertibility, and connectibility.
Toffler, Alvin. Powershift: Knowledge, Wealth, and Power at the Edge of the 21st Century (p. 356). Random House Publishing Group. Kindle Edition.  

Friday, August 22, 2025

Not too late to build Al Gore’s “information superhighway.”

If Congress could turn back the calendar to the 1990s when then Vice President Al Gore envisioned a digital “information superhighway,” it could have adopted a different strategy than unsustainably relying on legacy voice telephone service to chip away at its construction and the unrealistic idea that investor-owned service providers would compete to build high cost, long ROI fiber telecommunications infrastructure to replace legacy metallic voice telephone and cable TV plant. Congress should have instead formed a Digital Infrastructure Authority.

The regionally administered authority would similar to the Federal Highway Fund fuel tax that operates as an excise tax on companies that originate and send traffic over this fiber optic freeway, something that has been proposed by service providers and their policy advocates. 

It would provide long term, low interest loans to publicly and consumer utility cooperative owned networks so as to not favor any privately owned provider and function as an open access network – a public resource available to anyone who wants to use it. The authority would also have the ability to purchase existing networks and their rights of way in order to increase economies of scale, cost efficient construction and network reliability.

There would be plenty of economic opportunity for private sector players to design, build and operate the network. And it would reach farther than fiber networks they could afford to build, which limit them to proscribed builds that favor densely developed areas but leave other areas without service.

The Digital infrastructure Authority would also make access more affordable for end users since it would not have to generate profits for investors or pay business taxes. By charter, it would reach any doorstep on the electrical grid.

The good news is it’s not too late four decades later for Congress to choose this course. Call it a course correction.

Wednesday, August 06, 2025

U.S. telecom policy split: broadbanders versus infrastructuralists

Lacking a global policy to support the modernization of legacy copper analog telephone infrastructure to fiber to support modern Internet protocol-based voice, video and data services, the United States has defaulted to multiple, one off piecemeal subsidy programs. Determining how these programs operate has resulted in further fragmentation into two camps. They are the broadbanders and the infrastructuralists.

The broadbanders have held sway since the 1996 Telecom Act. It directed the Federal Communications (FCC) to annually survey the deployment of advanced telecommunications infrastructure and identify and correct impediments.

The FCC chose broadband speed – how fast bytes travel to and from end user premises – as the metric by which to gauge deployment. As long as the numbers were increasing over the past three decades, the FCC declared sufficient progress.

Various subsidy programs also adopted this metric as an eligibility factor. Only premises offered specified broadband speeds falling below an arbitrary cutoff were deemed eligible. That in turn led to the creation of “broadband maps” to determine which addresses were considered served and thus ineligible and which were “unserved” or “underserved” and thus eligible.

The infrastructuralists argue this is inherently wasteful and short lived since what is deemed adequate “broadband speed” is dynamic and growing rapidly such that by the time subsidies are awarded, projects face imminent obsolescence. They favor subsidizing fiber to the premise delivery infrastructure because of its long-term life, relatively low upgrade costs and its capacity to easily accommodate the longstanding trend of increased device and data use.

The infrastructuralists’ influence peaked in 2021 when the Biden administration’s infrastructure legislation proposed appropriating $90 billion to subsidize public and utility cooperative owned fiber that the president noted have a lower cost structure since they don’t have to produce profit for investors.

Naturally, investor owned providers that dominate America’s market-based telecommunications were opposed. The bill was quickly scaled down and amended to favor the broadbander camp, using the broadband speed metric and related broadband mapping to determine subsidy eligibility.

The Biden administration proposed guidance for the amended measure’s Broadband Equity Access and Deployment Program that allowed states to prioritize fiber projects in parceling out grants awarded to the states under the legislation. That gave the infrastructuralists leverage.

But the broadbanders -- particularly wireless and low earth orbit satellite services – claimed that was unfair. Americans in areas with obsolete legacy metallic infrastructure needed better service decades ago and suffered long enough. We can provide it much faster than building out fiber to them "to get people online," they claimed, urging the feds to liberalize BEAD so some of the subsidies flow our way.

The broadbanders gained influence in the waning months of the Biden administration and now hold sway in the current Trump administration. In the BEAD battle, some states are claiming they know what’s best to meet the needs of their residents and businesses and insist fiber is the best use of taxpayer dollars. But the billions needed to build it largely come from Washington, giving federal policymakers the ultimate say.

As they have for decades, the broadbanders remain dominant over the infrastructuralists.

Saturday, August 02, 2025

Quantum enabled SDN

The company operates over a million miles of fiber and cable that deliver internet to 31.5 million homes and businesses. That means that for any piece of data to travel from Point A to Point B, there’s a near infinite number of combinations, said Elad Nafshi, Comcast’s chief network officer. 

Data going into New York for example, could travel along the George Washington Bridge, the Lincoln Tunnel or the Amtrak train tracks, he said. And the fastest route also depends on other factors like, if there’s a fiber cut somewhere or a big surge of data into New York while everyone streams the Giants game. 

Being able to calculate, in real time, all those variables to determine the optimal flow of data and deliver it at the fastest speeds for the highest number of people is something conventional computers struggle with. But, “that’s something that Quantum could do extremely well,” Nafshi said. 

 https://www.wsj.com/articles/heres-how-quantum-computing-could-change-the-world-c7a995b1

This recalls the Cold War origins of the Internet. It was designed as ARPANET in the 1960s by the U.S. Department of Defense to provide a computerized governmental communication network that was self healing -- meaning it could automatically route around metro areas destroyed by nuclear weapon attacks.

Here, it is routing around network congestion.