[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: terminology: trying to clarify
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: terminology: trying to clarify |
Date: |
Mon, 31 Jan 2022 14:27:38 +0100 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository lsd0001.
The following commit(s) were added to refs/heads/master by this push:
new 883e822 terminology: trying to clarify
883e822 is described below
commit 883e822ff2378065833c8b21c9739452d3c13827
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Mon Jan 31 14:27:35 2022 +0100
terminology: trying to clarify
---
draft-schanzen-gns.xml | 29 ++++++++++++++++-------------
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index b323607..652ce02 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -183,7 +183,7 @@
A GNS label is a label as defined in <xref target="RFC8499"/>.
Within this document, labels are always assumed to be strings of
UTF-8 characters <xref target="RFC8499"/> with a maximum length of
- 63 bytes. When hashed, labels MUST be canonicalized using
+ 63 bytes. When hashed, labels MUST be canonicalized using
Normalization Form C (NFC) <xref target="Unicode-UAX15"/>.
</dd>
<dt>Name</dt>
@@ -195,26 +195,27 @@
</dd>
<dt>Top-Level Domain</dt>
<dd>
- A GNS Top-Level Domain is a GNS label and a Top-Level
- Domain (TLD) as defined in <xref target="RFC8499"/>.
- With the exception of Zone Top-Level Domains (see below),
+ The rightmost label in a GNS name is a GNS Top-Level Domain (TLD).
+ Unlike DNS Top-Level Domains (defined in <xref target="RFC8499"/>),
+ GNS does not use a root zone as such. Instead,
+ with the exception of Zone Top-Level Domains (see below),
GNS TLDs are part of the configuration of the local resolver
(see <xref target="governance"/>) and may not be globally unique.
</dd>
<dt>Zone</dt>
<dd>
A GNS zone contains authoritative information (resource records).
- A zone is uniquely identified by its zone key.
+ A zone is uniquely identified by its zone key. Unlike DNS zones,
+ a GNS zone does not need to have a SOA record at its apex.
</dd>
<dt>Zone Type</dt>
<dd>
- The type of a GNS zone determines the format and type of the
- zone key.
+ The type of a GNS zone determines the cipher system and binary
encoding
+ format of the zone key, blinded zone keys, and signatures.
</dd>
<dt>Zone Key</dt>
<dd>
The zone key uniquely identifies a zone.
- Its format and type depend on the associated zone type.
The zone key is usually a public key of an asymmetric key pair.
</dd>
<dt>Blinded Zone Key</dt>
@@ -224,16 +225,18 @@
</dd>
<dt>Zone Owner</dt>
<dd>
- The owner of a GNS zone is the holder of the private key
corresponding to
- the respective zone key.
+ The owner of a GNS zone is the holder of the secret (typically a
private key)
+ that (together with a label and a value to sign) allows the creation
of zone
+ signatures that can be validated against the respective blinded zone
key.
</dd>
<dt>Zone Top-Level Domain</dt>
<dd>
- A GNS Zone Top-Level Domain (zTLD) is a GNS name and a Top-Level
- Domain (TLD) as defined in <xref target="RFC8499"/>.
- It represents a sub-group of all TLDs and encodes the zone type and
+ A GNS Zone Top-Level Domain (zTLD) is a GNS label used as the
+ rightmost label in a GNS name which encodes a zone type and
zone key of a zone.
Due to the statistical uniqueness of zone keys, zTLDs are also
globally unique.
+ A zTLD label can only be distinguished from ordinary TLD labels
+ by attempting to decode the label to a zone type and zone key.
</dd>
<dt>Resource Record</dt>
<dd>
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0001] branch master updated: terminology: trying to clarify,
gnunet <=