commit df07946be57e0a3c7a9d79da14fc7910cf26d11d
parent 67205e1c1af4b9e422279d4f05e514f8f190326b
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Fri, 8 Sep 2023 14:45:54 +0200
update
Diffstat:
| M | IETF118/r5n.tex | | | 71 | +++++++++++++++++++++++++++++++++++++++++++++++------------------------ |
1 file changed, 47 insertions(+), 24 deletions(-)
diff --git a/IETF118/r5n.tex b/IETF118/r5n.tex
@@ -8,22 +8,56 @@
\usepackage{blkarray}
\usepackage{amsmath}
\usepackage{multirow}
-\title{The R5N Distributed Hash Table\\\small{IETF118}}
-\date{XX/11/2013}
-\author{Martin Schanzenbach}
+\title{The R5N Distributed Hash Table --- \url{https://datatracker.ietf.org/doc/draft-schanzen-r5n/}\\\small{IETF118}}
+\date{XX/11/2023}
+\author{\textbf{Martin Schanzenbach}, Christian Grothoff, Bernd Fix}
\institute{\hfill\large{GNUnet} \includegraphics[trim={0cm 1.5cm 0cm 0cm},clip,width=4em]{gnunet}}
\begin{document}
\metroset{block=fill,sectionpage=progressbar,numbering=counter}
\maketitle
-\section{The R5N DHT In a Nutshell}
-\begin{frame}{Motivation}
+% \section{The R5N DHT In a Nutshell}
+\begin{frame}{Open, peer-to-peer routing}
\begin{itemize}
- \item Open, peer-to-peer routing mechanism.
- \item Ad-hoc permissionless participation.
- \item Supports topologies in restricted-route environments.
- \item Optional recording of routes messages take through the overlay.
- \item Implemented in GNUnet, used (among other things) by the GNU Name System (GNS, RFCXXXX).
+ \item Problem: Access control leads to centralization.
+ \item Solution: Unlike RELOAD (RFC 6940), we want ad-hoc permissionless participation.
+ \end{itemize}
+\end{frame}
+
+\begin{frame}{Support for in restricted-route environments}
+ \begin{itemize}
+ \item Problem: Restricted routes: what is that?
+ \item Solution: Randomized routing
+ \end{itemize}
+\end{frame}
+
+\begin{frame}{Route recording}
+ \begin{itemize}
+ \item Problem: ?
+ \item Solution: TODO
+ \end{itemize}
+\end{frame}
+
+
+\begin{frame}{In-band response validation}
+ \begin{itemize}
+ \item Problem: ?
+ \item Solution: Pluggable, extensible \textit{block types}.
+ \item Validated by each hop.
+ \end{itemize}
+\end{frame}
+
+\begin{frame}{Result filtering}
+ \begin{itemize}
+ \item Problem: Already known information.
+ \item Solution: \textit{Result Bloom filter}.
+ \end{itemize}
+\end{frame}
+
+\begin{frame}{Routing loop prevention}
+ \begin{itemize}
+ \item Problem: Routing loops
+ \item Solution: \textit{Peer Bloom filter}.
\end{itemize}
\end{frame}
@@ -62,23 +96,12 @@
\end{center}
\end{frame}
-\section{Quo Vadis?}
-\begin{frame}{Roadmap}
- \begin{itemize}
- \item In progress:
- \begin{itemize}
- \item 2019-2020: Technical specification of GNS protocol, packaging and alternative implementations.\footnote{Funded by NLnet under EU Next Generation Internet program (\url{https://nlnet.nl/project/GNS/}).}
- \item Continuous development and integration into applications.
- \end{itemize}
- \item 2020--: Establishment of governing body.
- \end{itemize}
-\end{frame}
-
\begin{frame}
\begin{center}
The R5N DHT\\
- \vspace{2cm}
- \url{https://gnunet.org}\\
+ \url{https://datatracker.ietf.org/doc/draft-schanzen-r5n/}\\
+ \vspace{1cm}
+ DISPATCH: Are there any WGs interested in adopting/working on this?\\
\vspace{1em}
{\tiny
\texttt{schanzen@gnunet.org}\\
