X-Git-Url: http://git.rohieb.name/skm-ma-ws1314.git/blobdiff_plain/a937e7aa8fcc17fb98a80bd0a9362d11b188087f..bbf634a989779b4193d927a3f0046ba61e19f1c7:/main.tex

diff --git a/main.tex b/main.tex
index 843e8de..51d61f4 100644
--- a/main.tex
+++ b/main.tex
@@ -3,16 +3,21 @@
 \usepackage[T1]{fontenc}
 \usepackage{ae}
 \usepackage{color}
+\usepackage{graphicx}
+\usepackage{wrapfig}
+\usepackage{hyperref}
+
+\urlstyle{sf}
 
 \newcommand{\pages}[1]{\marginpar{#1 pages}}
-\newcommand{\todo}{\textcolor{red}{TODO} \\}
+\newcommand{\todo}[1][]{\textcolor{red}{TODO #1} \\}
 \newcommand{\term}[1]{\emph{#1}}
-\newcommand{\code}[1]{\texttt{#1}}
+\newcommand{\code}[1]{\textsf{#1}}
 
 \title{Chatty Things -- Making the Internet of Things Readily Usable for the
 Masses with XMPP}
 \author{Roland Hieber}
-\date{Seminar Communications and Multimedia, TU~Braunschweig \\ \today}
+\date{Seminar Communications and Multimedia, TU~Braunschweig \\[1em] \today}
 
 \begin{document}
 \maketitle
@@ -24,25 +29,24 @@ Masses with XMPP}
 short overview, not too long: what do we want, what are we
 going to do
 
+basically: how do we talk to our smart home?
+\paragraph{Human-to-Machine Communication:} especiall in the Internet of Things,
+	Chatty Things need to be accessible for the user and should be easy to talk
+	to.
+\paragraph{Interoperability} integration into already existing
+infrastructure.
 
 %% Prerequisites
 \section{Prerequisites}
 \todo
 overview to the techniques used in the paper by Klauk and Kirsche
 
-basically: how do we talk to our smart home?
 \cite{klauck-kirsche-chattythings}
 
-\input{address-allocation.tex}
-\input{dns-extensions.tex}
-\input{xmpp.tex}
-
-\section{System Architecture of Chatty Things}
-\todo
-\pages{3}
-\subsection{Service Provisioning Sublayer}
-\subsection{Bootstrapping}
-\subsection{Presence Subscription}
+\input{sec-address-allocation.tex}
+\input{sec-dns-extensions.tex}
+\input{sec-xmpp.tex}
+\input{sec-chatty-things.tex}
 
 \section{Related Approaches}
 \todo
@@ -50,8 +54,36 @@ basically: how do we talk to our smart home?
 Middleware, Application protocol gateways:
 \begin{itemize}
 	\item Constrained Application Protocol \cite{draft-ietf-core-coap-18}
+	\begin{itemize}
+		\item machine-to-machine
+		\item everything-built-in
+		\item discovery over multicast, service discovery over /.well-known
+			entry-point
+		\item maps to HTTP => stateless => relies on application gateway
+		\item low protocol overhead and parsing complexity (binary messages)
+		\item only draft status
+		\item UDP with Ack and IDs instead of TCP... (limited state machine)
+		\item proxies
+		\item asynchronous messages
+	\end{itemize}
 	\item MQ Telemetry Transport \cite{mqtt}
+	\begin{itemize}
+		\item TCP/IP
+		\item small overhead: 2 byte header + variable header length
+		\item publish-subscribe with topic names
+		\item binary protocol => application-level gateway
+		\item discovery?
+	\end{itemize}
 	\item Devices Profile for Web Services \cite{zeeb-moritz-ws4d}
+	\begin{itemize}
+		\item TCP/IP -> HTTP -> SOAP -> Web Services. Overhead!
+		\item but very extendable and composable
+		\item discovery as a service
+		\item focused on multiple platforms, deeply embedded and servers
+		\item IPv6 partly experimental
+		\item ROM usage of uDPWS: 45 kByte
+	\end{itemize}
+
 \end{itemize}
 
 \section{Discussion}