From d538b2704c39dd5638a1dc91a55ee510ecde90fa Mon Sep 17 00:00:00 2001 From: Aaron Kaplan Date: Tue, 4 Mar 2014 15:45:13 +0000 Subject: [PATCH] add a slide --- slides/ietf-89/content.tex | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/slides/ietf-89/content.tex b/slides/ietf-89/content.tex index c406c0e..fea90ec 100644 --- a/slides/ietf-89/content.tex +++ b/slides/ietf-89/content.tex @@ -37,7 +37,16 @@ \end{centering} \end{frame} -\begin{frame}[t]{Motivation} +\begin{frame}[t]{Why pDNS? Answer which Questions?} +\begin{itemize} +\item Historic data: ,,What was the A record for a certain FQDN last year?'' +\item Inverse Lookups: ,,Which domains have A records that are in a given address range?'' +\item Generic reseach on bulk DNS data: T. Frosch, T. Holz: ,,Predentifier: Detecting Botnet C\&C Domains From Passive DNS Data'' +\item The first time, we can get a sampled subset of \emph{the DNS} per se. I.e.: what is actually out there? +\end{itemize} +\end{frame} + +\begin{frame}[t]{Motivation for the I-D} \begin{itemize} \item Nowadays Passive DNS servers are created\footnote{To our knowledge, there are more than 15 software implementations} and used worldwide \item DNS data is very \emph{localized}. It makes sense to have multiple, local DBs (different legal environments, access rights, restrictions to data,...)