\usepackage{color}
\usepackage{graphicx}
\usepackage{wrapfig}
-\usepackage{hyperref}
+\usepackage[hidelinks=true]{hyperref}
+\usepackage{todonotes}
+\usepackage{tikz}
+\usepackage{enumitem} % for sparse lists with \setlist
+\usetikzlibrary{arrows}
\urlstyle{sf}
+\setlist[enumerate]{noitemsep}
+\setlist[itemize]{noitemsep}
\newcommand{\pages}[1]{\marginpar{#1 pages}}
-\newcommand{\todo}{\textcolor{red}{TODO} \\}
\newcommand{\term}[1]{\emph{#1}}
\newcommand{\code}[1]{\textsf{#1}}
%% Introduction
\section{Introduction}
-\todo
+\todo{asdf}
\pages{0-1}
-short overview, not too long: what do we want, what are we
-going to do
+short overview, not too long: what do we want, what are we going to do?
-basically: how do we talk to our smart home?
+how do we talk to our smart home?
-%% Prerequisites
-\section{Prerequisites}
-\todo
-overview to the techniques used in the paper by Klauk and Kirsche
+what are the challenges? (interoperability, H2M interface, self-configuration,
+information filtering to prevent information overflow)
-\cite{klauck-kirsche-chattythings}
+In a distributed context like the Internet of Things, devices need to be ready
+to use out of the box. Users often do not want to set up configurations for each
+device they use, and when using several of those devices, it is often not
+reasonable having to configure every single one.
-\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}
+%\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.
-\section{Related Approaches}
+%% Prerequisites
+\section{Prerequisites}
\todo
-\pages{3}
-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
- \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
- \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}
+overview to the techniques used in the paper by Klauk and Kirsche
-\section{Discussion}
-\todo
-comparison of mentioned approaches
+\cite{klauck-kirsche-chattythings}
-\pages{1-2}
+\input{sec-address-allocation.tex}
+\input{sec-dns-extensions.tex}
+\input{sec-xmpp.tex}
+\input{sec-chatty-things.tex}
+\input{sec-discussion.tex}
\bibliographystyle{plain}
\bibliography{biblio}