lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 93623deac1ff0390fb6cb7c5b4da474ae5ffffd6
parent bd80a2c08f5c51e857447e6059b080c8c09ad1ac
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sat, 26 Aug 2023 15:30:33 +0200

underlay URI schema are out of scope

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

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -2660,12 +2660,8 @@ BEGIN control such as <xref target="RFC6940"/> which, like R<sup>5</sup>N, provides a peer-to-peer (P2P) signaling protocol with extensible routing and topology mechanisms. - Some decentralized applications such as the GNU Name System (<xref target="I-D.schanzen-gns"/>) - require a more open system that enables ad-hoc participation and other means to prevent common - attacks on P2P overlays. - GNS, for example, would be in conflict with its goals of providing a solution to the issues of a - "Single Hierarchy with a Centrally Controlled Root" and "Distribution and Management of Root Servers" - in DNS as raised in <xref target="RFC8324"/>. + Some decentralized applications, such as the GNU Name System (<xref target="I-D.schanzen-gns"/>), + require an open system that enables ad-hoc participation. </t> </section> </section> @@ -2687,15 +2683,6 @@ BEGIN as an RFC. </t> </section> - <section anchor="r5n-uri" title="R5N URI Scheme Registration"> - <t> - IANA maintains the "Uniform Resource Identifier (URI) - Schemes" registry. The registry should be updated to include - an entry for the 'r5n+udp+ip' URI scheme. IANA is requested to - update that entry to reference this document when published - as an RFC. - </t> - </section> </section> <section anchor="gana" numbered="true" toc="default">