diff options
author | Martin Schanzenbach <schanzen@gnunet.org> | 2022-05-01 14:04:15 +0200 |
---|---|---|
committer | Martin Schanzenbach <schanzen@gnunet.org> | 2022-05-01 14:04:15 +0200 |
commit | 0c3e00cd8c113e9ff32e5ea62de5e3a32fb0a02e (patch) | |
tree | fa6edaba7359581bd41fc5f3c04df57e4169a6b9 | |
parent | 14f3c80c0a9206525f8e2b28eb3446bb406de969 (diff) | |
download | lsd0001-0c3e00cd8c113e9ff32e5ea62de5e3a32fb0a02e.tar.gz lsd0001-0c3e00cd8c113e9ff32e5ea62de5e3a32fb0a02e.zip |
terminology wording
-rw-r--r-- | draft-schanzen-gns.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 5765b17..72988d0 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml | |||
@@ -189,18 +189,18 @@ | |||
189 | <dl> | 189 | <dl> |
190 | <dt>Application</dt> | 190 | <dt>Application</dt> |
191 | <dd> | 191 | <dd> |
192 | An application refers to a component which uses a GNS implementation | 192 | A component which uses a GNS implementation |
193 | to resolve names into records and processes its contents. | 193 | to resolve names into records and processes its contents. |
194 | </dd> | 194 | </dd> |
195 | <dt>Resolver</dt> | 195 | <dt>Resolver</dt> |
196 | <dd> | 196 | <dd> |
197 | The resolver is the part of the GNS implementation which provides | 197 | The component of a GNS implementation which provides |
198 | the recursive name resolution logic defined in | 198 | the recursive name resolution logic defined in |
199 | <xref target="resolution"/>. | 199 | <xref target="resolution"/>. |
200 | </dd> | 200 | </dd> |
201 | <dt>Zone Master</dt> | 201 | <dt>Zone Master</dt> |
202 | <dd> | 202 | <dd> |
203 | The zone master is the part of the GNS implementation which provides | 203 | The component of a GNS implementation which provides |
204 | local zone management and publication as defined in | 204 | local zone management and publication as defined in |
205 | <xref target="publish"/>. | 205 | <xref target="publish"/>. |
206 | </dd> | 206 | </dd> |
@@ -233,7 +233,7 @@ | |||
233 | </dd> | 233 | </dd> |
234 | <dt>Apex Label</dt> | 234 | <dt>Apex Label</dt> |
235 | <dd> | 235 | <dd> |
236 | The apex label is used to publish resource | 236 | This type of label is used to publish resource |
237 | records in a zone that can be resolved without providing a specific | 237 | records in a zone that can be resolved without providing a specific |
238 | label. It is the GNS method to provide what is the "zone apex" in DNS | 238 | label. It is the GNS method to provide what is the "zone apex" in DNS |
239 | <xref target="RFC4033"/>. | 239 | <xref target="RFC4033"/>. |
@@ -258,7 +258,7 @@ | |||
258 | </dd> | 258 | </dd> |
259 | <dt>Top-Level Domain</dt> | 259 | <dt>Top-Level Domain</dt> |
260 | <dd> | 260 | <dd> |
261 | The rightmost part of a GNS name is a GNS Top-Level Domain (TLD). | 261 | The rightmost part of a GNS name is a GNS Top-Level Domain (TLD). |
262 | A GNS TLD can consist of one or more labels. | 262 | A GNS TLD can consist of one or more labels. |
263 | Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>), | 263 | Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>), |
264 | GNS does not expect all users to use the same global root zone. Instead, | 264 | GNS does not expect all users to use the same global root zone. Instead, |
@@ -279,12 +279,12 @@ | |||
279 | </dd> | 279 | </dd> |
280 | <dt>Zone Key</dt> | 280 | <dt>Zone Key</dt> |
281 | <dd> | 281 | <dd> |
282 | The zone key uniquely identifies a zone. | 282 | A key which uniquely identifies a zone. |
283 | The zone key is usually a public key of an asymmetric key pair. | 283 | It is usually a public key of an asymmetric key pair. |
284 | </dd> | 284 | </dd> |
285 | <dt>Blinded Zone Key</dt> | 285 | <dt>Blinded Zone Key</dt> |
286 | <dd> | 286 | <dd> |
287 | A blinded zone key is derived from the zone key and a label. | 287 | The key derived from a zone key and a label. |
288 | The zone key and the blinded zone key are unlinkable without knowledge of the label. | 288 | The zone key and the blinded zone key are unlinkable without knowledge of the label. |
289 | </dd> | 289 | </dd> |
290 | <dt>Zone Key Derivation Function</dt> | 290 | <dt>Zone Key Derivation Function</dt> |
@@ -293,7 +293,7 @@ | |||
293 | </dd> | 293 | </dd> |
294 | <dt>Zone Owner</dt> | 294 | <dt>Zone Owner</dt> |
295 | <dd> | 295 | <dd> |
296 | The owner of a GNS zone is the holder of the secret (typically a private key) | 296 | The holder of the secret (typically a private key) |
297 | that (together with a label and a value to sign) allows the creation of zone | 297 | that (together with a label and a value to sign) allows the creation of zone |
298 | signatures that can be validated against the respective blinded zone key. | 298 | signatures that can be validated against the respective blinded zone key. |
299 | </dd> | 299 | </dd> |