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
//! The TXT record data type.
use ;
use ;
use crate;
use crate*;
use crate;
use crateUnsizedCopy;
//----------- Txt ------------------------------------------------------------
/// Free-form text strings about this domain.
///
/// A [`Txt`] record holds a collection of "strings" (really byte sequences),
/// with no fixed purpose. Usually, a [`Txt`] record holds a single string;
/// if data has to be stored for different purposes, multiple [`Txt`] records
/// would be used.
///
/// Currently, [`Txt`] records are used systematically for e-mail security,
/// e.g. in SPF ([RFC 7208, section 3]), DKIM ([RFC 6376, section 3.6.2]), and
/// DMARC ([RFC 7489, section 6.1]). As a record data type with no strict
/// semantics and arbitrary data storage, it is likely to continue being
/// used.
///
/// [RFC 6376, section 3.6.2]: https://datatracker.ietf.org/doc/html/rfc6376#section-3.6.2
/// [RFC 7208, section 3]: https://datatracker.ietf.org/doc/html/rfc7208#section-3
/// [RFC 7489, section 6.1]: https://datatracker.ietf.org/doc/html/rfc7489#section-6.1
///
/// [`Txt`] is specified by [RFC 1035, section 3.3.14].
///
/// [RFC 1035, section 3.3.14]: https://datatracker.ietf.org/doc/html/rfc1035#section-3.3.14
///
/// ## Wire Format
///
/// The wire format of a [`Txt`] record is the concatenation of a (non-empty)
/// sequence of "character strings" (see [`CharStr`]). A character string is
/// serialized as a 1-byte length, followed by up to 255 bytes of content.
///
/// The memory layout of the [`Txt`] 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 [`Txt`] 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
///
/// [`Txt`] is a _dynamically sized type_ (DST). It is not possible to store
/// a [`Txt`] in place (e.g. in a local variable); it must be held indirectly,
/// via a reference or a smart pointer type like [`Box`]. This makes it more
/// difficult to _create_ new [`Txt`]s; but once they are placed somewhere,
/// they can be used by reference (i.e. `&Txt`) exactly like any other type.
///
/// [`Box`]: https://doc.rust-lang.org/std/boxed/struct.Box.html
///
/// It is currently a bit difficult to build a new [`Txt`] from scratch. It
/// is easiest to build the wire format representation of the [`Txt`] manually
/// (by building a sequence of [`CharStr`]s) and then to parse it.
///
/// ```
/// # use domain::new::base::CharStrBuf;
/// # use domain::new::base::wire::ParseBytesZC;
/// # use domain::new::rdata::Txt;
/// #
/// // From an existing wire-format representation.
/// let bytes = b"\x0DHello, World!\x0AAnd again!";
/// let from_bytes: &Txt = Txt::parse_bytes_by_ref(bytes).unwrap();
/// // It is also possible to use '<&Txt>::parse_bytes()'.
///
/// // To build a wire-format representation manually:
/// let strings: [CharStrBuf; 2] = [
/// "Hello, World!".parse().unwrap(),
/// "And again!".parse().unwrap(),
/// ];
/// let mut buffer: Vec<u8> = Vec::new();
/// for string in &strings {
/// buffer.extend_from_slice(string.wire_bytes());
/// }
/// assert_eq!(buffer.as_slice(), bytes);
///
/// // From an existing wire-format representation, but on the heap:
/// let buffer: Box<[u8]> = buffer.into_boxed_slice();
/// let from_boxed_bytes: Box<Txt> = Txt::parse_bytes_in(buffer).unwrap();
/// assert_eq!(from_bytes, &*from_boxed_bytes);
/// ```
///
/// As a DST, [`Txt`] does not implement [`Copy`] or [`Clone`]. Instead, it
/// implements [`UnsizedCopy`]. A [`Txt`], held by reference, can be copied
/// into a different container (e.g. `Box`) using [`unsized_copy_into()`].
///
/// [`unsized_copy_into()`]: UnsizedCopy::unsized_copy_into()
///
/// For debugging, [`Txt`] can be formatted using [`fmt::Debug`].
///
/// To serialize a [`Txt`] in the wire format, use [`BuildBytes`] (which
/// will serialize it to a given buffer) or [`AsBytes`] (which will
/// cast the [`Txt`] into a byte sequence in place). It also supports
/// [`BuildInMessage`].
//--- Construction
//--- Interaction
//--- Canonical operations
//--- Building into DNS messages
//--- Parsing from bytes
// SAFETY: The implementations of 'parse_bytes_by_{ref,mut}()' always parse
// the entirety of the input on success, satisfying the safety requirements.
unsafe
//--- Formatting
//--- Cloning
//--- Equality
//--- Hashing
//--- Parsing record data