Browse wiki

Jump to: navigation, search
Software defined networking using OpenFlow
Approved Pending  +
DueDate 3 June 2016  +
Keywords Software defined network  + , IPv6  +
Methods The tools and methods in this thesis are bThe tools and methods in this thesis are based on * A set of scenario, describing the challenges * A list of requirements being extracted from the scenarios * A description and evaluation of technologies and tools being candidates for solutions * A functional architecture/description of the envisaged system * An implementation of the core concepts * A demonstration of the solution * An evaluation of the solution, including a critical review of the descisions taken earlier * Conclusions * Referencess taken earlier * Conclusions * References  +
Objective Most network devices today have the controMost 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. decision, and how redundancy is achieved.  +
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  +
Schedule The envisaged time schedule (for a long thThe envisaged time schedule (for a long thesis/60 ECTS) is: :T0 0 starting month, T0+m denotes the month where the contribution to a certain chapter shalle be finalized :T0+2 months: create an initial page describing the scenario :T0+3: Provide a list of technologies which you think are necessary for the thesis :T0+4: Establish the table of content (TOC) of the envisaged thesis. Each section shall contain 3-10 keywords describing the content of that section :T0+7: Provide a draft of section 2 (scenario) and 3 (technologies) :T0+10: Establish a draft on what to implement/architecture :T0+11: Set-up an implementation, testing and evaluation plan :T0+15: Evaluate your solution based on a set of parameters, keep in mind <i>there is no such thing as a free lunch</i> :T0+17: Deliver the thesislunch</i> :T0+17: Deliver the thesis  +
Supervisor Knut Øvsthus  + , Josef Noll  +
ThesisStatus Finished  +
Titel IPv6 transition mechanisms  +
User Joachim Tingvold  +
Creation dateThis property is a special property in this wiki. 16 April 2013 12:14:05  +
Categories Thesis  +
Modification dateThis property is a special property in this wiki. 30 June 2016 12:08:39  +
hide properties that link here 
  No properties link to this page.


Enter the name of the page to start browsing from.