Henri van den Bulk edited OpenFlow Switch.tex  about 9 years ago

Commit id: 2a7a66bfe045209e8944a6bb6c03a82587dcb199

deletions | additions      

       

\subsubsection{OpenFlow Switch}  In the previous section the high level OpenFlow protocol is described. To create the level abstraction OpenFlow addresses three (3) concerns: (1) Defining how data should flow that is received by a switch (flow-table), (2) ability to control/change the flow-tables based on network conditions, and (3) a standard communication between the controlling part and the switch. These different concerns are represented in Figure \ref{fig:switch}, Figure\ref{fig:switch},  which was taken from the OpenFlow switch specification documentation\cite{Goransson_2014}. The switch maintains flow-tables, typically build using Ternary Content Addressable Memory (TCAMs)\cite{yeung2014ternary}. Before describing what TCAM is we have to understand what the Content Addressable Memory (CAM) is. This is a specialized memory that is different then the typical Random Access Memory (RAM) found in modern computer systems.