Othman Othman M.M. 30/1/2012 1. Outline: 1. Advisory Committee Meeting: 1. Content Anycasting. 2. OpenFlow Enhancement. 3. Current Status. 4. Next Research

1

Updates of Study Progress

Othman Othman M.M.

30/1/2012

2

Outline:

1. Advisory Committee Meeting:1. Content Anycasting.2. OpenFlow Enhancement.3. Current Status.4. Next Research.

3

Outline:


4

1-Content Anycasting:Outline:1. Goal .2. Current Technologies.

3. Advantages of Combining Technologies.4. How to Combine Technologies.

5. Current Technologies’ Scenarios.6. Content Anycast Scenario.

7. Evaluation.1. Anycast Comparison.2. P2P Comparison.

8. Conclusion.

5

1-Content Anycasting: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.

Nowadays many Future Internet researches, technologies going.OpenFlow is one of candidate Future Internet

technologies. to create Circuit based like systems.

To support mobility, computing centers ……

6

1-Content Anycasting:2-Current Technologies.

Anycast:Multiple nodes with

the same address (Sa).

Packet sent to (Sa) will be delivered to the node with nearest location.

Peer to Peer:Depends on user clients

to provide service.Implements an

application layer overlay network.

Fig 2. BitTorrentSource :http://en.wikipedia.org/wiki/Image:Torrentcomp_small.gif

Sa

Sa

SaFig 1. Anycast

7

1-Content Anycasting:2-Current Technologies.

Anycast:All of the content

servers must have identical contents.

Lacks the flexibility, and not dynamic.

Peer to Peer:Overhead because of

overlay nature, protocol, peer discovery, and looking up in index.

10.10.10.1

10.10.10.1

192.168.0.2

192.168.0.1

Router 1Router 2

Router 3 Router 4

Routing Table : Destination Next-Hop Distance

192.168.0.0 127.0.0.1 010.0.0.1 192.168.0.1 110.0.0.1 192.168.0.2 2

Cont 1Cont 2Cont 3Cont

n

Cont 1Cont 2Cont 3Cont

n

Fig 2. BitTorrentSource : http://computer.howstuffworks.com/bittorrent2.htm

8

1-Content Anycasting:3-Advantages of Combining Technologies.

Anycast.Content Centric

Networks.Peer to Peer.

Combination of those technologies:Users contributing in service: to improve the

availability, and improves the overall use of bandwidth in whole network.

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.

9

1-Content Anycasting:4-How to Combine Technologies.

Content anycasting does its role 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. Conte

nt Server

Client A

Anycast Manager

Client B

Su

Au BuOpenFlow Router

10

1-Content Anycasting:4-How to Combine Technologies.

The new procedure for getting the content:

Phase 1: getting the content ID. (e.g.: from the URL).

Phase2: using the content ID in Probe protocol.

Phase 3: getting file via TCP.

Fig 1: Procedure for getting content(Hand shake of the Probe Protocol)

New ClientOpenFlo

wrouter

Current Client

Destination: serverIP :START

Destination: CurrentClientIP :START

START/ACKWith CurrentClientIP in the probe header

ACK / ACKDestination: CurrentClientIP

TCP Session

Ph

ase

2P

hase

3

11

1-Content Anycasting:5-Current Technologies’ Scenarios.

Anycast:

10.10.10.1

10.10.10.1

Cont 1Cont 2Cont 3Cont n



10.10.10.1

Client will send

packet to

10.10.10..1

Network will

choose end node based on routing

measures

12

1-Content Anycasting: 5-Current Technologies’ Scenarios.

P2P; BitTorrent:

Tracker

100%Seeder

100%Seeder

70%

30%

0%

13

1-Content Anycasting:6-Content Anycast Scenario.

Content Server

Client A

Anycast Manager

Client B

Su

AuBu

Get Content ID form

URL

Content ID = X, in URL

To: SuCont id=X

To: AuCont id=X

Redirection Req.

Threshold

reached

Redirection

OpenFlow Router

TCP Session

14

1-Content Anycasting:7-1Evaluation: Anycast Comparison.

Using simple simulator, built using Java.Simulates a network with 5 areas (5 networks);

Content Anycast: use only one server.Regular Anycast: 5 replica servers each in one network.

Measure the server load : number of connections the server serves.

Shows that :Regular Client server: single server load is 100% (one

server for all)

Regular anycast: each server out of 5 load is 20%.Content Anycast : single server load is 50%,33%, 25%

and 20% respectively for case of client can serve 1, 2, 3, 4 other clients.

15

1-Content Anycasting:7-1Evaluation: Anycast Comparison.

Content Anycast can achieve same load as regular anycast but using only one server instead of 5.

16

1-Content Anycasting:7-2Evaluation: P2P Comparison.

To evaluate start-up time:Count the number of hops that the client

request travels across the network + hops reply travels.

Content Anycast, average hops = 5.

Regular P2P, average hops = 14.

Content Anycast has a lower hop count due to using pre-installed redirections that lead request to peer in same network.

17

1-Content Anycasting:7-2Evaluation: P2P Comparison.

To evaluate serve/management entity load.

Generate flash crowds periodically every 100 cycle.

Count the number of peer quivery requests received by the server/ management entity.

Content Anycast has a lower load due to using pre-installed redirections that lead request to peer in same network rather than the server.

Server load limit

18

1-Content Anycasting:8-Conclusion.

New mechanism for requesting content is designed to enable content anycasting.Using the content id in the process of getting the content.A Probe protocol is designed (modification to UDP) to be used.

Simulation shows that Content anycast can reduce load to match reduction of the regular

anycast (under some conditions) using only one server. On simulation scenario: 80% reduction in number of

servers.

Achieve shorter start-up time and less load on the management entity/ server compared to P2P. On simulation scenario: 74% reduction in number of hops

needed to get contents.

19

Outline:


20

2-OpenFlow Enhancement:

Outline:1. Motivation and Goal.2. An attempt to solve the problem (3

enhancements).1. First: Network Equipment to Equipment flow

installation.2. Second: Low Level Header Description.3. Third: Inactive Flows.

3. Flow Aggregation Algorithm.4. Evaluation.5. Conclusion.

21

2-OpenFlow Enhancement:1-Motivation and Goal.

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.

OpenFlow supports MAC, VLAN, IP, TCP, UDP.Better to have; more room for researchers.

[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.

22

2-OpenFlow Enhancement:1-Motivation and Goal.

Improve OpenFlow.Support self-reactive behavior.Reduce load on controller.Giving researchers more flexibility.Step towards having wider adoption of OpenFlow.

If OpenFlow is thought of as one of the Future Internet technologies, However some debate that OpenFlow have some limitations.

So our aim is to enhance OpenFlow, to make it more suitable for wider adoption and implementation within networks or in whole OpenFlow networks.

23

2-OpenFlow Enhancement:2-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.

2. Low level description of Headers:To easily adopt new protocols.To be able to program flows in very exact way.

3. New type of Flows: Programed as inactive flows and later activated by the flow. To provide the controller with a more relaxed way to handle

precisely timed tasks. Can cooperate with Device to Device programming.

24

2-OpenFlow Enhancement: 2-1 First: 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

PP

P

Packet

Packet

Packet

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

PP

P

Packet

Packet Packe

t

Packet

Packet

Flows to manipulate headers in

packetsFig3. Reduced load off the overloaded equipment.

25

2-OpenFlow Enhancement: 2-2 Second: Low Level Header Description.

OpenFlow can deal with headers of:Ethernet, IP, TCP, UDP,

ICMP, ARP, VLAN

This limits the usage to those protocols.

Using Low level definition of header fields can be more usable in case of new protocols.

Fig1: Fields from packets used to match against flow entriesAs shown in : OpenFlow Switch Specification Version 1.0.0, December 31, 2009

Offset form

beginning

Length

NameIs wild-carded?

Wildcard value

Value

0 6 MAC src No 00:11:22:33:44:55

16 4 New L3 Protocol src

Yes FF:FF:00:00:00

00:11:22:33:44

… …. …. …. …. .…

20 4 New L4 protocol filed

No 111111

Fig2: Low level description of headers

26

2-OpenFlow Enhancement: 2-3 Third: Inactive Flows.

Original OpenFlow: flows activated by default, controller keeps track of time.

Initially installed as inactive. (not usable).Activated on right time, by:

Explicit activation packet. Activation Flow. Preset time.

Migration

Migration

Fig3. Migration and Redirection using OpenFlow and Inactive Flows.

Inactive

Flows

Flows activatio

n

Migration

Migration

Fig1. Migration and Redirection using OpenFlow.

Migration

Migration

?

Fig2. Delay due to controller overload in Migration.

27

2-OpenFlow Enhancement:3-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.

Flow Aggregatio

n Algorithm

aggregated flow (one or more)

Flow Table


Start

Build Histograms for all Fields

Aggregation

percentage?

Finish

StrictNone

Wide

Aggregate SrcIP

Aggregate DstIP

Strict

Wide

Find common values from two wide aggregations.

None

Strict Wide

Fail None

Strict None,Wide

28

29

2-OpenFlow Enhancement:4-Evaluation.

Java Program to evaluate the efficiency of Flow Aggregation Algorithm.

FAA success rate of aggregation = 79.7 %

NS3 simulation to evaluate:Controller load reduction .Efficiency in reducing load off overloaded equipment.Traffic generated due to the new enhancements.

Compare the enhanced OpenFlow with the current OpenFlow by comparing; controller load, OpenFlow equipment load.

1%

-10%

10%

-20%

20%

-30%

30%

-40%

40%

-50%

50%

-60%

60%

-70%

70%

-80%

80%

-90%

90%

-100%

0%

40%

80%

120%

Success Rate of the TA-FAA

Range of traffic portion to be ag-gregated

Su

ccess

Rate

30

2-OpenFlow Enhancement:5-Conclusion.

Aim to improve OpenFlow by reducing load off the controller, make it self-aware and self-reactive, enable researchers to support their own protocols, and enable an easier support for time critical functions.

Achieving goals by proposing 3 new enhancements to OpenFlow:Network equipment to equipment flow installation.Low level Header description.Inactive flows.

Proposing Flow Aggregation Algorithm, to enable the enhancements.

Simulation shows the success rate of FAA is 79.7 %

31

Outline:


32

3-Current Status:1. Content Anycasting.

IEICE. Title of Special Section: Architectures, Protocols, and

Applications for the Future Internet. Title: On Demand Content Anycasting to Enhance Content Server

Using P2P Network. Volume and Number: Vol.E95-D,No.2,pp.-,Feb. 2012.

2. OpenFlow Enhancement. Working on the evaluation.

3. Next Research. Working on design.

33

Outline:


34

4- Next Research:Proposing a design for Future Internet.

Current internet faces many difficulties:Mobility.Multi-homing.Multicasting and Anycasting.Routing table growth.Security.Accountability.

A totally new design (clean slate) ; would be easier to solve the problems than add-on .

35

4- Next Research:An example scenario that shows the motivation.

Current Internet.

Target Future Internet.

Traffic Transfer agreement

ConnectionVPN

Traffic Transfer agreement

Connection

Traffic

Traffic of the mobile node will be treated same as it would be when the node was in its original network.

36

4- Next Research:Initial Design Steps:

Gathering information about current internet’s problems.

Making expectations for the Future Internet. (How we expect it to be, what we want it to handle).

Designing the Naming and addressing and their spaces.

Designing rules or guidelines that governs the naming and addressing.

Designing data transfer methods and mechanisms (such as; routing, delivering data, ….).

37

Outline:


38

Thanks for Listening.

39

Backup Slides:

40

1-Content Anycasting:Outline:1. Goal .2. Anycast vs. Multicast.

3. Current Technologies.

4. Advantages of Combining Technologies.5. How to Combine Technologies.

6. Current Technologies’ Scenarios.7. Content Anycast Scenario.

8. Evaluation.1. Anycast Comparison.2. P2P Comparison.

9. Conclusion.

41

1-Content Anycasting:3-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”)

42

1-Content Anycasting:2-Anycast vs. Multicast.

Anycast:Deliver original

packet to one out a group of hosts.

Deliver to nearest node depending on routing measures.

Multicast:Deliver multiple

copies of packets to multiple hosts.

AnycastMulticast

43




Combination of those technologies:Users contributing in service: to improve the

availability, and improves the overall use of bandwidth in whole network.

Regular Client/Server

User contributionIn Content Anycasting

44




Combination of those technologies:Choosing destination by network: to remove

the burden of finding destination and thus a faster response.

Tracker

Tracker Role in BitTorrentChoosing Destination By NetworkIn Content Anycasting

?Content Server

OpenFlow Router

45




Combination of those technologies:Content ID: to have more flexibility down to the

level of contents rather than the node level.

Using Content IDIn Content Anycasting

Content Server

Decision based on:

• IP address.• Content ID.

Regular

Content Server

Decision based on:

• IP address.• sometimes port#

OpenFlow Router

46

OF Enhancement:

47

4-2- Inputs of the FAA.Input is Flow Table.

Flow table entry have one or more fields form Fig 1.

Src IP and Dst IP can be wildcarded as defined by OpenFlow


Flow Aggregatio

n Algorithm


Flow Table

48

4-3-Outputs of the FAA.Aggregated Flow can use:

Parts of Src IP, Dst IP using wildcards.

Any other field as an exact match.


Flow Aggregatio

n Algorithm


Flow Table

Range of portions of total traffice.g.

(20%-30%)

49


By Building a Trie.Find length of wildcard.Value of wildcarded IP.

StartAdd the most

significant bit of each IP in each flow

to trie.If exist increment trie

node counter. Else create node and

increment counterIs

aggregation

successful?

Is memory

limit reached?

Add the next less significant bit of

each IP in each flow to trie.

If exist increment trie node counter. Else create node and

increment counter

Finish

Yes

Yes

No

No

1

2

3

45

7

Mark the trie node that has the best

ratio .6

Start


Aggregation %?

Finish

StrictNone

Wide

Aggregate SrcIP

Aggregate DstIP

Strict

Wide

Find common values from two

wide aggregations.

None

Strict Wide

Fail

None

Strict None,Wide

50


By building Histogram.

Start

Build Histogram

Is aggregatio

n successful

?

Finish

NoYes

1

2

3

4

7

Find nodes with right aggregation

ratio

Start


Aggregation %?

Finish

StrictNone

Wide

Aggregate SrcIP

Aggregate DstIP

Strict

Wide

Find common values from two

wide aggregations.

None

Strict Wide

Fail

None

Strict None,Wide

Documents

Othman Othman M.M. 30/1/2012 1. Outline: 1. Advisory Committee Meeting: 1. Content Anycasting. 2. OpenFlow Enhancement. 3. Current Status. 4. Next Research