[lsd0008] branch master updated: Add underscore prefix terminology to the document

[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 556a941  Add underscore prefix terminology to the document
556a941 is described below

commit 556a941ad5c5f2b25152a89dd924275b162e01ee
Author: Sebastian Nadler <sebastian.nadler@tum.de>
AuthorDate: Wed Dec 13 13:08:25 2023 +0100

    Add underscore prefix terminology to the document
---
 draft-nadler-sbox.xml | 40 ++++++++++++++++++++++++----------------
 1 file changed, 24 insertions(+), 16 deletions(-)

diff --git a/draft-nadler-sbox.xml b/draft-nadler-sbox.xml
index b33cb1c..3593d0b 100644
--- a/draft-nadler-sbox.xml
+++ b/draft-nadler-sbox.xml
@@ -95,6 +95,13 @@
     <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>
+      <dt>Underscore prefix:</dt>
+        <dd>
+          The underscore prefix contains the first underscore label and all 
subsequent labels, traversing a name from right to left.
+          For example, the underscore prefix of "_service._proto.example.com" 
is "_service._proto" and 
+          the underscore prefix of "c93f1e400.abcd._info.example.com" is 
"c93f1e400.abcd._info".
+       </dd>
     </section>
     <section anchor="rrecords">
       <name>Resource Records</name>
@@ -119,25 +126,25 @@
             include them in the record set of the label they are associated
             with.</t>
           <t>This way of handling and storing restricts the allowed and 
processable underscore
-            labels to the format of "_SERVICE._PROTOCOL" as well as only 
services registered in
+            prefixes to the format of "_SERVICE._PROTOCOL" as well as only 
services registered in
             the corresponding IANA registry. A new SBOX record is proposed to 
enable the use of labels
             such as 
"c93f1e400f26708f98cb19d936620da35eec8f72e57f9eec01c1afd6._smimecert" and other 
variations of 
-            underscore labels for SMIMEA/URI/SRV, and other records. The SBOX
-            record is supposed to handle all variations of underscore labels. 
The concept
-            here is to store the string representation of the underscore label 
and all subsequent
-            labels, instead of the service and protocol numbers. 
-            A SBOX record boxes the record's type, data, underscore label, and 
subsequent labels, and adds them to the record set
+            underscore prefixes for SMIMEA/URI/SRV, and other records. The SBOX
+            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 label
-            "_schema._trust" and record type URI and the URI records data</t>
-          <t>For reference, see also <xref target="RFC8552" />. A SBOX DATA 
entry is illustrated in <xref
-              target="figure_boxrecord" />. </t>
+            will be stored as an SBOX record in the record set of 
"example.com" 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
+              target="figure_boxrecord" />.</t>
           <figure anchor="figure_boxrecord">
             <name>The SBOX DATA Wire Format</name>
             <artwork name="" type="" alt="">
 0     8     16    24    32    40    48    56
 +-----+-----+-----+-----+-----+-----+-----+-----+
-|          TYPE         |         LABEL         /
+|          TYPE         |         PREFIX        /
 +-----------+-----------+                       /
 /                                               /
 /                                               /
@@ -168,7 +175,7 @@
               Records saved as BOX records can also be saved as SBOX records. 
               Thus, upon encountering underscore labels processable by BOX 
records, 
               the resolver must store the labels as their protocol and service 
numbers, 
-              as well as their string representation. This way, the resolver 
should be able to 
+              as well as the underscore prefix. This way, the resolver should 
be able to 
               return all boxed records later, whether they are SBOX or BOX 
records. 
               More on this in <xref target="resolution" />.
               BOX records are more efficient for boxing resource records due 
to their smaller wire format.
@@ -183,19 +190,20 @@
       <section anchor="record_processing">
         <name>Record Processing</name>
         <t> The first step in processing the records remains the same as 
described in <xref
-            target="RFC9498" /> Section 4.1. </t>
+            target="RFC9498" /> Section 7. </t>
         <t> The next step depends on the context of the name being resolved. 
Case 3, as defined in <xref
-            target="RFC9498" /> Section 4.1, is modified and Case 6 is added 
to the list: </t>
+            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" />.
-            If the remainder of the name to be resolved is starting with "_" 
and the record set
+            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
               target="sbox_processing" />.
+            The final result is obtained by combining the unboxed records of 
the matched SBOX and BOX records.
         </dl>
         <section anchor="box_processing">
           <name>BOX</name>
@@ -212,7 +220,7 @@
           <name>SBOX</name>
           <t>
             When a SBOX record is received, a GNS resolver must unbox it if the
-            name to be resolved continues with "_" at the start of the next 
label.
+            name to be resolved continues with an underscore prefix.
             Otherwise, the SBOX record is to be left untouched.
           </t>
         </section>

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