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
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
//! The ZONEMD record type.
//!
//! See [RFC 8976](https://www.rfc-editor.org/rfc/rfc8976.html).
use ;
use crate::;
//----------- ZoneMD ---------------------------------------------------------
/// A message digest of the enclosing zone.
///
/// A [`ZoneMD`] record contains a deterministically computed digest (i.e.
/// cryptographic hash) of the contents of the surrounding zone. It can
/// be used to verify the integrity (and possibly authenticity) of all the
/// records in the zone, including glue records, even at rest.
///
/// [`ZoneMD`] is specified by [RFC 8976]. As discussed within, it provides
/// unique functionality over other means of checking and authenticating DNS
/// zones; when DNSSEC-signed, it asserts the authenticity of glue records
/// present with the zone. This is especially important for the root zone.
///
/// [RFC 8976]: https://www.rfc-editor.org/rfc/rfc8976.html
///
/// ## Computation
///
/// [`ZoneMD`] specifies a [scheme] and a [hash algorithm]. The scheme decides
/// how the records in the zone will be collected, serialized, and hashed. The
/// hash algorithm simply selects a cryptographic hash function. The scheme
/// and hash algorithm are completely independent selections; at present,
/// there are no (overt or subtle) interactions hindering certain combinations
/// of scheme and hash algorithm.
///
/// [scheme]: ZoneMDScheme
/// [hash algorithm]: ZoneMDHashAlg
///
/// At present, [`ZoneMD`] has some drawbacks. The defined schemes do not
/// support parallelization or incrementality, so arbitrarily small changes
/// to the zone require re-computing the digest (effectively) from scratch.
/// While this is acceptable for smaller zones, it hinders usage in larger
/// zones (primarily TLDs). New algorithms may be defined in the future which
/// provide parallelization and incrementality without loss of security.
///
/// ## Wire Format
///
/// The wire format of a [`ZoneMD`] record is the concatenation of its fields,
/// in the same order as the `struct` definition.
///
/// The memory layout of the [`ZoneMD`] type is identical to its serialization
/// in the wire format. This means it can be parsed from the wire format in a
/// zero-copy fashion, which is more efficient.
///
/// ## Usage
///
/// Because [`ZoneMD`] is a record data type, it is usually handled within
/// an enum like [`RecordData`]. This section describes how to use it
/// independently (or when building new record data from scratch).
///
/// [`RecordData`]: crate::new::rdata::RecordData
///
/// By default, [`ZoneMD`] is a _dynamically sized type_ (DST). It is not
/// possible to store a [`ZoneMD`] in place (e.g. in a local variable); it
/// must be held indirectly, via a reference or a smart pointer type like
/// [`Box`].
///
/// [`Box`]: https://doc.rust-lang.org/std/boxed/struct.Box.html
///
/// However, [`ZoneMD`] _can_ be constructed in place by taking advantage of
/// its generic parameter. Just as you can define a `[u8; 48]` in a local
/// variable, then hold it by reference as a `&[u8]`, you can define a
/// `ZoneMD<[u8; 48]>` in a local variable, then hold it by reference as a
/// `&ZoneMD<[u8]>`. `[u8]` is the default for that generic parameter.
///
/// There's a few ways to build a [`ZoneMD`]:
///
/// ```
/// # use domain::new::base::wire::{ParseBytes, ParseBytesZC, BuildBytes};
/// # use domain::new::rdata::{ZoneMD, ZoneMDScheme, ZoneMDHashAlg};
/// #
/// // Construct a 'ZoneMD' directly:
/// let direct: ZoneMD<[u8; 48]> = ZoneMD {
/// serial: 42.into(),
/// scheme: ZoneMDScheme::SIMPLE,
/// hash_alg: ZoneMDHashAlg::SHA384,
/// digest: [
/// 0xb9, 0x10, 0xcb, 0xc5, 0x64, 0xfa, 0x4d, 0x47,
/// 0x52, 0xde, 0x22, 0x31, 0x27, 0x4a, 0x42, 0xcc,
/// 0xfd, 0x3d, 0x88, 0xde, 0x1c, 0x16, 0x4b, 0xfa,
/// 0xc2, 0x61, 0x20, 0x32, 0x30, 0x01, 0x48, 0xa9,
/// 0x7e, 0x73, 0x00, 0x4a, 0x63, 0x6f, 0x0e, 0xa5,
/// 0xfc, 0x17, 0xe6, 0xbe, 0x74, 0x8f, 0x3f, 0x2a,
/// ],
/// };
/// // Taken by reference, the generic parameter can be dropped.
/// // This is an unsizing coercion to 'ZoneMD<[u8]>'.
/// let direct: &ZoneMD = &direct;
///
/// // Parse a 'ZoneMD' from the DNS wire format:
/// let bytes = [
/// 0, 0, 0, 42, 1, 1,
/// 0xb9, 0x10, 0xcb, 0xc5, 0x64, 0xfa, 0x4d, 0x47,
/// 0x52, 0xde, 0x22, 0x31, 0x27, 0x4a, 0x42, 0xcc,
/// 0xfd, 0x3d, 0x88, 0xde, 0x1c, 0x16, 0x4b, 0xfa,
/// 0xc2, 0x61, 0x20, 0x32, 0x30, 0x01, 0x48, 0xa9,
/// 0x7e, 0x73, 0x00, 0x4a, 0x63, 0x6f, 0x0e, 0xa5,
/// 0xfc, 0x17, 0xe6, 0xbe, 0x74, 0x8f, 0x3f, 0x2a,
/// ];
/// let from_bytes = ZoneMD::parse_bytes_by_ref(&bytes).unwrap();
/// // It is also possible to use '<&ZoneMD>::parse_bytes()'.
/// # assert_eq!(from_bytes, direct);
///
/// // Serialize a 'ZoneMD' in the DNS wire format:
/// let mut buffer = vec![0u8; from_bytes.built_bytes_size()];
/// from_bytes.build_bytes(&mut buffer).unwrap();
/// assert_eq!(buffer, bytes);
///
/// // Parse a 'ZoneMD' from the wire format, but on the heap:
/// let buffer: Box<[u8]> = buffer.into_boxed_slice();
/// let from_boxed_bytes: Box<ZoneMD> = ZoneMD::parse_bytes_in(buffer).unwrap();
/// assert_eq!(from_bytes, &*from_boxed_bytes);
/// ```
///
/// [`ZoneMD`] implements [`Copy`], [`Clone`], and/or [`UnsizedCopy`] if
/// its digest type implements them. By default, its digest type is `[u8]`,
/// which only implements [`UnsizedCopy`]. A `&ZoneMD` can be copied into a
/// different container (e.g. `Box`) using [`unsized_copy_into()`].
///
/// [`unsized_copy_into()`]: UnsizedCopy::unsized_copy_into()
///
/// For debugging, [`ZoneMD`] can be formatted using [`fmt::Debug`].
///
/// To serialize a [`ZoneMD`] in the wire format, use [`BuildBytes`]
/// (which will serialize it to a given buffer) or [`AsBytes`] (which will
/// cast the [`ZoneMD`] into a byte sequence in place). It also supports
/// [`BuildInMessage`].
//--- Formatting
//--- Cloning
// The following impl would be ideal, but it conflicts with
// 'impl<T: Clone> Clone for Box<T>'.
//
//impl<Digest: UnsizedCopy> Clone for Box<ZoneMD<Digest>> { ... }
//
// The common case is 'ZoneMD<[u8]>' (i.e. just 'ZoneMD'), so we only
// implement 'Clone' for that.
//--- Canonical operations
//--- Parsing record data
//--- Building into DNS messages
//----------- ZoneMDScheme ---------------------------------------------------
/// A scheme for computing [`ZoneMD`] digests.
///
/// This enumeration describes the [`ZoneMD::scheme`] field. It is specified
/// by [RFC 8976, section 2.2.2]. IANA maintains [a registry][iana] of defined
/// schemes.
///
/// [RFC 8976, section 2.2.2]: https://www.rfc-editor.org/rfc/rfc8976.html#section-2.2.2
/// [iana]: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#zonemd-schemes
///
/// Scheme values 240-254 (inclusive) are allocated for "Private Use". Scheme
/// values 0 and 255 are "Reserved".
//--- Associated Constants
//--- Formatting
//----------- ZoneMDHashAlg --------------------------------------------------
/// A hash algorithm for computing [`ZoneMD`] digests.
///
/// This enumeration describes the [`ZoneMD::hash_alg`] field. It is specified
/// by [RFC 8976, section 2.2.3]. IANA maintains [a registry][iana] of defined
/// hash algorithms.
///
/// [RFC 8976, section 2.2.3]: https://www.rfc-editor.org/rfc/rfc8976.html#section-2.2.3
/// [iana]: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#zonemd-hash-algorithms
///
/// Algorithm values 240-254 (inclusive) are allocated for "Private Use".
/// Algorithm values 0 and 255 are "Reserved".
//--- Associated Constants
//--- Formatting