lsd0004

LSD0004: R5N Distributed Hash Table
Log | Files | Refs

commit 3f0cec40b22cfdf999dbeb79d8197c7071f1f9eb
parent 4bc268fe86e04d5cde8176655d06b8ac92bc898b
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Fri, 11 Mar 2022 03:08:42 +0100

IANA/GANA considerations

Diffstat:
Mdraft-schanzen-r5n.xml | 94+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------
1 file changed, 73 insertions(+), 21 deletions(-)

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml @@ -683,16 +683,30 @@ Connectivity | |Underlay| |Underlay| is the URL-escaped payload of the address URI without the "://". </t> <t> - For example, consider the URL -""" -gnunet://hello/RH1M20EPK834M6MHZ72G3CMBSF3ECKNY4W0T9VAQP9Z7SZEM6Y3G/ -NGRTAH6RA04X467CGCH7M7CEXR5F9CV5HTZFK0G9BWETY3CCE2QWGVT4WA7JN5M9HMWG -60A00R71F1PJP8N5628EKGHHBAGA7M8JW30/1647134480?udp=127.0.0.1%3A2086 -""" + For example, consider the following URL: + </t> + <figure> + <artwork type="abnf"><![CDATA[ +gnunet://hello/RH1M20EPK834M6MHZ72\ +G3CMBSF3ECKNY4W0T9VAQP9Z7SZEM6Y3G/\ +NGRTAH6RA04X467CGCH7M7CEXR5F9CV5HT\ +ZFK0G9BWETY3CCE2QWGVT4WA7JN5M9HMWG\ +60A00R71F1PJP8N5628EKGHHBAGA7M8JW3\ +0/1647134480?udp=127.0.0.1%3A2086 + +FIXME: signature is invalid, should +maybe generate proper test vector. +]]> + </artwork> + </figure> + <t> It specifies that the peer with the ID "RH1M...6Y3G" is reachable via "udp" at 127.0.0.1 on port 2086 until - 1647134480 seconds after the Epoch. - FIXME: signature is invalid, generate proper test vector. + 1647134480 seconds after the Epoch. Note that "udp" + here is underspecified and just used as a simple example. + In practice, the key (addr-name) + <bcp14>MUST</bcp14> refer to a scheme supported by a + DHT Underlay. </t> <t> The general syntax of HELLO URLs specified using @@ -700,17 +714,17 @@ NGRTAH6RA04X467CGCH7M7CEXR5F9CV5HTZFK0G9BWETY3CCE2QWGVT4WA7JN5M9HMWG </t> <figure> <artwork type="abnf"><![CDATA[ - hello-URL = "gnunet://hello/" meta [ "?" addrs ] - meta = pid "/" sig "/" exp - pid = *bchar - sig = *bchar - exp = *DIGIT - addrs = addr *( "&" addr ) - addr = addr-name "=" addr-value - addr-name = scheme - addr-value = *pchar - bchar = *(ALPHA / DIGIT) - ]]> +hello-URL = "gnunet://hello/" meta [ "?" addrs ] +meta = pid "/" sig "/" exp +pid = *bchar +sig = *bchar +exp = *DIGIT +addrs = addr *( "&" addr ) +addr = addr-name "=" addr-value +addr-name = scheme +addr-value = *pchar +bchar = *(ALPHA / DIGIT) +]]> </artwork> </figure> <t> @@ -1975,8 +1989,16 @@ gnunet+tcp://12.3.4.5/ \ <section anchor="iana" numbered="true" toc="default"> <name>IANA Considerations</name> <t> - TODO: URI handler for "common" URI handler that Underlays may want - to use as part of HELLOs. + TODO: URI schema for "common" URI handler that Underlays may want + to use as part of HELLOs, i.e. what we currently term "ip+udp" + (but maybe change to "r5n+ip+udp://"!?). + </t> + <t> + TODO: URI schema for "gnunet://", as used for HELLO URIs + and for GNUnet-underlay addresses! We basically use both + gnunet://hello/ and gnunet://address/, so we should also register + "gnunet://" and say that the sub-registry is managed + by GANA! </t> </section> <section anchor="gana" numbered="true" toc="default"> @@ -2012,6 +2034,36 @@ Number| Name | Contact | References | Description 11 GNS N/A GNS Block for storing record data ]]></artwork> </figure> + + <t> + GANA <xref target="GANA"/> + is requested to create a "gnunet://" sub-registry. + The registry shall record for each entry: + </t> + <ul> + <li>Name: The name of the subsystem (case-insensitive ASCII + string, restricted to alphanumeric characters</li> + <li>Comment: Optionally, a brief English text describing the purpose of + the subsystem (in UTF-8)</li> + <li>Contact: Optionally, the contact information of a person to contact for + further information</li> + <li>References: Optionally, references describing the syntax of the URL + (such as an RFC or LSD)</li> + </ul> + <t> + The registration policy for this sub-registry is "First Come First + Served", as described in <xref target="RFC8126"/>. + GANA is requested to populate this registry as follows: + </t> + <figure anchor="figure_gnunetschema" title="GNUnet schema Subregistry."> + <artwork name="" type="" align="left" alt=""><![CDATA[ +Nam | Contact | References | Description +---------------+---------+------------+------------------------- +HELLO N/A [This.I-D] How to contact a peer. +ADDRESS N/A N/A Network address. +]]></artwork> + </figure> + <t> GANA is requested to amend the "GNUnet Signature Purpose" registry as follows: