Using network flows to enhance the P2P networks

Future internetProceeding the First Exercises on Computer and Systems Engineering Professor OKAMURA Laboratory.Othman Othman M.M.

11Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.22Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.331- Introduction:40 years ago Internet was designed for simple reliable communication of packets between ends.

But human needs are more demanding and more complicated.

Current internet fails to cope with needs.

The solution is Future internet.Overcome limitations.Provide more functionality. 44Flow of presentation 1/2:EIFFEL report:Brainstorming.Ideas.Lessons.

AKARI document: more specific details about:needs required form the future internet.correlating design requirements.design principles.5Related to :Technology.Economics.Society.5Flow of presentation 2/2:GENI system over view: Provides information about GENI a future internet testbed.

OpenFlow:Describe OpenFlow which is one of the promising technologies enabling the future internet..66Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.772- EIFFEL report:EIFFEL report.Brief introduction.Studying future internet along the technological axis.Studying future internet along the economical axis.Studying future internet along the society axis.88Brief introduction:Among the European future internet project.Founded by the 7th framework.

Provides: Brainstorming.Ideas.Lessons.Long 3 axes :Technological.Economical.Social.

99future internet along the technological axis:Impossible to see future, and so look to the past to learn.

What was the reasons for the internets success:Architecture.Applications and their variety.Practitioners.Enablers for the success. (processing and connectivity).

Cooperate engineering and science in future internet design.Engineering: design best network.Science: study of the nature of the network.1010future internet along the technological axis:Lessons to learnt from current internet design:New demands should be continuously identified and addressed.Reduce the big gap between reality and research community.Successful internet architecture should evolve by time.1111future internet along the economics axis:Addressing problems requires economic cooperation.Challenges that requires joint work: Joint system design: accommodate the differences of research styles between research fields .

Sustainable value chain: (value chain: activities creating a competitive advantage). Sustainability is required to make investment happen. Must be able to account for the usage of resources .

Business structures and their validity to the future.

1212future internet along the Society axis:Internet reflects parts of social structure.Internet has strong influence on the social structure.

Enovation has element of surprise.Like the attacks and other anti-social activities.

Studying information overload.too much information, too many services, too many options and too many individuals.

Study the impact of internet on governance and vice versa.1313Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.14143- AKARI Conceptual Design:AKARI document.Brief introduction. Goals of AKARI project.Why to use the clan state principle.Societal considerations and their correlating design requirements. Basic design principles of the AKARI.1515Brief introduction and Goals :AKARI small light in Japanese.Architecture Design Project.Funded by the NICT.

AKARI Goal: design the network of the future which will serve for 50 or 100 years. developing network architecture.creating a network design based on that architecture.

1616Why clan state?clean state : designing without being restrained by current network technologies .without being impeded to the current constrains.

Functions and Layers were added over 30 years:difficult to ensure reliability . current internet became complex and incompatible.17

17Societal considerations 1/2:Peat-bps class backbone network, 10Gbps FTTH, e-Science. 100 billion devices, machine to machine (M2M), 1 million broadcasting stations.Principles of competition and user-orientation.Essential services (medical care, transportation, emergency services), 99.99% reliability.Safety, peace of mind (privacy, monetary and credit services, food supply traceability, disaster services). Affluent society, disabled persons, aged society, long-tail applications. Monitoring of global environment and human society. Integration of communication and broadcasting, Web 2.0. Economic incentives (business-cost models). Ecology and sustainable society. Human potential, universal communication.1818Capacity Vs. Access:19

19Moors Law:20

20correlating design requirements 1/2:Large capacity: estimated to be approximately 1000 times in 13 years. Scalability: extremely diverse connected devices, servers to single-function sensors. Enormous number of small device.Openness: open and able to support appropriate principles of competition. Robustness: High availabilitySafety: authenticate connections. safety and robustness during a disaster. Diversity. designed and evaluated based on diverse communication requirements.

2121correlating design requirements 2/2:Ubiquity: A network for monitoring the global environment. Integration and simplification: simplified by integrating selected common parts. Simplification increases reliability and facilitates subsequent extensions. Network model: the architecture must have a design that includes a business-cost model. Electric power conservation: As network performance increases, its power consumption increases. must be more Earth friendly. Extendibility: Have enough flexibility to enable the network to be extended as society develops.2222Basic design principles 1/4:23

23Basic design principles 2/4:KISS (Keep It Simple, Stupid): for increasing the diversity, expandability and reliability. And to support that :Crystal Synthesis: simplification of technologies to reduce complexity even when integrating functions.Common Layer: Will have a common layer and will eliminate redundant functions in other layers.End to End: should not be constructed based on a specific application.

2424Current Internet Common layer:25

25Basic design principles 3/4:Reality Connection principle: network entities must have association with real world society. To support this association:Separation of physical and logical addressing: to support mobility and multi-homing.

Bi-directional authentication.

Traceability: to reduce attacks on the network. considered in addressing, routing and transport on top of them.

2626Separation of physical and logical addressing:27

27Basic design principles 4/4:Sustainable and Evolutionary principle: sustainable network evolvable in response to changing requirements.Self-* properties: self-distributed, self-organizing.Scalable, distributed controls: To scale controls even in large scale or topologically varying networks,Robust large-scale network: designed to handle simultaneous or serious failures.Controls for a topologically fluctuating network: in rapid changing topology controls for finding resources on demand are more effective than controls for maintaining routes or addresses. Balance must be made due to high overhead of finding resources on demand.Controls based on real-time traffic measurement: routing must adopt controls of precision-optimised real-time traffic measurement.Openness: to encourage innovation.

2828Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.29294- GENI system over view :GENI system over view.Brief introduction.Core concepts.Design goals.Building blocks.Stages of experiment.

3030Brief introduction and core concepts:GENI Global Environment for Network Innovations.Funded by NSF.The core concepts of GENI:Programmability: researchers may download software into nodes to control them.Virtualization and Other Forms of Resource Sharing: nodes implement virtual machines, to share the infrastructure. Federation: parts of the GENI are owned and/or operated by different organizations.Slice-based Experimentation: GENI experiments will be an interconnected set of reserved resources on platforms in diverse locations.

313132

32Design Goals 1/2:to ensure the resulting infrastructure suite will be useful:Generality: experimenter has the flexibility to perform the experiment.This means that components should be programmable. Diversity & Extensibility: include a wide class of networking technologies, Fidelity: ability to support experiments reflect a real network. Observability: support for measurement-based quantitative research. Ease of Use: researchers must able to make full use of infrastructure.3333Design Goals 1/2:Sliceability: GENI must be a shared infrastructure.Controlled Isolation: strong isolation between slices. Opt-in: give users the ability to participate in the service. Security: must be secure, must not be used to attack todays Internet.Federation & Sustainability: must be designed for a 15-20 year lifetime.3434Building Blocks 1/2:The researcher.Components: the primary building block. it encapsulates a collection or resources.Aggregate: a group of components.Clearinghouse: has the trust, slice and services. It performs tasks like managing trust between different federations, resource discovery, slice creation and many others.GENI Operations and Management: system-wide function to keep resources operating and manages services. And stops an overrun experiment or malicious experiments.Federation: permits the interconnection of independently owned and administered facilities.Slices: is a substrate-wide network of computing and communication resources.

3535Building Blocks 2/2:36

36Stages of experiment 1/5:Resource discovery: in this stage the researcher finds out about the available components through his federations clearinghouse.

37

37Stages of experiment 2/5:Slice Creation: in this stage the resources within this slice are linked together to form a coherent virtual network in which an experiment can run. This stage is also done through the clearinghouse.

38

38Stages of experiment 3/5:Experimentation: in this stage the researcher can download code into his slice, debug, collect measurements, and iterate. This stage is conducted directly between the researcher and the aggregates.

39

39Stages of experiment 4/5:Modifying a Slice: while running experiments researcher can modify his slice by adding or removing some components to his existing slice. done also through the clearinghouse. 40

40Stages of experiment 4/5:41

41Stages of experiment 5/5:Stopping the experiment: stopping of the experiment can be done by the researcher after finishing his experiment or might be done by the GENI operations and management as an emergency procedure to overcome an overrun or malicious experiment. 42

42Index:Introduction.

EIFFEL report.

AKARI document.

GENI system over view.

OpenFlow.43435- OpenFlowOpenFlow.Brief introduction.How Openflow works.Example of using Openflow.4444Brief introduction:Created in Stanford University.

OpenFlow first arise, to create an open, programmable, virtualized platform to run the researchers experiments on their campus network without affecting the production traffic.4545How Openflow works 1/3:OpenFlow components:OpenFlow switch or router.OpenFlow Protocol.Controller.The flow table entry.

46

46How Openflow works 2/3:OpenFlow components:OpenFlow switch or router: has the regular routing or forwarding table and a new table called the flow-table .OpenFlow Protocol: secure channel that allow the controller to add or remove entries in the switches flow-table.Controller: responsible for adding and removing entries to the OpenFlow switchs flow-table through the OpenFlow protocol .The flow table entry: consists of a header and an action related to that header.47

47How Openflow works 3/3:Actions related to the flow-table entry:forwarding the packet to a specific port or ports. encapsulating the incoming packet header and sending it to the controller so the controller will decide what to do and takes action by adding flows.dropping the packet for some purpose like security.forwarding the packet according to the switchs normal switching table.

When a packet arrives its header will be compared to the headers in the flow-table and if the packet matches the action associated to the matching flow-table entry will be executed.4848Example of using OpenFlow:using it to implement a network-wide policy for a campus network in a central controller. This controller can apply polices like: allowing gests to use HTTP but through a special proxy. preventing VoIP phones from communicating with laptops. and any other policy needed. 49ProxyInternetCampus

GueststaffVoIP phone

Controller49Thanks for listening.50505151