With over 19 Internet of Things (IoT) radio protocols in use today, the need for consolidation is clear.
Short of consolidation, integration of IoT devices will occur at the application layer with robust APIs.
Many of the ‘things’ in the IoT like lights, sensors, switches, HVAC controls, and other actuators will be connected via wireless gateways because rewiring a building is expensive. I counted over 19 wireless protocols between standards-based protocols, proprietary protocols, and protocols that have a basis in both standards and proprietary protocols. Continue reading “Over 19 IoT Radio Protocols Drive the Need for Integration APIs”→
Standards are great for ensuring interoperability when the requirements are well understood.
The requirements needed to support applications leveraging SDN are not well understood and standardization will inhibit innovation.
SDN northbound APIs don’t need standardization – at least not at the functional level where command and control semantics live. Like others, I think SDN is far too early in its development to warrant standardization at a functional level. SDN would benefit from a standardized architectural approach such as SOAP or REST, which describe different programmatic approaches to interconnecting services, because those are software architectures that are familiar to application developers. In order to generate and maintain momentum for SDN innovation, there must be as few barriers to application development as possible. Continue reading “Now Is Not the Time to Standardize Northbound SDN APIs”→
Standards without conformance are useless. Conformance testing resolves varying interpretations which enables interoperability.
OpenFlow is starting to fragment along product and vendor partner lines, which isn’t good for either vendors or customers.
When it comes to standards, most if not all IT professionals agree that standards are important. The obvious reason is that standards allow enterprises to integrate the software and hardware they want to use rather than being confined to a subset of products from one vendor or a vendor’s partner program. That’s the high road. The reality is that IT just wants equipment that works whether or not they are standards based, and that’s because having a technical standard isn’t going to enable interoperation and integration. Continue reading “Without Standards Conformance, OpenFlow Fails to Deliver Interoperability”→
Mobility to be the next big product trend for enterprise video conferencing technology
There are a number of ways to extend corporate video conferencing solutions to mobile devices
The increasing adoption of video conferencing systems in the enterprise combined with the increasing adoption of video-capable mobile devices is set to both challenge and annoy IT departments. One of the problems is that the software and systems that deliver business-class video conferencing (from Cisco, IBMLifeSize, Magor, Microsoft, Polycom, Vidyo etc.) are completely different from the software that runs on the mobile devices wheedling their way into the enterprise as part of the BYOD phenomenon (from Apple, Google, Fuze, Skype, Tango, etc.). It’s unlikely that the two will learn to coexist peacefully anytime soon. Enterprise IT departments will continue to deploy on-premise or cloud-based video conferencing solutions that meet security and compliance requirements. And end users will separately use separate consumer-friendly video conferencing technology on their mobile devices with or without IT’s formal blessing. Continue reading “Extending Corporate Video Conferencing to Mobile Devices”→
You must be logged in to post a comment.