lsd0001

LSD0001: GNU Name System
Log | Files | Refs | README

commit 92b9a3c1f7b4cd67c902f8f2d8fd5e9175668b63
parent 63b8257b4e6eb4dcd279a3d9f1b4cefcbea3226f
Author: Schanzenbach, Martin <mschanzenbach@posteo.de>
Date:   Tue, 17 Dec 2019 21:30:16 +0100

minor fix

Diffstat:
Mdraft-schanzen-gns.html | 8++++----
Mdraft-schanzen-gns.txt | 12++++++------
Mdraft-schanzen-gns.xml | 8++++----
3 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/draft-schanzen-gns.html b/draft-schanzen-gns.html @@ -2086,18 +2086,18 @@ async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(le If the name to be resolved is of the format "_SERVICE._PROTO" and the record set contains one or more matching BOX records, the records in the BOX records are the result and the recusion - is concluded (Section <a href="#box_processing" class="xref">Section 6.2.4</a>).<a href="#section-6.2-2.2" class="pilcrow">¶</a> + is concluded (<a href="#box_processing" class="xref">Section 6.2.4</a>).<a href="#section-6.2-2.2" class="pilcrow">¶</a> </li> <li id="section-6.2-2.3"> Case 3: If the remainder of the name to resolve is not empty and does not match the "_SERVICE._PROTO" syntax, then the current record set MUST consist of a single PKEY record - (Section <a href="#pkey_processing" class="xref">Section 6.2.1</a>), + (<a href="#pkey_processing" class="xref">Section 6.2.1</a>), a single CNAME record - (Section <a href="#cname_processing" class="xref">Section 6.2.3</a>), + (<a href="#cname_processing" class="xref">Section 6.2.3</a>), or one or more GNS2DNS records - (Section <a href="#gns2dns_processing" class="xref">Section 6.2.2</a>), + (<a href="#gns2dns_processing" class="xref">Section 6.2.2</a>), which are processed as described in the respective sections below. Otherwise, resolution fails diff --git a/draft-schanzen-gns.txt b/draft-schanzen-gns.txt @@ -880,16 +880,16 @@ Internet-Draft The GNU Name System November 2019 2. Case 2: If the name to be resolved is of the format "_SERVICE._PROTO" and the record set contains one or more matching BOX records, the records in the BOX records are the - result and the recusion is concluded (Section Section 6.2.4). + result and the recusion is concluded (Section 6.2.4). 3. Case 3: If the remainder of the name to resolve is not empty and does not match the "_SERVICE._PROTO" syntax, then the current - record set MUST consist of a single PKEY record - (Section Section 6.2.1), a single CNAME record - (Section Section 6.2.3), or one or more GNS2DNS records - (Section Section 6.2.2), which are processed as described in the + record set MUST consist of a single PKEY record (Section 6.2.1), + a single CNAME record (Section 6.2.3), or one or more GNS2DNS + records (Section 6.2.2), which are processed as described in the respective sections below. Otherwise, resolution fails and the resolver MUST return an empty record set. Finally, after the + recursion terminates, the client preferences for the record type @@ -898,7 +898,6 @@ Schanzenbach, et al. Expires 13 May 2020 [Page 16] Internet-Draft The GNU Name System November 2019 - recursion terminates, the client preferences for the record type SHOULD be considered. If a VPN record is found and the client requests an A or AAAA record, the VPN record SHOULD be converted (Section Section 6.2.5) if possible. @@ -949,6 +948,7 @@ Internet-Draft The GNU Name System November 2019 + Schanzenbach, et al. Expires 13 May 2020 [Page 17] Internet-Draft The GNU Name System November 2019 diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml @@ -917,18 +917,18 @@ If the name to be resolved is of the format "_SERVICE._PROTO" and the record set contains one or more matching BOX records, the records in the BOX records are the result and the recusion - is concluded (Section <xref target="box_processing" />). + is concluded (<xref target="box_processing" />). </li> <li> Case 3: If the remainder of the name to resolve is not empty and does not match the "_SERVICE._PROTO" syntax, then the current record set MUST consist of a single PKEY record - (Section <xref target="pkey_processing" />), + (<xref target="pkey_processing" />), a single CNAME record - (Section <xref target="cname_processing" />), + (<xref target="cname_processing" />), or one or more GNS2DNS records - (Section <xref target="gns2dns_processing" />), + (<xref target="gns2dns_processing" />), which are processed as described in the respective sections below. Otherwise, resolution fails