[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: add forward reference to ns ambig
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: add forward reference to ns ambig |
Date: |
Sat, 07 May 2022 14:20:10 +0200 |
This is an automated email from the git hooks/post-receive script.
martin-schanzenbach pushed a commit to branch master
in repository lsd0001.
The following commit(s) were added to refs/heads/master by this push:
new 72dc7ba add forward reference to ns ambig
72dc7ba is described below
commit 72dc7ba1e17edd424e6675ef0ac18be047bba68c
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Sat May 7 14:20:04 2022 +0200
add forward reference to ns ambig
---
draft-schanzen-gns.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 1f77330..4a90620 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -251,6 +251,9 @@
names and labels to ensure compatibility with DNS or support
specific user expectations, for example according to
<xref target="Unicode-UTS46"/>.
+ A GNS name may be indistinguishable from a DNS name and care must
+ be taken by applications and implementors when handling GNS names
+ (see <xref target="namespace_ambiguity"/>).
</dd>
<dt>Resolver</dt>
<dd>
@@ -2670,7 +2673,7 @@ NICK: john (Supplemental)
zone keys do become public during revocation.
</t>
</section>
- <section>
+ <section anchor="namespace_ambiguity">
<name>Namespace Ambiguity</name>
<t>
Some GNS names are indistinguishable from DNS names in their
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0001] branch master updated: add forward reference to ns ambig,
gnunet <=