\subsection{Objectives}
-%1. Objective
-The objective of this document is to propose a testing approach for an
-implementation of the \textit{Transmission Control Protocol}.
-\textit{Transmission Control} Protocol, from now on \textit{TCP}, is a
-communication protocol that provides a reliable connection on using a
-host-to-host protocol.
+%1, 2
+The objective of this document is to provide an approach for testing a
+particular implementation of \textit{Transmission Control Protocol} (TCP). TCP
+is a host-to-host protocol that provides a reliable communication.
-%2. Test Goal
+This testing approach can be used by either an internal test team or an
+independent testing team. The test effort's goal is to become confident about
+the conformance of an existing implementation to the specification created by
+\textit{The Internet Engineering Task Force}
+(IETF)\footnote{\url{http://www.ietf.org}} as document
+\textit{RFC793}~\cite{rfc793}. This document is explicitly \emph{not} intended
+to serve as guideline for testing during the development phase, but for testing
+conformity to the specification of an \emph{existing} implementation.
-\subsection{TCP}
-%3. The Product
-The \textit{System under test}(\textit{SUT}) is a ...%TODO
+\subsection{SUT}
+%3,4
+The \textit{System under test} (SUT) is a
+Java\footnote{\url{http://www.java.com}} TCP driven echo server that executed
+on a virtualized Ubuntu system\footnote{\url{http://www.ubuntu.com}} running on
+the Linux kernel\footnote{\url{http://www.kernel.org}} version $3.13$. To test
+the error behaviour custom iptables output policies have to be set
+Listing~\ref{listing:iptables}. This is needed because the kernel by default
+closes all connections from unknown sources and the manually created TCP
+packets used in testing the implementation are from a source unknown to the
+kernel.
-%4. The Specification
-The \textit{SUT} will be tested to a subset of the standard defined by
-\textit{Internet Engineering Task Force} in \textit{RFC793}~\cite{rfc793}.
+\begin{lstlisting}[label={listing:iptables},caption={settings iptables}]
+Chain OUTPUT (policy ACCEPT)
+target prot opt source destination
+ACCEPT tcp -- anywhere anywhere tcp flags:PSH/PSH
+DROP tcp -- anywhere anywhere tcp flags:RST/RST
+\end{lstlisting}
-%5. Risks, misschien moet dit in section 2
+\subsection{Risks} \label{sec:risks}
+%5. Risks
+Risks can be divided into two categories. Project risks and product risks.
+Because an existing implementation is used the project risk are non applicable.
+Product risks even more so, since it is unknown if the product has been tested
+during development.
+
+The product risks for the SUT are significant because misbehaviour of the SUT
+could have potential large consequences. The key characteristics of TCP are
+integrity and reliability~\cite{rfc793}, these characteristics cease to exist
+when the implementation is faulty.
+
+Because TCP is a core functionality of a networking capable system it is
+crucial that the TCP implementation functions according to the specification.
+Several critical systems could rely on the correct functionality of the TCP
+implementation. A failure in the SUT could therefore have extensive
+consequences. Even more so since TCP is a computer-to-computer protocol, which
+leaves no room for ambiguity, which could be solved in a computer-to-human
+protocol.
repositories / tt2015.git / blobdiff