commit 8d54b11c81eaa81e66bbea6ebcf9ea80982f0c41
parent 5fddcd5bd577cda614cdcba07d5d2f9d146cdb2b
Author: Sebastian Nadler <sebastian.nadler@tum.de>
Date: Fri, 8 Dec 2023 12:50:07 +0100
Fix typos in SBOX record descriptions
Diffstat:
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-nadler-sbox.xml b/draft-nadler-sbox.xml
@@ -51,7 +51,7 @@
(DNS) protocols. </t>
<t>
This document defines the normative wire format of an additional resource record
- and a modifyed resolution processes for use by implementers.
+ and a modified resolution processes for use by implementers.
</t>
<t>
This specification was developed outside the IETF and does not have
@@ -154,7 +154,7 @@
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
- of the associated label. For example, a URI record for "_scheme._trust.exampel.com"
+ 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
@@ -198,7 +198,7 @@
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.
- Thierfore SBOX records are not a replacement for BOX records.
+ Therefore, SBOX records are not a replacement for BOX records.
</t>
</section>
</section>
@@ -222,7 +222,7 @@
</dl>
<dl newline="false">
<dt>Case 6:</dt>
- <dd>If the remainder of the name to be resolved is strating with "_" and the record set
+ <dd>If the remainder of the name to be resolved is starting with "_" 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" />. An additional check for "Case 3" <bcp14>MUST</bcp14> be
