generated from martinthomson/internet-draft-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
11fede3
commit a004c55
Showing
1 changed file
with
4 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,8 +35,8 @@ author: | |
organization: "Naval Postgraduate School" | ||
email: [email protected] | ||
- ins: "M. Mularczyk" | ||
name: "Marta Mularczyk" | ||
organization: "AWS" | ||
name: "Marta Mularczyk" | ||
organization: "AWS" | ||
email: [email protected] | ||
- ins: "X. Tian" | ||
name: "Xisen Tian" | ||
|
@@ -179,7 +179,7 @@ User leaf nodes are first added to the PQ session following the sequence describ | |
| | | Commit'(Add'(KeyPackageB')) | | ||
| | | Commit(Add(KeyPackageB), PreSharedKeyID) | | ||
|<----------------------------------------------------------------------------------------------------+ | ||
|
||
Figure 2: | ||
Client A adds client B to the group. | ||
Messages with ' come from the PQ session. Processing Welcome and Commit in the traditional | ||
|
@@ -204,8 +204,7 @@ HPQMLS combiner provides PQ security to the traditional MLS session. Application | |
|
||
# Modes of Operation | ||
|
||
Security needs vary by organizations and system-specific risk tolerance and/or constraints. While this combiner protocol targets combining a PQ session and a traditional session the degree of PQ security may be tuned depending on the use-case: i.e., as PQ/T Confidentiality Only or both PQ/T Confidentiality and PQ/T Authenticity. For PQ/T Confidentiality Only, the PQ session MUST use a PQ KEM, while for PQ authenticity, the PQ session MUST use both a PQ KEM and a PQ DSA. | ||
The modes of operation are specified by the `mode` flag in HPQMLSInfo struct and are listed below. | ||
Security needs vary by organizations and system-specific risk tolerance and/or constraints. While this combiner protocol targets combining a PQ session and a traditional session the degree of PQ security may be tuned depending on the use-case: i.e., as PQ/T Confidentiality Only or both PQ/T Confidentiality and PQ/T Authenticity. For PQ/T Confidentiality Only, the PQ session MUST use a PQ KEM, while for PQ authenticity, the PQ session MUST use both a PQ KEM and a PQ DSA. The modes of operation are specified by the `mode` flag in HPQMLSInfo struct and are listed below. | ||
|
||
## PQ/T Confidentiality Only | ||
|
||
|