ts matter whether element is head-end, mid-point, or exit-point. To achieve TTP, moreover modifications are required as per the current need. As FAWG get success in developing, negotiated switch model through Table Type Patterns, it provides awareness about elements potential to the applications placed above the controller, at least from a behaviour profile aspects. Example of the need for TTP or FPMOD (Forwarding Plane Models) (OpenFlow, n.d.). Hardware tables can be shared when they have similar data with low key variation e.g., logical tables with two views: MAC forwarding and MAC Learning. This table can be implemented many different ways including as an individual hardware table. OpenFlow controller must have different tables for MAC learning and MAC bridging in order to implement MAC learning/bridging. Currently, there is no method to tie these two differing views. See Figure 5, for elementary example which shows the situation where synchronization of table of flow mods from the two different OpenFlow table entities may be requiredi.e., MAC forwarding before MAC learning is not possible. In Figure 5, IPv4 and IPv6 tables directed to group tables emulate the use of next hop abstraction in conventional FIBs for rapid convergence. CONFIG AND EXTENSIBILITY The of-config protocol was initially planned to set OpenFlow related information on the network element (of-config). OpenFlow Management and Configuration (of-config) is a unusual set of protocols that defines a mechanism for OpenFlow. OF-Config was developed under Open Network Foundation which provides set of rules to access and modify configuration data on an OpenFlow switches. It was designed for OpenFlow implementation on both physical and logical switches. (DiffServ --The Scalable End-to-End QoS Model. Retrieved March 30, 2017) The OF-Config protocol shows the following components of the controller- switch management: Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Introduction to OpenFlow Figure 5. Example of Compl