The recent NANOG 61 meeting was a pretty typical NANOG meeting, with a plenary stream, some interest group sessions, and an ARIN Public Policy session. The meeting attracted some 898 registered attendees, which was the biggest NANOG to date. No doubt the 70 registrations from Microsoft helped in this number, as the location for NANOG 61 was in Bellevue, Washington State, but even so the interest in NANOG continues to grow...
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.
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?
The timeline of the Net Neutrality issue has been detailed here. And quoting from Vox: 'Wheeler said that peering is "an issue that we are investigating, it's an issue we are very interested in, but it's not the issue here today."'
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.
Over the last few years, there has been an increased effort to modernize the U.S. electric grid. Building a "Smart Grid" has been central in the effort to help utilities better manage their resources, minimize power outages and reduce energy consumption. However, adding more electronic devices and sensors to the grid's network has made it a prime target of cyberattacks, like Distributed Denial of Service (DDoS) attacks, which if successful, could cause wide-spread disruption of services affecting many other sectors.
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.
Peering has come back in the news with the FCC mentioning it in its set of reviews of the telecommunications market in the USA, following its Network Neutrality decision. The peering and interconnect issues are going to the heart of the telecoms matter in relation to competition, innovation and the Open Network. You don't need Network Neutrality rules, if you have a well functioning, transparent, interoperable and competitive infrastructure environment.
A lot of ink and pixels have been spilled about the FCC's new rules for network neutrality. It's impossible to comment sensibly yet about the actual proposal, since as far as I know it's not been published anywhere, but the various news reports have left me confused about just what is being addressed. There are a number of different sorts of behavior that can result in performance differences to the end user... The purpose of this post is to give a simplified (with luck, not too horribly oversimplified) explanation of the different issues here.