Sometimes during exploration or projects, I want to take a YANG model and convert it along with related dependencies to a Swagger format (think OpenAPI if you’re not familiar with this) so I can create a REST or RESTConf API interface. OpenDayLight does something very similar for it’s Swagger based North Bound Interface (NBI), more information here and just being able to look at the model this way is sometimes helpful. If you’re wondering how helpful this could be, think about developing a client. Using this approach, it’s possible to create stub client and server code for a software implementation, leaving just the logic of what to do when a POST is made or a GET is requested etc.
You may be familiar enough with YANG to know that YANG is a modeling language with its own extensible type system. These YANG models are mostly used for modeling how a programmatic interface to control a feature should be on routers and switches. More recently thanks to the wave of automation sweeping across the globe, YANG models are now used for modeling services, which in turn are rendered over one or more nodes by something else. We’re not going to cover Continue reading
The move provides enterprises that are overwhelmed by available options with the choice of tested, open source tools that can be used to construct cloud-native-based applications.
The CableOS software core can be deployed on common-off-the-shelf servers.
Separating the control plane and the user plane in wireless networks will allow network operators more flexibility with different types of traffic.
The firm's SaaS platform acts as a translation layer between the language a developer is using to write code and where that code is being sent.
Over at CIMI, Tom Nolle Considers whether the open API is a revolution, or a cynical trap. The line of argument primarily relates to accessing functions in a Virtual Network Function (VNF), which is then related to Network Function Virtualization (NFV). The broader point is made in this line:
This is true—if you design the API first, it will necessarily impose information flow between the different system components, and even determine, at least to some degree, the structure of the software modules on either side of the API. For instance, if you decide to deploy a single network appliance vendor, then your flow of building packet filters will be similar across all devices. However, if you add a second vendor into the mix, you might find the way packet filters are described and deployed are completely different, requiring a per-device module that moves from intent to implementation.
While this problem will always Continue reading
Continue reading "Interview with Juniper Networks Ambassador Jeff Fry"
The integration will allow customers to deploy and manage Redis as a stateful Kubernetes service.

12 October to 6 November 1998, Minneapolis, United States: a point in time that cannot be forgotten. The ITU Plenipotentiary conference (PP-98) took place, recognizing perhaps for the first time points that impacted the future of Information and Communication Technologies (ICT) diplomacy.
The conference acknowledged the need to have the private sector as part of the union membership, together with the “associates category” for some of its study groups. Furthermore, the resolution calling for the World Summit on the Information Society (WSIS) first emerged, introducing ITU’s role in the “evolution of Internet as a means of global communication.”
The scene prior to this was an intense discussion on digital evolution. Governments were starting to understand how ICTs could help solve many issues and contribute to economic growth. The “divide” that was once prevailing between the north and the south economically, or between the developing and developed world, quickly started to shift to a “digital divide,” not only between different countries and regions, but among one country and its own boundaries and cities.
In 2001, the ITU Council approved the WSIS Summit in two phases (2003 in Geneva and 2005 in Tunisia). Later, the UN General Assembly approved the Continue reading

When you think of a “security” company, what comes to mind? Is it a software house making leaps in technology to save us from DDoS attacks or malicious actors? Maybe it’s a company that makes firewalls or intrusion detection systems that stand guard to keep the bad people out of places they aren’t supposed to be. Or maybe it’s something else entirely.
What comes to mind when you think of a traditional security company? What kinds of technology do they make? Maybe it’s a firewall. Maybe it’s an anti-virus program. Or maybe it’s something else that you’ve never thought of.
Is a lock company like Schlage a security company? Perhaps they aren’t a “traditional” IT security company but you can guarantee that you’ve seen their products protecting data centers and IDF closets. What about a Halon system manufacturer? They may not be a first thought for security, but you can believe that a fire in your data center is going cause security issues. Also, I remember that I learned more about Halon and wet/dry pipe fire sprinkler systems from my CISSP study than anywhere else.
The problem with classifying security companies as “traditional” or “non-traditional” Continue reading