diff options
author | Martin Schanzenbach <schanzen@gnunet.org> | 2022-03-26 13:34:28 +0100 |
---|---|---|
committer | Martin Schanzenbach <schanzen@gnunet.org> | 2022-03-26 13:34:28 +0100 |
commit | 92b46818b0f5a6375781cfb74d551d8c121b0068 (patch) | |
tree | 1baee46c9b1b4796141a84f28f358e517b09b30b | |
parent | 3767ef4116a2fc47aa64fd4da5ae159dea4be4b8 (diff) | |
download | lsd0001-92b46818b0f5a6375781cfb74d551d8c121b0068.tar.gz lsd0001-92b46818b0f5a6375781cfb74d551d8c121b0068.zip |
obsolete reference
-rw-r--r-- | draft-schanzen-gns.xml | 26 |
1 files changed, 15 insertions, 11 deletions
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml index c4474e1..096c0d2 100644 --- a/draft-schanzen-gns.xml +++ b/draft-schanzen-gns.xml | |||
@@ -19,7 +19,7 @@ | |||
19 | <!ENTITY RFC6895 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6895.xml"> | 19 | <!ENTITY RFC6895 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6895.xml"> |
20 | <!ENTITY RFC6979 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6979.xml"> | 20 | <!ENTITY RFC6979 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6979.xml"> |
21 | <!ENTITY RFC7363 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7363.xml"> | 21 | <!ENTITY RFC7363 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7363.xml"> |
22 | <!ENTITY RFC7706 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7706.xml"> | 22 | <!ENTITY RFC8806 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8806.xml"> |
23 | <!ENTITY RFC7748 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml"> | 23 | <!ENTITY RFC7748 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml"> |
24 | <!ENTITY RFC8032 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml"> | 24 | <!ENTITY RFC8032 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml"> |
25 | <!ENTITY RFC8126 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml"> | 25 | <!ENTITY RFC8126 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml"> |
@@ -35,13 +35,13 @@ | |||
35 | <?rfc sortrefs="yes" ?> | 35 | <?rfc sortrefs="yes" ?> |
36 | <?rfc compact="yes" ?> | 36 | <?rfc compact="yes" ?> |
37 | <?rfc subcompact="no" ?> | 37 | <?rfc subcompact="no" ?> |
38 | <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="info" docName="draft-schanzen-gns-11" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" version="3"> | 38 | <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="info" docName="draft-schanzen-gns-12" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" version="3"> |
39 | <!-- xml2rfc v2v3 conversion 2.26.0 --> | 39 | <!-- xml2rfc v2v3 conversion 2.26.0 --> |
40 | <front> | 40 | <front> |
41 | <title abbrev="The GNU Name System"> | 41 | <title abbrev="The GNU Name System"> |
42 | The GNU Name System | 42 | The GNU Name System |
43 | </title> | 43 | </title> |
44 | <seriesInfo name="Internet-Draft" value="draft-schanzen-gns-11"/> | 44 | <seriesInfo name="Internet-Draft" value="draft-schanzen-gns-12"/> |
45 | <author fullname="Martin Schanzenbach" initials="M." surname="Schanzenbach"> | 45 | <author fullname="Martin Schanzenbach" initials="M." surname="Schanzenbach"> |
46 | <organization>Fraunhofer AISEC</organization> | 46 | <organization>Fraunhofer AISEC</organization> |
47 | <address> | 47 | <address> |
@@ -158,7 +158,7 @@ | |||
158 | where root zone governance is centralized at the Internet Corporation | 158 | where root zone governance is centralized at the Internet Corporation |
159 | for Assigned Names and Numbers (ICANN). | 159 | for Assigned Names and Numbers (ICANN). |
160 | In DNS terminology, GNS roughly follows the idea of a local | 160 | In DNS terminology, GNS roughly follows the idea of a local |
161 | root zone deployment (see <xref target="RFC7706"/>), with the difference that it is not | 161 | root zone deployment (see <xref target="RFC8806"/>), with the difference that it is not |
162 | expected that all deployments use the same root zone, | 162 | expected that all deployments use the same root zone, |
163 | and that users can easily delegate control of arbitrary domain names to | 163 | and that users can easily delegate control of arbitrary domain names to |
164 | arbitrary zones. | 164 | arbitrary zones. |
@@ -227,7 +227,8 @@ | |||
227 | special purposes in the resolution protocol which are defined | 227 | special purposes in the resolution protocol which are defined |
228 | in the rest of the document. | 228 | in the rest of the document. |
229 | Zone administrators <bcp14>MAY</bcp14> disallow certain labels that | 229 | Zone administrators <bcp14>MAY</bcp14> disallow certain labels that |
230 | might be easily confused with other labels through registration policies. | 230 | might be easily confused with other labels through registration policies |
231 | (see also <xref target="security_abuse"/>). | ||
231 | </dd> | 232 | </dd> |
232 | <dt>Apex Label</dt> | 233 | <dt>Apex Label</dt> |
233 | <dd> | 234 | <dd> |
@@ -443,7 +444,8 @@ | |||
443 | <section anchor="zones" numbered="true" toc="default"> | 444 | <section anchor="zones" numbered="true" toc="default"> |
444 | <name>Zones</name> | 445 | <name>Zones</name> |
445 | <t> | 446 | <t> |
446 | An implementation <bcp14>SHOULD</bcp14> enable the user to create and manage zones. | 447 | A zone master implementation <bcp14>SHOULD</bcp14> enable the user to |
448 | create and manage zones. | ||
447 | If this functionality is not implemented, names can still be resolved | 449 | If this functionality is not implemented, names can still be resolved |
448 | if zone keys for the initial step in the name resolution are available | 450 | if zone keys for the initial step in the name resolution are available |
449 | (see <xref target="resolution"/>). | 451 | (see <xref target="resolution"/>). |
@@ -2195,7 +2197,7 @@ example.com = zTLD2 := Base32GNS(ztype2||zk2) | |||
2195 | <t> | 2197 | <t> |
2196 | Otherwise, it is expected that the resolver first resolves the | 2198 | Otherwise, it is expected that the resolver first resolves the |
2197 | IP addresses of the specified DNS name servers. | 2199 | IP addresses of the specified DNS name servers. |
2198 | The DNS name may have to be converted to an IDNA compliant | 2200 | The DNS name <bcp14>MUST</bcp14> be converted to an IDNA compliant |
2199 | representation <xref target="RFC5890" /> for resolution in DNS. | 2201 | representation <xref target="RFC5890" /> for resolution in DNS. |
2200 | GNS2DNS records <bcp14>MAY</bcp14> | 2202 | GNS2DNS records <bcp14>MAY</bcp14> |
2201 | contain numeric IPv4 or IPv6 addresses, allowing the resolver to | 2203 | contain numeric IPv4 or IPv6 addresses, allowing the resolver to |
@@ -2213,7 +2215,9 @@ example.com = zTLD2 := Base32GNS(ztype2||zk2) | |||
2213 | in which case the resolver <bcp14>MUST</bcp14> try all of them. | 2215 | in which case the resolver <bcp14>MUST</bcp14> try all of them. |
2214 | The resolver <bcp14>MAY</bcp14> try them in any order or even in parallel. | 2216 | The resolver <bcp14>MAY</bcp14> try them in any order or even in parallel. |
2215 | If multiple GNS2DNS records are present, the DNS name <bcp14>MUST</bcp14> be | 2217 | If multiple GNS2DNS records are present, the DNS name <bcp14>MUST</bcp14> be |
2216 | identical for all of them, if not the resolution fails and an | 2218 | identical for all of them. Otherwise, it is not clear which name |
2219 | the resolver is supposed to follow. If multiple DNS names are | ||
2220 | present the resolution fails and an | ||
2217 | appropriate error is <bcp14>SHOULD</bcp14> be returned to the application. | 2221 | appropriate error is <bcp14>SHOULD</bcp14> be returned to the application. |
2218 | </t> | 2222 | </t> |
2219 | <t> | 2223 | <t> |
@@ -2252,7 +2256,7 @@ example.com = zTLD2 := Base32GNS(ztype2||zk2) | |||
2252 | The (possibly recursive) resolution of the DNS name <bcp14>MUST NOT</bcp14> | 2256 | The (possibly recursive) resolution of the DNS name <bcp14>MUST NOT</bcp14> |
2253 | delegate back into GNS and should only follow the DNS specifications. | 2257 | delegate back into GNS and should only follow the DNS specifications. |
2254 | For example, names contained in DNS CNAME records <bcp14>MUST NOT</bcp14> be | 2258 | For example, names contained in DNS CNAME records <bcp14>MUST NOT</bcp14> be |
2255 | interpreted as GNS names. | 2259 | interpreted by resolvers that support both DNS and GNS as GNS names. |
2256 | </t> | 2260 | </t> |
2257 | <t> | 2261 | <t> |
2258 | GNS resolvers <bcp14>SHOULD</bcp14> offer a configuration | 2262 | GNS resolvers <bcp14>SHOULD</bcp14> offer a configuration |
@@ -2343,7 +2347,7 @@ NICK: eve (non-Supplemental) | |||
2343 | In this example, the returned NICK record is non-supplemental. | 2347 | In this example, the returned NICK record is non-supplemental. |
2344 | For the application, this means that the NICK belongs to the zone | 2348 | For the application, this means that the NICK belongs to the zone |
2345 | "alice.example" and is published under the apex label along with an A | 2349 | "alice.example" and is published under the apex label along with an A |
2346 | record. The NICK record should be interpreted as: The zone defined by | 2350 | record. The NICK record is interpreted as: The zone defined by |
2347 | "alice.example" wants to be referred to as "eve". | 2351 | "alice.example" wants to be referred to as "eve". |
2348 | In contrast, consider the following: | 2352 | In contrast, consider the following: |
2349 | </t> | 2353 | </t> |
@@ -2925,7 +2929,7 @@ Purpose | Name | References | Comment | |||
2925 | <!-- &RFC6781; --> | 2929 | <!-- &RFC6781; --> |
2926 | &RFC7363; | 2930 | &RFC7363; |
2927 | &RFC8324; | 2931 | &RFC8324; |
2928 | &RFC7706; | 2932 | &RFC8806; |
2929 | &RFC6761; | 2933 | &RFC6761; |
2930 | 2934 | ||
2931 | <!-- &RFC3912;--> | 2935 | <!-- &RFC3912;--> |