Othman Othman M.M. , Koji Okamura Kyushu University 1 Outline: Goal - PowerPoint PPT Presentation

Othman Othman M.M. , Koji Okamura Kyushu University 1

Outline: Goal . 1. 2. Current Technologies. 3. Limitations of Current Technologies. 4. Advantages of Combining Technologies. 5. How to Combine Technologies. 6. Anycast Scenario 7. BitTorrent (P2P) Scenario. 8. Usage Scenario. 9. OpenFlow Overview. 10. Requesting Content. 11. Implementation. 12. Conclusion. 2

1 ‐ Goal: � To have contents with high availability. � Improving the availability of the content server. � To improve the overall usage of bandwidth of the whole network. 3

2 ‐ Current Technologies: � Anycast: � Peer to Peer: � Multiple nodes with the � Depends on user clients to same anycast address (Sa). provide service. � Packet sent to (Sa) will be � Implements an application delivered to the node with layer overlay network. nearest location according � Overlays used to for indexing to the routing table. and peer discovery. Sa Sa Sa Fig 1. Anycast Fig 2. BitTorrent 4 Source :http://en.wikipedia.org/wiki/Image:Torrentcomp_small.gif

3 ‐ Limitations of Current Technologies: � Peer to Peer: � Anycast: � Overhead because of overlay � All of the content servers nature, protocol, peer must have identical discovery, and looking up in contents. index. � Lacks the flexibility, and � Service depends on user’s not dynamic. 10.10.10.1 contribution. Cont 1 192.168.0.1 Cont 2 Cont 3 Router 1 Router 2 Cont n Fig 2. BitTorrent 10.10.10.1 Router 3 Router 4 Source : Cont 1 http://computer .howstuffworks. Cont 2 192.168.0.2 com/bittorrent2 Cont 3 .htm Cont n Dest ination Next ‐ Hop Distance 192.168.0.0 127.0.0.1 0 10.0.0.1 192.168.0.1 1 5 10.0.0.1 192.168.0.2 2

4 ‐ Advantages of Combining Technologies: � Advantages of Anycast: � Advantages of Peer to Peer: � Fast and does not require any � High availability of popular effort of the users, because contents, due to users’ contribution choosing destination (decision in providing service. making) is done in the network. � Content Centric Network: � Treats contents as a primitive not the connection. � Combination of those technologies: � Choosing destination by network: to remove the burden of finding destination and thus a faster response. � Users contributing in service: to improve the availability, and improves the overall use of bandwidth in whole network (reduce bandwidth used by server). � Content ID: to have more flexibility down to the level of contents rather than the node level. 6

4 ‐ Advantages of Combining Technologies: � Anycast. � Peer to Peer. � Content Centric Networks. � Combination of those technologies: � Users contributing in service: to improve the availability, and improves the overall use of bandwidth in whole network (reduce bandwidth used by server). � Choosing destination by network: to remove the burden of finding destination and thus a faster response. � Content ID: to have more flexibility down to the level of contents rather than the node level. Anycast Manager Content Server To: Au Content Su Cont id=X ID = X To: Su Get Cont id=X Content Client A Client B ID? Au Bu 7

5 ‐ How to Combine Technologies: � We have designed the “Content Anycasting” that combines different technologies strength points as shown in the previous slide. � Content anycasting manages to do its rule by using: � OpenFlow for the process of choosing the destination, along with the aid of the content server. � A new procedure for requesting content is introduced to enable the clients to get the contents. 8

6 ‐ Anycast Scenario: 10.10.10.1 10.10.10.1 Cont 1 Cont 2 Cont 1 10.10.10.1 Client Cont 3 Cont 2 will send Cont 3 Cont n packet to Cont n 10.10.10..1 Cont 1 Cont 2 Cont 3 Network will Cont n choose end 10.10.10.1 node based on routing measures 9

7 ‐ BitTorrent (P2P) Scenario: 100% Seeder 70% 30% Tracker 100% Seeder 0% 10

8 ‐ Usage Scenario: 1 Anycast Manager Content Server 2 10.10.10.1 3 if Destination IP: 10.10.10.1 & Content id: 12345 Change : Destination IP: 192.168.10.1 Client A Client B 192.168.10.1 192.168.20.1 11

8 ‐ Usage Scenario: This figure shows the first phase of the content request. Anycast Content Manager 1 Server � Step 1: client B 10.10.10.1 requests the content 192.168.20.1 192.168.10.1 id. 2 Client B Client A � Step 2: server sends Content id: 12345 the content id to the client B. 12

8 ‐ Usage Scenario: Anycast Manager Content Destination IP: Server 2 10.10.10.1 10.10.10.1 Content id: 12345 Destination IP: 1 192.168.10.1 Content id: 12345 Client B Client A 3 192.168.20.1 192.168.10.1 13

9 ‐ OpenFlow Overview: � Separates routing decision making (in controller) and the forwarding (in the switch or router). � Matching in the switch or router is done according to Layer 2, 3 and VLAN headers. Figure 1: OpenFlow switch (ref: Nick McKeown et al, “OpenFlow: enabling innovation in campus networks”) 14

9 ‐ OpenFlow Overview: � OpenFlow relies on the Flow ‐ table, which is contains: Figure 1 � Header fields are the ones the incoming packet is matched against: Figure 2 � The actions can be : forwarding the packet to physical port, enqueue the packet in a physical port’s queue, dropping the packet or modifying incoming packet’s header fields 15

10 ‐ Requesting Content: Two phases: � Phase 1: � Client browses to find desired content. � Client sends the request (e.g. HTTP GET) � Server responds with content ID, to be sued in phase 2 to get the file. � Phase 2: � Uses 3 way handshake. � Requires modification to the TCP. 16

10 ‐ Requesting Content: � Phase 2: 3 way handshake: OpenFlow New Client Current Client router � Start with SYN packet that Destination: is sent to the server. serverIP :SYN Destination: CurrentClientIP � Using OpenFlow and the :SYN content id packet will be SYN/ACK redirected to an other client With CurrentClientIP (Current Client). � Current client acknowledge Destination: to the SYN with its IP in CurrentClientIP :SYN packet. � New client starts to use the Current client’s IP address in the session. 17

11 ‐ Implementation: � Currently we are building redirection system, modified content server, modified clients and using the reference OpenFlow implementation. � First, Redirection system with one Anycast manager. � Second, duplicate redirection systems each with its own Anycast manager. � Aiming to measure: communication cost, response time, efficiency in different load patterns and others. � And comparing those values to other solutions like the anycast and peer to peer. 18

12 ‐ Conclusion: � Content anycasting aims to combine the strength points of different technologies like the anycast, peer to peer and content centric networks . � The goal is to improve the content server by increasing its serving capacity, with less overhead and more efficient usage of the bandwidth in the whole network. � In a way that overcomes the limitations of those technologies. 19

13 ‐ Q&A: � Thank you for listening. 20

Backup: 21

4 ‐ System Overview: Anycast Manager: Receive � Functionality: redirection request � Receive the redirection request form the content Lookup AS numbers for each current user server. client’s IP address in the � If the redirections are in the redirection request same AS make redirections Generate copies of the and send them to the redirection request OpenFlow routers or each designated for one AS switches. � And if in different AS send Is the Yes No the redirection request to the copy for this AS appropriate anycast manager. Send it to the Anycast Process it by the manager of the AS to Redirection which this copy is controller designated to 22

1 ‐ Introduction: � Internet plays many roles, one of them is delivering content. � Relying mainly on the Client / Server model and Peer to Peer models. � Divers contents: audio, video, large files. � Number of users increases. � Bandwidth for users increases. � Traffic increases by a factor of 1.7 / year. 23

2 ‐ Motivation: � This created a kind of imbalance: � Number of client increases. � Servers have to implement solutions to keep up with � Also the bandwidth for the this increase. clients increases. � More efforts on the server � Client side have more and side. more demands. diverse content diverse content more bandwidth more bandwidth more clients more clients Server Clients Server Clients 24

8 ‐ Usage Scenario: This figure shows the initiation of the redirection : � Step 1: the server sends the redirection request, which includes the contents ids and the IP addresses of the clients downloading those files along with their uploading capabilities. � Step 2: the Anycast manager makes the OpenFlow redirections and sends them to the OpenFlow switch or router. � Step 3: OpenFlow switch or router stores the redirections. 25

7 ‐ System Overview: � Content Server. � Anycast Manager. � OpenFlow router or switch. � User Client. Content Anycast Anycast Server Manager Manager client client Autonomous System 1 Autonomous System 2 26

27