commit 6e6cbec9febcc4002208fe483cafd1c979552173
parent 1f24da95f9bda547be7663b5be51ea46fd2890ce
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Wed, 22 Dec 2021 15:06:22 +0100
typos
Diffstat:
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
@@ -144,7 +144,7 @@
</t>
<t>
This document defines the normative wire format of resource records, resolution processes,
- cryptographic routines and security considerations for use by implementors.
+ cryptographic routines and security considerations for use by implementers.
</t>
<t>
This specification was developed outside the IETF and does not have
@@ -182,7 +182,7 @@
delegations which are iteratively queried from the storage (<xref target="resolution"/>).
</t>
<t>
- In this document, the "implementor" refers to the developer building
+ In this document, the "implementer" refers to the developer building
a GNS implementation including, for example, zone management tools and
name resolution components.
An "application" refers to a component which uses a GNS implementation
@@ -648,7 +648,7 @@ zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
<section anchor="rrecords" numbered="true" toc="default">
<name>Resource Records</name>
<t>
- A GNS implementor MUST provide a mechanism to create and manage resource
+ A GNS implementer MUST provide a mechanism to create and manage resource
records for local zones. A local zone is established by selecting a
zone type and creating a zone key pair.
The creation of zone keys for the default zone types are specificed in
@@ -716,8 +716,8 @@ zTLD := zkl[126:129].zkl[63:125].zkl[0:62]
Flags indicate metadata surrounding the resource record. A flag
value of 0 indicates that all flags are unset.
Applications creating resource records MUST set all bits which are
- not defined as a flag to 0. As additional flags may be defined in
- future protocol versions, applications MUST ignore unknown flags.
+ not defined as a flag to 0. Additional flags may be defined in
+ future protocol versions.
If an implementation encounters a flag which it does not
recognize, the resource record is not valid and MUST be discarded.
<xref target="figure_flag"/>
@@ -1047,8 +1047,8 @@ h[31] &= 7 // Implies h mod L == h
zk' := h * zk
]]></artwork>
<t>
- We note that implementors must employ a constant time scalar
- multiplication for the constructions above. Also, implementors
+ We note that implementers must employ a constant time scalar
+ multiplication for the constructions above. Also, implementers
must ensure that the private key a is an ed25519 private key
and specifically that "a[0] & 7 == 0" holds.
</t>
@@ -2083,11 +2083,11 @@ NICK: john (Supplemental)
<t>
This document does not specifiy the properties of the underlying
storage which is required by any GNS implementation.
- For implementors using a DHT as underlying storage, it is important
+ For implementers using a DHT as underlying storage, it is important
to note that the properties of the DHT are directly inherited by the
GNS implementation. This includes both security as well as
other non-functional properties such as scalability and performance.
- Implementors should take great care when selecting or implementing
+ Implementers should take great care when selecting or implementing
a DHT for use in a GNS implementation.
DHTs with strong security and performance guarantees exist
<xref target="R5N"/>.
@@ -2104,7 +2104,7 @@ NICK: john (Supplemental)
key is lost, compromised or replaced in the furture.
Pre-calculated revocations may become invalid due to expirations
or protocol changes such as epoch adjustments.
- Consequently, implementors and users must make precautions in order
+ Consequently, implementers and users must make precautions in order
to manage revocations accordingly.
</t>
<t>
