diff options
Diffstat (limited to 'draft-schanzen-gns.xml')
-rw-r--r-- | draft-schanzen-gns.xml | 30 |
1 files changed, 20 insertions, 10 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index 9139921..52e9fd4 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml | |||
@@ -276,6 +276,11 @@ | |||
276 | It enables the user to manage zones (<xref target="publish"/>) and | 276 | It enables the user to manage zones (<xref target="publish"/>) and |
277 | resolve names (<xref target="resolution"/>). | 277 | resolve names (<xref target="resolution"/>). |
278 | </dd> | 278 | </dd> |
279 | <dt>Application</dt> | ||
280 | <dd> | ||
281 | An application refers to a component which uses a GNS implementation | ||
282 | to resolve records from the network and (usually) processes its contents. | ||
283 | </dd> | ||
279 | </dl> | 284 | </dl> |
280 | </section> | 285 | </section> |
281 | <section anchor="overview" numbered="true" toc="default"> | 286 | <section anchor="overview" numbered="true" toc="default"> |
@@ -344,19 +349,22 @@ | |||
344 | In the remainder of this document, the "implementer" refers to the developer building | 349 | In the remainder of this document, the "implementer" refers to the developer building |
345 | a GNS implementation including, for example, zone management tools and | 350 | a GNS implementation including, for example, zone management tools and |
346 | name resolution components. | 351 | name resolution components. |
347 | An "application" refers to a component which uses a GNS implementation | ||
348 | to resolve records from the network and (usually) processes its contents. | ||
349 | </t> | 352 | </t> |
350 | </section> | 353 | </section> |
351 | <section anchor="zones" numbered="true" toc="default"> | 354 | <section anchor="zones" numbered="true" toc="default"> |
352 | <name>Zones</name> | 355 | <name>Zones</name> |
353 | <t> | 356 | <t> |
354 | <!-- FIXME: MUST or SHOULD? --> | ||
355 | A client implementation MUST enable the user to manage zones. | ||
356 | A zone in GNS is uniquely identified by its zone type and zone key. | 357 | A zone in GNS is uniquely identified by its zone type and zone key. |
357 | Each zone can be represented by a Zone Top-Level Domain (zTLD) string. | 358 | Each zone can be represented by a Zone Top-Level Domain (zTLD) string. |
358 | </t> | 359 | </t> |
359 | <t> | 360 | <t> |
361 | <!-- FIXME: MUST or SHOULD? Was must reformulated SHOULD --> | ||
362 | A client implementation SHOULD enable the user to create and manage zones. | ||
363 | If this functionality is not implemented, names can still be resolved | ||
364 | if zone keys for the initial step in the name resolution are available | ||
365 | (see <xref target="resolution"/>). | ||
366 | </t> | ||
367 | <t> | ||
360 | Each zone type (ztype) is assigned a unique 32-bit number when it is registered | 368 | Each zone type (ztype) is assigned a unique 32-bit number when it is registered |
361 | in the GNUnet Assigned Numbers Authority <xref target="GANA" />. | 369 | in the GNUnet Assigned Numbers Authority <xref target="GANA" />. |
362 | The ztype determines which cryptosystem is used for the | 370 | The ztype determines which cryptosystem is used for the |
@@ -1847,6 +1855,7 @@ q := SHA-512 (ZKDF-Public(zk, label)) | |||
1847 | <xref target="governance" />. | 1855 | <xref target="governance" />. |
1848 | </t> | 1856 | </t> |
1849 | <t> | 1857 | <t> |
1858 | <!-- FIXME removed client everywhere. We only have an implementation --> | ||
1850 | The client implementation MAY allow the user to provide a desired | 1859 | The client implementation MAY allow the user to provide a desired |
1851 | record type for the resolver. | 1860 | record type for the resolver. |
1852 | The desired record type is used to guide processing. | 1861 | The desired record type is used to guide processing. |
@@ -1857,9 +1866,10 @@ q := SHA-512 (ZKDF-Public(zk, label)) | |||
1857 | provided record type and normatively define that resolver MUST NOT | 1866 | provided record type and normatively define that resolver MUST NOT |
1858 | filter? THe normative statement for the CLIENT does not make sense. | 1867 | filter? THe normative statement for the CLIENT does not make sense. |
1859 | We need a normative statement for the implementer of GNS. --> | 1868 | We need a normative statement for the implementer of GNS. --> |
1860 | The resolver MUST NOT filter according to the desired record type. | 1869 | The resolver implementation MUST NOT filter results according to the desired |
1861 | Filtering of record sets types MAY still be done by the client after the | 1870 | record type. |
1862 | resource record set is retrieved. | 1871 | Filtering of record sets MAY still be done by the client which |
1872 | could be a stub resolver. | ||
1863 | </t> | 1873 | </t> |
1864 | <section anchor="governance" numbered="true" toc="default"> | 1874 | <section anchor="governance" numbered="true" toc="default"> |
1865 | <name>Start Zones</name> | 1875 | <name>Start Zones</name> |
@@ -1884,13 +1894,13 @@ q := SHA-512 (ZKDF-Public(zk, label)) | |||
1884 | management of root servers in DNS (see <xref target="RFC8324"/>, Section 3.10 and 3.12). | 1894 | management of root servers in DNS (see <xref target="RFC8324"/>, Section 3.10 and 3.12). |
1885 | </t> | 1895 | </t> |
1886 | <t> | 1896 | <t> |
1887 | In the following, we give examples how a local client resolver SHOULD | 1897 | In the following, we give examples how a local client SHOULD |
1888 | discover the start zone. The process given is not exhaustive and | 1898 | discover the start zone. The process given is not exhaustive and |
1889 | clients MAY supplement it with other mechanisms or ignore it if the | 1899 | clients MAY supplement it with other mechanisms or ignore it if the |
1890 | particular application requires a different process. | 1900 | particular application requires a different process. |
1891 | </t> | 1901 | </t> |
1892 | <t> | 1902 | <t> |
1893 | GNS clients MUST first try to interpret the top-level domain of | 1903 | GNS implementations MUST first try to interpret the top-level domain of |
1894 | a GNS name as a zone key representation (i.e. a zTLD). | 1904 | a GNS name as a zone key representation (i.e. a zTLD). |
1895 | If the top-level domain can be converted to a valid ztype and zone | 1905 | If the top-level domain can be converted to a valid ztype and zone |
1896 | key value, the resulting zone key is used as the start zone: | 1906 | key value, the resulting zone key is used as the start zone: |
@@ -2360,7 +2370,7 @@ NICK: john (Supplemental) | |||
2360 | ensure that their local start zone information is not compromised or | 2370 | ensure that their local start zone information is not compromised or |
2361 | outdated. | 2371 | outdated. |
2362 | It can be expected that the processing of zone revocations and an | 2372 | It can be expected that the processing of zone revocations and an |
2363 | initial start zone is provided with a GNS client implementation | 2373 | initial start zone is provided with a GNS implementation |
2364 | ("drop shipping"). Shipping an initial start zone with an entry for | 2374 | ("drop shipping"). Shipping an initial start zone with an entry for |
2365 | the root (".") effectively establishes a root zone. | 2375 | the root (".") effectively establishes a root zone. |
2366 | Extension and customization of the zone is at the full discretion of | 2376 | Extension and customization of the zone is at the full discretion of |