Development of print clients and print servers that are compliant with
the developing ECMA and ISO Print Service standards.  

These clients
and servers should be implemented for BSD 4.2, but be easily ported
to System V.  

They should be developed for layering on a respected
industry RPC system (e.g. SUN or Apollo).  

The implementations should
be backwards interwork-compatible with existing BSD 4.x and System
V print systems.

The implementations should
support development of clients and servers that are forward compatible
with future revisions of these components.

Name to address mapping should be implemented by the client before
invoking the RPC bind mechanism.  (This ensures that the client
can use the Name Service of choice and remain independent of
any name service supported by the RPC system.)

Allow different Name Service implementations to be used.
[Either at source-code level, build-level or configuration-level.]

Allow different Authentication Service implementations to be used.
[Either at source-code level, build-level or configuration-level.]

Allow different Authorization Service implementations to be used.
[Either at source-code level, build-level or configuration-level.]

Allow different Accounting Service implementations to be used.
[Either at source-code level, build-level or configuration-level.]

Allow different Notification Service implementations to be used.
[Either at source-code level, build-level or configuration-level.]

Allow different Scheduling Algorithm implementations to be used.
[Either at source-code level, build-level or configuration-level.]

(Note that scheduling algorithms are outside the scope of these
requirements.  Scheduling, internal job DBs, printer queues, etc.
are implementation-specific concerns.)

Use existing scheduling algorithms, control files, interfaces, etc.
wherever possible and appropriate.

Should not require additional functional support at the workstation
(e.g. file transfer queuing,s taging, local job ids, etc.).

{Steal management requirements from original implementation
requirements.}


Support of ECMA management operations is an open issue.