From: Roland Hieber Date: Sun, 8 Dec 2013 02:53:15 +0000 (+0100) Subject: sync: finish mdns X-Git-Tag: erste-version~11 X-Git-Url: https://git.rohieb.name/skm-ma-ws1314.git/commitdiff_plain/a937e7aa8fcc17fb98a80bd0a9362d11b188087f?ds=sidebyside sync: finish mdns --- diff --git a/dns-extensions.tex b/dns-extensions.tex new file mode 100644 index 0000000..1bb5ac0 --- /dev/null +++ b/dns-extensions.tex @@ -0,0 +1,39 @@ +\subsection{Extensions to the DNS protocol} + +\subsubsection{Multicast DNS} +\term{Multicast DNS}~\cite{rfc6762} (mDNS) describes an extension of the Domain Name +System that allows DNS resource records to be distributed on multiple hosts in a +network, therefore avoiding the need of a central server. + +Software that supports resolution of mDNS records listens on the reserved +link-local multicast address \code{224.0.0.251} (for IPv4 queries) or +\code{FF02::FB} (for IPv6 queries) on UDP port 5353 for incoming queries. +Queries sent to those multicast address and port are standard DNS queries, and +if a host receiving a query knows about the queried resource, it responds to the +querying host with a standard DNS response. The querying host can then simply +finish and use the result, or wait until other hosts respond to its query. The +latter is typically the case when querying for \code{SRV} records to obtain a +list of services which are present in the network. + +Another feature of Multicast DNS is the reduction of traffic through +\term{Known-Answer Suppression}. It allows a querying host to specify already +known resources in its query when querying resources that could exist on more +than one host (e.~g., SRV records). The hosts matching those resources then do +not generate a response. + +Finally, hosts may also send unsolicited responses. This can be used to notify +the network of new services available on the host. + +\pages{1} + +\subsubsection{DNS-Based Service Discovery} +\todo +\term{DNS-based Service Discovery} \cite{rfc6763} +\begin{itemize} + \item allows flexible mapping of available services to ports + \item utilization of SRV \cite{rfc2782}, TXT and PTR records + \item case study for IoT in \cite{Klauck:2012:BCC:2352852.2352881} +\end{itemize} + +\pages{1} +% vim: set ft=tex et ts=2 sw=2 : diff --git a/main.tex b/main.tex index 7044ce7..843e8de 100644 --- a/main.tex +++ b/main.tex @@ -29,42 +29,13 @@ going to do \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} - -\subsection{DNS-Based Service Discovery} -\todo -\cite{rfc6763} -\begin{itemize} - \item allows flexible mapping of available services to ports - \item utilization of SRV \cite{rfc2782}, TXT and PTR records - \item case study for IoT in \cite{Klauck:2012:BCC:2352852.2352881} -\end{itemize} - -\pages{1} - -\subsection{XMPP} -\todo -\cite{rfc6120} -\begin{itemize} - \item architecture: client-server, use of DNS-SD - \item addressing: JIDs, resources - \item XML-based communication primitives, stanzas and streams - \item presence - \item publish/subscribe \cite{xep-0060}, roster - \item multi-user chats \cite{xep-0045} -\end{itemize} - -\pages{3-4} - -\subsection{Multicast DNS} -\todo -\cite{rfc6762} \pages{1} - -\subsection{XMPP Serverless Messaging} -\todo -\cite{xep-0174} \pages{1} +\input{dns-extensions.tex} +\input{xmpp.tex} \section{System Architecture of Chatty Things} \todo diff --git a/xmpp.tex b/xmpp.tex new file mode 100644 index 0000000..56ed185 --- /dev/null +++ b/xmpp.tex @@ -0,0 +1,20 @@ +\subsection{XMPP} +\todo +\cite{rfc6120} +\begin{itemize} + \item architecture: client-server, use of DNS-SD + \item addressing: JIDs, resources + \item XML-based communication primitives, stanzas and streams + \item presence + \item publish/subscribe \cite{xep-0060}, roster + \item multi-user chats \cite{xep-0045} +\end{itemize} + +\pages{3-4} + + +\subsubsection{XMPP Serverless Messaging} +\todo +\cite{xep-0174} \pages{1} + +% vim: set ft=tex et ts=2 sw=2 :