aboutsummaryrefslogtreecommitdiff
path: root/draft-schanzen-gns.xml
diff options
context:
space:
mode:
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r--draft-schanzen-gns.xml5
1 files changed, 4 insertions, 1 deletions
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 @@
251 names and labels to ensure compatibility with DNS or support 251 names and labels to ensure compatibility with DNS or support
252 specific user expectations, for example according to 252 specific user expectations, for example according to
253 <xref target="Unicode-UTS46"/>. 253 <xref target="Unicode-UTS46"/>.
254 A GNS name may be indistinguishable from a DNS name and care must
255 be taken by applications and implementors when handling GNS names
256 (see <xref target="namespace_ambiguity"/>).
254 </dd> 257 </dd>
255 <dt>Resolver</dt> 258 <dt>Resolver</dt>
256 <dd> 259 <dd>
@@ -2670,7 +2673,7 @@ NICK: john (Supplemental)
2670 zone keys do become public during revocation. 2673 zone keys do become public during revocation.
2671 </t> 2674 </t>
2672 </section> 2675 </section>
2673 <section> 2676 <section anchor="namespace_ambiguity">
2674 <name>Namespace Ambiguity</name> 2677 <name>Namespace Ambiguity</name>
2675 <t> 2678 <t>
2676 Some GNS names are indistinguishable from DNS names in their 2679 Some GNS names are indistinguishable from DNS names in their