Software defined networking using OpenFlow
| Wiki for ITS | ||||||
|---|---|---|---|---|---|---|
|
|
Software defined networking using OpenFlow
| by | Joachim Tingvold |
|---|---|
| Supervisor(s) | Knut Øvsthus, Josef Noll |
| Due date | 1.8.2014 |
| Status | Ongoing |
| Problem description: | Most network devices today have the control and data plane within the same physical unit. The individual deveices have little-to-know knowledge of the state of the rest of the network, and makes forwarding decisions based upon the little formation it have.
An emerging architecture to solve this is known as software defined networking (SDN), and is done by separating the control plane and the data plane. One of the leading SDN architectures is OpenFlow, where the control plane is a software running on centralized units. The OpenFlow controller has full knowledge of the entire network, and can make forwarding decisions based on this. When looking at OpenFlow, we want to find out how it can be used for traffic engineering, so that we can maximize utilization of network links. We want to look at how the security is implemented by centralizing the forwarding decision, and how redundancy is achieved. |
| Methods and Tools: | The tools and methods in this thesis are based on
|
| Time schedule | The envisaged time schedule (for a long thesis/60 ECTS) is:
|
| Pre-Knowledge | This thesis includes a reasonable amount of programming. The envisaged thesis is based on radio communications, thus expects the user to have followed at least two radio-related courses |
| Approved | Pending by |
| Keywords | OpenFlow, Software defined network |
| Depiction |
this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Software defined networking using OpenFlow
This page provides hints on what to include in your master thesis.
TOC
Title page, abstract, ...
- 1. Introduction, containing: short intro into the area, what is happening
- 1.1 Motivation, containing: what triggered me to write about what I'm writing about
- 1.2 Methods, containing: which methods are you using, how do you apply them
- 2. Scenario, optional chapter for explaining some use cases
- 2.1 user scenario, (bad name, needs something bedre)
- 2.2 Requirements/Technological challenges
- 3. State-of-the art/Analysis of technology, structure your content after hardware/SW (or other domains). Describe which technologies might be used to answer the challenges, and how they can answer the challenges
- 3.1 technology A
- 3.2 technology B
- 4. Implementation
- 4.1 Architecture, functionality
- 4.2
- 5. Evaluation
- 6. Conclusions
- References
Comments
Red line
Your thesis should have a "red line", which is visible throughout the whole thesis. This means you should mention in the beginning of each chapter how the chapter contributes to the "goals of the thesis".
Use of scientific methods
A thesis follows a standard method:
- describe the problem (problemstilling)
- extract the challenges. These challenges should be measurable, e.g. method is too slow to be useful to voice handover.
- Analyse technology with respect to challenges. Don't write & repeat "everything" from a certain technology, concentrate on those parts (e.g. protocols) which are of importance for your problem
References
- Wikipedia is good to use to get an overview on what is happening. But there is not scientific verification of Wikipedia, thus you should use wikipedia only in the introduction of a chapter (if you use text from wikipedia). Use scientific literature for your thesis.
- Scientific library is "at your hand", you can get there directly from UiO: [[How to get access to IEEE, Springer and other scientific literature -> Unik/UiOLibrary]]
- I suggest that references to web pages, e.g. OASIS, W3C standards, are given in a footnote. Only if you find white papers or other .pdf documents on a web page then you refer to them in the reference section.
Evaluation of own work
Perform an evaluation of your own work. Revisit the challenges and discuss in how you fulfilled them. Provide alternative solution and discuss what should be done (or what could have been done).
