Jabref thesis

• Title, abstract, introduction
• What problems?
• What are the current approaches?
• What is the authors' approach, contribution?

Problems:

Current approaches:

Contribution:

Problems:

Current approaches:

Contribution: Survey

2007

Problems:

Current approaches:

Contribution: Analytical approach, learning approach

In this article we advance the idea of a cognitive network, capable of perceiving current network conditions and then planning, learning, and acting according to end-to-end goals. Cognitive networks are motivated by the complexity, heterogeneity, and reliability requirements of tomorrow's networks, which are increasingly expected to self-organize to meet user and application objectives. We compare and contrast cognitive networks with related research on cognitive radios and cross-layer design. By defining cognitive networks, examining their relationship to other technologies, discussing critical design issues, and providing a framework for implementation, we aim to establish a foundation for further research and discussion

Problems:

Current approaches:

Contribution: Software mobility

Problems: SDN in infrastructure based and infrastructure less networks.

Current approaches:

Contribution: Usecases in H-SDN.

Motivated by a vision of a fully connected world, we ex- plore how Software{Dened Networking (SDN) can be uti- lized to support heterogeneous environments consisting of both infrastructure{based and infrastructure{less networks. To make the case for SDN in heterogeneous networks, or Heterogeneous SDN (H{SDN), we examine application sce- narios in which H{SDN is a key enabling technology.

Published 2012 OFELIA project.

Problems: Content routing where routing intelligent is provided by controller.

Current approaches:

Contribution:
In this paper, we will describe how coCONET can be implemented over an OpenFlow (the most popular SDN instantiation, to date) network and how OpenFlow should be modified to better suit the operations of coCONET and, more in general, of ICN solutions

Define requirements of ICN which can be solved with SDN: this paper deals with the latter one, focusing on the required enhancements to the OpenFlow architecture, interfaces and protocol that allow the supporting of ICN.

The Information-Centric Networking (ICN) paradigm is expected to be one of the major innovation of the Future Internet An ICN can be characterized by some key components like: (i) the content-centric request/reply paradigm for data distribution, (ii) route-by-name operations, and (iii) in-network caching. In this paper we focus on a framework for ICN called CONET (COntent NETwork) and in particular on a solution devised under this framework called coCONET. coCONET characteristics make it suitable for deployment in accordance to the Software Defined Networks (SDN) philosophy. In this paper, we will describe how coCONET can be implemented over an OpenFlow (the most popular SDN instantiation, to date) network and how OpenFlow should be modified to better suit the operations of coCONET and, more in general, of ICN solutions

2013 OFELIA

Problems:

Current approaches:

Contribution: Informative, detailed architecture of Conext to support SDN-based ICN. Experiment and results.

Problems:

Current approaches:

Contribution: ICN-SDN node design, architecture.

Problems:

Current approaches:

Contribution: architecture, content metadata driven services. usecase

Mechanism to extract content metadata and use it to Supporting traffic engineering in an ICN 2) Supporting a content fire- wall service 3) Performing network-wide cache management based on a function of size and popularity.

Open issues: detailed on implementation and less on algorithm and methods. Simple link utilization optimization problem.

This paper describes a content centric network architecture which uses software defined networking principles to implement efficient metadata driven services by extracting content metadata at the network layer. The ability to access content metadata transparently enables a number of new services in the network. Specific examples discussed here include: a metadata driven traffic engineering scheme which uses prior knowledge of content length to optimize content delivery, a metadata driven content firewall which is more resilient than traditional firewalls and differentiated treatment of content based on the type of content being accessed. A detailed outline of an implementation of the proposed architecture is presented along with some basic evaluation.