[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [lsd0001] 01/02: settle for UTF-8 LEHOs
From: |
gnunet |
Subject: |
[GNUnet-SVN] [lsd0001] 01/02: settle for UTF-8 LEHOs |
Date: |
Fri, 04 Oct 2019 19:04:48 +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 7034bf5b1704a8b980efb4d107d97aa1b1f36b4e
Author: Schanzenbach, Martin <address@hidden>
AuthorDate: Fri Oct 4 19:02:23 2019 +0200
settle for UTF-8 LEHOs
---
draft-schanzen-gns.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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.