gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [lsd0001] branch master updated: replace rfc8032 mostly


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] branch master updated: replace rfc8032 mostly
Date: Fri, 04 Oct 2019 18:59:27 +0200

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 3a76cba  replace rfc8032 mostly
3a76cba is described below

commit 3a76cba5563fe4d459aed27deb63e696580fcec4
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Oct 4 18:57:16 2019 +0200

    replace rfc8032 mostly
---
 draft-schanzen-gns.xml | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index d69133c..6a4e3d4 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -83,7 +83,8 @@
    <t>
     A zone in GNS is defined by a public/private ECC key pair (d,zk),
     where d is the private key and zk the corresponding public key.
-    GNS combines the EC parameters of Ed25519 (<xref target="RFC8032" />)
+    GNS employs the curve parameters of the twisted edwards representation
+    of Curve25519 <xref target="RFC7748" /> (edwards25519)
     with the ECDSA scheme (<xref target="RFC6979" />).
     The deterministic property of ECDSA (as opposed to EdDSA) is required
     in order to achieve zone privacy.
@@ -93,27 +94,29 @@
    <dl>
     <dt>d</dt>
     <dd>
-      is a private key. It is defined in <xref target="RFC8032" /> as a b-bit
-      string. In our case, b is 256.
+      is a 256-bit ECDSA private key.
       In GNS, records are signed using a key derived from "d" as described in
       <xref target="publish" />.
     </dd>
     <dt>p</dt>
     <dd>
-      is the prime of Ed25519 as defined in <xref target="RFC8032" />, i.e.
+      is the prime of edwards25519 as defined in <xref target="RFC7748" />, 
i.e.
       2^255 - 19.
     </dd>
     <dt>B</dt>
     <dd>
-      is the group generator of the elliptic curve as defined in
-      <xref target="RFC8032" /> for Ed25519.
+      is the group generator (X(P),Y(P)) of edwards25519 as defined in
+      <xref target="RFC7748" />.
+    </dd>
+    <dt>L</dt>
+    <dd>
+      is the order of edwards25519 in <xref target="RFC7748" />.
     </dd>
     <dt>zk</dt>
     <dd>
       is the ECDSA public key corresponding to d. It is defined in
       <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.
+      generator of the elliptic curve.
       The public key is used to uniquely identify a GNS zone and is referred to
       as the "zone key".
     </dd>
@@ -809,6 +812,7 @@
 <back>
   <references>
     <name>Normative References</name>
+    <reference anchor="RFC7748" 
target="https://www.rfc-editor.org/info/rfc7748";><front><title>Elliptic Curves 
for Security</title><author initials="A." surname="Langley" fullname="A. 
Langley"><organization/></author><author initials="M." surname="Hamburg" 
fullname="M. Hamburg"><organization/></author><author initials="S." 
surname="Turner" fullname="S. Turner"><organization/></author><date year="2016" 
month="January"/><abstract><t>This memo specifies two elliptic curves over 
prime fields [...]
     <reference anchor="RFC3826" 
target="https://www.rfc-editor.org/info/rfc3826";><front><title>The Advanced 
Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security 
Model</title><author initials="U." surname="Blumenthal" fullname="U. 
Blumenthal"><organization/></author><author initials="F." surname="Maino" 
fullname="F. Maino"><organization/></author><author initials="K." 
surname="McCloghrie" fullname="K. McCloghrie"><organization/></author><date 
year="2004" month="June" [...]
     <reference anchor="RFC5890" 
target="https://www.rfc-editor.org/info/rfc5890";><front><title>Internationalized
 Domain Names for Applications (IDNA): Definitions and Document 
Framework</title><author initials="J." surname="Klensin" fullname="J. 
Klensin"><organization/></author><date year="2010" 
month="August"/><abstract><t>This document is one of a collection that, 
together, describe the protocol and usage context for a revision of 
Internationalized Domain Names for Applications (IDNA), [...]
     <reference anchor="RFC5869" 
target="https://www.rfc-editor.org/info/rfc5869";>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]