The goal of public policy for connectivity should be to assure access to our common facilities as a public good by adopting sustainable business models that don't put owners and users at odds with each other. Such balances are typically difficult to achieve which is what makes connectivity so unusual - we can achieve both once we fund the facilities as a public good apart from the particular applications such as telephone calls and cable content.
Few CSPs would dispute that IP-based mobile communications are the future. But some still see little reason to replace TDM switches that, on the surface, cost them little beyond energy and housing expenses. At the recent Neustar Interactive Insights Summit, telecommunications experts Jennifer Pigg, Vice President at Yankee Group, outlined the conundrum -- and revealed the cost of doing nothing is higher than many think.
The Internet Engineering Task Force (IETF) is the standards body for the Internet. It is the organization that publishes and maintains the standards describing the Internet Protocol (IP -- versions 4 and 6), and all directly related and supporting protocols, such as TCP, UDP, DNS (and DNSSEC), BGP, DHCP, NDP, the list goes on, and on... But how do they do that? How does the IETF produce documents, and ensure that they are high quality, relevant, and influential?
While there is much discussion in the United States about the mergers of Comcast and Time Warner Cable, and of AT&T and DirectTV, issues such as this are generally discussed from a very narrow perspective and, we maintain, from the wrong underlying telecoms regime operating in that country - one that has stifled competition in the telecoms for nearly two decades. The same wrong parameters apply to the endless debates on net neutrality an issue that is, by the way, largely of significance to the US market alone.
Want to easily show people where a specific submarine cable goes? Or what cables terminate in a particular location? Last year I wrote about Telegeography's cool interactive submarine cable map and how useful it is to understand the submarine cable side of Internet infrastructure. In that article I mentioned how great it would be if you could get a link for a particular cable or location that you could pass along to other people.
T-Mobile filed a petition today making it clear that the FCC's commercial reasonableness standard is a failure. Anyone following net neutrality knows that the FCC is proposing to authorize discrimination and pay-for-priority deals known as fast lanes. The FCC is claiming we need not worry, however, because the FCC can make sure that entrepreneurs and users face only "commercially reasonable" discrimination.
You can't open a newspaper today, listen to the radio, or watch TV without hearing about the enormous explosion in the use of telecommunications technology - be it fixed or mobile broadband, the internet, social media, smartphones, tablets, wearables, IoT, cloud computing, the list is endless... Yet, at the same time, many telcos and ISPs are struggling to maintain their profitability. This defies economic logic.
What is the impact of IPv6 on telecommunications, VoIP, unified communications, etc? Why should telecom operators care about IPv6? What VoIP systems already support IPv6? What efforts are underway within organizations like the IETF and the SIP Forum to ensure that telecommunications can work over IPv6?
People working on net neutrality wish for a "third way" — a clever compromise giving us both network neutrality and no blowback from AT&T;, Verizon, Comcast and others. That dream is delusional because the carriers will oppose network neutrality in any real form; they want paid fast lanes. They have expressed particular opposition to "Title II" of the Communications Act — something telecom lawyers mention the same way normal people might reference the First or Second Amendments. Title II is the one essential law to ban paid fast lanes.
When talking about the problems of attracting infrastructure funds to the telecoms industry, I would make one exception; that is backbone infrastructure... We increasingly describes mobile networks as fibre networks with a wireless access component. This clearly indicates the need for fixed backbone network capacity, eventually all the way to the street.