commit a9f618b4621bf49e888d612967223d75f2147230
parent 609099da0a758749d67a74cca1dc55ec94d0c8c1
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Mon, 18 Mar 2024 15:12:07 +0100
update
Diffstat:
1 file changed, 25 insertions(+), 16 deletions(-)
diff --git a/2024-gns-ngi-webinar/gns.tex b/2024-gns-ngi-webinar/gns.tex
@@ -23,13 +23,13 @@
\begin{frame}{Directories / DNS}
$$
\mathrlap{\overbrace{\phantom{\text{www}}}^{\text{Label}}}
- \text{www}
- \mathrlap{\underbrace{{\color{fhggreen}\phantom{\text{.example.com}}}}_{\text{Namespace}}}
- {\color{fhggreen}\text{.example.com}}
+ \text{www.}
+ \mathrlap{\underbrace{{\color{fhggreen}\phantom{\text{.example.com}}}}_{\text{Zone}}}
+ {\color{fhggreen}\text{example.com}}
$$
\end{frame}
-\begin{frame}{The .alt TLD}
+\begin{frame}{The Domain Name System}
Whats wrong with DNS? See RFC 8324\footnote{DNS Privacy, Authorization, Special Uses, Encoding, Characters,
Matching, and Root Structure: Time for Another Look?}:
\begin{itemize}
@@ -45,13 +45,13 @@
\begin{frame}{Directories / GNS}
$$
\mathrlap{\overbrace{\phantom{\text{www}}}^{\text{Label}}}
- \text{www}
- \mathrlap{\underbrace{{\color{fhggreen}\phantom{\text{.myzone.gns.alt}}}}_{\text{Namespace}}}
- {\color{fhggreen}\text{.myzone.gns.alt}}
+ \text{www.}
+ \mathrlap{\underbrace{{\color{fhggreen}\phantom{\text{.myzone.gns.alt}}}}_{\text{Zone}}}
+ {\color{fhggreen}\text{myzone.gns.alt}}
$$
\end{frame}
-\begin{frame}{DNSSEC}
+\begin{frame}{The .alt TLD}
Why ``.gns.alt''?
\begin{itemize}
\item RFC9476: ``The .alt Special-Use Top-Level Domain'' defines the TLD to be used for alternative (from the point of view of DNS) name systems.
@@ -64,7 +64,7 @@
\begin{frame}{The GNU Name System}
\begin{itemize}
- \item Namespaces are created and uniquely identified using \textbf{public zone keys}.
+ \item Zones are created and uniquely identified using \textbf{public zone keys}.
\item \textbf{Records} are grouped by \textbf{label}, encrypted, signed, and published in a key-value store (usually, a DHT\footnote{\url{https://datatracker.ietf.org/doc/draft-schanzen-r5n/}}).
\item Supported zone types and crypto (for now):
\begin{itemize}
@@ -76,6 +76,15 @@
\includegraphics[width=1\textwidth]{GNS-BlockCreation-0}
\end{frame}
+\begin{frame}{Zone key TLD}
+ $$
+ \mathrlap{\overbrace{\phantom{\text{www}}}^{\text{Label}}}
+ \text{www.}
+ \mathrlap{\underbrace{{\color{fhggreen}\phantom{\text{000G005096M367VCT5D\ldots BXVBBBHX1GF0}}}}_{\text{Zone}}}
+ {\color{fhggreen}\text{000G005096M367VCT5D\ldots BXVBBBHX1GF0}}
+ $$
+\end{frame}
+
\begin{frame}{Zone management}
\includegraphics[height=0.9\textheight]{deleg0.pdf}
\end{frame}
@@ -124,12 +133,12 @@
\end{small}
\end{frame}
-\begin{frame}[fragile]{The GNUnet Registrar}
+\begin{frame}[fragile]{GNS Registrars}
How do I get my zone published?
\begin{itemize}
\item Entities in Start Zones are prime candiates to offer registrar services.
\item But, \textbf{anyone} can become a registrar!
- \item The GNUnet Project offers an experimental registrar service.
+ \item The GNUnet Project offers an experimental registrar service where you can pay with GNU Taler.
\end{itemize}
\end{frame}
@@ -220,7 +229,7 @@
\item[2012:] ``GNU Alternative Domain System'', Master's Thesis, TUM.
\item[2013:] ``The GNU Name System'', 30c3, Hamburg.
\item[2015:] ``Special Use Domain Names of P2P Systems''@DNSOP, IETF 93, Prague.
- \item[2019:] ``The GNU Name System: 2019 Edition''@DINGRG, IETF 104, Prague
+ \item[2019:] ``The GNU Name System: 2019 Edition''@DINRG, IETF 104, Prague
\item[2019:] ``The GNU Name System'', ICANN66, Montreal.
\end{itemize}
Around this time, NGI Search and discovery funding aquired to create the specification.
@@ -238,7 +247,7 @@
\end{itemize}
\item IRTF
\begin{itemize}
- \item Similar to IETF WGs but focussed on research topics. E.g. CFRG.
+ \item Similar to IETF WGs but focussed on research topics. E.g. DINRG.
\item Technically don't work on ``Standards'' (RFCs never have status ``Proposed Standard'').
\end{itemize}
\item ISE
@@ -265,8 +274,8 @@
There will be questions, and feedback!
\begin{itemize}
\item ``Why should this document be published as RFC (as opposed to self-published)''
- \item You need to propose (at least) two expert reviewers that can (and will!) provide extensive expert reviews to the ISE. The ISE may be able to help you with that, but take this into account \textbf{early}.
- \item There is going to be a lot of ping-pong with the ISE and all kinds of reviewers of the document from withing or outside of the IETF.
+ \item You need to propose (at least) two expert reviewers that can (and will!) provide extensive expert reviews to the ISE. The ISE may be able to help you with that, but take this into account \textbf{early}.
+ \item There is going to be a lot of ping-pong with the ISE and all kinds of reviewers of the document from withing or outside of the IETF.
\end{itemize}
\end{frame}
@@ -276,7 +285,7 @@
\item Includes the ``IETF conflict review''.
\item In our case, GNS potentially conflicts with other IETF work: DNS.
\item Again, extensive discussions with domain experts (DNSOP, IESG reviewer).
- \item Close coordination with RFC 9476 (dot-alt) to argumentatively deconflict.
+ \item Close coordination with RFC 9476 (dot-alt) to argumentatively deconflict.
\end{itemize}
\end{frame}
