Othman Othman M.M., Koji Okamura Kyushu University Proceedings of the 33 nd Asia-Pacific Advanced Network Meeting Thailand, Chiang Mai, 2012/2/15 1

Outline: 1. Goal. 2. Motivation. 3. An attempt to solve the problem Network Equipment to Equipment flow installation. 4. Steps for Flow delegation. 1. Flow Aggregation Algorithm. 2. Finding Equipment. 3. Programming flows & Security aspect. 4. Tunneling. 5. Evaluation. 6. Conclusion. 2

1- Goal: Improve OpenFlow. Support self-reactive behavior. Step towards having wider adoption of OpenFlow. Reduce load on controller. 3

2- Motivation: Tight coupling between OpenFlow switch and controller. Every thing is up to the controller. Controller might be bottleneck. number of flows that can be installed by the NOX controller as shown in [1] are 30K flow/sec, and the flow arrival rate in [2] that is 100K flow per second. Figures might have changed but debate still going. [1].Tavakoli, A., Casado, M., Koponen, T., & Shenker, S. (n.d.). Applying NOX to the Datacenter. Proc. HotNets (October 2009). [2]. Kandula, S., Sengupta, S., Greenberg, A., Patel, P., & Chaiken, R. (2009). The nature of data center traffic: measurements & analysis. Proceedings of the 9th ACM SIGCOMM conference on Internet measurement conference (p. 202–208). ACM. 4

2- Motivation: Current OpenFlow’s control model: Controller to Equipment only: Equipment exchange information only with the controller. Current Internet: Equipment to Equipment only: equipment exchange information with each other. Target: Controller to Equipment, AND Equipment to Equipment: to give OpenFlow the ability to exchange information between equipment in addition to controller. Figure 1: OpenFlow Control Mode Fig2. Regular Network Information exchange. Figure 3: Enhanced OpenFlow Control Mode 5

2- Motivation: Why Equipment to Equipment can help: Network edges are suitable for installing flows, since all of the incoming and outgoing packets must pass through them. Network edges can be used in different applications like, implementing security, traffic policies, traffic tagging, ….. However, equipment flow table is limited. Also Controller can be a bottleneck. Equipment to Equipment Flow installation: Provide a new method for the overloaded equipment to act on their own, without involving the controller. 6

3-An attempt to solve the problem: 1. Network equipment to Network equipment Flow Programming: To create traffic-aware self-reactive network. Can be used to delegate some flows to less loaded network equipment. To easily program whole network without loading controller. 7

3- Network Equipment to Equipment flow installation : To reduce load off the controller. Give the equipment ability to act by their own to reduce load off loaded equipment. Alternative way to install flows to whole network (e-e propagation). PE P P P Packet Flows to manipulate headers in packets Fig1. Equipment overloaded, due to many flows to carry out. PE P P P Fig2. Overloaded equipment delegates some flows to other equipment. PE P P P Packet Flows to manipulate headers in packets Fig3. Reduced load off the overloaded equipment. 8

4- Steps for Flow delegation : No Start Need to delegate? Find aggregate able flows. And aggregate them. Find equipment to program. Program flows from 3 to equipment form 4 Finish Yes Tunnel aggregated flows from 3 to target equipment form

4- Steps for Flow delegation : 1- Flow Aggregation Algorithm : How to delegate flows? Aggregate flows that have common features, and responsible for some portion of traffic. i.e. to aggregate many flows to one. Delegate the aggregated flows to other equipment. Use Flow Aggregation Algorithm. Overloaded equipment flows = original flows – delegated flows. aggregated flow (one or more) Flow Table Range of portions of total traffic e.g. (20%-30%) 10

4-Steps for Flow delegation: 1- Flow Aggregation Algorithm : Java Program to evaluate the efficiency of Flow Aggregation Algorithm. FAA success rate of aggregation = 79.7 % TA-FAA Evaluation: Start Build Histograms for all Fields Aggregation percentage? Finish Strict None Wide Aggregate SrcIP Aggregate DstIP Strict Wide Find common values from two wide aggregations. None Strict Wide Fail None Strict None, Wide TA-FAA : 11

4: Steps for Flow delegation 2- Finding Equipment : 3 way programming method: Request, Accept, Confirm Request is a kind of controlled flooding. The delegating device The device receiving delegation Installation Request? Flows to be delegated. LFI= 2, TTL=5 Confirm Other device receiving delegation Accept Self Identification. Confirm Installation Request? Flows to be delegated. LFI= 1, TTL=4 Accept Self Identification. Request is a kind of controlled flooding: Limited propagation; request will have a count to valid hop counts.(TTL) Limited number of acceptance, (LFI); Level of Flow Installation. Negative Acknowledgement. Expiry time. 12

4: Steps for Flow delegation 3- Programming flows & Security aspect : Signed by Controller Signed by Equipment 1 Signed by Equipment 2 Figure 1: Initial Flow Installation. 1 2 Flow Figure 2: Flow Delegation (e-e Flow Installation) 1 2 Request Flow Req. hash 2’s ID Flow Flow’s Hash 2’s ID 1’s ID

4: Steps for Flow delegation 3- Programming flows & Security aspect : Why to do that: case of flow includes sending packet to controller Signed by Controller Signed by Equipment 1 Signed by Equipment 2 Figure 1: Controller installs flow. 1 2 Flow Expect packet from eq.1 Figure 2: This flow was delegated. 1 2 Flow Expect packet from eq.1 Figure 3: Accepting packets form eq.2 instead of eq Expect packet from eq.1 Flow Flow’s Hash 2’s ID 1’s ID eq.2 used the signed fields it got form eq.1 So controller will accept 14

4: Steps for Flow delegation 4- Tunneling : In such cases: eq.4 have to tunnel packets to eq.2. This is done using IP tagging. (similar to VLAN tag) Also eq.1 uses the aggregated flow (1 flow) to tunnel traffic to eq.4. Flow Fig1. flows are stitched to form a path defined by controller Flow Fig2. Path might break because eq.2 expects packets from eq.1 or the interface of eq.2 that connects it to eq

5- Evaluation: Run simulation on NS3 using : Regular OpenFlow. Modified OpenFlow. Collaboration for experimenting on NICT’s JGN-X. Compare edge equipment load, all equipment load. Evaluate efficiency to reduce load. Evaluate traffic generated by the new enhancement. 16

6- Conclusion: Aim to improve OpenFlow by reducing load off the controller, make it self-aware and self-reactive,. Achieving goals by proposing a new enhancements to OpenFlow: Network equipment to equipment flow installation. Proposing Flow Aggregation Algorithm, to enable the enhancements. Simulation shows the success rate of FAA is 79.7 % 17

Q & A: Thanks for listening. 18