IPP Mail Archive: IPP> Identifying jobs in requests

IPP Mail Archive: IPP> Identifying jobs in requests

IPP> Identifying jobs in requests

Paul Moore (paulmo@microsoft.com)
Thu, 4 Jun 1998 10:58:28 -0700

It seem to me that the fundamental question comes down to - should
the IPP protocol form, transmit and use information that is specific to the
underlying transport.

We have chosen to use URI as our way of identifying endpoints. The
assumptions we make about these URIs (there actual syntax is irrelevant)
are:-
a) an agent knows how to form them
b) the only thing an agent may do with a URI it receives to it is to
pass it to its underlying transport. This means that the creator of the URI
MUST use the same URI forming convention as that which will be used by the
receivers transport stack (ie. this is not a private issue for a given
implementation). It also means that the receiver may not look at the URI to
infer any deeper meaning (because that is a private issue for the sending
implementation).
This last restriction made us invent job-id. We moved to explicitly
stating in IPP the way of identifying an endpoint.
The real problem is that we end up with leakage from the transport
up into the IPP layer. I cannot blindly forward requests from
IPP-on-protocolX to IPP-on-protocolY. I have to find all the URIs and change
them on the fly.
There is another problem that assumpion b causes. It assumes that a
printer knows how to form an address (URI) that makes sense in the clients
transport stack. This is true for HTTP but not true (or certainly
non-trivial) for other transports.

I would propose that we use an adressing scheme that corresponds to
the transport endpoint only. We then specifiy in IPP the ways of identifying
the logical object that we wish to talk to (printer-ID, Job-ID,...).