lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 0d4577cd9759c791185fff8ef2ba10c11ac9c7f6
parent a74e8aa5d720da763d0ee628356434c9f785b13e
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri, 12 Jul 2024 08:55:54 +0200

fix build issues

Diffstat:
Mdraft-schanzen-r5n.xml | 26+++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -22,7 +22,6 @@ <!ENTITY RFC8032 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml"> <!ENTITY RFC8126 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml"> <!ENTITY RFC8174 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"> -<!ENTITY RFC8324 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8324.xml"> <!ENTITY RFC9498 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.9498.xml"> ]> <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> @@ -1195,12 +1194,14 @@ BEGIN <dl> <dt>SIGNATURE</dt> <dd> - is a 64 byte EdDSA signature using the current hop's private - key affirming the peer public keys of the previous and next hops. + is a 64 byte EdDSA signature <xref target="ed25519"/> created + using the current hop's private + key which affirms the public keys of the peers from the + previous and next hops. </dd> <dt>PRED PEER PUBLIC KEY</dt> <dd> - is the EdDSA public key of the previous peer on the path. + is the EdDSA public key <xref target="ed25519"/> of the previous peer on the path. </dd> </dl> <t> @@ -1473,7 +1474,7 @@ BEGIN </dd> <dt>SIGNATURE</dt> <dd> - is a 64 byte EdDSA signature using the sender's private + is a 64 byte EdDSA signature <xref target="ed25519"/> using the sender's private key affirming the information contained in the message. The signature is signing exactly the same data that is being signed in a <tt>HELLO</tt> block as described in <xref target="hello_block"/>. @@ -1669,7 +1670,7 @@ BEGIN <dd> is only provided if the RECORD ROUTE flag is set in FLAGS. If present, this is - an EdDSA signature of the sender of this message + an EdDSA signature <xref target="ed25519"/> by the sender of this message (using the same format as the signatures in PUTPATH) affirming that the sender forwarded the message from the predecessor (all zeros if PATH_LEN is 0, @@ -2170,7 +2171,7 @@ BEGIN <dd> is only provided if the <tt>RecordRoute</tt> flag is set in FLAGS. If present, this is - an EdDSA signature of the sender of this message + an EdDSA signature <xref target="ed25519"/> by the sender of this message (using the same format as the signatures in PUTPATH) affirming that the sender forwarded the message from the predecessor (all zeros if PATH_LEN is 0, @@ -2555,7 +2556,7 @@ BEGIN <dt>ValidateBlockStoreRequest(Block) -&gt; BlockEvaluationResult</dt> <dd> - To validate a block store request is to verify + To validate a block store request is to verify the EdDSA <tt>SIGNATURE</tt> over the hashed <tt>ADDRESSES</tt> against the public key from the PEER PUBLIC KEY field. If the signature is valid BLOCK_VALID is returned. @@ -2945,14 +2946,16 @@ Type | Name | References | Description <name>Normative References</name> &RFC2119; + &RFC2663; + &RFC3561; &RFC3629; &RFC3986; &RFC4634; &RFC5234; + &RFC5245; &RFC6940; &RFC8126; &RFC8174; - &RFC8324; &RFC9498; <reference anchor="ed25519" target="http://link.springer.com/chapter/10.1007/978-3-642-23951-9_9"><front><title>High-Speed High-Security Signatures</title><author initials="D." surname="Bernstein" fullname="Daniel Bernstein"><organization>University of Illinois at Chicago</organization></author><author initials="N." surname="Duif" fullname="Niels Duif"><organization>Technische Universiteit Eindhoven</organization></author><author initials="T." surname="Lange" fullname="Tanja Lange"><organization>Technische Universiteit Eindhoven</organization></author><author initials="P." surname="Schwabe" fullname="Peter Schwabe"><organization>National Taiwan University</organization></author><author initials="B." surname="Yang" fullname="Bo-Yin Yang"><organization>Academia Sinica</organization></author><date year="2011"/></front></reference> @@ -3253,8 +3256,9 @@ Type | Name | References | Description The general format of a <tt>HELLO</tt> URL uses "gnunet://" as the scheme, followed by "hello/" for the name of the GNUnet subsystem, followed by "/"-separated values - with the GNS Base32 encoding (<xref target="RFC9498"/>) of - the peer public key, a Base32-encoded EdDSA signature, and an expiration + with the GNS Base32 encoding <xref target="RFC9498"/> of + the peer public key, a Base32-encoded EdDSA signature + <xref target="ed25519"/>, and an expiration time in seconds since the UNIX Epoch in decimal format. After this a "?" begins a list of key-value pairs where the key is the URI scheme of one of the peer's addresses and the value