[Desktop_printing] Usability: Printing roles, tasks and envir onments

McDonald, Ira imcdonald at sharplabs.com
Wed Mar 8 10:20:15 PST 2006


Hi Ellen,

_All_ humans who interact with computers (in any role) are
"users" (per the OSI Model).  IETF IPP/1.1 (RFC 2911) and
all subsequent IETF and PWG printing standards use the term
"end user" to distinguish the "unprivileged user".  And the
term "job owner" to distinguish the "end user" who submitted
a particular print job (and therefore has the right to invoke
Cancel-Job, which is NOT available to an "end user" who is 
not the "job owner").

For the activities performed by the three IPP roles (end user,
operator, and administrator), see IETF Design Goals for an 
Internet Printing Protocol (RFC 2567).  Here's the table of 
contents:

   1. INTRODUCTION.....................................................4
   2. TERMINOLOGY......................................................4
   3. DESIGN GOALS.....................................................6
   3.1. End-user.......................................................6
   3.1.1. Finding or locating a printer................................6
   3.1.2. Create an instance of the printer............................7
   3.1.3. Viewing the status and capabilities of a printer.............7
   3.1.4. Submitting a print job.......................................8
   3.1.5. Viewing the status of a submitted print job..................9
   3.1.6. Canceling a Print Job........................................9
   3.2. Operator (NOT REQUIRED FOR V1.0)...............................9
   3.2.1. Alerting.....................................................9
   3.2.2. Changing Print and Job Status...............................10
   3.3. Administrator (NOT REQUIRED FOR v1.0).........................10
   4. OBJECTIVES OF THE PROTOCOL......................................10
   4.1. SECURITY CONSIDERATIONS.......................................11
   4.2. Interaction with LPD (RFC1179)................................12
   4.3. Extensibility.................................................12
   4.4. Firewalls.....................................................13
   4.5. Internationalization..........................................13
   5. IPP SCENARIOS...................................................13
   5.1. Printer Discovery.............................................14
   5.2. Driver Installation...........................................15
   5.3. Submitting a Print Job........................................15
   5.4. Getting Status/Capabilities...................................16
   5.5. Asynchronous Notification.....................................17
   5.6. Job Canceling.................................................17
   6. Security Considerations.........................................18
   7. REFERENCES......................................................18
   8. ACKNOWLEDGMENTS.................................................19
   9. AUTHOR'S ADDRESS................................................19
   10. APPENDIX - DETAILED SCENARIOS..................................20
   10.1. Printer discovery within an enterprise.......................20
   10.2. Printer discovery across enterprises.........................21
   10.3. Printer discovery on the Internet -logical operations........21
   10.4. Printer discovery on the Internet - authentication...........22
   10.5. Driver Download..............................................23
   10.6. Submitting a print job as a file.............................24
   10.7. Submitting a print job with two documents....................24
   10.8. Submitting a print job as a file, printing fails.............25
   10.9. Submitting a print job with authentication, PRIVACY and
         payment......................................................26
   10.10. Submitting a print job with decryption error................27
   10.11. Submitting a print job with authentication..................28
   10.12. Submitting a print job generated dynamically................29
   10.13. Submitting a print job with a Printer jam - CANCELED........29

Note - Please do not modify significantly definitions of the printer
user roles specified in Printer MIB and IPP - this will simply add
confusion for implementors and end users.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com

> -----Original Message-----
> From: desktop_printing-bounces at lists.osdl.org
> [mailto:desktop_printing-bounces at lists.osdl.org]On Behalf Of Ellen
> Reitmayr
> Sent: Tuesday, March 07, 2006 8:01 AM
> To: desktop_printing at osdl.org
> Subject: [Desktop_printing] Usability: Printing roles, tasks and
> environments
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Hi,
> 
> I've just gone through the printing roles as stated in RFC 3805. The
> information in the beginning of the document was very useful to get an
> idea of how printers work, and seeing the roles being split 
> into single
> units was also a valuable information. After all, a home user needs to
> take these roles over by himself!
> 
> Trying to reduce the complexity of the roles, I formed these
> (preliminary) task-related groups:
> 
> 1. Installing
> Printer identification and localisation, DTD selection, local system
> configuaration, printer configuration
> 
> 2. Configuring
> Settings, Properties, Defaults - may be changed on demand.
> 
> 3. Printing
> Job submission and removal, job status, capabilities, current 
> settings ...
> 
> 4. Printer Feedback
> Job status, event notivication, alerts, consumables, print job
> identification, printer status, printer identification, ...
> 
> 
> The complexity of each of these groups is highly dependent on the
> printer model and its capabilites, but also of the tasks the 
> user wants
> to accomplish with the printer, and the environment (distributed roles
> versus joined roles).
> 
> 
> Questions that popped up so far:
> 
> - - What tasks do we want to address in the meeting? Is 
> installation an
> issue, or will that further on be handled by the distributions?
> 
> - - What is the scope of configuration options? Could you 
> provide examples
> of the configuration options for a very basic printer, two or three
> intermediate ones, and one or two high-end machines?
> 
> - - Is there more information of possible alerts and event 
> notifications?
> 
> - - Are alert codes standardised between manufacturers so the 
> equal error
> messages can be provided, or are there differences?
> 
> - - Are there more roles that need to be considered? For example, is
> Raymond's Aunt Tillie a combination of some of the existing roles
> (having less knowledge, though), or are there roles that haven't been
> considered so far?
> 
> 
> Cheers,
> /el
> 
> 
> - --
> 
> ______________________________________________________
> 
> Ellen Reitmayr          email: reitmayr at relevantive.de
> Usability Engineer      mobil: +49.177.3325867
> relevantive AG          fon:   +49.30.23455630
> Saarbruecker Str. 38    fax:   +49.30.23455639
> 10405 Berlin            web:   www.relevantive.de
> _______________________________________________________
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFEDYQB2mIgQiX+cvcRAvj9AKCgsND7hNFPbbZThm76gfDTUwbpvACbBgvw
> wKE20Hj2HlGmwyjhGA0a92g=
> =d6Sk
> -----END PGP SIGNATURE-----
> _______________________________________________
> Desktop_printing mailing list
> Desktop_printing at lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/desktop_printing
> 



More information about the Printing-summit mailing list