adding DCC docs

DCC/config.sty

+\usepackage[english]{babel}
+\usepackage[utf8]{inputenc}
+\usepackage{graphicx}
+\usepackage{caption}
+\usepackage{float}
+\usepackage{subcaption}
+\usepackage{fancyhdr}
+\usepackage{xargs}
+\usepackage{wrapfig}
+\usepackage{multicol}
+\usepackage{latexsym}
+\usepackage{listings}
+\usepackage[usenames,dvipsnames]{color}
+\usepackage{amsmath}
+\usepackage{amsthm}
+\usepackage{amsfonts}
+\usepackage{hyperref}
+\usepackage{verbatim}
+\usepackage[justification=centering]{caption} 
+\graphicspath{ {images/} }
+
+\usepackage[toc]{glossaries}
+\usepackage{mathtools}
+\usepackage[right=2cm,left=2cm,top=2.5cm,bottom=2cm,footskip=0.5cm]{geometry}
+\renewcommand*{\glstextformat}[1]{\textbf{#1}}%Hace los link al glosario bold
+%%\renewcommand{\baselinestretch}{1.9} % Controla el interlineado el numero indica el factor de aumento
+
+%Redefinimos el campo caption como Code
+\renewcommand{\lstlistingname}{Código}
+%Definir colores:
+\definecolor{dkgreen}{rgb}{0,0.6,0}
+\definecolor{gray}{rgb}{0.5,0.5,0.5}
+\definecolor{mauve}{rgb}{0.58,0,0.82}
+%Presentacion del codigo
+\lstset{frame=tb,
+  language=C,
+  aboveskip=3mm,
+  belowskip=3mm,
+  showstringspaces=false,
+  columns=flexible,
+  basicstyle={\small\ttfamily},
+  numbers=none,
+  numberstyle=\tiny\color{gray},
+  keywordstyle=\color{blue},
+  commentstyle=\color{dkgreen},
+  stringstyle=\color{mauve},
+  breaklines=true,
+  breakatwhitespace=true
+  tabsize=6
+}
+
+  
+% TODO notes
+
+\usepackage[colorinlistoftodos,prependcaption,textsize=tiny]{todonotes}
+\newcommandx{\unsure}[2][1=]{\todo[linecolor=red,backgroundcolor=red!25,bordercolor=red,#1]{#2}}
+\newcommandx{\change}[2][1=]{\todo[linecolor=blue,backgroundcolor=blue!25,bordercolor=blue,#1]{#2}}
+\newcommandx{\info}[2][1=]{\todo[linecolor=OliveGreen,backgroundcolor=OliveGreen!25,bordercolor=OliveGreen,#1]{#2}}
+\newcommandx{\improvement}[2][1=]{\todo[linecolor=Plum,backgroundcolor=Plum!25,bordercolor=Plum,#1]{#2}}
+\newcommandx{\thiswillnotshow}[2][1=]{\todo[disable,#1]{#2}}
+
+%Circled numbers
+\usepackage{tikz}
+\newcommand*\circled[1]{\tikz[baseline=(char.base)]{
+            \node[shape=circle,draw,inner sep=2pt] (char) {#1};}}
\ No newline at end of file

DCC/pro_camila.tex

+\documentclass[12pt,letterpaper]{article}
+\input{config.sty}
+\input{funcion.tex}
+\loadglsentries{glossEntries.tex}
+\makeglossaries
+%\pagestyle{fancy}
+%\fancyhead[l]{\sf{\large{Informe Práctica I}}} %% Titulo superior Izquierdo.
+%\fancyhead[r]{\thepage} %% numero de pagina Derecha.
+%\fancyfoot{}
+%\renewcommand{\headrulewidth}{0.6pt}
+\begin{document}
+\section{Proposal}
+Chile belongs to the group of countries that are highly susceptible to natural disasters: earthquakes, tsunamis, volcanic eruptions, and landslides are just a few that may be mentioned. A typical effect of such disasters is to cause damages to large areas, which not only affects the population in general but also affects the communication networks.
+
+Internet has been designed to withstand these difficulties, but there are limitations. A clear example is the earthquake that occurred in Chile on February 27, 2010, where national connectivity failed and most of web requests were made to servers outside the country, saturating the international link \cite{ChileanInternet}. This fact caused an important tsunami warning from the United States not to reach the National Emergency Office of the Interior Ministry of Chile\footnote {J. Piquer. \textit {Terremoto 2010: ¿Internet resistió bien la prueba?} http://goo.gl/wTY36j}, generating a misinformation state in the population. This is just one of the reasons why ensuring the availability and quality of Internet service, in such situations, is so important.
+
+Damages to large areas caused by natural disasters generate massive failures of nodes and links in the affected zone. The problem is that the current network infrastructure is not able to detect this situation because each node works independently: only knows its routing table and forwards the information only based on it. If we could timely detect the massive failure of nodes and links, it would be possible to take steps to address the problem: redirect the data flows to avoid dead or saturated connections, prioritize national messages, among other measures. However, the independence of the nodes also prevents the implementation of these actions.
+
+Software-defined networking (SDN) is a new approach in computer networking. It proposes a new network architecture that separates the control plane from the data plane (originally together in each node of traditional networks), moving the first one to an external controller that monitors a set of nodes of the network. For each new information flow, the controller decides its route based on the monitored network state. This feature makes SDN a candidate solution to address the problem of large failures.
+
+This project aims to study SDN as a solution to the problem, to identify the key variables, benefits and difficulties of its implementation, using the Chilean metropolitan network as an example, aiming at designing different SDN applications to improve network resilience to natural disasters.
+
+
+\section{Objectives}
+
+The objectives to achieve on this study are presented below. General and specific objectives are both included.
+
+\subsection{General objective}
+The general objective is to identify the key variables, benefits and difficulties to consider in the hypothetical implementation of SDN in the Chilean network and to design specialized controller applications to improve resilience to natural disasters and manage the network in these situations.
+
+\subsection{Specific objectives}
+
+\begin{enumerate}
+	\item Identify the key variables to consider on the hypothetical implementation of SDN in the Chilean network. This is critically important due to Chilean network topology. Questions like \textit{how many controllers are needed?} and \textit{where they should be placed to improve efficiency and avoid being damaged?} will be answered in this study.
+	
+	\item Identify existing SDN solutions that improve resilience and adapt them, or propose new ones, to improve resilience and quality of service in natural disasters.
+	\item Design the specialized controller applications.
+	\item Implement those applications. This will be done following the SDN architecture, as shown in Figure \ref{fig:sdnArch}.
+	\item Validate the implementation and efficiency of these applications in a simulated software-defined Chilean network in massive failure of nodes and links scenario. This validation will be carried out in a simulated environment through Mininet, and also in a small-scale SDN testbed.
+\end{enumerate}
+
+\begin{figure}[H]
+    \centering
+    \includegraphics[width=0.5\textwidth]{DiagramaNDResAPP.png}
+    \centering
+    \caption{A high-level overview of the SDN architecture. The Natural Disaster Resilient applications will be implemented in the Application Layer.}
+    \label{fig:sdnArch}
+\end{figure}
+
+\section{Expected results}
+
+\subsection{Proposal contributions}
+The expected contributions of the project are listed as follows:
+
+\begin{itemize}
+    \item A comprehensive study on the current state of the art of SDN in the context of applicability to network resilience in case of natural disasters.
+    \item A study about the SDN implementation in a vulnerable country such as Chile, with their respective advantages and difficulties, to improve the network response against massive failure of nodes. While this study is restricted to the conditions of the Chilean network, it could be a basis for a general study to other vulnerable countries.
+    \item The behavior definition and implementation of the SDN controller applications with its respective validation by testing on a network simulator and a small-scale test-bed.
+\end{itemize}
+
+\subsection{Success measure}
+Success will be measured according to the completion of studies and behavioral design validation and implementation of the prototype of the SDN controller. The expected results of the study must be consistent with the validation tests results.
+
+\nocite{PrioID}
+\nocite{ControllerPos}
+\nocite{DisasterResilientWAN}
+
+
+\bibliography{science}{}
+\bibliographystyle{unsrt}
+
+
+
+
+\end{document}
\ No newline at end of file

DCC/science.bib

+@article{ControllerPos,
+  title={On reliable controller placements in Software-Defined Networks},
+  author={Ros, Francisco J and Ruiz, Pedro M},
+  journal={Computer Communications},
+  year={2015},
+  publisher={Elsevier}
+}
+
+@inproceedings{PrioID,
+  title={Network operational method by using software-defined networking for improvement of communication quality at disasters},
+  author={Ogawa, Koichi and Yoshiura, Noriaki},
+  booktitle={Network Operations and Management Symposium (APNOMS), 2014 16th Asia-Pacific},
+  pages={1--4},
+  year={2014},
+  organization={IEEE}
+}
+
+@incollection{SysReview,
+  title={Guidelines for performing systematic literature reviews in software engineering},
+  author={Keele, Staffs},
+  booktitle={Technical report, Ver. 2.3 EBSE Technical Report. EBSE},
+  year={2007}
+}
+
+@inproceedings{DisasterResilientWAN,
+  title={A software-defined networking approach for disaster-resilient WANs},
+  author={Nguyen, Kien and Minh, Quang Tran and Yamada, Shigeru},
+  booktitle={Computer Communications and Networks (ICCCN), 2013 22nd International Conference on},
+  pages={1-5},
+  year={2013},
+  organization={IEEE}
+}
+
+@article{ChileanInternet,
+  title={The Chilean Internet: Did it survive the earthquake?},
+  author={Ramiro, V and Piquer, J and Barros, T and Sep{\'u}lveda, P}
+}
\ No newline at end of file