John Roese’s Blog CTO, Nortel

Megatrends Part 1 cont’d: Hyper-Connectivity - The Implications

Location: On Flight from London to Ottawa

Continuing the dialog on mega-trends from my last blog…

(First, let me just say that I sincerely appreciate the very thoughtful and insightful comments people have been making. It's definitely the start of what I hope will be an interesting and on-going dialog. With that in mind, I'm going to start to intersperse my more in-depth technology posts with responses to some of your great questions, comments, and observations. I think that might be the most effective way for me to handle some of the volume and to keep the conversation going on some of the topics you've raised.)

So, more on hyperconnectivity...

If the future is about a hyper-connected environment, where everything that can and should be connected is connected, then what will this mean to the telecommunications industry? What network technology will be needed to support this trend and its impacts?

I’ve been through this thinking exercise before, as I’m sure many of you have been. My best example was in the late 1990’s when a few industry colleagues and I were considering the fact that local area networks lacked an essential element of intelligence that would be critical to realizing the goals of policy-based networking. That missing intelligence was the need to understand who was actually using the network. In other words, what was missing was human identity as an element of network intelligence.

We collaborated on a technical paper, documenting a model that used the extensible authentication protocol over Ethernet (EAPOE) to bring authentication into the network in a flexible and effective way. When I first began talking about this in the late 1990’s, most people’s response was that there was no need for this because the network was doing just fine as a big, fast, cheap pipe and intelligence of this kind was unnecessary.

Well, a few years later, after we experienced the Code Red worm, Nimda, and a host of other denial-of-service attacks, along with a surge in regulation that required businesses to protect and control their IT systems from unauthorized users, the idea that an intelligent authenticated network might be needed was suddenly being widely discussed.

The reason I bring this up is not to suggest that I was smarter than any other IT person but rather to point out that the most important new technologies are the result of a need and, in many cases, that need is seen far in advance and solutions are formulated well ahead of the time when both the need and the solution become obvious. Had we not started work on IEEE 802.1X (what EAPOE became) far in advance of the need, we would have had a far less evolved toolset to deal with the inevitable security and control issues that some of us knew were a mega-trend that was inevitable.

Hyper-connectivity is as significant a mega-trend as security threats ultimately became to IT. Imagine, for example, what your IT systems and networks will look like if the number of connected nodes increases by 10 or 100 fold. Will the standard configuration process of element-by-element configuration via such primitive interfaces as CLI (command line interface) work any more? CLIs are a nice rudimentary way to make specific actions happen on a switch or another network device, but imagine if you had to define services in a dynamic network consisting of 100,000 ports with a wide range of end systems attaching to them dynamically. Could you even use the existing network management systems to deal with this?

Even the most robust policy-based management systems today will probably be inadequate because they only scale so far. Bear in mind that most IT budgets today are not set based on the size of the network, but rather on a percentage of the total organization’s gross budget and/or, in some cases, on a cost per employee. Neither of these funding calculations takes into account a hyper-connected network. Since there is usually little chance of increasing IT funding, and we do not have more hours in the day, we must look to new technologies to achieve operational efficiency as networks scale.

So how will we deal with this inevitable trend? I put forward that there are three technical areas of innovation that will help us scale to operate in the hyper-connected world. First, we must use intelligent automation in our management systems so that any task that can be automated is automated, freeing human operators to focus on the exceptions. Second, we must de-layer our architectures to make the network system simpler (fewer nodes to manage). And, third, we must make the core functions and protocols extensible so that we can use one method of service to address a very diverse environment. We must build networks that architecturally are prepared to deal with the op-ex part of the equation by simplifying the operating paradigm at a rate faster than the inevitable growth of the system.

Today, too many enterprise and carrier networks insert complexity into the network to deal with one type of end system or application and then repeat that process until dozens or hundreds of unique abstractions or overly complex protocols are running in parallel over a single network. At the risk of being called a heretic, some examples of this are the use of MPLS technologies to deliver Ethernet services over an Ethernet network (why not just make Ethernet services smarter and de-layer the system?) or using a proprietary routing protocol to build resiliency into one part of a network (constructed by one vendor’s gear) instead of using standard protocols to create resiliency throughout the entire network. At the time decisions like these were made, they made sense and, in some cases, may even make sense today. However, if we think about the future where large, complex heterogeneous networks with hugely diverse end systems and applications are attached, simplicity will matter more than we can imagine.

One of my jobs at Nortel is to make sure that we see the future trends in advance so that we can research and develop the solutions needed to make sure that our customers are prepared for that event.

Consider this blog entry as an early warning on a trend that, by most analysis, is inevitable as we see value in connecting more and more nodes and people. (Remember Metcalfe’s Law: The value of the network is equal to the square of the number of connected users, where a network with one user, for example, has a value of 1, a network with 2 users a value of 4, a network with 4 users a value of 16, and so on…).

In the new Nortel, this kind of dialog is now being internalized and the R&D community is focused on solving for this scenario. Will we get it completely right? Of course not, but I believe we see it clearer than many and will not be surprised by it.

Apologies for another long blog entry, but I thought I would take advantage of finally having some time to write after a very busy week and got a little deeper than originally intended. :)

Trackbacks/Pings

  1. […] Older: Megatrends Part 1 cont’d: Hyper-Connectivity - The Implications […]

Comments

  1. …a further implication of this megatrend is a widening of the gap between technological haves and have nots. If we see increased value from hyperconnectivity then people in developed markets will further extend - and have the opportunity to more easily exploit - this differential over the billion or so global citizens still living in poverty. It is incumbent on those of us leading these megatrends that we look to exploit developments in networking technology to bridge the social and economic divide.

  2. It’s sounds like the hyperconnectivity would need a database and search function to determine what connection to send/receive and when to use it.

    Is each pixel you see or photon of sound you hear considered a network connection?

    Where are the boundaries of the hyperconnections?

  3. So I have been thinking about the hyperconnectivity thing and trying to imagine what things in day to day life would benefit from network connectivity. I was in the gym the other day and was irritated about several machines being broken .. then I thought if they were connected to the network they could automatically send an alert with diagnostic information and even dispatch a tech. Thinking further it could be used to record maintenance logs and reliability records for equipment and many other managment functions. I kept going and then thought, well if thi equipment is on the network, it could automatically keep track of my progress … upload the info to a web portal where i could view my progress and get customized recomendations.
    I looked into this a little bit and found out their are very mature systems on the market for this that are rapidly gaining in popularity … yet another piece of evidence for the hyperconnectivity trend (see fitlinxx.com)

  4. When you add RFID technology to the mix, the number of interconnected nodes and the potential applications become mind boggling.

    When the RFID tag in my shirt tells the washing machine that it prefers to be washed in cold water only, or a warning that you’ve accidentally put a red shirt into your white laundry, or those pants you just put in should really be dry cleaned.

    When the milk tells the fridge that it has expired, and the fridge notifies the pantry to add milk to the shopping list, and the pantry noticing that I’m driving by the grocery store lets my car know that I should pick up milk (and bread and cheese while I’m there, oh and there is a sale on my favorite brand of soft drink).

    Think of the advantage when a company can query any component anywhere in it’s supply chain (even in a shipping container in the middle of the Pacific) and see if it has been dropped, gotten wet or exposed to temperatures outside of spec, know exactly where it is and when it will arrive, and retrieve any test results and approval records for that one part.

    This is the incredible power of a hyperconnected world.

  5. Network complexity is having a measurable and real impact to business today. Network operators show an increasing trend of bringing in contracted resources to assist in the operation of these complex, multi-node networks. They simply cannot keep up with the quantity of resources and training required to manage the evolving network. Each node requires specific expertise because of unique management interfaces, engineering requirements, and specialized protocols. Based on this pattern, OPEX will continue to rise to an unsustainable level.

    There exists a lucrative opportunity in “intelligent automation” for software developers. Imagine a management platform that can interface with hundreds or thousands of network nodes, monitor key performance indicators, and react autonomously to those indicators. A network which can dynamically reallocate it’s resources based on demand and which can heal itself after a catastrophe, without any human intervention. To build that type of functionality into the existing network elements would require long term architecture investment. Don’t get me wrong, that type of investment is necessary. But for the enterprising folks, there exists the immediate opportunity of developing an off-board platform that can perform this function.

    Management systems today simply provide alarms and logs which indicate symptoms of network problems such as congestion, link outages, hardware failures, etc. Why not take it a step further? Correlate these indicators across the entire network and execute reactive measures autonomously. All the building blocks are in place: alarms, logs, performance counters, protocol analyzers, and remote management interfaces such as CLI. All that needs to be done is to pull it together using an intelligent and rules-based software suite. The benefit to the network operator would be a significant reduction in OPEX costs such as headcount and training.

    Of course I’m in no way claiming credit for such an innovation. There are already a handful of platforms available in the IT world which do this at a rudimentary level. But for traditional telephone, wireless networks, VoIP, digital cable, IPTV, etc? Some would see a gap, others see opportunity.

  6. Regarding the earlier comment about gym & fitness equipment connected to the network…. I haven’t investigated it further, but coincidentally, my neighbor (who happens to work for Cisco), noticed I had installed a new underground sprinker system in my yard. Honest-to-goodness, when she saw me out there one day programming the small 6-station automatic timer box attached to the side of my house, she smiled broadly and asked: “So, when’s that thing going to be network addressable?”. Hmmm. I wonder.

  7. If you want to read an account (albeit fictional) of what a hyperconnected world could look like, I’d strongly suggest reading Rainbows End, by Vernor Vinge (a former computer science professor) http://www.chapters.indigo.ca/books/item/books-978081253636/0812536363/Rainbows-End

    The idea’s he presents are one of the reasons I find this stuff cool to work on - the possibilities are nearly endless, and they are coming sooner than we think.

  8. Back in 1981, IEEE Spectrum published an article about the use of microprocessors in everyday life. The author ended the article with something like “we may not brush our teeth with microprocessors but their applications will be innumerable…”. Long and behold 25 years later we do brush our teeth with microprocessor equipped tooth brushes. I bet you that in 25 years time everything will be connected to a network even people, that’s the way technology is going, and Nortel will be part of it.

  9. But just how far?
    What if we were actually headed towards MHC (massive hyper connectivity)?
    Wouldn’t we then need a different way to look at the issue: more like a “connectivity field” rather than “connection lines”? In a way, untethered connectivity has already done that, but the interaction with the field is still at a particle-like sensor level.
    In a MHC scenario, this also is probably going away in favor of a wave-like distributed sensor.
    I wonder if the parallel with the power grid holds true: we already hit MHP (massive hyper power) status but we’re still using plugs, but this is only because wireless power was never efficient/viable: instead we developed power storage technology to replace that.

  10. Response to David Skowronski.

    Google … not just an internet search engine.

  11. I think hyper-connectivity will end up being ubiquitous around the world. It will be the hyper-applications that will drive the wedge between the haves and have-nots. The higher end hyper-applications will drive health, finance and personal management capabilities to a level not yet seen and gives the haves more to uh… have.

    The have-nots will have access to most of these apps but without all the bells and whistles. Similar to buying a Lexus vs a Toyota. The app companies will be working their higher profit margins on the Lexus market and leaving the lower end to always be wanting a bit more. It keeps the market segmented, easier to manage and ultimately more profitable That doesn’t means that society profits as much as it could, though. That would take some wholesale shifts in market dynamics. Something like a Grameen Bank approach to the hyper-apps might turn the tide in the future…

  12. John,

    I am curious about your view on ‘hyper-connectivity’. Your blog itemizes things like HVAC, home security, power meters etc. as part of your hyper-connectivity vision. I recently heard Bob Metcalfe mention that over 10 billion such monitoring and control devices are expected to be sold world-wide in 2007 and very few of these are networked, which severely limits their utility. The IEEE 802.15.4 standard already provides a standards based, and just as importantly and Ethernet based, approach to these devices that could integrate nicely with an Ethernet based vision of Business Made Simple.

    Does your vision include Nortel moving into the production of such devices? developing management applications? Perhaps just their integration into existing networks? It would first require a bit of a paradigm shift from low numbers of devices, high cost, higher speed, greater scalability, more powerful to low power, low speed, low cost however very great numbers. sort of a ‘Slow Food’ approach applied to networking.

  13. Is Nortel working with the likes of NTT, in regards to ubiquitous open platform. For example, I know that NTT have been working with a number of manufacturers (Hitachi, Sony, Ricoh, Panasonic) to look into IPv6 development & testing across their network. NTT have been part of the Japanese governments drive to promote the ubiquitous open platforms.

Leave a Reply