IPP Mail Archive: IPP> Re: Stick to job submission and job mgmt, not printer mgmt

IPP Mail Archive: IPP> Re: Stick to job submission and job mgmt, not printer mgmt

IPP> Re: Stick to job submission and job mgmt, not printer mgmt

kugler@us.ibm.com
Thu, 24 Jun 1999 10:46:02 -0600

Peter-

Why didn't you raise this objection back when Microsoft introduced the
Pause-Printer, Resume-Printer, and Purge-Jobs operations? Are you suggesting
that we should pull those operations out of IPP/1.1?

-Carl

PETER_E_MELLQUIST@hp-roseville-om3.om.hp.com on 06/23/99 08:15:17 PM

To: ipp@pwg.org, Carl Kugler/Boulder/IBM@IBMUS
cc: Claudia Alimpich/Boulder/IBM@IBMUS, hastings@cp10.es.xerox.com, Jeffrey
Longstaff/Boulder/IBM@IBMUS
Subject: Stick to job submission and job mgmt, not printer mgmt

I believe that job submission and job management are clearly features in which
IPP is targeted for, but it seems IPP has crossed into the printer management
space with attributes like "Shutdown-Printer". I firmly believe that we do no
need Yet Another Management Protocol (YAMP). We already have SNMP, DMI,
WBEM/CIM and embedded web, and don't need another way of performing printer
management functions with a protocol designed for job submission and job
management. I would therefore recommend to leave out the following attributes
as well as those which are not focused on job submission or job management.
have to be dealt with.

Shutdown-Printer
Enable-Printer
Disable-Printer

Being that IPP is an IETF protocol and SNMP is THE management protocol within
the IETF, my bet the IETF / IESG folks would not like to see another management
protocol proliferate here.

Stick to job submission and job mgmt, not printer mgmt

Peter Mellquist
Hewlett-Packard Company

-----Original Message-----
From: Non-HP-kugler /HP-Roseville,mimegw4/dd.HPMEXT1=kugler@us.ibm.com
Sent: Wednesday, June 23, 1999 9:23 AM
To: Non-HP-ipp /HP-Roseville,mimegw4/dd.HPMEXT1=ipp@pwg.org
Cc: Non-HP-kugler /HP-Roseville,mimegw4/dd.HPMEXT1=kugler@us.ibm.com;
Non-HP-hastings /HP-Roseville,mimegw4/dd.HPMEXT1=hastings@cp10.es.xerox.com;
Non-HP-alimpich /HP-Roseville,mimegw4/dd.HPMEXT1=alimpich@us.ibm.com;
Non-HP-longstaf /HP-Roseville,mimegw4/dd.HPMEXT1=longstaf@us.ibm.com
Subject: Re: IPP> MOD - comments on Carl's Set and Admin operations
registration pr

We'd like to make a few more changes to the proposal.

1) Add the "message" attribute to the request operation attribute group for
these operations:

Set-Job-Attributes
Set-Printer-Attributes
Cancel-Current-Job
Shutdown-Printer
Enable-Printer
Disable-Printer

"message" (text(127)):
The client OPTIONALLY supplies this attribute. The Printer object
OPTIONALLY supports this attribute. It is a message to the operator. This
"message" attribute is not the same as the "job-message-from-operator"
attribute. That attribute is used to report a message from the operator to
the end user that queries that attribute. This "message" operation
attribute is used to send a message from the client to the operator along
with the operation request. It is an implementation decision of how or
where to display this message to the operator (if at all).

2) Rename "Backspace-Current-Job" to "Space-Current-Job" and add these OPTIONAL
request operation attributes:

"back-space" (integer(1:MAX)) the number of impressions to backspace before
continuing to print.
"forward-space" (integer(1:MAX)) the number of impressions to forward space
before continuing to print.
"non-process-run-out" (boolean) specifies whether the printer should perform an
NPRO (move the last printed sheet to the stacker) before restarting printing.
An NPRO makes it easier to see exactly where the spacing took place.

Remove the previously proposed "job-impressions" operation attribute for this
operation.

3) Add the following OPTIONAL operation attributes to the Shutdown-Printer
request:
"non-process-run-out" (boolean) specifies whether the printer should perform an
NPRO (move the last printed sheet to the stacker) before shutting down.
"synchronize" (boolean) specifies whether to synchronize the checkpoint data for
the current job with the pages that have actually printed. If this attribute is
supported, a value of true implies that the Printer will be able to resume the
job at the point of synchronization when restarted.

?) Is Reprocess-Job just like Restart-Job except that new "job-id" and "job-uri"
are generated?

-Carl

<< File: Re_ IPP_ MOD - comments on Carl's Set and Admin operations
registration pr.TXT >>