[lsd0001] branch master updated: GANA considerations

[gnunet]

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

grothoff pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 0829d70  GANA considerations
0829d70 is described below

commit 0829d70db1c679890d04bc61c938a96cbcd289df
Author: Christian Grothoff <address@hidden>
AuthorDate: Tue May 5 23:49:34 2020 +0200

    GANA considerations
---
 draft-schanzen-gns.xml | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 58a4c64..1ba49ce 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -948,7 +948,7 @@
            <t>
              When the resolver encounters a PKEY record and the remainder of
              the name is not empty, resolution continues
-             recursively with the remainder of the name in the 
+             recursively with the remainder of the name in the
              GNS zone specified in the PKEY record.
            </t>
            <t>
@@ -966,7 +966,7 @@
            <t>
              When a resolver encounters one or more GNS2DNS records and the 
remaining name
              is empty and the desired record type is GNS2DNS, the GNS2DNS
-             records are returned.  
+             records are returned.
            </t>
            <t>
              Otherwise, it is expected that the resolver first resolves the
@@ -1025,7 +1025,7 @@
              current zone.  Otherwise, the resulting name is resolved via the
              default operating system name resolution process.
              This may in turn again trigger a GNS resolution process depending
-             on the system configuration.  
+             on the system configuration.
              <!-- Note: this permits non-DNS resolvers to be triggered via 
NSS! -->
            </t>
            <t>
@@ -1038,7 +1038,7 @@
              If the last CNAME was a DNS name, the resolver returns the DNS 
name
              as a supplemental LEHO record (<xref target="gnsrecords_leho" />)
              with a relative expiration time of one hour.
-       <!-- Note: Martin: do we actually implement this in GNS today? 
+       <!-- Note: Martin: do we actually implement this in GNS today?
       Seems rather tricky to detect if we go via NSS... -->
            </t>
          </section>
@@ -1462,13 +1462,13 @@
      </section>
      </section>
      <section anchor="iana" numbered="true" toc="default">
-       <name>IANA Considerations</name>
+       <name>GANA Considerations</name>
        <t>
-         IANA is requested to create an "GNU Name System Record Type" registry.
+         GANA is requested to create an "GNU Name System Record Types" 
registry.
 The registry shall record for each entry:
        </t>
        <ul>
-         <li>Type: The name of the record type (case insensitive ASCII
+         <li>Name: The name of the record type (case-insensitive ASCII
            string, restricted to alphanumeric characters</li>
          <li>Number: 32-bit, above 65535</li>
          <li>Contact: The contact information of a person to contact for
@@ -1479,11 +1479,11 @@ The registry shall record for each entry:
        <t>
          The registration policy for this sub-registry is "First Come First
          Served", as described in <xref target="RFC8126"/>.
-         IANA is requested to populate this registry as follows:
+         GANA is requested to populate this registry as follows:
        </t>
        <figure anchor="figure_rrtypenums">
          <artwork name="" type="" align="left" alt=""><![CDATA[
-           Number   | Type            | Contact | References
+           Number   | Name            | Contact | References
            ---------+-----------------+---------+---------
            65536    | PKEY            | N/A     | [This.I-D]
            65537    | NICK            | N/A     | [This.I-D]
@@ -1491,7 +1491,6 @@ The registry shall record for each entry:
            65539    | VPN             | N/A     | [This.I-D]
            65540    | GNS2DNS         | N/A     | [This.I-D]
            65541    | BOX             | N/A     | [This.I-D]
-           FIXME We have a lot more?
            ]]></artwork>
          <!--        <postamble>which is a very simple example.</postamble>-->
        </figure>
@@ -1661,7 +1660,7 @@ The registry shall record for each entry:
       password hashing and proof-of-work applications.  We provide an
       implementer-oriented description with
       test vectors.  The purpose is to simplify adoption of Argon2 for
-      Internet protocols.  This document is a product of the Crypto Forum 
Research Group (CFRG) 
+      Internet protocols.  This document is a product of the Crypto Forum 
Research Group (CFRG)
        in the IRTF.
              </t>
            </abstract>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.