[lsd0001] branch master updated: update slides

[gnunet]

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 51fce83  update slides
51fce83 is described below

commit 51fce83e9a175409075b3d908d75a49f3338c45e
Author: Martin Schanzenbach <mschanzenbach@posteo.de>
AuthorDate: Sat Jul 25 12:26:37 2020 +0200

    update slides
---
 ietf/secdispatch/gns.tex | 113 +++++++++++++++++++++++++++++------------------
 1 file changed, 69 insertions(+), 44 deletions(-)

diff --git a/ietf/secdispatch/gns.tex b/ietf/secdispatch/gns.tex
index 06f5e1c..88999b0 100644
--- a/ietf/secdispatch/gns.tex
+++ b/ietf/secdispatch/gns.tex
@@ -8,8 +8,8 @@
 \usepackage{blkarray}
 \usepackage{amsmath}
 \usepackage{multirow}
-\title{The GNU Name System\\\small{secdispatch -- IETF 108}}
-\date{11/5/2019}
+\title{The GNU Name System\\\small{secdispatch -- IETF 
108}\\\small{\url{https://datatracker.ietf.org/doc/draft-schanzen-gns/}}}
+\date{30/7/2020}
 \author{Martin Schanzenbach}
 \institute{\hfill\large{GNUnet} \includegraphics[trim={0cm 1.5cm 0cm 
0cm},clip,width=4em]{gnunet}}
 \begin{document}
@@ -113,45 +113,8 @@
   \includegraphics[height=0.9\textheight]{deleg2.pdf}
 \end{frame}
 
-\section{How do we bootstrap the top-level zones?}
-\begin{frame}
-  \includegraphics[height=0.9\textheight]{deleg3.pdf}
-\end{frame}
-
-
-\begin{frame}{The GNU Name System Root}
-  ``Hyper-hyper local root'' concept:
-  \begin{itemize}
-    \item Resolver ships with initial root zone configuration.
-    \item Root zone configurable \emph{locally} at \emph{each} endpoint.
-    \item User override/extension of root at top-level or subdomain-level for:
-      \begin{itemize}
-        \item Circumvent censorship if necessary.
-        \item Private networks.
-      \end{itemize}
-  \end{itemize}
-\end{frame}
-
-\begin{frame}{Envisioned Governance Model}
-  \begin{itemize}
-    \item Non-profit organization.
-    \item Multi-stakeholder model: Board, supporting organizations, \ldots
-    \item Examples for possible stakeholders:
-      \begin{itemize}
-        \item Software and OS Distributors
-        \item Browser vendors
-        \item Governments
-      \end{itemize}
-    \item Funding options:
-      \begin{itemize}
-        \item Applications for new top-level domains.
-        \item Registrations of new top-level domains.
-        \item \ldots
-      \end{itemize}
-  \end{itemize}
-\end{frame}
-
-\begin{frame}{Previous occurrences at IETF/W3C/ICANN}
+\section{Why are we here?}
+\begin{frame}{Discussions at IETF/W3C/ICANN}
   \begin{itemize}
     \item IETF 93: \url{https://datatracker.ietf.org/doc/slides-93-dnsop-5/}
       \begin{itemize}
@@ -167,6 +130,11 @@
 
 \begin{frame}{Current Status}
   \begin{itemize}
+    \item Who is (and will be) working on it:
+      \begin{itemize}
+        \item GNUnet project.
+        \item Current funding for specfication by NLnet: 
\url{https://nlnet.nl/project/GNS/}.
+      \end{itemize}
     \item Implementation
       \begin{itemize}
         \item Reference implementation in C part of GNUnet: 
\url{https://git.gnunet.org/gnunet.git/tree/src/gns}
@@ -175,17 +143,35 @@
     \item Specification
       \begin{itemize}
         \item Current draft: \texttt{draft-schanzen-gns-01}.
-        \item Status: Finished but not complete.
+        \item Status: Documents current implementation. Collecting feedback to 
improve protocol (and spec).
       \end{itemize}
   \end{itemize}
 \end{frame}
 
-\begin{frame}{Roadmap}
+\begin{frame}{Next steps}
+  \begin{itemize}
+    \item Address received feedback:
+      \begin{itemize}
+        \item Better trust agility to address questions on choice of 
Hierarchical Deterministic Key Derivation (HKDF). Options:
+          \begin{itemize}
+            \item ECDSA w/ Cuve25519 (in draft)
+            \item Schnorr/Ed25519 (``Tor-style'')
+            \item BIP32-Ed25519\footnote{Has issues: 
\url{https://forum.web3.foundation/t/key-recovery-attack-on-bip32-ed25519/44}}
+          \end{itemize}
+        \item Update to symmetric encryption scheme for IND-CCA.
+        \item Address choice of DHT better.
+        \item Address key management / recovery.
+      \end{itemize}
+    \item Desired next steps at IETF:
   \begin{itemize}
-    \item Looking for a home at IETF.
+    \item Receive feedback from IETF experts on protocol and document.
+    \item Is this document interesting to any existing IETF/IRTF WG?
+  \end{itemize}
   \end{itemize}
 \end{frame}
 
+
+
 \begin{frame}
   \begin{center}
     The GNU Name System\\
@@ -214,4 +200,43 @@
   }
 \end{frame}
 
+\section{How do we bootstrap the top-level zones?}
+\begin{frame}
+  \includegraphics[height=0.9\textheight]{deleg3.pdf}
+\end{frame}
+
+
+\begin{frame}{The GNU Name System Root}
+  ``Hyper-hyper local root'' concept:
+  \begin{itemize}
+    \item Resolver ships with initial root zone configuration.
+    \item Root zone configurable \emph{locally} at \emph{each} endpoint.
+    \item User override/extension of root at top-level or subdomain-level for:
+      \begin{itemize}
+        \item Circumvent censorship if necessary.
+        \item Private networks.
+      \end{itemize}
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Envisioned Governance Model}
+  \begin{itemize}
+    \item Non-profit organization.
+    \item Multi-stakeholder model: Board, supporting organizations, \ldots
+    \item Examples for possible stakeholders:
+      \begin{itemize}
+        \item Software and OS Distributors
+        \item Browser vendors
+        \item Governments
+      \end{itemize}
+    \item Funding options:
+      \begin{itemize}
+        \item Applications for new top-level domains.
+        \item Registrations of new top-level domains.
+        \item \ldots
+      \end{itemize}
+  \end{itemize}
+\end{frame}
+
+
 \end{document}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.