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.xml19
1 files changed, 14 insertions, 5 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 6d50df2..8063830 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -266,6 +266,13 @@
266 A GNS resource record contains information as defined by its 266 A GNS resource record contains information as defined by its
267 resource record type. 267 resource record type.
268 </dd> 268 </dd>
269 <dt>Client (Resolver)</dt>
270 <dd>
271 FIXME: We are using the word "client" often and it is not clearly
272 defined what a client is. Sometimes it is a "client resolver".
273 Is there another part of the resolver? What is it called?
274 This is mostly an issue in the name resolution section.
275 </dd>
269 </dl> 276 </dl>
270 </section> 277 </section>
271 <section anchor="overview" numbered="true" toc="default"> 278 <section anchor="overview" numbered="true" toc="default">
@@ -1840,7 +1847,8 @@ q := SHA-512 (ZKDF-Public(zk, label))
1840 provided by the client to guide processing. 1847 provided by the client to guide processing.
1841 <!-- FIXME: Is this still necessary? Clarify the purpose of the 1848 <!-- FIXME: Is this still necessary? Clarify the purpose of the
1842 provided record type and normatively define that resolver MUST NOT 1849 provided record type and normatively define that resolver MUST NOT
1843 filter? --> 1850 filter? THe normative statement for the CLIENT does not make sense.
1851 We need a normative statement for the implementer of GNS. -->
1844 However, filtering of record sets according to the required record 1852 However, filtering of record sets according to the required record
1845 types MUST still be done by the client after the resource record set 1853 types MUST still be done by the client after the resource record set
1846 is retrieved. 1854 is retrieved.
@@ -1849,13 +1857,14 @@ q := SHA-512 (ZKDF-Public(zk, label))
1849 <name>Start Zones</name> 1857 <name>Start Zones</name>
1850 <t> 1858 <t>
1851 <!-- FIXME: This is a mess --> 1859 <!-- FIXME: This is a mess -->
1852 The resolution of a GNS name must start in a given start zone 1860 The resolution of a GNS name starts in an initial start zone.
1853 indicated to the resolution algorithm using a (public) zone key. 1861 The local resolver may have one or more local start zones configured
1854 The local resolver may have one or more local start zones configured/hard-coded 1862 which point to local or remote zone keys.
1855 which point to local or remote zone public keys.
1856 A resolver may also determine the start zone from the 1863 A resolver may also determine the start zone from the
1857 suffix of the name given for resolution, or using information 1864 suffix of the name given for resolution, or using information
1858 retrieved out of band. 1865 retrieved out of band.
1866 </t>
1867 <t>
1859 The governance model of any zone is at the sole discretion 1868 The governance model of any zone is at the sole discretion
1860 of the zone owner. 1869 of the zone owner.
1861 However, the choice of start zone(s) is at the sole 1870 However, the choice of start zone(s) is at the sole