gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [lsd0001] branch master updated: English


From: gnunet
Subject: [GNUnet-SVN] [lsd0001] branch master updated: English
Date: Fri, 04 Oct 2019 11:53:38 +0200

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 1581257  English
1581257 is described below

commit 158125723fe980b022e384187b323fe62ac530a9
Author: Christian Grothoff <address@hidden>
AuthorDate: Fri Oct 4 11:51:29 2019 +0200

    English
---
 draft-schanzen-gns.xml | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 978edad..78e97a2 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -247,14 +247,16 @@
 
 <section anchor="gnsrecords_leho" numbered="true" toc="default">
   <name>LEHO</name>
-  <t>As names in GNS are not globally unique, established practices such as
-    virtual hosting do not apply directly. In order to support such use cases,
-    GNS support a legacy hostname record which can be used by applications
-    (e.g. HTTP clients) in order to provide the necessary information.
-    The resource record contains a 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>
+  <t>Legacy hostname records can be used by applications that are expected
+  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:</t>
   <figure anchor="figure_lehorecord">
     <artwork name="" type="" align="left" alt=""><![CDATA[
       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]