SendDocument: REF(http://ds.internic.org/pub/rfc/rfc1122.txt)
And that way I wouldn't have to suffer the time downloading the file
first to my machine, and then
PUSHing the document to the printer.
For this type of access, I don't think security is needed. For INTRAnet
printing, I pretty much agree
with Scott L. that it would be possible for printers to authenticate
themselves with a document
repository, because the domain of usage (departmental or company
divisional) would be small enough
to deal with.
Randy
Scott Lawrence wrote:
> >>>>> "RKD" == Roger K Debry <rdebry@us.ibm.com> writes:
>
> RKD> They want to make these accessible to anyone
> RKD> within their organization (no security requirements).
> RKD> [...] The printer gets the file and prints it.
>
> RKD> [...]
> RKD> The two conditions required are that the document be in a
> RKD> standard printable format and that the document be publicaly
> RKD> available.
>
> It doesn't seem to me that the exemption from ordinary security is
> really required. It is quite possible to give printers or print
> servers identities in order to support authentication and
> authorization functions; the document repository can then just
> decide whether or not a given document can be printed on the
> authority of a given printer (that is, the printer has access rights
>
> just as a user does).
>
> Granted, one would want to look at how secure the printer is before
> assigning it much access, but that is an issue for those using this
> model, not for the protocol.
>
> While I agree that the protocol should define the mechanism for the
> sort of print by reference you describe, I don't think that it
> should be a required part (that is it is a feature that may or may
> not be available from a conforming IPP server).
>
> --
> Scott Lawrence EmWeb Embedded Server
> <lawrence@agranat.com>
> Agranat Systems, Inc. Engineering
> http://www.agranat.com/