-\section{Related Approaches}
-\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 => 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}
-\todo
-comparison of mentioned approaches
-
-\pages{1-2}
-