I would like to see the clarification of how client applications handle the LockBox. In section 8.1.1 of Plasma Service Trust Processing, which describes the XML request created by the client which is sent to the server prior to creating the email's CMS form, it states that the LockBox is a "base64 encoded Recipient Info structure", but in section 3, Encoding Recipient Info, of Plasma Service CMS Processing (the only place I see a sufficiently detailed description of encoding PLASMA RecipientInfo structures), it says "A recipient info structure as defined in this document MUST be created by a Plasma server and MUST NOT be created by client software". I can see the latter making sense in RecipientInfo structures returned by the server to the client, but not in the client request for the CMS token. The question remains then what is supposed to go into the LockBox in the sending client's CMS token XML request.
If it is the PLASMA-LockBox ASN.1 structure described in section 3.2 of Plasma Service CMS Processing, then more clarity is needed as to exactly what the client should send to the PLASMA server in a CMS token request (e.g. is it everything but the RecipientInfo blob in the PLASMA-LockBox structure?, if labels and recipient names are already specified in XML in the CMS token request, does/should the client really need to create label and NamedRecipient structures in the PLASMA-LockBox? (I suspect not)). Ed _______________________________________________ plasma mailing list [email protected] https://www.ietf.org/mailman/listinfo/plasma
