[lsd0008] branch master updated: Update terminology in draft-nadler-sbox.xml & clarifications

[gnunet]

This is an automated email from the git hooks/post-receive script.

sebi pushed a commit to branch master
in repository lsd0008.

The following commit(s) were added to refs/heads/master by this push:
     new fcbbe0f  Update terminology in draft-nadler-sbox.xml & clarifications
fcbbe0f is described below

commit fcbbe0f24c83d323c6ca59bad6404854a86c8f1d
Author: Sebastian Nadler <sebastian.nadler@tum.de>
AuthorDate: Thu Dec 14 17:20:09 2023 +0100

    Update terminology in draft-nadler-sbox.xml & clarifications
---
 draft-nadler-sbox.xml | 28 +++++++++++++++++-----------
 1 file changed, 17 insertions(+), 11 deletions(-)

diff --git a/draft-nadler-sbox.xml b/draft-nadler-sbox.xml
index 0808a73..927bf85 100644
--- a/draft-nadler-sbox.xml
+++ b/draft-nadler-sbox.xml
@@ -95,13 +95,19 @@
     <section>
       <name>Terminology</name>
       <t>The terminology defined in <xref target="RFC9498" /> also applies to 
this document.</t>
-      <t>The following terms are used in this document:</t>
+      <t>This document includes the following additional terms:</t>
+      <dl>
+      <dt>Underscore label:</dt>
+      <dd>
+        A label is considered an underscore label only if it begins with an 
underscore. (e.g., "_name")
+      </dd>
       <dt>Underscore prefix:</dt>
         <dd>
           The underscore prefix contains the rightmost underscore label and 
all subsequent labels to its left.
           For example, the underscore prefix of 
"_service._proto.example.gns.alt" is "_service._proto" and 
           the underscore prefix of "c93f1e400.abcd._info.example.gns.alt" is 
"c93f1e400.abcd._info".
        </dd>
+      </dl>
     </section>
     <section anchor="rrecords">
       <name>Resource Records</name>
@@ -133,8 +139,8 @@
             record is supposed to handle all variations of underscore 
prefixes. The idea
             is to store the string representation of the underscore prefix 
instead of the service and protocol numbers. 
             A SBOX record boxes the record's type and data as well as the 
underscore prefix, and adds them to the record set
-            of the associated label. For example, a URI record for 
"_scheme._trust.example.com"
-            will be stored as an SBOX record in the record set of 
"example.com" with the underscore prefix
+            of the associated label. For example, a URI record for 
"_scheme._trust.example.gns.alt"
+            will be stored as an SBOX record in the record set of 
"example.gns.alt" with the underscore prefix
             "_schema._trust" and record type URI and the URI records data.</t>
           <t>For reference, see also <xref target="RFC8552" />.</t>
           <t>A SBOX DATA entry is illustrated in <xref
@@ -195,15 +201,15 @@
             target="RFC9498" /> Section 7.3, is modified here. All other cases 
and further processing steps remain the same.</t>
         <dl newline="false">
           <dt>Case 3:</dt>
-          <dd>If the remainder of 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
-            part of the final result and the recursion is processed as 
described in <xref
-              target="box_processing" />.
-            Additionally if the remainder of the name to be resolved is an 
underscore prefix and the record set
-            contains one or more matching SBOX records, the records in the 
SBOX records are part of
-            the final result and the recursion is processed as described in 
<xref
+          <dd>If the record set contains SBOX records and the name to be 
resolved is an underscore prefix, 
+            the records in the matching SBOX records are part of the final 
result.
+            The recursion is processed as described in <xref
               target="sbox_processing" />.
-            The final result is obtained by combining the unboxed records of 
the matched SBOX and BOX records.
+            Additionally, it <bcp14>MUST</bcp14> be checked whether the record 
set contains BOX records and the underscore prefix is in the format 
"_SERVICE._PROTO".
+            If this is the case the matching BOX records are added to the 
final result.  The recursion is processed as described in <xref
+            target="box_processing" />.
+            The final result is the combination of the unboxed record sets of 
the matched SBOX and BOX records.
+          </dd>
         </dl>
         <section anchor="box_processing">
           <name>BOX</name>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.