Return to List
Login to Post Comment
There are privacy issues with any UUID since they uniquely identifies something. :) Anyways, I will clarify this and also talk a bit about the privacy implications of reusing the printer-uuid value and recommend generating a new UUID that the Proxy uses to identify the combination of Proxy and Printer(s) since the Proxy may in fact do fan-out behind the scenes...
The Proxy registers an Output Device with the Infrastructure Printer using the Update-Output-Device-Attributes operation, specifying a UUID for that Output Device using the "output-device-uuid" operation attribute. Subsequent operations performed by the Proxy on behalf of that Output Device will need to specify that same "output-device-uuid". The above details are not clearly articulated to the reader / implementer. This should be more clearly described. Additionally, where this UUID comes from or should come from is also not specified clearly. It could be that the Proxy reuses the value of the Output Device's "printer-uuid" Printer Description attribute. While this might be useful for auditing purposes, it also could violate privacy in some way. A better practice (that is followed in the current "ippproxy" code) is to generate a new UUID and specify that.