* Does it or does it not depend on the application?
Back in the early days of networking when Larry first went to his company’s data communications institute to learn about data networks, the most important acronym was “IDOTA” or “It Depends On The Application.” Twenty years ago, enterprises had to choose the right network protocol or network technology based on the individual application. For example, when an application needed a bulletproof data delivery guarantee between two points, the first choice was probably a private line. If an application needed to cross a multi-point public data network and still needed to guarantee data packet integrity, the choice was usually X.25. Of course, 20 years ago a 1200-baud modem (1.2K bit/sec) was used to support the “mobile worker.”
Today, we propose that the current acronym should be “IDDOTA”, or “It Doesn’t Depend On The Application.”
We believe the ultimate architectural goal for any private or public network is to evolve into an applications delivery platform. Networks should be created in a way that IDDOTA; rather any application needed by business or consumers should and can be supported.
Of course, we know that X.25 protocols are still being used – and somewhere token ring, Burroughs Poll Select and SNA are still sitting between an application packet and an IP frame.
But even though network planners still have to deal with legacy data-communications protocols, we think it’s time to change the acronym and the philosophy behind it. As network designers evolve their current multi-protocol, multi-service network into a multi-applications delivery platform, we think the IDOTA acronym should be retired and IDDOTA should rule the day. Maybe even someday, we’ll stop calling the IT staff “network designers” and start to call them “applications delivery magicians.”
