aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2022-02-02 17:33:11 +0100
committerChristian Grothoff <christian@grothoff.org>2022-02-02 17:33:11 +0100
commitd3f8491f9cc28d0d32dc8686d1fb55dcd024e167 (patch)
tree460547a58122705f39a85e85b760e17ae290417f
parenta928ebf3def4adec7767c7e52c0699e7202606bf (diff)
downloadlsd0001-d3f8491f9cc28d0d32dc8686d1fb55dcd024e167.tar.gz
lsd0001-d3f8491f9cc28d0d32dc8686d1fb55dcd024e167.zip
another idea
-rw-r--r--draft-schanzen-gns.xml3
1 files changed, 3 insertions, 0 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index ac04d78..b37e4ef 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -2128,6 +2128,9 @@ example.com = zk2
2128 If the implementation does not have the capacity to establish 2128 If the implementation does not have the capacity to establish
2129 a GTS tunnel, for example because it is not connected to the GNUnet 2129 a GTS tunnel, for example because it is not connected to the GNUnet
2130 network, the record set MUST be returned as retrieved from the network. 2130 network, the record set MUST be returned as retrieved from the network.
2131 <!-- FIXME: idea: what if we prescribe this ONLY for the dns2gns proxy,
2132 and not for a vanilla GNS resolver? That would allow us to more
2133 clearly separate VPN/legacy IP logic from GNS proper! -->
2131 </t> 2134 </t>
2132 </section> 2135 </section>
2133 <section anchor="nick_processing" numbered="true" toc="default"> 2136 <section anchor="nick_processing" numbered="true" toc="default">