diff options
Diffstat (limited to 'draft-schanzen-gns.xml')
| -rw-r--r-- | draft-schanzen-gns.xml | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 36c8f5b..8b2132c 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml @@ -2822,6 +2822,84 @@ NICK: john (Supplemental) </t> </section> </section> + <section anchor="gana" numbered="true" toc="default"> + <name>GANA Considerations</name> + <t> + GANA <xref target="GANA" /> + manages the "GNU Name System Record Types" registry. + Each entry has the following format: + </t> + <ul> + <li>Name: The name of the record type (case-insensitive ASCII + string, restricted to alphanumeric characters. For zone delegation + records, the assigned number represents the ztype value of the zone.</li> + <li>Number: 32-bit, above 65535</li> + <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> + <li>References: Optionally, references describing the record type + (such as an RFC).</li> + </ul> + <t> + The registration policy for this registry is "First Come First + Served". This policy is modeled on that described in <xref target="RFC8126"/>, + and describes the actions taken by GANA: + </t> + <t> + <!-- FIXME: Unclear who are the experts how are they selected and + by whom? GNUnet e.V. Politbüro? The DAO? + Unreserved/Reserved for private use record type range? --> + Adding new records is possible after expert review, using a + 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> + Any request <bcp14>MUST</bcp14> contain a unique name and a point of contact. + The contact information <bcp14>MAY</bcp14> be added to the registry given the consent + of the requester. + The request <bcp14>MAY</bcp14> optionally also contain relevant references as well + as a descriptive comment as defined above. + </t> + <t> + GANA has assigned numbers for the record types defined in this + specification in the "GNU Name System Record Types" registry + as listed in <xref target="figure_rrtypenums"/>. + </t> + <figure anchor="figure_rrtypenums" title="The GANA Resource Record Registry."> + <artwork name="" type="" align="left" alt=""><![CDATA[ +Number | Name | Contact | References | Comment +-------+---------+---------+------------+------------------------- +65536 | PKEY | N/A | [This.I-D] | GNS zone delegation (PKEY) +65537 | NICK | N/A | [This.I-D] | GNS zone nickname +65538 | LEHO | N/A | [This.I-D] | GNS legacy hostname +65540 | GNS2DNS | N/A | [This.I-D] | Delegation to DNS +65541 | BOX | N/A | [This.I-D] | Boxed records +65551 | REDIRECT| N/A | [This.I-D] | Redirection record. +65556 | EDKEY | N/A | [This.I-D] | GNS zone delegation (EDKEY) + ]]></artwork> + </figure> + <t> + GANA has assigned signature purposes in its + "GNUnet Signature Purpose" registry as listed in + <xref target="figure_purposenums"/>. + </t> + <figure anchor="figure_purposenums" title="Requested Changes in the GANA GNUnet Signature Purpose Registry."> + <artwork name="" type="" align="left" alt=""><![CDATA[ +Purpose | Name | References | Comment +--------+-----------------+------------+-------------------------- + 3 | GNS_REVOCATION | [This.I-D] | GNS zone key revocation + 15 | GNS_RECORD_SIGN | [This.I-D] | GNS record set signature + ]]></artwork> + </figure> + </section> + <!-- gana --> <section> <name>IANA Considerations</name> <t> |