Greetings,
Given the following scenario:
An IPP Printer has reported via Get-Printer-Attributes:
"job-password-supported" = 32
"job-password-encryption-supported" = 'none', 'md5'
(going to ignore "job-password-repertoire-configured" and "job-password-length-supported" for now...)
An IPP Client acquires from the User a job password "beeblebrox"
If the Client chooses 'none', then it should send in a Validate-Job operation
"job-password-encryption" = 'none'
"job-password" = 'beeblebrox'
However, if the Client chooses 'md5', how does it encode the md5 hash octets? Does it encode it as hex-ascii in 32 octets like so?
"job-password-encryption" = 'none'
"job-password" = '3f73fde3af41b6a50c84a75f84892b85'
Or since 'job-password' is defined in 5100.11 as "job-password (octetString(255))", is it reasonable for it to provide the raw binary value? I cannot find any statement in PWG 5100.11, RFC 8010, or wp-job-password-repertoire-20160101.pdf that makes this clear. Is the Printer expected to handle both scenarios?
Thoughts?
Smith
/**
Smith Kennedy
Wireless Architect - Client Software - IPG-PPS
Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF
Chair, IEEE ISTO Printer Working Group
HP Inc.
*/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170421/bd968b27/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4241 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170421/bd968b27/attachment.p7s>