Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify references to KEM definition and genm/genp usage in Section 5.1.3.4 #36

Closed
wants to merge 2 commits into from
Closed

Clarify references to KEM definition and genm/genp usage in Section 5.1.3.4 #36

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a11372e
Move reference to KEM definitions to the beginning of section
kiron-mx Oct 20, 2023
8e9de5f
Add reference to genm/genp data structure for its use with KEM
kiron-mx Oct 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions draft-ietf-lamps-rfc4210bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1728,6 +1728,8 @@ digital signature MAY be one of the options described in CMP Algorithms Section
{: id="sect-5.1.3.4"}


This approach uses the definition of Key Encapsulation Mechanism (KEM) algorithm functions in {{I-D.ietf-lamps-cms-kemri, Section 1}}.

In case the sender of a message has a KEM key pair, it can use a shared secret key obtained by KEM decapsulation of a ciphertext received using its private KEM key.

Note: In this section both entities in the communication need to send and receive messages. For ease of explanation we use the term "Alice" to denote the entity possessing the KEM key pair and who wishes to authenticate messages sent, and "Bob" to denote the entity who needs to authenticate the messages received.
Expand Down Expand Up @@ -1755,16 +1757,14 @@ mac is the algorithm identifier of the chosen MAC algorithm, and any associated

The KDF and MAC algorithms MAY be chosen from the options in CMP Algorithms [RFCCCCC].

This approach uses the definition of Key Encapsulation Mechanism (KEM) algorithm functions in {{I-D.ietf-lamps-cms-kemri, Section 1}}.

The InfoTypeAndValue transferring the KEM ciphertext is of type id-it-KemCiphertextInfo, which is defined in this document as:

~~~~ asn.1
id-it-KemCiphertextInfo OBJECT IDENTIFIER ::= { id-it TBD1 }
KemCiphertextInfoValue :== KemCiphertextInfo
~~~~

Note: This InfoTypeAndValue can be carried in a genm/genp message body or in the generalInfo field of PKIHeader in messages of other types.
Note: This InfoTypeAndValue can be carried in a genm/genp message body as specified in {{sect-5.3.19}} or in the generalInfo field of PKIHeader in messages of other types.

When id-it-KemCiphertextInfo is used, the value is either absent or of type KemCiphertextInfo. The syntax for KemCiphertextInfo is as follows:

Expand Down