1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
|
Independent Stream M.S. Schanzenbach
Internet-Draft GNUnet e.V.
Intended status: Informational 23 July 2019
Expires: 24 January 2020
The GNU Name System Specification
draft-schanzen-gns-00
Abstract
This document contains the GNU Name System (GNS) technical
specification.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 24 January 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Schanzenbach Expires 24 January 2020 [Page 1]
Internet-Draft The GNU Name System July 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. GNS resource records . . . . . . . . . . . . . . . . . . . . 2
2.1. GNS record blocks . . . . . . . . . . . . . . . . . . . . 2
2.1.1. GNS record block data cryptography . . . . . . . . . 3
2.2. GNS records . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4. Serialization format . . . . . . . . . . . . . . . . . . 5
2.5. Internationalization and Character Encoding . . . . . . . 5
2.6. Security Considerations . . . . . . . . . . . . . . . . . 5
3. Record Resolution . . . . . . . . . . . . . . . . . . . . . . 6
4. Namespace Revocation . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Normative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
This document contains the GNU Name System (GNS) technical
specification for secure, censorship-resistant and decentralised name
resolution.
This document defines the normative wire format of resource records,
resolution processes, cryptographic routines and security
considerations for use by implementors.
2. GNS resource records
2.1. GNS record blocks
TODO
A GNS record block has the following format:
Schanzenbach Expires 24 January 2020 [Page 2]
Internet-Draft The GNU Name System July 2019
0 8 16 24 32 40 48 56
+-----+-----+-----+-----+-----+-----+-----+-----+
| SIGNATURE |
| |
| |
| |
| |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
| PUBLIC KEY |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
| BDATA SIZE | PURPOSE |
+-----+-----+-----+-----+-----+-----+-----+-----+
| EXPIRATION |
+-----+-----+-----+-----+-----+-----+-----+-----+
/ BDATA /
/ /
+-----+-----+-----+-----+-----+-----+-----+-----+
Figure 1
where:
SIGNATURE The GNS record block signature.
PUBLIC KEY A public key which is used to verify SIGNATURE. This key
is not the public key of the namespace.
BDATA SIZE The GNS record block data length.
PURPOSE The signature purpose.
EXPIRATION The GNS record block expiration.
BDATA The GNS record block data
2.1.1. GNS record block data cryptography
Given a GNS record block a symmetric encryption scheme is used to
en-/decrypt "BDATA". The keys are derived from the record label "l"
and the public key "P". Both "l" and "P" are implicity known by the
GNS resolver. The key material "K" is derived as follows:
Schanzenbach Expires 24 January 2020 [Page 3]
Internet-Draft The GNU Name System July 2019
h := SHA512 (l,P)
d := h*x mod n
K := HKDF (P,l)
"HKDF" is a hash-based key derivation function as defined in
[RFC5869]. For the XTR, we use HMAC-SHA512 and HMAC-SHA256 in PRF as
proposed in (paper). Using this HKDF, we derive two symmetric
256-bit keys "Ka,Kt" from "K":
0 8 16 24 32 40 48 56
+-----+-----+-----+-----+-----+-----+-----+-----+
| AES KEY |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
| TWOFISH KEY |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
Figure 2
The two symmetric keys are used for a AES+TWOFISH combined cipher:
RDATA := TWOFISH256(Kt, AES256(Ka, BDATA))
2.2. GNS records
The RDATA consist of one or more entries in the following format:
Schanzenbach Expires 24 January 2020 [Page 4]
Internet-Draft The GNU Name System July 2019
0 8 16 24 32 40 48 56
+-----+-----+-----+-----+-----+-----+-----+-----+
| EXPIRATION |
+-----+-----+-----+-----+-----+-----+-----+-----+
| PUBLIC KEY |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
| RDATA SIZE | TYPE |
+-----+-----+-----+-----+-----+-----+-----+-----+
| FLAGS | DATA |
+-----+-----+-----+-----+ |
/ /
/ /
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
Figure 3
The a PKEY DATA entry has the following format:
0 8 16 24 32 40 48 56
+-----+-----+-----+-----+-----+-----+-----+-----+
| PUBLIC KEY |
| |
| |
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
Figure 4
2.3. Examples
TODO
2.4. Serialization format
TODO (Is this not the same as wire format?)
2.5. Internationalization and Character Encoding
TODO
2.6. Security Considerations
TODO
Schanzenbach Expires 24 January 2020 [Page 5]
Internet-Draft The GNU Name System July 2019
3. Record Resolution
TODO
4. Namespace Revocation
TODO
5. IANA Considerations
This will be fun
6. Normative References
[RFC5869] Krawczyk, H. and P. Eronen, "HMAC-based Extract-and-Expand
Key Derivation Function (HKDF)", RFC 5869,
DOI 10.17487/RFC5869, May 2010,
<https://www.rfc-editor.org/info/rfc5869>.
Author's Address
Martin Schanzenbach
GNUnet e.V.
Boltzmannstrasse 3
85748 Garching
Germany
Email: schanzen@gnunet.org
Schanzenbach Expires 24 January 2020 [Page 6]
|
