From 0ba2503cab57a81a733ee2d1feee9c2d5dcea4f9 Mon Sep 17 00:00:00 2001 From: Franziskus Kiefer Date: Thu, 7 Nov 2024 19:25:28 +0100 Subject: [PATCH] Fixing a few typos in the book --- book/src/user_manual/credential_validation.md | 9 ++++----- book/src/user_manual/custom_proposals.md | 2 +- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/book/src/user_manual/credential_validation.md b/book/src/user_manual/credential_validation.md index 65ef99acd0..4fcde1f28a 100644 --- a/book/src/user_manual/credential_validation.md +++ b/book/src/user_manual/credential_validation.md @@ -1,12 +1,11 @@ # Credential validation Credential validation is a process that allows a member to verify the validity -of the credentials of other members in the group. The process is described in -detail in the [MLS protocol -specification](https://messaginglayersecurity.rocks/mls-protocol/draft-ietf-mls-protocol.html#name-credential-validation). +of the credentials of other members in the group. The process is described in +detail in the [MLS protocol specification](https://www.rfc-editor.org/rfc/rfc9420.html#name-credential-validation). In practice, the application should check the validity of the credentials of other members in two instances: - - When joining a new group (by looking at the ratchet tree) - - When [processing messages](./processing.md) (by looking at a add & update proposals of a StagedCommit) \ No newline at end of file +- When joining a new group (by looking at the ratchet tree) +- When [processing messages](./processing.md) (by looking at a add & update proposals of a StagedCommit) \ No newline at end of file diff --git a/book/src/user_manual/custom_proposals.md b/book/src/user_manual/custom_proposals.md index 4611ca7dba..d421ab60fd 100644 --- a/book/src/user_manual/custom_proposals.md +++ b/book/src/user_manual/custom_proposals.md @@ -2,7 +2,7 @@ OpenMLS allows the creation and use of application-defined proposals. To create such a proposal, the application needs to define a Proposal Type in such a way that its value doesn't collide with any Proposal Types defined in Section 17.4. of RFC 9420. If the proposal is meant to be used only inside of a particular application, the value of the Proposal Type is recommended to be in the range between `0xF000` and `0xFFFF`, as that range is reserved for private use. -Custom proposals can contain arbitrary octet-strings as defined by the application. Any policy decisions based on custom proposals will have to be made by the application, such as the decision to include a given custom proposal in a commit, or whether to accept a commit that includes one or more custom proposals. To decide the latter, applications can inspect the queued proposals in a `ProcessedMessageContent::StagedCommitMesage(staged_commit)`. +Custom proposals can contain arbitrary octet-strings as defined by the application. Any policy decisions based on custom proposals will have to be made by the application, such as the decision to include a given custom proposal in a commit, or whether to accept a commit that includes one or more custom proposals. To decide the latter, applications can inspect the queued proposals in a `ProcessedMessageContent::StagedCommitMessage(staged_commit)`. Example on how to use custom proposals: