In this featured white paper from Edgewater Networks, we learn how an SaaS model gives an enterprise feel to SMB security. Download the white paper now to read more.
Now you can have a Telefónica NFV MANO stack of your very own.
For those that followed my SDN Protocols series last summer, you might have noticed a missing entry: NETCONF. This protocol has actually existed for some time (the original now-outdated specification was published in 2006), but is appearing more often, especially in discussions pertaining to network automation. The current, updated specification – RFC6241 - covers a fairly large amount of material, so I will attempt to condense here.
NETCONF operates at the management layer of the network, and therefore plays a role similar to that of OVSDB. This is in contrast to protocols like OpenFlow which operate at the control plane.
A key difference between NETCONF and other management protocols (including SNMP) is that NETCONF is built around the idea of a transaction-based configuration model. The NETCONF specification provides for some optional device capabilities aimed at assisting operators with the lifecycle of configuring a network device, such as rolling back a configuration upon an error. Unfortunately, not all network devices support such capabilities, but the protocol was built to make it easier to discover what kind of capabilities a network device can support.
Before getting into the semantics Continue reading
For those that followed my SDN Protocols series last summer, you might have noticed a missing entry: NETCONF. This protocol has actually existed for some time (the original now-outdated specification was published in 2006), but is appearing more often, especially in discussions pertaining to network automation. The current, updated specification - RFC6241 - covers a fairly large amount of material, so I will attempt to condense here.
NETCONF operates at the management layer of the network, and therefore plays a role similar to that of OVSDB. This is in contrast to protocols like OpenFlow which operate at the control plane.
A key difference between NETCONF and other management protocols (including SNMP) is that NETCONF is built around the idea of a transaction-based configuration model. The NETCONF specification provides for some optional device capabilities aimed at assisting operators with the lifecycle of configuring a network device, such as rolling back a configuration upon an error. Unfortunately, not all network devices support such capabilities, but the protocol was built to make it easier to discover what kind of capabilities a network device can support.
Before getting into the semantics of the NETCONF protocol itself, it’s worth briefly jumping ahead to address the Continue reading
You’ve hit brain freeze. It seemed like such a great idea at the time, but now that it’s 2am, the application is down, and you can’t find the problem, maybe it wasn’t after all. Or maybe it’s 4pm, and you’re sitting at your desk trying to figure out how to resolve a problem, or build a system. You’re completely stuck, and you’ve no idea what to do next.
In either case, it feels like you’ve researched every avenue, you’ve thought of every angle, you’ve gone over the problem time and time again, and your brain just can’t wrap around the problem any longer. You go back over the same material again and again, just trying to make sense of it.
You’ve hit brain freeze. What’s the solution?
Talk to the dummy.
No, I don’t mean your boss. And I don’t mean that person down the hall you think just doesn’t “get it.” We’ll cover that topic later. I mean, literally, the dummy. In the “old days,” there were software shops that would literally set aside an office for a dummy. There was a white board, a desk, and a dummy sitting behind the desk. Your job, as an engineer, Continue reading
Network complexity plays a very important role during network design. Every network designer tries to find the simplest design. Although there is no standard definition for the network complexity yet, there are many subjective definitions. In today network designs decisions are taken based on an estimation of network complexity rather than absolute, solid answer. If… Read More »
The post Network Complexity appeared first on Network Design and Architecture.
A few years ago Google made a proposal for a new HTTP compression method, called SDCH (SanDwiCH). The idea behind the method is to create a dictionary of long strings that appear throughout many pages of the same domain (or popular search results). The compression is then simply searching for the appearance of the long strings in a dictionary and replacing them with references to the aforementioned dictionary. Afterwards the output is further compressed with DEFLATE.
CC BY SA 2.0 image by Quinn Dombrowski
With the right dictionary for the right page the savings can be spectacular, even 70% smaller than gzip alone. In theory, a whole file can be replaced by a single token.
The drawbacks of the method are twofold: first - the dictionary that is created is fairly large and must be distributed as a separate file, in fact the dictionary is often larger than the individual pages it compresses; second - the dictionary is usually absolutely useless for another set of pages.
For large domains that are visited repeatedly the advantage is huge: at a cost of single dictionary download, all the following page views can be compressed with much higher efficiency. Currently we aware Continue reading
I will be attending this year’s Cisco Live US in San Diego!
This is my first Cisco Live, so I dont really know what to expect. There are alot of great sessions that I want to attend (if they are not already full), and I will be posting my week here when i have my sessions down.
If you want to connect for a coffee or a chat, feel free to drop me a mail/tweet, and im sure we can figure something out!
See you in San Diego!