diff options
author | Martin Schanzenbach <mschanzenbach@posteo.de> | 2020-07-25 12:26:37 +0200 |
---|---|---|
committer | Martin Schanzenbach <mschanzenbach@posteo.de> | 2020-07-25 12:26:37 +0200 |
commit | 51fce83e9a175409075b3d908d75a49f3338c45e (patch) | |
tree | e056a80bc783995c41835ef65bbfc9ea576fa07a | |
parent | 0010de43d832f39ffbb17898cfe052506aebd09e (diff) | |
download | lsd0001-51fce83e9a175409075b3d908d75a49f3338c45e.tar.gz lsd0001-51fce83e9a175409075b3d908d75a49f3338c45e.zip |
update slides
-rw-r--r-- | ietf/secdispatch/gns.tex | 113 |
1 files 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 @@ | |||
8 | \usepackage{blkarray} | 8 | \usepackage{blkarray} |
9 | \usepackage{amsmath} | 9 | \usepackage{amsmath} |
10 | \usepackage{multirow} | 10 | \usepackage{multirow} |
11 | \title{The GNU Name System\\\small{secdispatch -- IETF 108}} | 11 | \title{The GNU Name System\\\small{secdispatch -- IETF 108}\\\small{\url{https://datatracker.ietf.org/doc/draft-schanzen-gns/}}} |
12 | \date{11/5/2019} | 12 | \date{30/7/2020} |
13 | \author{Martin Schanzenbach} | 13 | \author{Martin Schanzenbach} |
14 | \institute{\hfill\large{GNUnet} \includegraphics[trim={0cm 1.5cm 0cm 0cm},clip,width=4em]{gnunet}} | 14 | \institute{\hfill\large{GNUnet} \includegraphics[trim={0cm 1.5cm 0cm 0cm},clip,width=4em]{gnunet}} |
15 | \begin{document} | 15 | \begin{document} |
@@ -113,45 +113,8 @@ | |||
113 | \includegraphics[height=0.9\textheight]{deleg2.pdf} | 113 | \includegraphics[height=0.9\textheight]{deleg2.pdf} |
114 | \end{frame} | 114 | \end{frame} |
115 | 115 | ||
116 | \section{How do we bootstrap the top-level zones?} | 116 | \section{Why are we here?} |
117 | \begin{frame} | 117 | \begin{frame}{Discussions at IETF/W3C/ICANN} |
118 | \includegraphics[height=0.9\textheight]{deleg3.pdf} | ||
119 | \end{frame} | ||
120 | |||
121 | |||
122 | \begin{frame}{The GNU Name System Root} | ||
123 | ``Hyper-hyper local root'' concept: | ||
124 | \begin{itemize} | ||
125 | \item Resolver ships with initial root zone configuration. | ||
126 | \item Root zone configurable \emph{locally} at \emph{each} endpoint. | ||
127 | \item User override/extension of root at top-level or subdomain-level for: | ||
128 | \begin{itemize} | ||
129 | \item Circumvent censorship if necessary. | ||
130 | \item Private networks. | ||
131 | \end{itemize} | ||
132 | \end{itemize} | ||
133 | \end{frame} | ||
134 | |||
135 | \begin{frame}{Envisioned Governance Model} | ||
136 | \begin{itemize} | ||
137 | \item Non-profit organization. | ||
138 | \item Multi-stakeholder model: Board, supporting organizations, \ldots | ||
139 | \item Examples for possible stakeholders: | ||
140 | \begin{itemize} | ||
141 | \item Software and OS Distributors | ||
142 | \item Browser vendors | ||
143 | \item Governments | ||
144 | \end{itemize} | ||
145 | \item Funding options: | ||
146 | \begin{itemize} | ||
147 | \item Applications for new top-level domains. | ||
148 | \item Registrations of new top-level domains. | ||
149 | \item \ldots | ||
150 | \end{itemize} | ||
151 | \end{itemize} | ||
152 | \end{frame} | ||
153 | |||
154 | \begin{frame}{Previous occurrences at IETF/W3C/ICANN} | ||
155 | \begin{itemize} | 118 | \begin{itemize} |
156 | \item IETF 93: \url{https://datatracker.ietf.org/doc/slides-93-dnsop-5/} | 119 | \item IETF 93: \url{https://datatracker.ietf.org/doc/slides-93-dnsop-5/} |
157 | \begin{itemize} | 120 | \begin{itemize} |
@@ -167,6 +130,11 @@ | |||
167 | 130 | ||
168 | \begin{frame}{Current Status} | 131 | \begin{frame}{Current Status} |
169 | \begin{itemize} | 132 | \begin{itemize} |
133 | \item Who is (and will be) working on it: | ||
134 | \begin{itemize} | ||
135 | \item GNUnet project. | ||
136 | \item Current funding for specfication by NLnet: \url{https://nlnet.nl/project/GNS/}. | ||
137 | \end{itemize} | ||
170 | \item Implementation | 138 | \item Implementation |
171 | \begin{itemize} | 139 | \begin{itemize} |
172 | \item Reference implementation in C part of GNUnet: \url{https://git.gnunet.org/gnunet.git/tree/src/gns} | 140 | \item Reference implementation in C part of GNUnet: \url{https://git.gnunet.org/gnunet.git/tree/src/gns} |
@@ -175,17 +143,35 @@ | |||
175 | \item Specification | 143 | \item Specification |
176 | \begin{itemize} | 144 | \begin{itemize} |
177 | \item Current draft: \texttt{draft-schanzen-gns-01}. | 145 | \item Current draft: \texttt{draft-schanzen-gns-01}. |
178 | \item Status: Finished but not complete. | 146 | \item Status: Documents current implementation. Collecting feedback to improve protocol (and spec). |
179 | \end{itemize} | 147 | \end{itemize} |
180 | \end{itemize} | 148 | \end{itemize} |
181 | \end{frame} | 149 | \end{frame} |
182 | 150 | ||
183 | \begin{frame}{Roadmap} | 151 | \begin{frame}{Next steps} |
152 | \begin{itemize} | ||
153 | \item Address received feedback: | ||
154 | \begin{itemize} | ||
155 | \item Better trust agility to address questions on choice of Hierarchical Deterministic Key Derivation (HKDF). Options: | ||
156 | \begin{itemize} | ||
157 | \item ECDSA w/ Cuve25519 (in draft) | ||
158 | \item Schnorr/Ed25519 (``Tor-style'') | ||
159 | \item BIP32-Ed25519\footnote{Has issues: \url{https://forum.web3.foundation/t/key-recovery-attack-on-bip32-ed25519/44}} | ||
160 | \end{itemize} | ||
161 | \item Update to symmetric encryption scheme for IND-CCA. | ||
162 | \item Address choice of DHT better. | ||
163 | \item Address key management / recovery. | ||
164 | \end{itemize} | ||
165 | \item Desired next steps at IETF: | ||
184 | \begin{itemize} | 166 | \begin{itemize} |
185 | \item Looking for a home at IETF. | 167 | \item Receive feedback from IETF experts on protocol and document. |
168 | \item Is this document interesting to any existing IETF/IRTF WG? | ||
169 | \end{itemize} | ||
186 | \end{itemize} | 170 | \end{itemize} |
187 | \end{frame} | 171 | \end{frame} |
188 | 172 | ||
173 | |||
174 | |||
189 | \begin{frame} | 175 | \begin{frame} |
190 | \begin{center} | 176 | \begin{center} |
191 | The GNU Name System\\ | 177 | The GNU Name System\\ |
@@ -214,4 +200,43 @@ | |||
214 | } | 200 | } |
215 | \end{frame} | 201 | \end{frame} |
216 | 202 | ||
203 | \section{How do we bootstrap the top-level zones?} | ||
204 | \begin{frame} | ||
205 | \includegraphics[height=0.9\textheight]{deleg3.pdf} | ||
206 | \end{frame} | ||
207 | |||
208 | |||
209 | \begin{frame}{The GNU Name System Root} | ||
210 | ``Hyper-hyper local root'' concept: | ||
211 | \begin{itemize} | ||
212 | \item Resolver ships with initial root zone configuration. | ||
213 | \item Root zone configurable \emph{locally} at \emph{each} endpoint. | ||
214 | \item User override/extension of root at top-level or subdomain-level for: | ||
215 | \begin{itemize} | ||
216 | \item Circumvent censorship if necessary. | ||
217 | \item Private networks. | ||
218 | \end{itemize} | ||
219 | \end{itemize} | ||
220 | \end{frame} | ||
221 | |||
222 | \begin{frame}{Envisioned Governance Model} | ||
223 | \begin{itemize} | ||
224 | \item Non-profit organization. | ||
225 | \item Multi-stakeholder model: Board, supporting organizations, \ldots | ||
226 | \item Examples for possible stakeholders: | ||
227 | \begin{itemize} | ||
228 | \item Software and OS Distributors | ||
229 | \item Browser vendors | ||
230 | \item Governments | ||
231 | \end{itemize} | ||
232 | \item Funding options: | ||
233 | \begin{itemize} | ||
234 | \item Applications for new top-level domains. | ||
235 | \item Registrations of new top-level domains. | ||
236 | \item \ldots | ||
237 | \end{itemize} | ||
238 | \end{itemize} | ||
239 | \end{frame} | ||
240 | |||
241 | |||
217 | \end{document} | 242 | \end{document} |