gnunet-svn
[Top][All Lists]
Advanced

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

[lsd0004] branch master updated: some comments


From: gnunet
Subject: [lsd0004] branch master updated: some comments
Date: Wed, 29 Sep 2021 11:45:47 +0200

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

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

The following commit(s) were added to refs/heads/master by this push:
     new d0ebb51  some comments
d0ebb51 is described below

commit d0ebb512f33e151adb1511a01266b67c9de46720
Author: Martin Schanzenbach <mschanzenbach@posteo.de>
AuthorDate: Wed Sep 29 11:45:39 2021 +0200

    some comments
---
 draft-schanzen-r5n.xml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 4f1afab..a62b15e 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -80,6 +80,11 @@
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
+     <!-- FIXME: Here we should also cite and discuss RELOAD 
(https://datatracker.ietf.org/doc/html/rfc6940)
+       and establish why we need this spec and are not a "Topology plugin"
+       in RELOAD. The argumentation revolves around the trust model (openness) 
and
+       security aspects (path signatures).
+     -->
      <t>
        Distributed Hash Tables (DHTs) are a key data structure for the
        construction of completely decentralized applications.
@@ -655,7 +660,10 @@ END
      </section>
    </section>
    <section anchor="security" numbered="true" toc="default">
-       <name>Security Considerations</name>
+     <name>Security Considerations</name>
+     <!-- FIXME: Here we should (again) discuss how the system is open and
+     does not have/require a trust anchor a priori. This is (again) in contrast
+     to RELOAD -->
    </section>
    <section anchor="gana" numbered="true" toc="default">
        <name>GANA Considerations</name>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

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