January 22, 2015 1 Comment
Software Defined Networking and Network Function Virtualization (NVF) themes dominated workshops and side conversations throughout the PTC 2015 venue in Honolulu, Hawai’i this week.
SDNs, or more specifically provisioning automation platforms service provider interconnections, and have crept into nearly all marketing materials and elevator pitches in discussions with submarine cable operators, networks, Internet Exchange Points, and carrier hotels.
While some of the material may have included a bit of “SDN Washing,” for the most part each operators and service provider engaging in the discussion understands and is scrambling to address the need for communications access, and is very serious in their acknowledgement of a pending industry “Paradigm shift” in service delivery models.
Presentations by companies such as Ciena and Riverbed showed a mature service delivery structure based on SDNS, while PacNet and Level 3 Communications (formerly TW Telecom) presented functional on-demand self-service models of both service provisioning and a value added market place.
Steve Alexander from Ciena explained some of the challenges which the industry must address such as development of cross-industry SDN-enabled service delivery and provisioning standards. In addition, as service providers move into service delivery automation, they must still be able to provide a discriminating or unique selling point by considering:
- How to differentiate their service offering
- How to differentiate their operations environment
- How to ensure industry-acceptable delivery and provisioning time cycles
- How to deal with legacy deployments
Alexander also emphasized that as an industry we need to get away from physical wiring when possible. With 100Gbps ports, and the ability to create a software abstraction of individual circuits within the 100gbps resource pool (as an example), there is a lot of virtual or logical provision that can be accomplished without the need for dozens or hundreds off physical cross connections.
The result of this effort should be an environment within both a single service provider, as well as in a broader community marketplace such as a carrier hotel or large telecomm interconnection facility (i.e., The Westin Building, 60 Hudson, One Wilshire). Some examples of actual and required deployments included:
- A bandwidth on-demand marketplace
- Data center interconnections, including within data center operators which have multiple interconnected meet-me-points spread across a geographic area
- Interconnection to other services within the marketplace such as cloud service providers (e.g., Amazon Direct Connect, Azure, Softlayer, etc), content delivery networks, SaaS, and disaster recovery capacity and services
Robust discussions on standards also spawned debated. With SDNs, much like any other emerging use of technologies or business models, there are both competing and complimentary standards. Even terms such as Network Function Virtualization / NFV, while good, do not have much depth within standard taxonomies or definitions.
During the PTC 2015 session entitled “Advanced Capabilities in the Control Plane Leveraging SDN and NFV Toward Intelligent Networks” a long listing of current standards and products supporting the “concpet” of SDNs was presented, including:
- Open Contrail
- Open Daylight
- Open Stack
- Open Flow
- Project Floodlight
- Open Networking
- and on and on….
For consumers and small network operators this is a very good development, and will certainly usher in a new era of on-demand self-service capacity provisioning, elastic provisioning (short term service contracts even down to the minute or hour), carrier hotel-based bandwidth and service marketplaces, variable usage metering and costs, allowing a much better use of OPEX budgets.
For service providers (according to discussions with several North Asian telecom carriers), it is not quite as attractive, as they generally would like to see long term, set (or fixed) contracts or wholesale capacity sales.
The connection and integration of cloud services with telecom or network services is quite clear. At some point provisioning of both telecom and compute/storage/application services will be through a single interface, on-demand, elastic (use only what you need and for only as long as you need it), usage-based (metered), and favor the end user.
While most operators get the message, and are either in the process of developing and deploying their first iteration solution, others simply still have a bit of homework to do. In the words of one CEO from a very large international data center company, “we really need to have a strategy to deal with this multi-cloud, hybrid cloud, or whatever you call it thing.”