Edits and content

Some more text to clarify the conceptual structure.

documentation/design-documentation/chapters/chapter03.tex

@@ -57,3 +57,9 @@ Configuration: Set, Query, Change etc. of configuration parameters
 \label{ch:underpinnings:requirements}
 
 Some requirements to be filed here. 
+
+\subsection{Basic properties of networks}
+\begin{enumerate}
+	\item recursion
+	\item abstraction
+\end{enumerate}

documentation/design-documentation/chapters/chapter04.tex

@@ -4,27 +4,39 @@
 \section{Conceptual Structures}
 \label{ch:conceptual-design:structures}
 
-This section discusses the basic conceptual organization forms for data networks, as this seems to not clear in many contexts. 
+This section discusses the basic conceptual organization forms for data networks, as this seems to not clear in many contexts. The main purpose is to clarify what in a network has to be managed, how it has to be managed and by what entity it has to be managed. 
 
 \subsection{Principal Network Domain (PND)}
 
-Any network consists out of basic components that are the collection of (network) elements used to form such particular network. These components, let it be any device attached to this network and the (physical) links, with their control-, data-, and management planes form the Principal Network Domain (PND). A specific network controller is in control of the specific components of a network. 
+Any network consists out of basic components that are the collection of (network) elements used to form such particular network. These components, let it be any device attached to this network and the (physical) links, with their control-, data-, and management planes, form the Principal Network Domain (PND). A network controller can be
+\begin{enumerate} 
+\item directly in charge of the devices in the PND and thus be able to manage these network elements directly,
+\item or connect to a different lower network controller. The network controller would be only able to indirectly communicate with the network elements via the lower network controller or even, in case of a recursion of network controllers, only be able to talk to an even lower level network controller. 
+\end{enumerate}
 
-The differentiation between the PND and the following definitions of network domain, IP network, etc is important for the design of a network controller that is supervising a network in its whole. The PND is the concept used by the network controller to keep track of all hosts and links associated~\footnote{XXXwhat means \emph{associated} exactly?} to this controller. 
+The differentiation between the PND and the following definitions of network domain, e.g., IP network, etc is important for the design of a network controller that is supervising a network in its whole. The PND is the concept used by the network controller to keep track of all hosts and links associated~\footnote{XXXwhat means \emph{associated} exactly?} to this controller. 
 
 A single controller may be in charge of multiple PNDs. 
 
 \subsection{Network Domain (ND)}
 
-A network domain is the collection of matt
+A network domain is the collection of network elements and links connecting the elements while these entities, i.e., the elements and links, can be either physically or logical. Examples for
+\begin{enumerate} 
+\item physical entities: an Ethernet switch with Ethernet links or an optical switch with fibre connections
+\item logical entities: a VLAN-enabled Ethernet switch where the VLANs from a logical topology on top of the physical infrastructure. 
+\end{enumerate}
 
+A network domain is bound to a single PND. Network domains can be part of network domains, i.e., this is a case of recursion. 
 
 \section{Building Blocks}
 \label{ch:conceptual-design:collection}
 
 Some conceptual building blocks for a network supervisor:
 \begin{description}
-	\item [element inventory] \hfill \\ This contains all known elements (such as end-hosts or network element as optical switches), independent of their relationship, of the network. This includes their hardware configuration, such as, interfaces attached to a particular host.
+	\item [principal element inventory] \hfill \\ This contains all known elements (such as end-hosts or network element as optical switches), independent of their relationship, of the network. This includes their hardware configuration, such as, interfaces attached to a particular host.
+	\item [principal topology inventory] \hfill \\  This contains all known links and their connection to interfaces of elements out of the principal element inventory.
+	\item [domain element inventory] \hfill \\ This contains the elements part of a particular network domain and it has to be a (sub)-set of the elements of the principal element inventory or a logical abstraction, such as a container or a virtual machine. 
+	\item [domain topology inventory] \hfill \\  This contains all known logical links and their connection to interfaces of elements out of the domain element inventory.
 	\item [host configuration] \hfill \\  This is based on the information provided by the host inventory and contains the actual operational configuration of the hosts. This will probably contain only the configuration of the network devices, such as, switches and routers, potentially also servers, but not end-hosts.		
 	\item [Network ] \hfill \\ 
 	\item [Network Configuration)] \hfill \\