gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [lsd0001] 02/02: update files


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] 02/02: update files
Date: Fri, 04 Oct 2019 19:04:49 +0200

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

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

commit 7e60d7f84371df6e8c4774c86b60182f6624b6ba
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Oct 4 19:02:35 2019 +0200

    update files
---
 draft-schanzen-gns.html | 4 ++--
 draft-schanzen-gns.txt  | 8 ++++----
 2 files changed, 6 insertions(+), 6 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
          +-----+-----+-----+-----+-----+-----+-----+-----+

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



reply via email to

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