OSPF was originally designed in an age when processors were much less capable, available memory was much smaller, and link bandwidths were much lower. To conserve processing power, memory, and n-the-wire bandwidth, OSPF was designed using fixed length fields (FLFs). TLVs are more difficult to process than an FLF; to process a set of FLFs, you build a structure that mimics the FLF formatting, and simple “impose” it on the memory location where you have stored the data to be decoded, as shown below.
In the FLF model, the structure can simply be imposed on the memory locations, and the values can be read directly. In the TLV model, each type code must be read to determine the kind of information and the length must be read to determine the size of the field. Only once these two items in the TLV header have been read can the actual data be related to a particular field in the resulting data structure.
In the intervening years, however, compute, storage, and network capabilities have increased dramatically; the following chart, taken from a book I’m working on, shows this growth since about the start of the “network era.”
As compute, storage, and Continue reading
Vendors marketing is getting overexcited with hyperbole and suddenly basic filtering such as access-lists are Deep Packet Inspection.
Packet munging for layer 2-4 is shallow packet inspection. Specifically, its when you match Ethernet MAC, IP Addresses and TCP/UDP port numbers but nothing else. At time of writing, shallow packet inspection is simple, cheap and part of the forwarding ASIC.
Devices that perform inspection at Layer 5-7 of the OSI model is deep packet inspection (DPI). This requires exponentially more complex handling of the data in the ASICs, awareness of data formats and flow operations. In addition, the applications that configure are complex and sophisticated (the CLI just doesn’t cut it).
The post Dictionary: Shallow Packet Inspection appeared first on EtherealMind.
The post Worth Reading: Fix EULAs appeared first on 'net work.