commit ffd74189451f6450ade88dddeeb8e6d3a0948483
parent a3505a88e96d706fe7918033f10ed2a8e5892b07
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date: Fri, 4 Oct 2019 15:37:48 +0200
update
Diffstat:
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -87,10 +87,6 @@
with the ECDSA scheme (<xref target="RFC6979" />).
The deterministic property of ECDSA (as opposed to EdDSA) is required
in order to achieve zone privacy.
- Records published in a zone are signed using a derived private key
- as described in <xref target="publish" />.
- The public key "zk" is used to uniquely identify and refer to the zone and
- is thus called "zone key".
In the following, we use the following naming convention for out
cryptographic primitives:
</t>
@@ -99,6 +95,8 @@
<dd>
is a private key. It is defined in <xref target="RFC8032" /> as a b-bit
string. In our case, b is 256.
+ In GNS, records are signed using a key derived from "d" as described in
+ <xref target="publish" />.
</dd>
<dt>p</dt>
<dd>
@@ -116,6 +114,8 @@
<xref target="RFC6979" /> as the curve point d*B where B is the group
generator of the elliptic curve. Note that this is NOT a Ed25519 public
key.
+ The public key is used to uniquely identify a GNS zone and is referred to
+ as the "zone key".
</dd>
</dl>
