gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lsd0001] branch master updated: more label clarifications


From: gnunet
Subject: [lsd0001] branch master updated: more label clarifications
Date: Fri, 18 Feb 2022 12:13:48 +0100

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

martin-schanzenbach pushed a commit to branch master
in repository lsd0001.

The following commit(s) were added to refs/heads/master by this push:
     new 6e078b8  more label clarifications
6e078b8 is described below

commit 6e078b8b5971981f6ef6d5ea099f6a7565663a85
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Fri Feb 18 12:13:44 2022 +0100

    more label clarifications
---
 draft-schanzen-gns.xml | 25 ++++++++++++++++++-------
 1 file changed, 18 insertions(+), 7 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index db0effc..769f6d7 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -14,6 +14,7 @@
 <!ENTITY RFC5869 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5869.xml";>
 <!ENTITY RFC5890 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml";>
 <!ENTITY RFC5891 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml";>
+<!ENTITY RFC5895 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5895.xml";>
 <!ENTITY RFC6234 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.6234.xml";>
 <!-- <!ENTITY RFC6781 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.6781.xml";> -->
 <!ENTITY RFC6895 PUBLIC '' 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.6895.xml";>
@@ -190,15 +191,14 @@
          A GNS label is a label as defined in <xref target="RFC8499"/>.
          It is always assumed to be a U-label as
          defined in <xref target="RFC5890"/> and <xref target="RFC5891"/>.
-         Consequently, labels are case-sensitive UTF-8 strings in Unicode
+         Labels are case-sensitive UTF-8 strings in Unicode
          Normalization Form C (NFC) <xref target="Unicode-UAX15"/>.
          GNS does not impose length restrictions on labels. However, 
applications
          MAY ensure that name and label lengths are compatible with legacy
          DNS.
-         <!-- FIXME U-labels MUST not be too long. Their A-label representation
-         must fit into a DNS label. Do we want this limitation for GNS?
-         Or do we define "compatibility" labels that follow this limitation?
-         -->
+         In the spirit of <xref target="RFC5895"/>, applications MAY preprocess
+         labels (and names) to ensure compatibility with legacy DNS, for
+         example according to <xref target="Unicode-UTS46"/>.
        </dd>
        <dt>Apex Label</dt>
        <dd>
@@ -2640,6 +2640,7 @@ Purpose | Name            | References | Comment
        &RFC5869;
        &RFC5890;
        &RFC5891;
+       &RFC5895;
        &RFC6234;
        &RFC6895;
        &RFC6979;
@@ -2710,12 +2711,22 @@ Purpose | Name            | References | Comment
        <reference anchor="Unicode-UAX15" 
target="http://www.unicode.org/reports/tr15/tr15-31.html";>
          <front>
            <title>Unicode Standard Annex #15: Unicode Normalization Forms, 
Revision 31</title>
-          <author fullname="The Unicode Consortium">
-            <organization>University of Illinois at Chicago</organization>
+          <author>
+            <organization>The Unicode Consortium</organization>
           </author>
            <date year="2009" month="September"/>
          </front>
        </reference>
+       <reference anchor="Unicode-UTS46" 
target="https://www.unicode.org/reports/tr46";>
+         <front>
+           <title>Unicode Technical Standard #46: Unicode IDNA Compatibility 
Processing, Revision 27</title>
+          <author>
+            <organization>The Unicode Consortium</organization>
+          </author>
+           <date year="2021" month="August"/>
+         </front>
+       </reference>
+
 
 
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]