Although I agree that the answer is conceptually yes, it's yucky from the
point of view of attributes like "operations-supported".
Which is why I suggest we rule it out and say that an SCS has an endpoint
in an IPP System new first-class object (available ONLY to an Operator or
Administrator and never to an End User). That actually matches the SM
definition of SCS much more faithfully and simplifies counter and diagnostic
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
mailto: blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Tue, Jan 14, 2014 at 3:13 PM, Michael Sweet <msweet at apple.com> wrote:
>> On Jan 14, 2014, at 3:03 PM, Ira McDonald <blueroofmusic at gmail.com> wrote:
> So, a question. Can an implementation of SCS (at some "ipp/ipps"
> URI endpoint) also accept Print commands at the same endpoint?
> I suggest yes, but could be argued out of this. It partly has to do with
> finding roll-up usage counters for all service instances from the SCS
> somewhere on an IPP system.
>>> Conceptually yes, although we would need to very carefully define this
> since ordinary users normally do not have access to the System Control
> Service, and you would need to define (or be able to define) the
> subordinate service that would receive the print jobs - this is especially
> important for systems with multiple marking engines (generally anything
> like CUPS).
> Michael Sweet, Senior Printing System Engineer, PWG Chair