commit 7e60d7f84371df6e8c4774c86b60182f6624b6ba
parent 7034bf5b1704a8b980efb4d107d97aa1b1f36b4e
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date: Fri, 4 Oct 2019 19:02:35 +0200
update files
Diffstat:
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git 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
@@ -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
+-----+-----+-----+-----+-----+-----+-----+-----+
