I spend a lot of time reading about network architecture. The problem is "networking" is overrun with vendor specific terms, technology, and products. It's anno

I spend a lot of time reading about network architecture. The problem is "networking" is overrun with vendor specific terms, technology, and products. It's annoying that if I want to learn about fundamental networking concepts, I need to sort through what jargon is referring to universal ideas, and what jargon is referring to a specific vendor ecosystem. Many experts have a tendency to refer to concepts using terms specific to the ecosystem they are familiar with. Often two vendors will refer to the same concept by two entirely different terms (e.g. competing implementations of the same protocol). Basically, the namespace for networking knowledge is polluted with proprietary crap from cisco, juniper and the like. The rise of SDN is slowly opening up the networking world, but there are quite a few proprietary holdovers. This makes broad learning quite difficult.