commit 38a0d0ae917d94a02244506676955277da627367
parent f195a7f5210e5c4c4c8312f67dd6684b01ee7eb1
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Wed, 22 Dec 2021 13:33:59 +0100
update gana
Diffstat:
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -2121,7 +2121,7 @@ NICK: john (Supplemental)
<li>Comment: Optionally, a brief English text describing the purpose of
the record type (in UTF-8)</li>
<li>Contact: Optionally, the contact information of a person to contact for
- further information</li>
+ further information.</li>
<li>References: Optionally, references describing the record type
(such as an RFC)</li>
</ul>
@@ -2132,18 +2132,23 @@ NICK: john (Supplemental)
</t>
<t>
Adding records is possible after expert review, using a
- first-come-first-served policy for unique "Name" allocation.
+ first-come-first-served policy for unique name allocation.
Experts are responsible to ensure that the chosen "Name" is
appropriate for the record type.
-
+ The registry will assign a unique number for the entry.
+ </t>
+ <t>
The current contact(s) for expert review are reachable at
gns-registry@gnunet.org.
</t>
<t>
- For the GANA First Come First Served policy, assignments are made to
- anyone on a first come, first served basis. There is no substantive
- review of the request, other than to ensure that it is well-formed
- and doesn't duplicate an existing assignment.
+ Any request MUST contain a unique name and a point of contact.
+ The contact information MAY be added to the registry given the consent
+ of the requestor.
+ The request MAY optionally also contain relevant references as well
+ as a descriptive comment as defined above.
+ </t>
+ <t>
GANA is requested to populate this registry as listed in
<xref target="figure_rrtypenums"/>.
</t>
