Connected: An Internet Encyclopedia
RFC 1421 - 4.6.4.1 Recipient-ID Fields

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.4 Per-Recipient Encapsulated Header Fields
Prev: 4.6.4 Per-Recipient Encapsulated Header Fields
Next: 4.6.4.1.1 Recipient-ID-Asymmetric Field

### 4.6.4.1 Recipient-ID Fields

A Recipient-ID encapsulated header field identifies a recipient and provides the recipient's IK identification component. One Recipient-ID field is included for each of a message's named recipients. Section 5.2, Interchange Keys, discusses the semantics of the subfields and specifies the alphabet from which they are chosen. Recipient-ID subfields are delimited by the comma character (","), optionally followed by whitespace.

For the symmetric case, all "Recipient-ID-Symmetric:" fields are interpreted in the context of the most recent preceding "Originator- ID-Symmetric:" field. It is illegal for a "Recipient-ID-Symmetric:" field to occur in a header before the occurrence of a corresponding "Originator-ID-Symmetric:" field. For the asymmetric case, "Recipient-ID-Asymmetric:" fields are logically independent of a message's "Originator-ID-Asymmetric:" and "Originator-Certificate:" fields. "Recipient-ID-Asymmetric:" fields, and their associated "Key-Info:" fields, are included following a header's originator- oriented fields.

4.6.4.1.1 Recipient-ID-Asymmetric Field
4.6.4.1.2 Recipient-ID-Symmetric Field

Next: 4.6.4.1.1 Recipient-ID-Asymmetric Field

Connected: An Internet Encyclopedia
RFC 1421 - 4.6.4.1 Recipient-ID Fields