commit 6f50cc0a7138953329cdac811410ebcf29010b6f
parent dd1fd4190c37b8181fe71579a7316f3b6d8a2032
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Sat, 19 Feb 2022 20:19:44 +0100
improve ztype
Diffstat:
1 file changed, 11 insertions(+), 14 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -384,22 +384,13 @@
(see <xref target="resolution"/>).
</t>
<t>
- Each zone type (ztype) is assigned a unique 32-bit number when it is registered
+ Each zone type (ztype) is a unique 32-bit number.
+ This number corresponds to a resource record type number
+ identifying a delegation record type
in the GNUnet Assigned Numbers Authority <xref target="GANA" />.
The ztype determines which cryptosystem is used for the
- asymmetric and symmetric key operations of the zone.
- The ztype number always corresponds to a resource record type
- number identifying a delegation into a zone of this type. To
- ensure that there are no conflicts with DNS record types, ztypes
- are always assigned numeric values above 65535.
- </t>
- <t>
- For any zone, let d be the private key and zk the public zone key.
- The specific wire format used depends on the ztype.
- The creation of zone keys for the default ztypes are specified in
- <xref target="gnsrecords_delegation"/>.
- New ztypes may be specified in the future, for example if the
- cryptographic mechanisms used in this document are broken.
+ asymmetric and symmetric key operations of the zone and the format of
+ the delegation record type.
Any ztype MUST define the following set of cryptographic functions:
</t>
<dl>
@@ -470,6 +461,12 @@
and otherwise "FALSE".
</dd>
</dl>
+ <t>
+ The cryptographic functions of the default ztypes are specified with
+ their corresponding delegation records in <xref target="gnsrecords_delegation"/>.
+ New ztypes may be specified in the future, for example if the
+ cryptographic mechanisms used in this document are broken.
+ </t>
<section anchor="zTLD" numbered="true" toc="default">
<name>Zone Top-Level Domain</name>
<t>
