Original text:
generate and publish multiple ClientInitKey objects to support multiple ciphersuites, or to reduce the likelihood of init key reuse. ClientInitKeys contain an identifier chosen by the client, which the <del> client MUST assure uniquely identifies a given ClientInitKey object </del>  among the set of ClientInitKeys created by this client. The value for init_key MUST be a public key for the asymmetric 8. Handshake and application messages use a common framing structure. <del> This framing provides encryption to assure confidentiality within the </del>  group, as well as signing to authenticate the sender within the group. messages encoded as MLSPlaintext objects in cases where it is necessary for the delivery service to examine such messages. <del> The remainder of this section describe how to compute the signature </del>  of an MLSPlaintext object and how to convert it to an MLSCiphertext object.  The overall process is as follows:

Reviewer comments:
I don't like the pattern of having a marker byte followed by zero-padding. It has to be parsed manually, backwards, unlike every other object in the protocol which all follow a common format.
Agreement at the interim was that people don't care about the overhead (for now), so we're going to go with the simpler, TLS-syntax-based structure.
Here's the Weekly Digest for : - - Last week 18 issues were created. Of these, 3 issues have been closed and 15 issues are still open. :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :greenheart: , by :heart: , by :heart: , by :heart: , by :speaker: , by It received 5 comments. - - Last week, 10 pull requests were created, updated or merged. Last week, 1 pull request was opened. :greenheart: , by Last week, 7 pull requests were updated. :yellowheart: , by :yellowheart: , by :yellowheart: , by :yellowheart: , by :yellowheart: , by :yellowheart: , by :yellowheart: , by Last week, 2 pull requests were merged. :purpleheart: , by :purpleheart: , by - - Last week there were 4 commits. :hammerandwrench: by :hammerandwrench: by :hammerandwrench: by :hammerandwrench: by - - Last week there were 4 contributors. :bustinsilhouette: :bustinsilhouette: :bustinsilhouette: :bustin_silhouette: - - Last week there were no stargazers. - - Last week there were no releases. - - That's all for last week, please :eyes: Watch and :star: Star the repository to receive next weekly updates. :smiley: You can also .

Revised text:
generate and publish multiple ClientInitKey objects to support multiple ciphersuites, or to reduce the likelihood of init key reuse. ClientInitKeys contain an identifier chosen by the client, which the  <ins> client MUST ensure uniquely identifies a given ClientInitKey object </ins> among the set of ClientInitKeys created by this client. The value for init_key MUST be a public key for the asymmetric 8. Handshake and application messages use a common framing structure.  <ins> This framing provides encryption to ensure confidentiality within the </ins> group, as well as signing to authenticate the sender within the group. messages encoded as MLSPlaintext objects in cases where it is necessary for the delivery service to examine such messages.  <ins> The remainder of this section describes how to compute the signature </ins> of an MLSPlaintext object and how to convert it to an MLSCiphertext object.  The overall process is as follows: