Greetings,
After the F2F meetings on Wednesday in El Segundo, I chatted with Joe Murdock for a few minutes about the overlap between this and what the IDS WG has been up to. At the moment, for some reason my instinct is to try to identify an appropriate MIME Media Type, if one exists, that has a header that encapsulates information on the format and any metadata, as well as the encrypted payload (if the payload is present). A document format that encapsulates all this information would allow the encrypted document to more easily traverse complex print system topologies that may contain mixtures of IPP and non-IPP transports, without requiring transcoding of the metadata at each hop.
However, IF it is decided that that is an inappropriate direction in which to proceed, I was looking in JPS1 (5100.7) and found the “document-format-details” attribute, which is a collection of various things including attributes to describe a digital signature. If we were to pursue describing this information via IPP attributes, extending this attribute’s “members” might be the right place to capture such information.
Please share your thoughts!
Cheers,
Smith
/**
Smith Kennedy
Hewlett-Packard Co.
*/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20150208/5672ce8e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4956 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20150208/5672ce8e/attachment.p7s>