Number one -- a business model that carriers can have that can make them profitable. This is really a joint industry effort -- no vendor alone, no carrier alone can do this.
Number two -- there are certain standards that need to be put in place for an effort like the Infranet to succeed. If, for example, the way in which client applications interact with the network, and the way in which carriers interact with other carriers is different from one carrier to another, and different from one client to another, you will have a mess. A very, very, complex mess. Things like this can only be addressed by standards -- worldwide, open universal standards.
What we would like to do is create two standards affiliated with the Infranet. One is called the client-to-network interface, where an application can tell the network what attributes it wants the network to satisfy, such as what level of security and quality it needs, and how long it needs them for. It passes this information to the network, and the network can then, in return, say whether or not it can satisfy the request.
The second is a carrier to carrier interface. Inside the network, [there is] more than one carrier. The problem there is that, for one request to get from its source to its destination it will probably pass through multiple carriers. If I'm not able to express the communication's needs from one carrier to another, I lose the ability to provide the high quality, reliability and security it needs.
Advanced IP Pipeline: And then there's the billing question.
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
