Connected: An Internet Encyclopedia
RFC 1421 - 4.6.2.3 MIC-Info Field

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1421
Up: 4. Processing of Messages
Up: 4.6 Summary of Encapsulated Header Fields
Up: 4.6.2 Encapsulated Header Fields Normally Per-Message
Prev: 4.6.2.2 Originator-Certificate Field
Next: 4.6.3 Encapsulated Header Fields with Variable Occurrences

### 4.6.2.3 MIC-Info Field

The "MIC-Info:" encapsulated header field, used only when asymmetric key management is employed for at least one recipient of a message, carries three arguments, separated by commas. The first argument identifies the algorithm under which the accompanying MIC is computed. The second argument identifies the algorithm under which the accompanying MIC is signed. The third argument represents a MIC signed with an originator's private key.

For the case of ENCRYPTED PEM messages, the signed MIC is, in turn, symmetrically encrypted using the same DEK, algorithm, mode and cryptographic parameters as are used to encrypt the message's encapsulated text. This measure prevents unauthorized recipients from determining whether an intercepted message corresponds to a predetermined plaintext value.

Appropriate MIC algorithms and identifiers, signature algorithms and identifiers, and signed MIC formats are defined in RFC 1423.

A "MIC-Info:" field will occur after a sequence of fields beginning with a "Originator-ID-Asymmetric:" or "Originator-Certificate:" field and followed by any associated "Issuer-Certificate:" fields. A "MIC-Info:" field applies to all subsequent recipients for whom asymmetric key management is used, until and unless overridden by a subsequent "Originator-ID-Asymmetric:" or "Originator-Certificate:" and corresponding "MIC-Info:".

Next: 4.6.3 Encapsulated Header Fields with Variable Occurrences

Connected: An Internet Encyclopedia
RFC 1421 - 4.6.2.3 MIC-Info Field