I think it would be a mistake to ignore printer driver installation for
internet printing.
1) IPP must meet the customers needs or it will not be used.
2) We must specify how internet printing will function.
3) Many users print from applications. Applications require print drivers.
4) Print drivers are printer specific and should be associated with
the device. This
would simplify site specific printer modifications.
5) IPP is intended for the internet. Printers should be able to
provide there own drivers
in this widely distributed environment.
6) Print driver installation should work in complex(multiple domains,
firewalls,
many printers etc) and simple(no directory service, 1 simple printer)
networks.
7) Solution should work with legacy drivers as well as next generation
IPP aware drivers.
8) Print driver installation process should be left up to venders.
IPP should specify how the
installation method will be located and invoked.
9) A user should be able to intervene to circumvent automatic print
driver installation. The
user will have to live with the results. We should not prevent a
user from using
an generic driver with an IPP printer if that is the users choice.
We should discuss, but not specify, how the IPP redirector, provider,
or library will be hooked into the print path or client utilities.
1) We will have "mapping" documents to address IPP over specific protocols.
2) IPP redirector, provider, or library installation will be platform
specific.
3) The print driver can communicate directly via IPP to the printer or can use
standard platform specific mechanisms to transfer the PDL stream.
4) IPP services must be installed on the client before IPP can be used
directly.
__________________________________
> 1. Printer Discovery
>
> 1.1 List printers by selected criteria
> 1.2 Display the capabilities of a printer
PJZ> 1.3 discovery by reference(URL of TCP address)
PJZ> 1.4 display of current site specific configuration
>
> 2. Driver Installation
>
> 2.1 Install support for a target printer
> 2.2 Uninstall support for a target printer
PJZ> 2.3 check current driver version
PJZ> 2.4 accommodate IPP aware or legacy drivers
>
> 3. Job Submission
>
> 3.1 Print the current web page
> 3.2 Print a specified URL
> 3.3 Select job parameters
PJZ> 3.4 print from application
PJZ> 3.5 print long job
>
> 4. Status Display
>
> 4.1 View the status of a printer
> 4.2 View the status of a job or set of jobs
> 4.3 Receive notification of a printer alert
> 4.4 Receive notification of job completion
>
> 5. Job Modification
>
> 5.1 Modify one or more parameters of a job
PJZ> NOTE: until IPP aware drivers are available late binding
PJZ> of job instructions is not very robust.
> 5.2 Cancel a job
>
>Note that, unlike the top level of the outline, there is no particular
>rationale for the order of the elements at the second level of the
>outline.
>
>Is this outline useful as a basis from which all scenarios are to
>be derived?
>
> ...jay
>
>PS: The astute reader may realize that a particular set of features
> have been omitted from this outline. Should this omission prove
> inappropriate, we can always add it to the outline.
>
>----------------------------------------------------------------------
>-- JK Martin | Email: jkm@underscore.com --
>-- Underscore, Inc. | Voice: (603) 889-7000 --
>-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
>-- Hudson, NH 03015-4915 | Web: http://www.underscore.com --
>----------------------------------------------------------------------
>
----- End Included Message -----