[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: -localyy authoritative
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: -localyy authoritative |
Date: |
Mon, 07 Mar 2022 16:32:21 +0100 |
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 117a47e -localyy authoritative
117a47e is described below
commit 117a47e3463ce91effc96be16a8e6a16ad88006c
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Mon Mar 7 16:32:17 2022 +0100
-localyy authoritative
---
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 1d57a3d..89553bd 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -156,8 +156,8 @@
This is an important distinguishing factor from the Domain Name System
where root zone governance is centralized at the Internet Corporation
for Assigned Names and Numbers (ICANN).
- In DNS terminology, GNS roughly follows the idea of a hyperlocal root
- zone deployment, with the difference that it is not
+ In DNS terminology, GNS roughly follows the idea of a locally
+ authoritative root zone deployment, with the difference that it is not
expected that all deployments use the same local root zone,
and that users can easily delegate control of arbitrary domain names to
arbitrary zones.
--
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: -localyy authoritative,
gnunet <=