General – Advice on Numbering Policies in Networking
There are several situations where we need to write some form of policy such as QoS, routing policies used in for example redistribution, filtering and policy-based routing, dot1x and so on. Lately I had to update a policy used by the master controller (MC) in an IWAN design. What are some important things to consider when writing the policy?
The number to start with – If you start with the number one then it won’t be possible to insert anything above this line at a later time. How certain are you that you will never have to put anything before the starting line? My recommendation is to start with a higher number such as 100.
Space between each line – Don’t number your lines 100, 101, 102, 103 and so on. Leave some more space between each line in case you have to insert something later between two lines. A spacing of 10 should be fine for most situations.
Go from most granular to least granular – The policy should go from as granular as possible to the least granular at the end. If you have a statement that is too broad you may catch more than you expected even Continue reading
It follows reports that Broadcom is planning an unsolicited bid for chipmaker Qualcomm.
This follows yesterday's news that Broadcom is relocating its headquarters to the U.S.
NetApp teamed up with Cisco on converged infrastructure seven years ago.
Expect more consolidation of SD-WAN and networking vendors to come.
Black Duck’s security technology automates the detection of vulnerabilities in open source software.
CenturyLink closes on Level 3 for $34B; Microsoft Azure to triple its capacity in China; Telefonica Chile virtualizes its core network with Ericsson.
The company’s revenues grew 50.8% year-over-year.