You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I personally don't like the underscored words in the html rendering of the document
It "blank" the new American spelling of "blanc" ?
has a corresponding _hash_ that summarizes the contents
I find "summarizes" a strange word here. It is not the hash contains a summary one can read.
[SECG] has no IETF equivalent? Should it?
proposaland -> proposal and
Figure 13: Cleaning up after removing the third member
I would say "after removing member C" (avoid ambiguity about "every third")
This section defines _tree
hashes_, and _parent hashes_ are defined in [Section 8.9](https://www.ietf.org/archive/id/draft-ietf-mls-protocol-15.html#section-8.9)
I read this wrong the first way, the "," vanishes due to the unscores. Maybe: This section defines tree hashes, the next section defines parent hashes. Or alternatively, leave onlthe the first sentence in 8.8, then put the remainder and next section in two subsections (so 8.8.1 and 8.8.2)
For example, a malicious group member could send
Maybe: For example, a malicious group member could otherwise send
to previously compromised public keys.
Maybe: to public keys whose private key was previously compromised.
Post-compromise security is also provided for new groups
This reads a little odd as "new groups" would have no history and thus no previous compromise.
The text was updated successfully, but these errors were encountered:
Comment by @paulwouters
I personally don't like the underscored words in the html rendering of the document
It "blank" the new American spelling of "blanc" ?
I find "summarizes" a strange word here. It is not the hash contains a summary one can read.
[SECG] has no IETF equivalent? Should it?
proposaland -> proposal and
I would say "after removing member C" (avoid ambiguity about "every third")
I read this wrong the first way, the "," vanishes due to the unscores. Maybe: This section defines tree hashes, the next section defines parent hashes. Or alternatively, leave onlthe the first sentence in 8.8, then put the remainder and next section in two subsections (so 8.8.1 and 8.8.2)
Maybe: For example, a malicious group member could otherwise send
Maybe: to public keys whose private key was previously compromised.
This reads a little odd as "new groups" would have no history and thus no previous compromise.
The text was updated successfully, but these errors were encountered: