[GNUnet-SVN] [lsd0001] branch master updated (fe02f57 -> 7e60d7f)

[gnunet]

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

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

    from fe02f57  minor changes
     new 7034bf5  settle for UTF-8 LEHOs
     new 7e60d7f  update files

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 draft-schanzen-gns.html | 4 ++--
 draft-schanzen-gns.txt  | 8 ++++----
 draft-schanzen-gns.xml  | 4 ++--
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html
index 33d1d56..4e23f72 100644
--- a/draft-schanzen-gns.html
+++ b/draft-schanzen-gns.html
@@ -1381,8 +1381,8 @@ async function addMetadata(){try{const 
e=document.styleSheets[0].cssRules;for(le
   is HTTP virtual hosting, which as-is would not work with GNS names as
   those may not be globally unique.
 
-  A LEHO resource record contains a string (which is not 0-terminated) 
representing
-  the legacy hostname to use (FIXME: in UTF-8 or PUNY?).
+  A LEHO resource record contains an UTF-8 string (which is not 0-terminated)
+  representing the legacy hostname to use.
   It is expected to be found together in a single
   resource record with an IPv4 or IPv6 address.
    A LEHO DATA entry has the following format:<a href="#section-3.3-1" 
class="pilcrow">¶</a></p>
diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt
index b0f50dd..b65f73e 100644
--- a/draft-schanzen-gns.txt
+++ b/draft-schanzen-gns.txt
@@ -288,10 +288,10 @@ Internet-Draft             The GNU Name System            
     July 2019
    to supply a DNS name on the application layer.  The most common use
    case is HTTP virtual hosting, which as-is would not work with GNS
    names as those may not be globally unique.  A LEHO resource record
-   contains a string (which is not 0-terminated) representing the legacy
-   hostname to use (FIXME: in UTF-8 or PUNY?).  It is expected to be
-   found together in a single resource record with an IPv4 or IPv6
-   address.  A LEHO DATA entry has the following format:
+   contains an UTF-8 string (which is not 0-terminated) representing the
+   legacy hostname to use.  It is expected to be found together in a
+   single resource record with an IPv4 or IPv6 address.  A LEHO DATA
+   entry has the following format:
 
          0     8     16    24    32    40    48    56
          +-----+-----+-----+-----+-----+-----+-----+-----+
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index a1bc79e..87bdb8a 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -284,8 +284,8 @@
   is HTTP virtual hosting, which as-is would not work with GNS names as
   those may not be globally unique.
 
-  A LEHO resource record contains a string (which is not 0-terminated) 
representing
-  the legacy hostname to use (FIXME: in UTF-8 or PUNY?).
+  A LEHO resource record contains an UTF-8 string (which is not 0-terminated)
+  representing the legacy hostname to use.
   It is expected to be found together in a single
   resource record with an IPv4 or IPv6 address.
    A LEHO DATA entry has the following format:</t>

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