INTERNET-DRAFT                                               T. Hastings
<draft-ietf-ipp-job-printer-set-ops-02.txt>
<draft-ietf-ipp-job-printer-set-ops-03.txt>                   R. Herriot
Category: standards track                              Xerox Corporation
                                                             Carl Kugler
                                                                H. Lewis
                                                         IBM Corporation
                                                          March 23, 2000
                                                        January 22, 2001

                     Internet Printing Protocol (IPP):
                      Job and Printer Set Operations

      Copyright (C) The Internet Society (2000). (2001). All Rights Reserved.

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of [RFC2026].  Internet-Drafts are
   working documents of the Internet Engineering Task Force (IETF), its
   areas, and its working groups.  Note that other groups may also
   distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress".

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt
   The list of Internet-Draft Shadow Directories can be accessed as
   http://www.ietf.org/shadow.html.

Abstract

   This document specifies 3 additional OPTIONAL operations for use with
   the Internet Printing Protocol/1.0 (IPP) [RFC2565, RFC2566], IPP/1.1
[ipp-mod, ipp-pro],
   [RFC2911, RFC2910], and future versions.  The end user, operator, and
   administrator Set-Job-Attributes and Set-Printer-Attributes
   operations are used to modify IPP Job objects and Printer objects,
   respectively.  The third administrator Get-Printer-Supported-Values
   operation returns values that the IPP Printer will accept for setting
   its "xxx-supported" attributes.

   Three out-of-band values are defined for use with these operations:
   'delete-attribute', 'admin-define', and 'not-settable', along with a
   'client-error-attributes-not-settable' status code.

   Two operation attributes:  "printer-message-from-operator" (text) and
   "job-message-from-operator" (text) are defined to set the
   corresponding IPP/1.1 Printer and Job Description attributes with the
   same names.

   Nine Printer Description attributes are defined:
     printer-settable-attributes-supported (1setOf type2 keyword)
     job-settable-attributes-supported (1setOf type2 keyword)
     document-format-varying-attributes (1setOf type2 keyword)
     printer-message-time (integer(MIN:MAX))
     printer-message-date-time (dateTime)

                     Expires:  September 23, 2000
     printer-xri-supported (1setOf collection)
     xri-uri-scheme-supported (1setOf uriScheme)
     xri-authentication-supported (1setOf type2 keyword)
     xri-security-supported (1setOf type2 keyword)

                     Expires:  September 23, 2000
   The full set of IPP documents includes:

   Design Goals for an Internet Printing Protocol [RFC2567]
   Rationale for the Structure and Model and Protocol for the Internet
   Printing Protocol [RFC2568]
   Internet Printing Protocol/1.1: Model and Semantics (this document) [RFC2911]
   Internet Printing Protocol/1.1: Encoding and Transport [IPP-PRO] [RFC2910]
   Internet Printing Protocol/1.1: Implementer's Guide [IPP-IIG]
   Mapping between LPD and IPP Protocols [RFC2569]

   The "Design Goals for an Internet Printing Protocol" document takes a
   broad look at distributed printing functionality, and it enumerates
   real-life scenarios that help to clarify the features that need to be
   included in a printing protocol for the Internet.  It identifies
   requirements for three types of users: end users, operators, and
   administrators.  It calls out a subset of end user requirements that
   are satisfied in IPP/1.0.  A few OPTIONAL operator operations have
   been added to IPP/1.1.

   The "Rationale for the Structure and Model and Protocol for the
   Internet Printing Protocol" document describes IPP from a high level
   view, defines a roadmap for the various documents that form the suite
   of IPP specification documents, and gives background and rationale
   for the IETF working group's major decisions.

   The "Internet Printing Protocol/1.1: Encoding and Transport" document
   is a formal mapping of the abstract operations and attributes defined
   in the model document onto HTTP/1.1 [RFC2616].  It defines the
   encoding rules for a new Internet MIME media type called
   "application/ipp".  This document also defines the rules for
   transporting over HTTP a message body whose Content-Type is
   "application/ipp".  This document defines a new scheme named 'ipp'
   for identifying IPP printers and jobs.

   The "Internet Printing Protocol/1.1: Implementer's Guide" document
   gives insight and advice to implementers of IPP clients and IPP
   objects.  It is intended to help them understand IPP/1.1 and some of
   the considerations that may assist them in the design of their client
   and/or IPP object implementations.  For example, a typical order of
   processing requests is given, including error checking.  Motivation
   for some of the specification decisions is also included.

   The "Mapping between LPD and IPP Protocols" document gives some
   advice to implementers of gateways between IPP and LPD (Line Printer
   Daemon) implementations.

                     Expires:  September 23, 2000

Table of Contents

   1  Introduction.....................................................7  Introduction....................................................8

   2  Terminology......................................................7  Terminology.....................................................8
   2.1   Conformance Terminology.......................................7 Terminology......................................9
   2.2   Other terminology.............................................8 terminology............................................9

   3  Requirements and Use Cases.......................................8 Cases......................................9

   4  Definition of the Set operations.................................9 operations...............................10
   4.1   Set-Printer-Attributes Operation..............................9 Operation............................11
   4.1.1   Settable and READ-ONLY Printer Description attributes....11 attributes.....13
   4.1.2   Set-Printer-Attributes Request...........................12 Request............................15
   4.1.3   Set-Printer-Attributes Response..........................13 Response...........................16
   4.2   Set-Job-Attributes Operation.................................15 Operation................................18
   4.2.1   Settable and READ-ONLY Job Description attributes........17 attributes.........21
   4.2.2   Set-Job-Attributes Request...............................17 Request................................21
   4.2.3   Set-Job-Attributes Response..............................18 Response...............................22
   4.3   Get-Printer-Supported-Values Operation.......................19 Operation......................24
   4.3.1   Definition of the usage of the 'admin-define' out-of-band
   attribute value..................................................20 value...................................................25

   5  New Operation attributes........................................21 attributes.......................................27
   5.1  "printer-message-from-operator" (text(127))..................22   printer-message-from-operator (text(127))...................27
   5.2  "job-message-from-operator" (text(127))......................23   job-message-from-operator (text(127)).......................28

   6  New Printer Description Attributes..............................24 Attributes.............................29
   6.1   printer-settable-attributes-supported (1setOf type2 keyword).24 keyword)29
   6.2   job-settable-attributes-supported (1setOf type2 keyword).....24 keyword)....30
   6.3   document-format-varying-attributes (1setOf type2 keyword)....24 keyword)...30
   6.4   printer-message-time (integer(MIN:MAX))......................25 (integer(MIN:MAX)).....................31
   6.5   printer-message-date-time (dateTime).........................25 (dateTime)........................31
   6.6   printer-xri-supported (1setOf collection)....................25 collection)...................32
   6.7   xri-uri-scheme-supported (1setOf uriScheme)..................27 uriScheme).................34
   6.8   xri-authentication-supported (1setOf type2 keyword)..........28 keyword).........35
   6.9   xri-security-supported (1setOf type2 keyword)................28 keyword)...............35

   7  Additional status codes.........................................28 codes........................................35
   7.1   'client-error-attributes-not-settable' (0x0413)..............28 (0x0413).............35

   8  Additional out-of-band values...................................29 values..................................36
   8.1   'not-settable' out-of-band value.............................29 value............................36
   8.1.1   Encoding of the 'not-settable' out-of-band attribute value29 value37
   8.2   'delete-attribute' out-of-band value.........................29 value........................37
   8.2.1   Encoding of the 'delete-attribute' out-of-band value.....30 value......37
   8.3   'admin-define' out-of-band attribute value...................30 value..................38
   8.3.1   Encoding of the 'admin-define' out-of-band attribute value31 value39
   9  Conformance Requirements........................................31 Requirements.......................................39

   10 IANA Considerations.............................................32

                     Expires:  September 23, 2000 Considerations............................................41
   10.1  Operation Registrations.....................................41
   10.2  Attribute Registrations.....................................41
   10.3  Status code Registrations...................................42
   10.4  Out-of-band Attribute Value Registrations...................42

   11 Internationalization Considerations.............................33 Considerations............................43

   12 Security Considerations.........................................33 Considerations........................................43

   13 Author's Addresses..............................................33 Addresses.............................................44

   14 References......................................................34 References.....................................................45

   15 Change History..................................................35
15.1 Changes to the March 21, 2000 version to make the March 23, 2000
version     35
15.2 Changes to the March 8, 2000 version to make the March 21, 2000
version     36
15.3 Changes to the March 1, 2000 version to make the March 8, 2000
version     37
15.4 Changes to the January 30, 2000 version to make the March 1, 2000
version     37
15.5 Changes to the January 20, 2000 version to make the January 30,
2000 version39
15.6 Changes to the January 4, 2000 version to make the January 20,
2000 version39
15.7 Changes to the December 8, 1999 version to make the January 4,
2000 version41

16 Appendix A: Allowed Values for Set-Printer-Attributes and Set-Job-
   Attributes requests................................................42

17 requests...............................................46

   16 Appendix B: Attributes returned from Get-Printer-Supported-Values47

18 Get-Printer-Supported-Values
      60

   17 Appendix C: Full Copyright Statement............................50 Statement...........................65

   Table of Tables

   Table 1 - Operation-Id assignments....................................9 assignments................................11
   Table 2 - Job State Transition Table for the Set-Job-Attributes
   operation........................................................16
      operation .....................................................20
   Table 3 - Member attributes of "printer-xri-supported" (1setOf
   collection)......................................................26
      collection) ...................................................33
   Table 4 - Validation rules for 'Any of "xxx-supported" '.............42 '..........47
   Table 5 - Validation rules for 'From Get-Printer-Supported-Values'...43 Get-Printer-Supported-Values'48
   Table 6 - Values allowed for Job Template Attributes in the Set-Job-
      Attributes Operation.............................................43 Operation ..........................................50
   Table 7 - Values allowed for Job Description Attributes in the Set-Job-
   Attributes Operation.............................................44 Set-
      Job-Attributes Operation ......................................52
   Table 8 - Values allowed for Printer Job Template Attributes in the Set-
   Printer-Attributes Operation.....................................45
      Set-Printer-Attributes Operation ..............................54
   Table 9 - Values allowed for Printer Description Attributes in the Set-
   Printer-Attributes Operation.....................................45
      Set-Printer-Attributes Operation ..............................57
   Table 10 - Printer Job Template Attributes returned from Get-Printer-
   Supported-Values.................................................48
      Supported-Values ..............................................61
   Table 11 - Printer Job Template Attributes returned from Get-Printer-
   Supported-Values.................................................48
      Supported-Values ..............................................61
   Table 12 - Printer Description Attributes returned from Get-Printer-
   Supported-Values.................................................48

                     Expires:  September 23, 2000
      Supported-Values ..............................................62
   Table 13 - Printer Job Template Attributes returned from Get-Printer-
   Supported-Values.................................................48
      Supported-Values ..............................................62
   Table 14 - Printer Job Template Attributes returned from Get-Printer-
   Supported-Values.................................................49
      Supported-Values ..............................................63
   Table 15 - Printer Description Attributes returned from Get-Printer-
   Supported-Values.................................................49

                     Expires:  September 23, 2000
      Supported-Values ..............................................64

1  Introduction

   The Internet Printing Protocol (IPP) is an application level protocol
   that can be used for distributed printing using Internet tools and
   technologies.  IPP version 1.1 [ipp-mod, ipp-pro] [RFC2911, RFC2910] focuses on end user
   functionality with a few administrative operations included.  This
   document defines additional OPTIONAL end user, operator, and
   administrator Set-Job-Attributes and Set-Printer-Attributes
   operations used to modify IPP Job objects and Printer objects,
   respectively.  It also defines a third administrator Get-Printer-Supported-Values Get-Printer-
   Supported-Values operation that returns values that the IPP Printer
   will accept for setting its "xxx-supported" attributes.  The Get-Printer-Supported-
Values Get-
   Printer-Supported-Values operation MUST be supported, if the
   implementation supports setting any "xxx-supported" Printer
   attributes using the Set-Printer-
Attributes Set-Printer-Attributes operation.

   Three out-of-band values are defined for use with these three
   operations:  'delete-attribute' for deleting Job attributes with the
   Set-Job-Attributes request, 'not-settable' for use in either the Set-
   Job-Attributes or Set-Printer-Attributes responses, and 'admin-define' 'admin-
   define' for use in the Get-Printer-Supported-Values response.

   Two operation attributes:  "printer-message-from-operator" (text) and
   "job-message-from-operator" (text) are defined to set the
   corresponding IPP/1.1 Printer and Job Description attributes with the
   same names.  These operation attributes may be used with any
   operation that affect the Printer or Job object for which an
   operation might want to indicate a message.  For the Set-Job-Attributes Set-Job-
   Attributes and Set-Printer-Attributes operations, the client MUST
   explicitly set them, rather than using these operation attributes.

   A Printer implementation can make the value of some attributes
   dependent on the document-format, e.g. "resolution-supported".

   This document is an extension to IPP/1.0 [RFC2565, RFC2566] and
   IPP/1.1
[ipp-mod, ipp-pro], [RFC2911, RFC2910], and future versions.

2  Terminology

   This section defines terminology used throughout this document.

2.1 Conformance Terminology

   Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
   NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
   conformance.  These terms are defined in [ipp-mod] [RFC2911] section 12.1 on
   conformance terminology, most of which is taken from RFC 2119
   [RFC2119].

   The following specialization of these terms apply to this document:

  REQUIRED: if an implementation supports the extensions described in
     this document, it MUST support a REQUIRED feature.

                     Expires:  September 23, 2000
  OPTIONAL: if an implementation supports the extensions described in
     this document, it MAY support an OPTIONAL feature.

2.2 Other terminology

   This document uses terms such as Job object (or Job), IPP Printer
   object (or Printer), "operation", "request", response", "attributes",
   "keywords", and "support".  These terms have special meaning and are
   defined in the model terminology [ipp-mod] [RFC2911] section 12.2.  The
   following additional terms are introduced in this document:

  READ-ONLY:  used in an attribute definition document to indicate that
     the attribute MUST NOT be settable using an IPP protocol Set
     operation.  In other words, the attribute is not settable by
     definition.
  not-settable:  an implementation does not support setting an
     attribute (whether or not the attribute's definition is READ-ONLY).

3  Requirements and Use Cases

   The following requirements and usage are intended to be met by the
   specification in this document.

1.The

  1. The end-user and the operator need a way to modify a Job that is in
     the 'pending' or 'pending-held' state.

     Usage:  The end-user discovers that he/she forgot to include a
     print instruction, such as "finishings" = 'staple' after submitting
     a job.  Rather than canceling the job and resubmitting it to the
     same IPP Printer, the end-user is able to modify the job on the IPP
     Printer.

     The operator needs to modify a job because it is requesting a
     particular kind of media for which there is no more, but the policy
     is to print the job on a comparable medium.

2.The

  2. The system administrator needs a way to re-configure or change the
     policy of the IPP Printer remotely.

     Usage:  The system administrator is adding additional named media
     to the supported media list (setting 'name' values to the "media-
     supported" Printer attribute).

     The system administrator is reducing the capability of the IPP
     Printer by removing one of the operations from the supported
     operations list, such as Cancel-Job, because the policy is to run
     the IPP Printer like a public facsimile machine.  After having
     removed Cancel-Job from the list of supported operations, an
     administrative client needs to be able to display to an
     administrator that the implementation is capable of being
     reconfigured to support Cancel-Job once again.

                     Expires:  September 23, 2000

     The system administrator is remotely configuring the IPP Printer
     after installing it, and so is replacing the Printer Description
     attributes that have the out-of-band 'no-value' value (see [ipp-mod]
     [RFC2911] section 4.1) with the proper values.

     The operator is changing the media loaded in the input tray and so
     is replacing the "media-ready" Job Template Printer attribute value
     with the proper values

4  Definition of the Set operations

   The Set-Printer-Attributes operation (as are all Printer operations)
   are directed at Printer objects.  A client MUST always supply the "printer-
uri"
   "printer-uri" operation attribute in order to identify the correct
   target of the operation.  These descriptions assume all of the common
   semantics of IPP/1.1 Model and Semantics document [ipp-mod] [RFC2911] section
   3.1.

   The Set-Job-Attributes operation (as are all Job operations) are
   directed at Job objects.  A client MUST always supply some means of
   identifying the Job object in order to identify the correct target of
   the operation.  That job identification MAY either be a single Job
   URI or a combination of a Printer URI with a Job ID as defined in [ipp-mod].
   [RFC2911].  The IPP object implementation MUST support both forms of
   identification for every job. If possible, a client SHOULD use the
   Printer URI with a Job ID rather than a Job URI, since the 32-bit
   "job-id" is more readily translated to and from other print protocols
   that MAY be serving as gateways into or out of the IPP
   implementation.

   The Set Printer operations are summarized in Table 1:

                    Table 1 - Operation-Id assignments

   Operation Name      Operation  Brief description
                       -Id

   Set-Printer-        0x0013     Sets attribute values of the target
   Attributes                     Printer object

   Set-Job-Attributes  0x0014     Sets attribute values of the target
                                  Job object

   Get-Printer-        0x0015     Gets values that are valid for
   Supported-Values               setting "xxx-supported" attributes
                                  using the Set-Printer-Attributes
                                  operation

4.1 Set-Printer-Attributes Operation

   This OPTIONAL operation allows a client to set the values of the
   attributes of a Printer object.   In the request, the client supplies
   the set of Printer keyword attribute names and values that are to be
   set.  In the response, the Printer object returns success or rejects
   the entire request with indications of which attribute or attributes
   could not be set.

                     Expires:  September 23, 2000

   The Printer object validates the client-supplied attributes in the Set-
Printer-Attributes
   Set-Printer-Attributes request.  For an attribute to validate it MUST
   meet all of the following rules:

  1. The number of attributes supplied by the client MUST NOT exceed the
     maximum number that the Printer supports in a Set-Printer-
     Attributes request.  A Printer MUST accept at least one attribute,
     but SHOULD accept a reasonable number in a single Set-Printer-
     Attributes request.

     Note:  There is no way for the client to determine the maximum
     number of attributes that the Printer supports in a Set-Printer-
     Attributes request, except to try a reasonable number.

  2. The Printer MUST support the attribute.

  3. The attribute MUST NOT be READ-ONLY, i.e., the definition of the
     attribute MUST NOT indicate that the attribute is READ-ONLY (see
     Appendix A for an indication of which IPP/1.1 attributes are READ-
     ONLY).

  4. The attribute MUST be settable in this implementation.

  5. The Printer MUST support the value according to the rules defined
     in Appendix A, i.e., each value of each supplied "xxx" attribute
     MUST be validated against a value of a corresponding "xxx-
     supported" Printer attribute.  One of those rules permits an
     administrator to set arbitrary 'name' values to those "xxx-
     supported" Printer attributes that include the 'name' attribute
     syntax if the implementation supports the 'admin-define' out-of-
     band value for that "xxx-supported" attribute (see section 0 15 and
     8.3).

  6. The attribute's values MUST NOT conflict with the values of other
     Printer attributes, including ones being set in this same
     operation.

   If any of the supplied attributes does not validate, the Printer
   object MUST reject the entire operation; the Printer object MUST NOT
   partially set some of the supplied attributes.  In other words, after
   the operation, all the supplied attributes MUST be set or none of
   them MUST be set, thus making the Set-Printer-Attributes an atomic
   operation.

   The Printer MUST accept this operation when its READ-ONLY "printer-
   state" attribute (see ipp-mod] RFC2911] section 4.4.11) is 'idle' or
   'stopped', and SHOULD accept it when the value is 'processing'.  The
   Printer MUST accept this operation for any of the values of the
   Printer object's READ-ONLY "printer-state-reasons" and "printer-is-accepting-jobs" "printer-is-
   accepting-jobs" attributes, unless explicitly defined otherwise in
   the definition of these attributes' values.

   This operation MUST NOT change the value of attributes not specified
   in the operation unless the definition of the attribute explicitly
   specifies such side-effects.  For example, this document explicitly

                     Expires:  September 23, 2000
   specifies that when this operation sets "printer-message-from-operator", "printer-message-from-
   operator", the Printer also MUST set the READ-ONLY "printer-message-time" "printer-message-
   time" and READ-
ONLY READ-ONLY "printer-message-date-time" attributes to the
   time of the operation as a side effect .  In particular, if this
   operation changes an "xxx-
default" "xxx-default" attribute, the new value MUST be
   in the "xxx-supported" attribute or the request MUST contain a new
   value for "xxx-supported" which contains the new value for the "xxx-default". "xxx-
   default".  Otherwise, the Printer MUST reject the operation.  In
   general, Printer attribute definitions that are settable will not
   define side-effects on other attributes that are settable, only side
   effects on READ-ONLY attributes, if any.

4.1.1Settable

4.1.1     Settable and READ-ONLY Printer Description attributes

   If the Printer supports the Set-Printer-Attributes operation, then it
   SHOULD support setting of:

     all Job Template Default ("xxx-default") attributes

     all Job Template Supported ("xxx-supported") attributes

     all Job Template Ready ("xxx-ready") attributes

   that the implementation supports (see [ipp-mod] [RFC2911] section 4.2 and
   extensions).

   Some Printer Description attributes (see [ipp-mod] [RFC2911] section 4.4) MUST
   NOT be settable, i.e., they are defined to be READ-ONLY.  An
   attribute marked as "READ-ONLY" in the Printer Description attribute
   table in Appendix A is such an attribute.  The Printer attributes
   that are not marked as "READ-ONLY" MAY be settable using the Set-Printer-Attributes Set-
   Printer-Attributes operation, depending on implementation.

   Note:  From now on, all extensions that define new object attributes
   will indicate whether or not the attributes are READ-ONLY, by
   including the "READ-ONLY" adjective in their descriptions and/or
   explicitly stating whether they MAY be settable.

   The current values of each "xxx-supported" Printer attribute MUST
   reflect the current policy for support of the corresponding "xxx"
   attribute.  If an "xxx-supported" Printer attribute is settable in an
   implementation, then its value(s) MUST affect the behavior of the
   implementation.  If an "xxx-supported" Printer attribute is defined
   to be READ-ONLY or is not-settable in an implementation, then its
   values MUST NOT be settable using the Set-Printer-Attributes
   operation.  Consider the following example:

     For example, if the "operations-supported" Printer Description
     attribute (see [ipp-mod] [RFC2911] section 4.4.15) is settable in a
     particular implementation, then changing its value with a Set-
     Printer-Attributes operation MUST affect the operations that the
     implementation accepts or rejects.  Such an implementation will
     need to be able to reject values for operations that it contains no
     code support for (see section 4.3).  If the "operations-supported"
     Printer Description attribute is not settable in a particular
     implementation, then that implementation MUST reject an attempt to

                     Expires:  September 23, 2000
     set it with a Set-Printer-Attributes operation, return the 'client-
     error-attributes-not-settable' status code (see section 7.1), and
     return the "operations-supported" attribute with the out-of-band
     'not-settable' value in the Unsupported Attributes Group.

     As another example, consider an implementation in which the "media-
     default" and "media-supported" are settable.  If a client supplies
     a Set-Printer-Attributes request that contains the "media-default"
     attribute with a value that is not a member of the Printer's
     "media-supported" attribute, the Printer MUST reject the request
     and return the "client-error-conflicting-attributes" status code
     with the "media-default" and "media-supported" attributes and their
     values (see [ipp-mod] [RFC2911] section 3.1.7).

     As a third example, if a client supplies a Set-Printer-Attributes
     request that contains both the "media-default" and the "media-
     supported" attributes, but includes a value in the "media-default"
     that is not a member of the supplied "media-supported" attribute,
     the Printer MUST reject the request and return the "client-error-
     conflicting-attributes" status code with the "media-default" and
     "media-supported" attributes and their values (see [ipp-mod] [RFC2911]
     section 3.1.7).

   Access Rights:  The authenticated user (see [ipp-mod] [RFC2911] section 8.3)
   performing this operation must be an operator or administrator of the
   Printer object (see [ipp-mod] [RFC2911] Sections 1 and 8.5).  Most Printer
   attributes will require administrator access rights to set, such as
   "xxx-supported", while some will require operator access rights only,
   such as "media-ready" and "printer-message-from-operator".  Which
   attributes require which access rights depends on implementation and
   MAY depend on site policy.

4.1.2Set-Printer-Attributes

4.1.2     Set-Printer-Attributes Request

   The following sets of attributes are part of the Set-Printer-Attributes Set-Printer-
   Attributes Request:

   Group 1: Operation Attributes

      Natural Language and Character Set:
         The "attributes-charset" and "attributes-natural-language"
         attributes as described in [ipp-mod] [RFC2911] section 3.1.4.1.

      Target:
         The "printer-uri" (uri) operation attribute which is the target
         for this operation as described in [ipp-mod] [RFC2911] section 3.1.5.

      Requesting User Name:
         The "requesting-user-name" (name(MAX)) attribute SHOULD be
         supplied by the client as described in [ipp-mod] [RFC2911] section 8.3.

      "document-format" (mimeMediaType):
         The client OPTIONALLY supplies this attribute.  The Printer
         object MUST support this attribute.  This attribute is useful
         for a client

                     Expires:  September 23, 2000 to select the document-format to which the
         attribute modification should be applied.  A Printer
         implementation MAY allow some attributes to have different
         values for each document format that it supports. See [ipp-mod] [RFC2911]
         section 3.2.5.1 "Get-Printer-Attributes Request".

         If the client includes this attribute, the Printer MUST change
         the supplied attributes for the document format specified by
         this attribute.  If a supplied attribute is a member of the "document-
     format-varying-attributes"
         "document-format-varying-attributes" (i.e., the attribute
         varies by document format, see section 6.3), the Printer MUST
         change the supplied attribute for the document format specified
         by this attribute, but not for other document formats.  If a
         supplied attribute isn't a member of the "document-format-varying-attributes" "document-format-
         varying-attributes" (i.e. it doesn't vary by document format),
         the Printer MUST change the supplied attribute for all document
         formats.

         If the client omits this attribute, the Printer MUST change the
         supplied attributes for all document formats whether or not
         they vary by document-format.

         If the client supplies a value for the "document-format"
         Operation attribute that is either 'application/octet-stream'
         or not supported by the Printer, i.e., is not among the values
         of the Printer object's "document-format-supported" attribute,
         the Printer object MUST reject the operation and return the 'client-error-
     document-format-not-supported'
         'client-error-document-format-not-supported' status code.
         Note: the document-
     format document-format 'application/octet-stream' is the
         union of several document-
     formats document-formats (see [ipp-mod] [RFC2911] section
         3.2.5.1, Get-Printer-Attributes) and is not a true document-format. document-
         format.

   Group 2: Printer Attributes

         The client MUST supply a set of Printer attributes with one or
         more values (including explicitly allowed out-of-band values)
         as defined in [ipp-mod] [RFC2911] section 4.2 Job Template Attributes
         ("xxx-default", "xxx-supported", and "xxx-ready" attributes),
         section 4.4 Printer Description Attributes, and any attribute
         extensions supported by the Printer.  The value(s) of each
         Printer attribute supplied in Group 2 replaces the value(s) of
         the corresponding Printer attribute on the target Printer
         object.  For attributes that can have multiple values (1setOf),
         all values supplied by the client replace all values of the
         corresponding Printer object attribute.  If a Printer object
         attribute had not been configured yet and so had the 'no-value'
         out-of-band value (see [ipp-mod] [RFC2911] section 4.1), the supplied
         value(s) replace the 'no-value' value.

4.1.3Set-Printer-Attributes

4.1.3     Set-Printer-Attributes Response

   The Printer object returns the following sets of attributes as part
   of the Get-Printer-Attributes Response:

   Group 1: Operation Attributes

                     Expires:  September 23, 2000

      Status Message:
         In addition to the REQUIRED status code returned in every
         response, the response OPTIONALLY includes a "status-message"
         (text(255)) and/or a "detailed-status-message" (text(MAX))
         operation attribute as described in [ipp-mod] [RFC2911] sections 13 and
         3.1.6.

      Natural Language and Character Set:
         The "attributes-charset" and "attributes-natural-language"
         attributes as described in [ipp-mod] [RFC2911] section 3.1.4.2.

   Group 2: Unsupported Attributes

         See [ipp-mod] [RFC2911] section 3.1.7 for details on returning
         Unsupported Attributes.

         If some of the attributes in the operation fail to validate,
         the Printer MUST reject the operation, MUST NOT change any
         Printer attributes, and MUST return the indicated status code
         below.  In this group, the Printer MUST also return all
         attributes that fail to validate.  The following are the
         reasons that an attribute fails to validate and the value
         returned for the attribute, along with the indicated status
         code and order of detection:

       1. The

         1.The number of attributes supplied by the client exceeds the
           maximum number that the Printer supports in a Set-Printer-
           Attributes request:  return the 'client-error-request-entity-
          too-large' 'client-error-request-
           entity-too-large' (see [ipp-mod] [RFC2911] section 13.1.4.9).

       2. The

         2.The Printer doesn't support the attribute:  return the
           attribute with the "out-of-band" value 'unsupported' (see
          [ipp-mod]
           [RFC2911] section 3.1.7 and [ipp-pro]) [RFC2910]) and the 'client-error-
          attributes-or-values-not-supported 'client-
           error-attributes-or-values-not-supported (see [ipp-mod] [RFC2911]
           section 13.1.4.12).

       3. The

         3.The attribute is either READ-ONLY (in its definition) or is
           not-settable in this implementation:  return the attribute
           with the "out-of-band" value 'not-settable' (see section
           8.1) and the 'client-error-attributes-not-settable' status
           code (see section 7.1).

       4. The

         4.The Printer doesn't support the value:  if the attribute in
           the operation has a single value return it.  If the
           attribute in the operation is multi-valued, return only
           those values in a 1setOf that are not supported.  Return the 'client-error-
          attributes-or-values-not-supported'
           'client-error-attributes-or-values-not-supported' status
           code (see [ipp-mod] [RFC2911] section 13.1.4.12).

       5. The

         5.The values of some of the supplied attributes conflict with
           one another and/or other Printer attribute values not being
           set:  if the conflicting attribute in the operation has a
           single value return the attribute and the value.  If the
           attribute in the operation is multi-valued, return only the
           attribute and those values in a 1setOf that are conflicting

                     Expires:  September 23, 2000
           with other attributes.  Return the 'client-error-conflicting-
          attributes' 'client-error-
           conflicting-attributes' status code (see [ipp-mod] [RFC2911] section
           13.1.4.15).

4.2 Set-Job-Attributes Operation

   This OPTIONAL operation allows a client to set the values of the
   attributes of a Job object.  In the request, the client supplies the
   set of Job keyword attribute names and values that are to be set.  In
   the response, the IPP object returns success or rejects the entire
   request with indications of which attribute or attributes could not
   be set.

   This operation is almost identical to the Set-Printer-Attributes
   operation and follows the same rules for validation (see section
   4.1).  The only differences are that the Set-Job-Attributes operation
   is directed at a Job object rather than a Printer object, there is no
   "document-format" operation attribute used when setting a Job object,
   the operation can add an attribute to the (Job) object, the 'delete-
   attributes' out-of-band value is permitted to remove an attribute,
   and the validation is the same as the Job Creation operations (Print-Job, (Print-
   Job, Print-URI, and Create-Job), i.e., depends on the "xxx-supported"
   Printer Description attributes (see [ipp-mod] [RFC2911] section 3.1).   Using
   the Set-
Printer-Attributes Set-Printer-Attributes operation, the administrator can set
   arbitrary 'name' values to those "xxx-supported" Printer attributes
   that include the 'name' attribute syntax if the implementation
   supports the 'admin-
define' 'admin-define' out-of-band value for that "xxx-supported" "xxx-
   supported" attribute (see section 0 15 and 8.3).  However, the Set-Job-Attributes Set-Job-
   Attributes cannot be used to add unsupported names to the Job object.

   If a client supplies a job attribute in a Set-Job-Attributes request
   that the Printer supports, and the job was originally submitted
   without supplying that attribute, the Printer adds the attribute to
   the Job object.

   If the client supplies a job attribute with the "out-of-band" value
   'delete-attribute' (see section 8.2), then the Printer MUST remove
   the attribute and all of its values from the Job object, if present.
   The semantic effect of the client supplying the 'delete-attribute'
   value in a Set-Job-Attributes operation MUST be the same as if the
   attribute had not been supplied with the Job object in the Job
   Creation operation, i.e., the Printer applies its default attribute
   or behavior with lower precedence that the PDL (see the beginning of [ipp-mod]
   [RFC2911] section 4.2 and
[ipp-mod] [RFC2911] 3.2.1.1).  Any subsequent query
   of the Job object using Get-
Job-Attributes Get-Job-Attributes or Get-Jobs MUST NOT
   return any attribute that has been deleted using the 'delete-attribute' 'delete-
   attribute' out-of-band value.  However, a client can re-establish
   such a deleted Job attribute with any supported value(s) using a
   subsequent Set-Job-Attributes operation.

   If the client supplies an attribute in a Set-Job-Attributes request
   with the 'delete-attribute' value and that attribute is not present
   on the Job object, the Printer ignores that supplied attribute in the
   request, does not return the attribute in the Unsupported Attributes
   group, and returns the 'successful-ok' status code, if there are no
   other problems with the request.

                     Expires:  September 23, 2000

   The validation of the Set-Job-Attributes request is performed by the
   Printer as if the job had been submitted originally with the new
   attribute values (and the deleted attributes removed) and with "ipp-
   attribute-fidelity" set to 'true', i.e., all modified attributes Job
   attributes and values MUST be supported in combination with the Job
   attributes not modified.  If such a Job Creation operation would have
   been accepted, then the Set-Job-Attributes MUST be accepted.  If such
   a Job Creation operation would have been rejected, then the Set-Job-
   Attributes MUST be rejected and the Job MUST be unchanged.  In
   addition, if any of the supplied attributes are not supported, are
   not settable, or the values are not supported, the Printer object
   MUST reject the entire operation; the Printer object MUST NOT
   partially set some of the supplied attributes.  In other words, after
   the operation, all the supplied attributes MUST be set or none of
   them MUST be set, thus making the Set-Job-Attributes an atomic
   operation.

   The IPP object MUST accept or reject this operations when the Job's
   READ-ONLY "job-state" attribute has the values shown in Table 2.  The
   job's current state MUST affect whether the IPP object accepts or
   rejects the request. For example, in the case where the operation
   creates a request for unavailable resources, the Job transitions to a
   new state.  Table 2 shows the allowed behaviors in each job state and
   the transitions.

      Table 2 - Job State Transition Table for the Set-Job-Attributes
                                 operation

   Current "job-    New "job-       IPP object's response status code
   state"           state"             code          and action:

   'pending'        'pending'       'successful-ok'

   'pending'       'pending-        'pending-held'  'successful-ok' - needed
                  held' resources
                                    are not ready

   'pending-held'  'pending-   'pending-held'  'successful-ok'
                  held'

   'pending-held'   'pending'       'successful-ok' - needed resources
                                    are ready

   'processing'     'processing'    'successful-ok'  or 'client-
                                 error-not-possible' 'client-error-
                                    not-possible' depending on
                                    implementation, including the
                                    attributes being set, whether the
                                    job has started marking media,
                                    etc.

   'processing-     'processing-    'successful-ok'  or 'client- 'client-error-
   stopped'         stopped'       error-not-possible'        not-possible' depending on
                                    implementation, including the
                                    attributes being set, whether the
                                    job has started marking media,
                                    etc.

   'completed'      'completed'     'client-error-not-possible'

   'canceled'       'canceled'      'client-error-not-possible'

   'aborted'        'aborted'       'client-error-not-possible'

                     Expires:  September 23, 2000

   This operation MUST NOT change the value of attributes not specified
   in the operation unless the definition of the attribute explicitly
   specifies such side-effects.  In general, Job attribute definitions
   that are settable will not define side-effects on other attributes
   that are settable, only side effects on READ-ONLY attributes, if any.

4.2.1Settable

4.2.1     Settable and READ-ONLY Job Description attributes

   If the Printer supports the "job-message-from-operator" Job
   Description attribute (see [ipp-mod] [RFC2911] section 4.3.16) and the client
   explicitly supplies a new value for the "job-message-from-operator"
   in the Set-Job-
Attributes Set-Job-Attributes request, then the Printer MUST set the "job-message-from-
operator"
   "job-message-from-operator" Job attribute to this new value.

   If the Printer supports the Set-Job-Attributes operation, then it
   SHOULD support setting of:

     all Job Template job ("xxx") attributes

   that the implementation supports (see [ipp-mod] [RFC2911] section 4.2 and
   extensions).

   Some Job Description attributes (see [ipp-mod] [RFC2911] section 4.3) MUST NOT
   be settable, i.e., they are defined to be READ-ONLY.  An attribute
   marked as "READ-ONLY" in the Job Description attribute table in
   Appendix A is such an attribute.  The Job attributes not marked as
   "READ-ONLY" MAY be settable using the Set-Job-Attributes operation,
   depending on implementation.

   Note:  From now on, all extensions that define new object attributes
   will indicate whether or not the attributes are READ-ONLY, by
   including the "READ-ONLY" adjective in their descriptions and/or
   explicitly stating whether they MAY be settable.

   Access Rights: The authenticated user (see [ipp-mod] [RFC2911] section 8.3)
   performing this operation must either be the job owner (as determined
   in the Job Creation operation) or an operator or administrator of the
   Printer object (see [ipp-mod] [RFC2911] Sections 1 and 8.5).

4.2.2Set-Job-Attributes

4.2.2     Set-Job-Attributes Request

   The following sets of attributes are part of the Set-Job-Attributes
   Request:

   Group 1: Operation Attributes
      Natural Language and Character Set:
         The "attributes-charset" and "attributes-natural-language"
         attributes as described in [ipp-mod] [RFC2911] section 3.1.4.1.

      Target:
         Either (1) the "printer-uri" (uri) plus "job-id"
         (integer(1:MAX)) or (2) the "job-uri" (uri) operation
         attribute(s) which define the target for this operation as
         described in [ipp-mod] [RFC2911] section 3.1.5.

                     Expires:  September 23, 2000

      Requesting User Name:
         The "requesting-user-name" (name(MAX)) attribute SHOULD be
         supplied by the client as described in [ipp-mod] [RFC2911] section 8.3.

   Group 2: Job Attributes

         The client MUST supply a set of Job attributes with one or more
         values (including explicitly allowed out-of-band values) as
         defined in [ipp-mod] [RFC2911] section 4.2 Job Template Attributes ("xxx"
         attributes), section 4.3 Job Description Attributes, and any
         attribute extensions supported by the Printer.  The value(s) of
         each Job attribute supplied in Group 2 replaces the value(s) of
         the corresponding Job attribute on the target Job object.  For
         attributes that can have multiple values (1setOf), all values
         supplied by the client replace all values of the corresponding
         Job object attribute.

         If the client supplies an "xxx" attribute with the 'delete-
         attribute' out-of-band value (see section 8.2), the Printer
         MUST remove the "xxx" attribute from the Job object, if
         present.

4.2.3Set-Job-Attributes

4.2.3     Set-Job-Attributes Response

   The IPP object returns the following sets of attributes as part of
   the Set-Job-Attributes Response:

   Group 1: Operation Attributes

      Status Message:
         In addition to the REQUIRED status code returned in every
         response, the response OPTIONALLY includes a "status-message"
         (text(255)) and/or a "detailed-status-message" (text(MAX))
         operation attribute as described in [ipp-mod] [RFC2911] sections 13 and
         3.1.6.

      Natural Language and Character Set:
         The "attributes-charset" and "attributes-natural-language"
         attributes as described in [ipp-mod] [RFC2911] section 3.1.4.2.

   Group 2: Unsupported Attributes

         See [ipp-mod] [RFC2911] section 3.1.7 for details on returning
         Unsupported Attributes.

         If some of the attributes in the operation fail to validate,
         the Printer MUST reject the operation, MUST NOT change any Job
         attributes, and MUST return the indicated status code below.
         In this group, the Printer MUST also return all attributes that
         fail to validate.  The following are the reasons that an
         attribute fails to validate and the value returned for the
         attribute, along with the indicated status code and order of
         detection:

       1. The

         1.The number of attributes supplied by the client exceeds the
           maximum number that the Printer supports in a Set-Printer-

                     Expires:  September 23, 2000
           Attributes request:  return the 'client-error-request-entity-
          too-large' 'client-error-request-
           entity-too-large' (see [ipp-mod] [RFC2911] section 13.1.4.9).

       2. The

         2.The Printer doesn't support the attribute:  return the
           attribute with the 'unsupported' out-of-band attribute value
           (see [ipp-mod] [RFC2911] section 3.1.7 and [ipp-pro]) [RFC2910]) and the 'client-
           error-attributes-or-values-not-supported (see [ipp-mod] [RFC2911]
           section 13.1.4.12).

       3. The

         3.The attribute is READ-ONLY (in its definition) or is not-
           settable in this implementation:  return the attribute with
           the 'not-settable' out-of-band attribute value (see section
           8.1) and the 'client-error-attributes-not-settable' status
           code (see section 7.1).

       4. The

         4.The Printer doesn't support the value:  if the attribute in
           the operation has a single value return it.  If the
           attribute in the operation is multi-valued, return only
           those values in a 1setOf that are not supported.  Return the 'client-error-
          attributes-or-values-not-supported'
           'client-error-attributes-or-values-not-supported' status
           code (see [ipp-mod] [RFC2911] section 13.1.4.12).

       5. The

         5.The values of some of the supplied attributes conflict with
           one another and/or other Job attribute values not being set:
           if the conflicting attribute in the operation has a single
           value return the attribute and the value.  If the attribute
           in the operation is multi-valued, return only the attribute
           and those values in a 1setOf that are conflicting with other
           attributes.  Return the 'client-error-conflicting-attributes' 'client-error-conflicting-
           attributes' status code (see [ipp-mod] [RFC2911] section 13.1.4.15).

4.3 Get-Printer-Supported-Values Operation

   This OPTIONAL operation allows a client to request the values that
   the Printer allows in the Set-Printer-Attributes operation for "xxx-
   supported" attributes.  If the Printer supports the Set-Printer-
   Attributes operation AND some of its "xxx-supported" Printer
   attributes are settable, then the Printer MUST also support this
   operation.

   The Printer MUST return in the Get-Printer-Supported-Values response
   those, and only those, "xxx-supported" Printer attributes that it
   supports setting with the Set-Printer-Attributes operation.
   Furthermore, if a client requests the value of an attribute that is
   not settable or is not supported (as in the Get-Printer-Attributes
   response), the Unsupported Attributes Group of the response NEED NOT
   contain the "requested-attributes" operation attribute with any such
   requested (attribute keyword) values.

   This operation has identical request/response attributes to the Get-
   Printer-Attributes operation in IPP/1.1 [ipp-mod]. [RFC2911].  The operation
   also behaves identically to the Get-Printer-Attributes operation in
   IPP/1.1
[ipp-mod] [RFC2911] with the following exceptions:

                     Expires:  September 23, 2000
  1. The

   1.The Get-Printer-Supported-Values operation supports only "xxx-
     supported" attributes.

  2. The

   2.The Get-Printer-Attributes operation returns the few "xxx-
     supported" attributes that are defined to be single valued, such
     as "page-ranges-supported" (boolean) or "pdl-override-supported"
     (type2 keyword), as single values, while Get-Printer-Supported-
     Values returns the possible values that can be set as a 1setOf of
     the same attribute syntax type (See Appendix B: Attributes
     returned from Get-Printer-Supported-Values).

  3. The

   3.The Get-Printer-Attributes operation returns the current values of
     requested attributes while the Get-Printer-Supported-Values
     operation returns the values that are inherently supported by the
     implementation code, i.e., the values that an administrative
     client can set in  a Set-Printer-Attributes request.

  4. The

   4.The Get-Printer-Attributes operation returns the current values of
     requested "xxx-supported" attributes that the Printer is
     configured to accept in Job Creation operations, including
     additional values defined by the administrator, while the Get-Printer-Supported-
     Values Get-
     Printer-Supported-Values operation returns only the values of
     "xxx-supported" attributes that are inherently supported by the
     implementation and does not return any additional values defined
     by the administrator where the implementation supports the 'admin-define' 'admin-
     define' out-of-band value.

  5. The

   5.The Get-Printer-Attributes never returns the 'admin-define' out-of-
     band out-
     of-band attribute value, while the Get-Printer-Supported-Attributes Get-Printer-Supported-
     Attributes operation does, if the implementation allows the
     administrator to define name values by setting that "xxx-supported" "xxx-
     supported" attribute with any 'name' value(s).

  6. The

   6.The Get-Printer-Attributes operation only requires end-user access
     rights, while the Get-Printer-Supported-Values requires
     administrator access rights.

   Access Rights:  The authenticated user (see [ipp-mod] [RFC2911] section 8.3)
   performing this operation must be an administrator of the Printer
   object (see [ipp-mod] [RFC2911] Sections 1 and 8.5).

4.3.1Definition

4.3.1     Definition of the usage of the 'admin-define' out-of-band
     attribute value

   If the Set-Printer-Attributes operation allows the System
   Administrator to define arbitrary 'name' values for an "xxx-supported" "xxx-
   supported" attribute, then the Get-Printer-Supported-Values operation
   MUST return the 'admin-
define' 'admin-define' out-of-band attribute value (see
   section 8.3) as one of the values of the "xxx-supported" attribute.
   In other words, the 'admin-
define' 'admin-define' out-of-band attribute value
   indicates that the Printer implementation supports clients setting
   arbitrary 'name' attribute syntax values for that "xxx-supported"
   attribute using the Set-Printer-

                     Expires:  September 23, 2000

Attributes Set-Printer-Attributes operation as long as the
   attribute is defined with the 'name' attribute syntax.

   For example, if the Get-Printer-Supported-Values operation returns
   several keywords as the value of the "media-supported" attribute,
   then the Set-Printer-Attributes operation MUST accept any of these
   keywords as values for the "media-supported" attribute.  If the Get-Printer-
Supported-Values Get-
   Printer-Supported-Values operation returns an 'admin-define' out-of-band out-of-
   band attribute value as one of the values of the "media-supported"
   attribute, then the Set-Printer-Attributes operation MUST accept any
   value whose attribute syntax is 'name' as a value for the "media-supported" "media-
   supported" attribute (provided that the user is properly
   authenticated to use the Set-Printer-Attributes operation, e.g., has
   administrative access rights).

   The Get-Printer-Supported-Values MAY return the 'admin-define' out-of-
band out-
   of-band attribute value for any IPP/1.1 or extension Job Template
   attribute if the implementation supports allowing the System
   Administrator to add values to the "xxx-supported" attribute using
   the Set-Printer-Attributes operation.  In this case, the Printer MUST
   accept any 'name' value of the correct attribute syntax in a Set-Printer-Attributes Set-
   Printer-Attributes operation that is setting that attribute.  For
   "xxx-supported" attributes that are defined with a choice of
   attribute syntaxes, such as 'keyword | name', it is the 'name'
   attribute syntax that the System Administrator can use to add new
   values, not the 'keyword' attribute syntax.  For IPP/1.1 this
   requirement includes the following Job Template attributes:

     media-supported
     job-hold-until-supported
     job-sheets-supported

   Implementations that support additional Job Template attributes that
   include the 'name' attribute syntax, MAY use the 'admin-define' out-of-
band out-
   of-band value with them.

   If the 'admin-define' out-of-band attribute value is not one of the
   values of an "xxx-supported" attribute returned in a Get-Printer-
   Supported-Values response, then the Printer MUST NOT allow the Set-
   Printer-Attributes operation for that attribute to contain a value
   that is not one of the explicit 'keyword' or 'name' values returned
   in a Get-
Printer-Supported-Values Get-Printer-Supported-Values response.

   See Appendix B: Attributes returned from Get-Printer-Supported-Values
   for a full list of values returned by this operation.

5  New Operation attributes

   This section defines new operation attributes for use with the
   IPP/1.1 operations indicated.  As new operations are defined they
   will also indicate explicitly whether these operation attributes are
   defined for use with them.

                     Expires:  September 23, 2000

5.1 "printer-message-from-operator" printer-message-from-operator (text(127))

   The Printer SHOULD support this Operation attribute in following
   operations if it supports the corresponding "printer-message-from-
   operator" Printer Description attribute.

         Pause-Printer
         Resume-Printer
         Purge-Jobs

   The client OPTIONALLY supplies this attribute in the above
   operations. The value of this attribute is a message from the
   operator about the Printer object on which the operator is performing
   the operation.  If this operation attribute is supported, the Printer
   copies the value to its "printer-message-from-operator" Printer
   Description attribute (see
[ipp-mod] [RFC2911] section 4.4.25) even if this
   Operation attribute is a zero-
length zero-length text value or consists solely of
   white space.

   If the Printer supports this operation attribute, it MUST support
   both a zero-length text value and the 'no-value' out-of-band value
   (see [ipp-
mod] [RFC2911] section 4.1) to indicate that the operator has sent no
   message.  In this case, the Printer sets the value of the "printer-message-from-
operator" "printer-
   message-from-operator" to the zero-length value or 'no-value' out-of-band out-of-
   band value, respectively.  If the client queries the "printer-message-from-operator" "printer-
   message-from-operator" Printer attribute, the Printer returns the
   attribute with the zero-
length zero-length value or the 'no-value' value,
   respectively.

   In addition, the Printer automatically copies:

  1. the

   1.the value of its "printer-up-time" attribute (see [ipp-mod] [RFC2911]
     section 4.4.29) to its "printer-message-time" attribute,

  2. the
   2.the value of its printer-current-time" (dateTime) attribute (see
     [ipp-mod]
     [RFC2911] section 4.4.30) to its "printer-message-date-time"
     attribute, if supported.

   If the client omits this operation attribute, the Printer does not
   change the value of its "printer-message-from-operator", "printer-
   message-time" and "printer-message-date-time" Printer Description
   attributes.

   The "printer-message-from-operator" operation attribute MUST NOT be
   supported as an operation attribute for the Set-Printer-Attributes
   operation.  If the operator wants to set the Printer's "printer-message-
from-operator" "printer-
   message-from-operator" Printer Description attribute when issuing the Set-
Printer-Attributes
   Set-Printer-Attributes operation, the client supplies the "printer-message-
from-operator" "printer-
   message-from-operator" explicitly with its new value as one of the
   Printer Description attributes in Group 2 in the request.  The
   Printer also updates its "printer-message-time" and "printer-message-date-time" "printer-message-
   date-time" Printer Description attributes.  If the client does not
   explicitly supply the "printer-message-from-operator" with its new
   value in the Set-Printer-Attributes request, the Printer leaves the
   value of the

                     Expires:  September 23, 2000 Printer's "printer-message-from-operator" Printer
   Description attribute unchanged.

5.2 "job-message-from-operator" job-message-from-operator (text(127))

   The Printer SHOULD support this Operation attribute in following
   operations if it supports the corresponding "job-message-from-operator" "job-message-from-
   operator" Job Description attribute.

         Cancel-Job
         Hold-Job
         Release-Job
         Restart-Job

   The client OPTIONALLY supplies this attribute in the above
   operations. The value of this attribute is a message from the
   operator about the Job object on which the operator has just
   performed an operation.  If supported, the Printer copies the value
   to the Job's "job-message-from-
operator" "job-message-from-operator" Job Description attribute
   (see [ipp-mod] [RFC2911] section 4.3.16) (even if this Operation attribute is a
   zero-length text value or consists solely of white space).

   If the Printer supports this operation attribute, it MUST support
   both a zero-length text value and the 'no-value' out-of-band value
   (see [ipp-
mod] [RFC2911] section 4.1) to indicate that the operator has sent no
   message.  In this case, the Printer sets the value of the "job-message-from-operator" "job-
   message-from-operator" to the zero-length value or 'no-value' out-of-band out-of-
   band value, respectively.  If the client queries the "job-message-from-operator" "job-message-
   from-operator" Job attribute, the IPP object returns the attribute
   with the zero-length value or the 'no-
value' 'no-value' value, respectively.

   If the client omits this attribute, the Printer does not change the
   value of its "job-message-from-operator" Job Description attribute.

   Note:  There are no corresponding 'job-message-time" and "job-message-
date-time" "job-
   message-date-time" Job Description attributes, since the usual
   lifetime of a job is limited.

   The "job-message-from-operator" operation attribute MUST NOT be
   supported as an operation attribute for the Set-Job-Attributes
   operation.  If the operator wants to set the Job's "job-message-from-
   operator" Job Description attribute when issuing the Set-Job-Attributes Set-Job-
   Attributes operation, the client MUST supply the "job-message-from-operator" "job-message-from-
   operator" with its new value as one of the Job Description attributes
   in Group 2 in the request.  Otherwise, the Printer leaves the value
   of the Job's "job-
message-from-operator" "job-message-from-operator" Job Description attribute
   unchanged by not explicitly setting the attribute.   If the client
   does not explicitly supply the "job-message-from-operator" with its
   new value in the Set-
Job-Attributes Set-Job-Attributes request, the Printer leaves the
   value of the Job's "job-
message-from-operator" "job-message-from-operator" Job Description
   attribute unchanged.

                     Expires:  September 23, 2000

6  New Printer Description Attributes

   The following new Printer Description attributes are needed to
   support the new operations defined in this document.

6.1 printer-settable-attributes-supported (1setOf type2 keyword)

   This REQUIRED READ-ONLY Printer attribute identifies the Printer
   object attributes that are settable in this implementation, i.e.,
   that are settable using the Set-Printer-Attributes operations (see
   section 4.1).  This attribute MUST be supported if the Set-Printer-Attributes Set-Printer-
   Attributes operations is supported.  The Printer MUST reject attempts
   to set any Printer attributes that are not one of the values of this
   attribute, returning the 'client-error-attributes-not-settable'
   status code (see section 7.1).  The value of this attribute MAY
   depend on the value of the "document-format" operation attribute
   supplied in the Get-Printer-
Attributes Get-Printer-Attributes operation (see [ipp-mod] [RFC2911]
   section 3.2.5.1).

   Standard keyword values are:

     'none':  There are no settable Printer attributes.
     'xxx':   Where 'xxx' is any of the keyword attribute names allowed
       by section 4.1.1

6.2 job-settable-attributes-supported (1setOf type2 keyword)

   This REQUIRED READ-ONLY Printer attribute identifies the Job object
   attributes that are settable in this implementation, i.e., that are
   settable using the Set-Job-Attributes operation (see section 4.2).
   This attribute MUST be supported if the Set-Job-Attributes operations
   is supported.  The Printer MUST reject attempts to set any Job
   attributes that are not one of the values of this attribute,
   returning the 'client-
error-attributes-not-settable' 'client-error-attributes-not-settable' status code (see
   section 7.1).

   Standard keyword values are:

     'none':  There are no settable Job attributes.
     'xxx':   Where 'xxx' is any of the keyword attribute names allowed
       by section 4.2.1.

6.3 document-format-varying-attributes (1setOf type2 keyword)

   This OPTIONAL READ-ONLY Printer Description attribute contains a set
   of attribute name keywords.  This attribute SHOULD be supported by a
   Printer object, if the Printer object has Printer attributes whose
   value vary depending on document format (see [ipp-mod] Get-Printer-Attributes [RFC2911] Get-Printer-
   Attributes operation).  This attribute specifies which attribute
   values can vary by document-format.  If an attribute's name "xxx" is
   a member of this attribute and the value of attribute "xxx" is
   changed with the Set-
Printer-Attributes Set-Printer-Attributes operation that included the
   "document-format" operation attribute, then the Printer MUST change
   the value for the specified document format and no other document
   formats (see section

                     Expires:  September 23, 2000 4.1.2).  If an attribute's name "xxx" is not a
   member of this attribute and the value of attribute "xxx" is changed
   with the Set-Printer-
Attributes Set-Printer-Attributes operation, then the attribute is
   changed for all document formats (whether or not the client supplied
   the "document-format" operation attribute).

6.4 printer-message-time (integer(MIN:MAX))

   This OPTIONAL READ-ONLY Printer Description attribute contains the
   time that the Printer's "printer-message-from-operator" was changed
   by the operator using any operation where the client supplied the "printer-
message-from-operator"
   "printer-message-from-operator" operation attribute (see section 5.1)
   or was explicitly set using the Set-Printer-Attributes operation (see
   section 4.1).  This attribute allows the users to know when the "printer-
message-from-operator"
   "printer-message-from-operator" attribute was last set.

   The Printer sets the value of this attribute by copying the value of
   the Printer's "printer-up-time" attribute (see [ipp-mod] [RFC2911] section
   4.3.14).  If the Printer resets its "printer-up-time" attribute to 1
   on power-up, then it MUST change the value of the "printer-message-time" "printer-message-
   time" to 0 or a negative number as specified in [ipp-mod] [RFC2911] section
   4.3.14.

   Note:  This attribute helps users better understand the context for
   the "printer-message-from-operator" message.

6.5 printer-message-date-time (dateTime)

   This OPTIONAL READ-ONLY Printer Description attribute contains the
   date and time that the Printer's "printer-message-from-operator" was
   changed by the operator using any operation where the client supplied
   the "printer-message-from-operator" operation attribute (see section
   5.1) or was explicitly set using the Set-Printer-Attributes operation
   (see section 4.1).  This attribute allows the users to know when the
   "printer-message-from-operator" attribute was last set.

   This attribute MUST be supported if the Printer supports both the
   "printer-message-time" and the "printer-current-time" (dateTime)
   attributes (see [ipp-mod] [RFC2911] section 4.4.30).

   Note:  This attribute helps users better understand the context for
   the "printer-message-from-operator" message.

6.6 printer-xri-supported (1setOf collection)

   This OPTIONAL Printer Description attribute is a multi-valued
   attribute where each value has the 'collection' attribute syntax (see
   [ipp-coll]) containing member attributes with the same semantics as
   the following IPP/1.1 READ-ONLY Printer Description attributes,
   except for cardinality:

         printer-uri-supported (1setOf uri) - see [ipp-mod] [RFC2911] section
         4.4.1

                     Expires:  September 23, 2000
         uri-authentication-supported (1setOf type2 keyword) - see [ipp-mod]
         [RFC2911] section 4.4.2
         uri-security-supported (1setOf type2 keyword) - see [ipp-mod] [RFC2911]
         section 4.4.3

   When setting the "printer-xri-supported" attribute with a Set-Printer-
Attributes Set-
   Printer-Attributes request, the Printer MUST also set these three
   IPP/1.1 READ-
ONLY READ-ONLY Printer Description attributes as a defined side
   effect.  Thus, this collection attribute provides the means to set
   these three IPP/1.1 READ-ONLY attributes atomically so that they are
   never left in a partially inconsistent state.

   An IPP Printer MUST NOT provide any other way using IPP to set these
   three IPP/1.1 READ-ONLY Printer Description attributes, since they
   are READ-ONLY and MUST have consistent values at all times.  Note:
   The "xri-printer-supported" (1setOf collection) attribute can be put
   into a directory schema that requires a single text string value,
   such as SLP or LDPA, by using suitable delimiting characters to
   separate member attributes of the collection and/or terminating
   collection values.  See [svrloc-printer] and [ldap-printer].

   The member attributes of the "printer-xri-supported" (1setOf
   collection) are given in Table 3.

      Table 3 - Member attributes of "printer-xri-supported" (1setOf
                                collection)

     Member attribute                             client    Printer
                                                  MUST      MUST
                                                  supply    support

     xri-uri (uri)                                yes       yes

     xri-authentication (1setOf type2 keyword)    yes       yes

     xri-security (1setOf type2 keyword)          yes       yes

   Each collection value MUST contain a single unique value for the "xri-
uri"
   "xri-uri" member attribute.  However, the other two member attributes
   are multi-valued, so that a single URI can support more than one
   authentication scheme and/or more than one security scheme.  Other
   than the uniqueness and the cardinality requirements, the semantics
   of these three member attributes is given in [ipp-mod] [RFC2911] sections
   4.4.1, 4.4.2, and 4.4.3, respectively.

   A client can query the current values using the Get-Printer-Attributes Get-Printer-
   Attributes operation by supplying either:

  1. the

   1.the three IPP/1.1 attribute names:  "printer-uri-supported", "uri-
     authentication-supported", "uri-security-supported" and getting
     back the parallel values OR

                     Expires:  September 23, 2000
  2. the

   2.the single attribute name: "printer-xri-supported" and getting
     back the 1setOf collection which contains the same information
     semantically, but in a different form.

   A client can query what member attribute values can be set by
   supplying the three attribute names: "xri-uri-scheme-supported", "xri-
authentication-supported",
   "xri-authentication-supported", and "xri-security-supported" in a Get-
Printer-Supported-Values
   Get-Printer-Supported-Values request and getting back the uriScheme
   and type2 keyword values that can be set.  Since the "printer-xri-
   supported", "uri-authentication-supported", and "uri-security-supported" "uri-security-
   supported" attributes are READ-ONLY, they are not queriable with the Get-Printer-
Supported-Values
   Get-Printer-Supported-Values operation (see section 4.3).  See Table
   15.

   When performing a Set-Printer-Attributes operation, if there are
   multiple values for the "xri-authentication" and/or "xri-security"
   member attributes, the Printer MUST set the corresponding three READ-
   ONLY attributes with all possible combinations of values.  For
   example, setting the "printer-xri-supported" with the following two
   collection values where the first URI has both 'basic' and 'digest'
   authentication:

     "printer-xri-supported =
         {  "xri-uri" = ipp://abc.com/p1
            "xri-authentication" = basic, digest
            "xri-security" = tls
         },
         {  "xri-uri" = http://abc.com/pq
            "xri-authentication" = none
            "xri-security" = none
         }

   would cause the Printer to set the three corresponding IPP/1.1 READ-ONLY READ-
   ONLY attributes, each with three parallel values as follows:

      "printer-uri-supported" = { ipp://abc.com/p1, ipp://abc.com/p1,
                                  http://abc.com/pq }
      "uri-authentication-supported" = { basic, digest, none }
      "uri-security-supported" = { tls, tls, none }

   Because there were two authentication values for the ipp://abc.com/p1
   URL, that URL value is repeated.  Had the ipp URL had 2
   authentication values and 3 security values, then there would have
   been 7 (2*3 + 1) parallel values for each of the three attributes, 6
   with the same ipp URI and 1 with the http URI.

6.7 xri-uri-scheme-supported (1setOf uriScheme)

   This OPTIONAL READ-ONLY Printer Description attribute identifies the
   URI schemes that the implementation supports for use in the "printer-uri-
supported" "printer-
   uri-supported" (1setOf uri) Printer Description attribute (see [ipp-mod]
   [RFC2911] section 4.4.1) and the "xri-uri" member attribute of the "xri-printer-

                     Expires:  September 23, 2000

supported"
   "xri-printer-supported" (1setOf collection) Printer Description
   attribute (see section 6.6).

   A Printer MUST support this attribute if it supports setting the
   "printer-xri-supported" (1setOf collection) with the Set-Printer-
   Attributes operation.

6.8 xri-authentication-supported (1setOf type2 keyword)

   This OPTIONAL READ-ONLY Printer Description attribute identifies the
   Client Authentication mechanisms that the implementation supports for
   use in the "printer-authentication-supported" "uri-authentication-supported" (1setOf type2 keyword)
   Printer Description attribute (see [ipp-mod] [RFC2911] section 4.4.2) and the
   "xri-authentication" member attribute of the "xri-printer-supported"
   (1setOf collection) Printer Description attribute (see section 6.6).

   A Printer MUST support this attribute if it supports setting the
   "printer-xri-supported" (1setOf collection) with the Set-Printer-
   Attributes operation.

6.9 xri-security-supported (1setOf type2 keyword)

   This OPTIONAL READ-ONLY Printer Description attribute identifies the
   URI schemes that the implementation supports for use in the "printer- "uri-
   security-supported" (1setOf type2 keyword) Printer Description
   attribute (see [ipp-mod] [RFC2911] section 4.4.3) and the "xri-security" member
   attribute of the "xri-printer-supported" (1setOf collection) Printer
   Description attribute (see section 6.6).

   A Printer MUST support this attribute if it supports setting the
   "printer-xri-supported" (1setOf collection) with the Set-Printer-
   Attributes operation.

7  Additional status codes

   This section defines new status codes used by the operations defined
   in this document.

7.1 'client-error-attributes-not-settable' (0x0413)

   The Set-Printer-Attributes or Set-Job-Attributes operation failed
   because one or more of the specified attributes cannot be set either
   because the attribute is defined to be READ-ONLY or the attribute is
   not settable in this implementation (see sections 4.1.3 and 4.2.3),
   the Printer MUST return this error code and the attribute keyword
   name(s) and the 'not-settable' out-of-band value (see section 8.1) in
   the Unsupported Attributes Group(see [ipp-mod] [RFC2911] section 3.1.7) for all
   of the attributes that could not be set. When the Printer returns
   this status, it MUST NOT change any of the attributes supplied in the
   operation.

                     Expires:  September 23, 2000

8  Additional out-of-band values

   This section defines additional out-of-band values.  As with all out-of-
band out-
   of-band values, a client or a Printer MUST NOT use an out-of-band
   value unless the definition of the attribute in an operation request
   and/or response explicitly allows such usage.  See the beginning of [ipp-mod]
   [RFC2911] section 4.1.

8.1 'not-settable' out-of-band value

   The 'not-settable' out-of-band attribute value is returned by the IPP
   Printer in the Unsupported Attributes group of a response to indicate
   that the attribute supplied by the client in the request is READ-ONLY
   by definition or is not settable in this implementation.

   The 'not-settable' out-of-band attribute value is defined for use
   with the Set-Job-Attributes and Set-Printer-Attributes response only.
   If a future additional "set" operation allows the 'not-settable' out-of-band out-
   of-band value, its definition document MUST indicate such use
   explicitly, including with which attributes.

   An IPP object MUST support the 'not-settable' out-of-band value in a
   Set-Job-Attributes or Set-Printer-Attributes request if it supports
   those operations.  A client MUST NOT supply the 'not-settable' out-of-
band out-
   of-band value in any request.  An IPP object MUST NOT support the 'not-
settable'
   'not-settable' out-of-band value in other operations, unless the
   operations' definition document explicitly defines such usage.  If a
   Printer receives this out-of-band value in any operation request, the
   Printer MUST either (1) reject the entire request and return the 'client-error-
bad-request'
   'client-error-bad-request' status code or (2) ignore the attribute
   and return it with the 'unsupported' out-of-band value.

   See sections 4.1.3 and 4.2.3 in this document for an example
   definition of the usage of the 'not-settable' out-of-band value in
   the Set-Printer-
Attributes Set-Printer-Attributes and Set-Job-Attributes responses.

8.1.1Encoding

8.1.1     Encoding of the 'not-settable' out-of-band attribute value

   The encoding of the 'not-settable' out-of-band value is 0x15 (see [ipp-
pro]).
   [RFC2910]).  The value-length MUST be 0 and the value empty.

8.2 'delete-attribute' out-of-band value

   The 'delete-attribute' out-of-band attribute value is supplied by the
   client in a request to indicate that the Printer is to remove the
   supplied attribute and all of its values from the target object, if
   present.

   The 'delete-attribute' out-of-band attribute value is defined for use
   with the Set-Job-Attributes request only.  If a future additional
   "set" operation allows the 'delete-attribute' out-of-band value, its

                     Expires:  September 23, 2000
   definition document MUST indicate such use explicitly, including with
   which attributes.

   An IPP Printer MUST support the 'delete-attribute' out-of-band value
   if it supports the Set-Job-Attributes operation.  A client MUST NOT
   supply and an IPP object MUST NOT support the 'delete-attribute' out-of-band out-
   of-band value in other operations, unless the operations' definition
   document explicitly defines such usage.  For example, the 'delete-attribute' out-
of-band 'delete-
   attribute' out-of-band value MUST NOT be used in the Set-Printer-Attributes Set-Printer-
   Attributes operation, where the absence of an attribute from an IPP
   object indicates that the attribute is not supported.  If a Printer
   receives this out-of-band value in other operation requests, the
   Printer MUST either (1) reject the entire request and return the
   'client-error-bad-request' status code or (2) ignore the attribute
   and return it with the 'unsupported' out-of-
band out-of-band value.

   See section 4.2 in this document for the definition of the usage of
   the 'delete-attribute' out-of-band value in the Set-Job-Attributes
   request.

8.2.1Encoding

8.2.1     Encoding of the 'delete-attribute' out-of-band value

   The encoding of the 'delete-attribute' out-of-band value is 0x16 (see
[ipp-pro]).
   [RFC2910]).  The value-length MUST be 0 and the value empty.

8.3 'admin-define' out-of-band attribute value

   Section 4.3 defines the Get-Printer-Supported-Values response to
   contain the values of an "xxx-supported" attribute that are supported
   by the implementation before any additional value are defined by the
   administrator.  The 'admin-define' out-of-band attribute value is
   returned as an additional value of an "xxx-supported" attribute in a
   Get-Printer-Supported-Values response to  indicate that the
   implementation supports allowing an administrator to define
   additional arbitrary 'name' values for that "xxx-supported"
   attribute.

   For example, if the "media-supported" (1setOf (type3 keyword | name))
   attribute contains this value, then the Printer MUST permit an
   administrator to add new media names to the Printer's "media-supported"
attribute. "media-
   supported" attribute.  In order for an administrator to add new
   values to a Printer's "xxx-supported" attribute, the client supplies
   the existing and new values in a Set-Printer-Attributes request for
   that attribute.  The client MUST supply any such administratively
   defined values in the Set-Printer-Attributes request using the 'name'
   attribute syntax.

   The 'admin-define' out-of-band attribute value is defined for use
   with the Get-Printer-Supported-Values response only.  A Printer MUST
   NOT return the 'admin-define' out-of-band value in a Get-Printer-Attributes Get-Printer-
   Attributes response, since such a response indicates what an end-user
   client can supply in a Job Creation operation.  If a future
   additional "get" operation allows the 'admin-define' out-of-band
   value, its definition document MUST indicate such use explicitly,
   including with which attributes.

                     Expires:  September 23, 2000

   An IPP Printer MUST support the 'admin-define' out-of-band value, if
   it supports a client setting arbitrary 'name' values of an "xxx-supported" "xxx-
   supported" Printer attribute using the Set-Printer-Attributes
   operation.  A client MUST NOT supply the 'admin-define' out-of-band
   value in any request.  An IPP object MUST NOT support the 'admin-define' 'admin-
   define' out-of-band value in other operations, unless the operations'
   definition document explicitly defines such usage.  If a Printer
   receives this out-of-band value in any operation request, the Printer
   MUST either (1) reject the entire request and return the 'client-error-bad-request' 'client-
   error-bad-request' status code or (2) ignore the attribute and return
   it with the 'unsupported' out-of-band value.

   This document defines that the 'admin-define' out-of-band value MUST
   be used only with "xxx-supported" attributes that are defined to
   include the 'name' attribute syntax.  This out-of-band value is not
   intended to be used with "xxx-supported" attributes of other
   attribute syntaxes, such as 'uri', even though the administrator
   defines arbitrary values for such attributes.  If other documents
   extend the use of the 'admin-
define' 'admin-define' out-of-band value to other
   attribute syntaxes, such a document MUST define such use explicitly,
   including with which attributes.

   See section 4.3 in this document for an example definition of the
   usage of the 'admin-define' out-of-band attribute value in any "xxx-supported" "xxx-
   supported" attribute returned in a Get-Printer-Supported-Values
   response that is defined to include the 'name' attribute syntax.

8.3.1Encoding

8.3.1     Encoding of the 'admin-define' out-of-band attribute value

   The encoding of the 'admin-define' out-of-band attribute value is
   0x17 (see [ipp-pro]). [RFC2910]).  The value-length MUST be 0 and the value
   empty.

9  Conformance Requirements

   This section specifies the conformance requirements for clients and
   IPP objects.

   Both the Set-Job-Attributes and the Set-Printer-Attributes operations
   defined in the document are OPTIONAL for an IPP object to support.
   Either one MAY be supported without the other or both MAY be
   supported.  However, if the Set-Printer-Attributes operation is
   supported, then the Get-Printer-Supported-Values operation MUST be
   supported if any "xxx-
supported" "xxx-supported" attributes are settable.  Otherwise,
   the Get-Printer-
Supported-Values Get-Printer-Supported-Values operation is OPTIONAL for an IPP
   Printer to support.

   If the Set-Printer-Attributes operation is supported, then the
   Printer MUST support the following additional items:

     1.the Get-Printer-Supported-Values operation (see section 5), if
       any "xxx-supported" attributes are settable.

     2.the "printer-settable-attributes-supported" Printer Description
       attribute (see section 6.1)

                     Expires:  September 23, 2000

     3.the 'not-settable' out-of-band value in responses (see section
       8.1)

     4.the 'client-error-not-settable' status code (see section 7.1)

     5.If "printer-message-from-operator" Printer Description attribute
       is supported (see [ipp-mod] [RFC2911] section 4.4.25), then it MUST be
       settable.

     6.the Get-Printer-Supported-Values operation (see section 4.3), if
       any "xxx-supported" attributes are settable.

     7.If a client can set a value with the 'name' attribute syntax for
       one or more "xxx-supported" attributes, then the 'admin-define'
       out-of-band attribute value (see section 8.3) MUST be supported
       in the Get-Printer-Supported-Values response for each such
       settable attribute (see section 4.3)

   If the Set-Job-Attributes operation is supported, then the Printer
   MUST support the following additional items:

     1.the "job-settable-attributes-supported " Printer Description
       attribute (see section 6.2)

     2.the 'not-settable' out-of-band value in responses (see section
       8.1)

     3.the 'delete-attribute' out-of-band value in requests (see
       section 8.2)

     4.the 'client-error-not-settable' status code (see section 7.1)

     5.If the "job-message-from-operator" Printer Description attribute
       is supported (see [ipp-mod] [RFC2911] 4.3.16), then it MUST be settable.

   It is OPTIONAL for the Printer object to support the "printer-message-
time" "printer-
   message-time" (integer) and "printer-message-date-time" (dateTime)
   Printer Description attributes.  If both the "printer-message-time"
   (integer) and the "printer-current-time" (dateTime) (see [ipp-mod] [RFC2911]
   section 4.4.30) attributes are supported, then the "printer-message-date-time" "printer-message-
   date-time" (dateTime) Printer Description attribute MUST be
   supported.

   As with all out-of-band values, a client or a Printer MUST NOT use an
   out-of-band value unless the definition document for the attribute in
   an operation request and/or response explicitly allows such usage.

10 IANA Considerations

Since this document is intended

   This section contains the exact information for IANA to be a standards track document, there
is no need add to also register the operations, attributes, status codes,
and out-of-band values defined here-in with IANA
   IPP Registries according to the procedures defined in RFC 2566 [rfc2566] 2911
   [RFC2911] section 6.  However, other registration

                     Expires:  September 23, 2000

proposals may site the out-of-band attribute values or

    Note to RFC Editors:  Replace RFC NNNN below with the status codes
defined in RFC number for
    this document.

11 Internationalization Considerations

This document has the same localization considerations as the [ipp-mod].

12 Security Considerations

The IPP Model and Semantics document [ipp-mod section 8] discusses high
level security requirements (Client Authentication, Server
Authentication and Operation Privacy). Client Authentication is document, so that it accurately reflects the
mechanism by which content of the client proves its identity to
    information for the server IANA Registry.

10.1 Operation Registrations

   The operations defined in a
secure manner. Server Authentication is the mechanism this document will be published by which the
server proves its identity IANA
   according to the client procedures in a secure manner. Operation
Privacy is defined as a mechanism for protecting operations from
eavesdropping.

In addition, RFC 2911 [RFC2911] section 6.4 with
   the introduction of following path:

     ftp.isi.edu/iana/assignments/ipp/operations/

   The registry entry will contain the following information:

   Operations:                                       Ref.      Section:
   Set-Printer-Attributes and Set-Job-
Attributes operations creates another security threat, since the client
is able                            RFC NNNN       4.1
   Set-Job-Attributes                                RFC NNNN       4.2
   Get-Printer-Supported-Values                      RFC NNNN       4.3

10.2 Attribute Registrations

   The attributes defined in this document will be published by IANA
   according to modify the Printer and Job attributes stored procedures in RFC 2911 [RFC2911] section 6.2 with
   the Printer.
Such modifications could lead to denial of service.

A malicious user could alter following path:

     ftp.isi.edu/iana/assignments/ipp/attributes/

   The registry entry will contain the policy established following information:

   Operation attributes:                             Ref.      Section:
   printer-message-from-operator (text(127))         RFC NNNN       5.1
   job-message-from-operator (text(127))             RFC NNNN       5.2

   Printer Description attributes:                   Ref.      Section:
   printer-settable-attributes-supported (1setOf type2 keyword)
                                                     RFC NNNN       6.1
   job-settable-attributes-supported (1setOf type2 keyword)
                                                     RFC NNNN       6.2
   document-format-varying-attributes (1setOf type2 keyword)
                                                     RFC NNNN       6.3
   printer-message-time (integer(MIN:MAX))           RFC NNNN       6.4
   printer-message-date-time (dateTime)              RFC NNNN       6.5
   printer-xri-supported (1setOf collection)         RFC NNNN       6.6
   xri-uri-scheme-supported (1setOf uriScheme)       RFC NNNN       6.7
   xri-authentication-supported (1setOf type2 keyword)              6.8
   xri-security-supported (1setOf type2 keyword)     RFC NNNN       6.9

10.3 Status code Registrations

   The status codes defined in this document will be published by IANA
   according to the system
administrator and stored procedures in RFC 2911 [RFC2911] section 6.6 with
   the Printer attributes.  Such alteration
could either grant access to more resources or deny access to resources
that following path:

     ftp.isi.edu/iana/assignments/ipp/status-codes/

   The registry entry will contain the system administrator has established.  For example, following information:

   Status codes:                                     Ref.      Section:
   'client-error-attributes-not-settable' (0x0413)   RFC NNNN       7.1

10.4 Out-of-band Attribute Value Registrations

   The out-of-band attribute values defined in this document will be
   published by IANA according to the
malicious user could remove all of procedures in RFC 2911 [RFC2911]
   section 6.7 with the document-format values from following path:

     ftp.isi.edu/iana/assignments/ipp/out-of-band-attribute-value-tags/

   The registry entry will contain the
"document-format-supported" Printer following information:

   Out-of-band Attribute Values:                     Ref.      Section:
   'not-settable' out-of-band value                  RFC NNNN       8.1
   'delete-attribute' out-of-band value              RFC NNNN       8.2
   'admin-define' out-of-band attribute so that value        RFC NNNN       8.3

11 Internationalization Considerations

   This document has the Printer would
refuse to accept all jobs. same localization considerations as the
   [RFC2911].

12 Security Considerations

   The general remedy for such malicious user actions against Printer
attributes is to have strong IPP Model and Semantics document [RFC2911 section 8] discusses
   high level security requirements (Client Authentication, Server
   Authentication and Operation Privacy). Client Authentication coupled with Printer
access control to limit is the users who
   mechanism by which the client proves its identity to the server in a
   secure manner. Server Authentication is the mechanism by which the
   server proves its identity to the client in a secure manner.
   Operation Privacy is defined as a mechanism for protecting operations
   from eavesdropping.

   In addition, the introduction of the Set-Printer-Attributes and Set-
   Job-Attributes operations creates another security threat, since the
   client is able to modify the Printer and Job attributes stored in the
   Printer.  Such modifications could lead to denial of service.

   A malicious user could alter the policy established by the system
   administrator and stored in the Printer attributes.  Such alteration
   could either grant access to more resources or deny access to
   resources that the system administrator has established.  For
   example, the malicious user could remove all of the document-format
   values from the "document-format-supported" Printer attribute so that
   the Printer would refuse to accept all jobs.

   The general remedy for such malicious user actions against Printer
   attributes is to have strong Client Authentication coupled with
   Printer access control to limit the users who have System
   Administrator or Operator privileges.

   A malicious user could modify the Job Template attributes of another
   user's Job, such as the "copies" attribute.  For example, setting the
   number of copies to a large number.

   The general remedy for such malicious user actions against another
   user's job is to have strong Client Authentication coupled with
   Printer access control to limit the users who have System
   Administrator or Operator privileges who can modify any job and, in
   addition, store the Client Authentication with each Job so that only
   the job owner End User can modify his/her own job.

13 Author's Addresses

   Carl Kugler

                     Expires:  September 23, 2000
   IBM
   P.O. Box 1900
   Boulder, CO 80301-9191

   Phone: (303) 924-5060
   FAX:
   e-mail:  kugler@us.ibm.com

   Tom Hastings
   Xerox Corporation
   737 Hawaii St.  ESAE 231
   El Segundo, CA  90245

   Phone: 310-333-6413
   Fax: 310-333-5514
   e-mail: hastings@cp10.es.xerox.com

   Robert Herriot
   Xerox Corp.
   3400 Hill View Ave, Building 1
   Palo Alto, CA 94304

   Phone: 650-813-7696
   Fax:    650-813-6860
   e-mail: robert.herriot@pahv.xerox.com

   Harry Lewis
   IBM
   P.O. Box 1900
   Boulder, CO 80301-9191

   Phone: (303) 924-5337
   FAX:
   e-mail:  harryl@us.ibm.com

14 References

   [ipp-coll]
     deBry, R., , Hastings, T., Herriot, R., "Internet Printing Protocol
     (IPP): The Collection Attribute Syntax", <draft-ietf-ipp-
     collection-02.doc>, work in progress, March 9, 2000.

[ipp-mod]
     R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
     "Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf-
     ipp-model-v11-06.txt>, March 1, 2000.

[ipp-pro]
     Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
     Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
     05.txt, March 1, 2000.

                     Expires:  September 23, 2000

   [ipp-set2]
     Kugler, C, Hastings, T., Lewis, H., "Internet Printing
     Protocol/1.1: Job and Printer Administrative Operations", <draft-
     ietf-ipp-ops-set2-01.txt>, December 8, 1999.

   [ldap-printer]
     Fleming, P., Jones, K., Lewis, H., McDonald, I., "Internet Printing
     Protocol (IPP): LDAP Schema for Printer Services", <draft-ietf-ipp-
     ldap-printer-schema-00.txt>, work in progress, March 8, 2000.

   [RFC2565]
     Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
     Protocol/1.0: Encoding and Transport", RFC 2565, April 1999.

   [RFC2566]
     R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
     "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
     April 1999.

[svrloc-printer]
     St. Pierre, P., Isaacson,

   [RFC2910]
     Herriot, R., Butler, S., McDonald, I., "Definition of the
     Printer Abstract Service Type v2.0", <draft-ietf-svrloc-printer-
     scheme-06.txt>, work in progress, March 8, Moore, P., Turner, R., "Internet Printing
     Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.

15 Change History

This section summarizes the changes.  Each sub-section is in reverse
chronological order.  Adding or removing ISSUES that don't change the
document are not listed here.

15.1Changes to the March 21, 2000 version to make the March 23, 2000
    version

The following changes have been made to the March 21, 2000 version to
make the March 23, 2000 version as a result of the IPP WG telecons and
mailing list discussion:

1.Changed the name of the 'custom' out-of-band value to 'admin-define'.

2.Tightened up the spec for 'admin-define' so that it cannot be used
  returned in a Get-Printer-Attributes response to allow users to
  submit arbitrary values in a Job Creation operation.  If that
  functionality is needed, it will have to be done with another out of
  band value.

3.Clarified that the 'admin-define' out-of-band value is only intended
  to be used with "xxx-supported" attributes in a Get-Printer-
  Supported-Values response that are defined to include the 'name'
  attribute syntax.  If other documents extend this usage, they MUST
  define for which attributes and operations.

                     Expires:  September 23, 2000

4.Added the definitions of the xri-uri-scheme-supported (1setOf
  uriScheme), xri-authentication-supported (1setOf type2 keyword), and
  xri-security-supported (1setOf type2 keyword) READ-ONLY Printer
  attributes that were only referred to.  Also made them returnable
  only in Get-Printer-Attributes, not Get-Printer-Supported-Values,
  since they are READ-ONLY and the administrator cannot change them.

5.Clarified that the few "xxx-supported" attributes that are single
  valued, are made 1setOf X in the Get-Printer-Supported-Values so that
  the implementation can indicate what possible values can be set.

6.Required the client to have administrator access rights in order to
  use the Get-Printer-Supported-Values operation, since its purpose is
  for administrators to use before doing a Set-Printer-Attributes
  operation.

7.Clarified that if an implementation supports setting arbitrary names
  in a Set-Printer-Attributes request, then it MUST support the 'admin-
  define' out-of-band value in the Get-Printer-Supported-Values
  response.

8.Copied the validation rules from the Implementer's Guide into
  Appendix A, since the IIG is not a standards track document.  Still
  refer to the IIG for additional non-normative explanation.

15.2Changes to the March 8, 2000 version to make the March 21, 2000
    version

The following changes have been made to the March 8, 2000 version to
make the March 21, 2000 version as a result of the IPP WG telecons and
mailing list discussion:

9.Changed the name of the 'any-value' out-of-band value to 'custom'.
  Removed the idea of encoding the attribute syntax that the 'custom'
  out-of-band value goes with.  Required the value length to be zero.
  Instead, the spec for the attribute or attribute syntax defines
  whether or not the 'custom' out-of-band value can be used.

10.  Clarified that the 'custom' out-of-band value can be used in
  combination with other values of an "xxx-supported" Printer
  attribute.

11.  Clarified that an implementation is not prevented from supporting
  some 'name' attribute values for "xxx-supported" out-of-the-box, if
  desired.  But these values would be returned in a Get-Printer-
  Supported-Values response, such like keywords are.

                     Expires:  September 23, 2000

15.3Changes to the March 1, 2000 version to make the March 8, 2000
    version

The following changes have been made to the March 1, 2000 version to
make the March 8, 2000 version as a result of the IPP WG telecons and
mailing list discussion:

1.Added the "printer-xri-supported" (1setOf collection) attribute so
  that the three parallel IPP/1.1 "printer-uri-supported", "uri-
  authentication-supported", and "uri-security-supported" attributes
  could be set as one atomic attribute.  Consequently, changed the
  three parallel attributes to be READ-ONLY and removed the requirement
  that three attributes MUST be set in a single request if the three
  parallel IPP/1.1 "printer-uri-supported", "uri-authentication-
  supported", and "uri-security-supported" were settable.

2.Clarified Get-Printer-Supported-Values so that if an implementation
  does not support setting a settable attribute, it MUST NOT return the
  attribute in the Printer Attribute group and it NEED NOT return the
  attribute in the Unsupported Attributes group, same as in a Get-
  Printer-Attributes response for unsupported attributes.  Same
  clarification when unsupported attributes are requested.

3.Fixed "printer-message-date-time" (dateTime) attribute to be
  OPTIONAL.

4.Added note as to why the "printer-current-time" Printer Description
  attribute is settable (to fix an incorrect time or time zone).

5.Added "xri-authentication-supported" (1setOf type2 keyword) and "xri-
  security-supported" (1setOf type2 keyword) attributes to the table of
  attributes that can be queried with Get-Printer-Supported-Values.
  Added a note that these two attributes are NOT queriable with Get-
  Printer-Attributes, since the client queries either (1) the three
  "printer-uri-supported" (1setOf uri), "uri-authentication-supported"
  (1setOf type2 keyword), "uri-security-supported" (1setOf type2
  keyword) attributes, or (2) the single "printer-xri-supported"
  (1setOf collection) attribute.

15.4Changes to the January 30, 2000 version to make the March 1, 2000
    version

The following changes to the January 30, 2000 version to make the March
1, 2000 version as a result of the IPP WG telecons and mailing list
discussion:

1.Clarified that this extension may be used with any IPP version,
  including 1.0, 1.1, and future versions.

2.Added "READ-ONLY" and "not-settable" terms to the terminology
  section.  READ-ONLY is by definition, and "not-settable" is by
  implementation.

                     Expires:  September 23, 2000

3.Assigned the "operation-id" values 0x0013, 0x0014, and 0x0015,
  respectively, for the Set-Printer-Attributes, Set-Job-Attributes, and
  Get-Printer-Supported-Values operations.

4.Clarified that the Set-Printer-Attributes operation while a Printer
  SHOULD accept a reasonable number of attribute, the Printer need only
  support setting one attribute in a request, unless it supports
  setting the three "parallel" attributes, ("printer-uri-supported",
  "uri-authentication-supported", and "uri-security-supported" (see
  [ipp-mod] sections 4.4.1 through 4.4.3), in which case it MUST
  support setting at least three attributes in a single request.

5.Clarified that for the Set-Printer-Attributes operation the Printer
  MUST validate all of the supplied attributes in combination with each
  other, as well as with all of the existing attribute of the Printer
  object Set-Printer-Attributes.

6.Changed the requirements for accepting the Set-Printer-Attributes
  operation when the Printer is in the 'stopped' state from MUST to
  SHOULD, since some implementations may not be able to accept requests
  when stopped.

7.Clarified that setting certain Printer attributes with Set-Printer-
  Attributes MAY require more access rights than other attributes,
  i.e., System Administrator rights to set policy and only Operator
  rights to set the configuration attributes to reflect the current
  hardware setup.

8.Clarified the order of error checking and what is returned in each
  case in the Set-Printer-Attributes response.

9.Changed the 'default' out-of-band value to 'delete-attribute' out-of-
  band value so that the effect is to actually remove the Job attribute
  entirely in the Set-Job-Attribute operation.

10.  Clarified that removing a Job attribute that is not present is not
  an error.

11.  Clarified the validation of the Set-Job-Attributes request and what
  is returned for each error.

12.  Changed the 'any-name' out-of-band attribute value to a more
  general 'any-value' out-of-band attribute value which in combination
  with an attribute syntax represents any value of that attribute
  syntax.  The 'any-value' value can be used with the 'name' attribute
  syntax in a Get-Printer-Supported-Values response to indicate whether
  or not a Set-Printer-Attributes will accept any name to be set for
  particular "xxx-supported" (1setOf name | ...) Printer attributes.

13.  Clarified that "printer-message-from-operator" and "job-message-
  from-operator" both REQUIRE that the Printer accept zero-length
  messages and the 'no-value' out-of-band value is synonymous with
  removing any value from these Printer attributes.

                     Expires:  September 23, 2000

14.  Clarified that the Get-Printer-Supported-Values is REQUIRED only if
  the Set-Printer-Attributes operation will accept setting some  "xxx-
  supported" Printer attributes.

15.  Changed the IANA Considerations to indicate that the operations,
  attributes, status codes, and out-of-band-values won't be registered
  and published by IANA, since this document is intended to be
  standards track.

16.  Added security considerations for denial of service and sabotage
  because of the Set operations.

15.5Changes to the January 20, 2000 version to make the January 30, 2000
    version

The following changes to the January 20, 2000 version to make the
January 30, 2000 version as a result of the IPP WG telecons and mailing
list discussion:

1.Deleted the "document-format-varying-scope" operation attribute from
  the Set-Printer-Attributes operation and made whether or not the
  "document-format" operation was present determine whether one or all
  document formats are affected, respectively.

2.Renamed the Get-Reset-Printer-Attributes operation to Get-Printer-
  Supported-Values, so that it only returns "xxx-supported" values.
  Relegate obtaining reset values to another operation to be paired
  with the Reset-Printer operation in the Set2 [ipp-set2] document.

3.Added "-supported" to the names of the "printer-settable-attributes"
  and "job-settable-attributes" Printer Description attributes, so that
  they could be returned in Get-Printer-Supported-Values and could be
  set by Set-Printer-Attributes.

4.Deleted "authentication-methods-supported" (1setOf type2 keyword) and
  "security-methods-supported" (1setOf type2 keyword) and clarified
  that "uri-authentication-supported" (1setOf type2 keyword) and "uri-
  security-supported" (1setOf type2 keyword) can return multiple
  keywords of the same value in a Get-Printer-Supported-Values
  operation.

15.6Changes to the January 4, 2000 version to make the January 20, 2000
    version

The following changes to the January 4, 2000 version to make the January
4, 2000 version as a result of the IPP WG telecons and mailing list
discussion:

1.Replaced the "factory-settings" operation attribute proposed to be
  added to the Get-Printer-Attributes operation with the Get-Rest-
  Printer-Attributes operation which returns the reset values and the
  possible "xxx-supported" values.

                     Expires:  September 23, 2000

2.Added the out-of-band 'any-name' value to be used with "xxx-
  supported" attributes with attribute syntax 'type3 keyword | name' to
  indicate that any name will be accepted in a Job Creation operation
  for configurations that support such a concept.

3.Added authentication-methods-supported (1setOf type2 keyword) and
  security-methods-supported (1setOf type2 keyword) Printer Description
  attributes so that clients can discover the possible values for use
  in Set-Printer-Attributes to set "uri-authentication-supported" and
  "uri-security-supported" attributes, since the Reset-Printer
  operation doesn't change them.

4.Added validation rules that the Printer MUST use to validate a Set-
  Printer-Attributes request.

5.Clarified that the Set-Printer-Attributes operation MUST NOT have any
  side effects on other attributes, unless explicitly specified in this
  document.

6.Moved the specification of the attributes that MUST be READ-ONLY to
  Appendix A.

7.Added the "document-format-varying-attributes" (1setOf type2 keyword)

8.Added the REQUIRED "document-format-varying-scope" operation
  attribute to Set-Printer-Attributes in order to control whether one
  or all document formats are affected for those attributes that vary
  by document format.

9.Clarified that the Printer returns the 'client-error-attributes-not-
  settable' status code in a Set-Printer-Attributes response whether
  the attribute is READ-ONLY, the attribute is not supported, or the
  value is not supported.

10.  Added the out-of-band 'default' value for use with Set-Job-
  Attributes and Job Creation operations.

11.  Deleted the "printer-message-operation" Printer Description
  attribute.

12.  Made the "Get-Reset-Printer-Attributes" operation, along with the
  "authentication-methods-supported" and the "security-methods-
  supported" Printer Description attributes REQUIRED, if the Set-
  Printer-Attributes operation is supported.

13.  Made the  'not-settable' out-of-band value

   [RFC2911]
     R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
     "Internet Printing Protocol/1.0: Model and the 'client-error-
  not-settable' status code REQUIRED, if the Set-Printer-Attributes
  operation is supported.

14.  Made the 'default' out-of-band value REQUIRED, if the Set-Job-
  Attributes operation is supported.

15.  Removed the requirement that "xxx-supported" Printer Description
  attributes that contain only one value be read-only.

                     Expires: Semantics", RFC 2911,
     September 23, 2000

15.7Changes to the December 8, 1999 version to make the January 4, 2000
    version

The following changes to the December 8, 1999 version to make the
January 4, 2000 version as a result 2000.

   [svrloc-printer]
     St. Pierre, P., Isaacson, S., McDonald, I., "Definition of the IPP WG telecons and mailing
list discussion:

1.Removed the Set operations and related items from the Set2
  specification [ipp-set2] to create this Set specification.

2.Added that an attribute that can only be set to one fixed value
  SHOULD NOT be included
     Printer Abstract Service Type v2.0", <draft-ietf-svrloc-printer-
     scheme-06.txt>, work in the "printer-settable-attributes" or "job-
  settable-attributes" attributes.

3.Indicated that the encoding of the 'not-settable' out-of-band value
  is TBD.

4.Added that Set-Job-Attributes operation adds an attribute to the Job
  object if it wasn't already there

5.Added the conformance section to make it easy to understand the
  conformance requirements.

                     Expires:  September 23, 2000

16 progress, March 8, 2000.

15 Appendix A: Allowed Values for Set-Printer-Attributes and Set-Job-
   Attributes requests

   This appendix is a normative part of this document and contains a
   table of all IPP/1.1 attributes.  Each row contains:

     @

     . an attribute and

     @

     . the values allowed in the Set-Printer-Attributes or Set-Job-
       Attributes request for the attribute.  The entry in each cell is
       the name (first few words) of each item below 1, 2, 3, 4a-g, and
       5.

   The allowed values include the following cases:

  1. READ-ONLY:

   1.READ-ONLY:  the Set-Printer-Attributes or Set-Job-Attributes
     operation MUST NOT change this attribute and MUST reject the
     entire operation (see section 7.1).

  2. Any

   2.Any of  "xxx-supported":  the  Set-Printer-Attributes or Set-Job-
     Attributes operation accepts values that are allowed according to
     the IPP/1.1 rules for validating the value(s) of an "xxx" Printer
     or Job attribute against the value(s) of the corresponding "xxx-
     supported" Printer attribute.  Table 4 summarizes those validation
     rules depending on each attribute syntax and value of an "xxx"
     attribute supplied in the request and that of the corresponding
     "xxx-supported" Printer attribute.  The "xxx-supported" attribute
     syntax type and value(s) are obtained from a Get-Printer-Supported-
     Values Get-Printer-
     Supported-Values response (see the tables in this Appendix).

         Table 4 - Validation rules for 'Any of "xxx-supported" '

     Type of "xxx" value  Type of "xxx-      Validates if:
     value to be set    supported" value
     set

     integer        rangeOfInteger     each value is in one of the
                                       "xxx-supported" ranges

     uri            uriScheme          each uri scheme matches one
                                       of the "xxx-
                                               supported" "xxx-supported"
                                       schemes

     any            boolean            if the boolean "xxx-
                                       supported" is 'true'

     any            same type          each value matches an
                                               "xxx-supported" "xxx-
                                       supported" value of the same
                                       type

     For additional non-normative explanatory information see section
     3.1.2.3 of the "Internet Printing Protocol/1.1: Implementer's
     Guide" [ipp-iig]).

  3. From Get-Printer-Supported-Values:  the  Set-Printer-Attributes
     operation accepts values that are allowed according to the IPP/1.1
     rules for validating the value(s) of an "xxx" Printer attribute
     against the value(s) of the corresponding "xxx-supported" Printer
     attribute.  Table 5 summarizes those validation rules depending on

                     Expires:  September 23, 2000
     each attribute syntax and value of an "xxx" attribute supplied in
     the request and that of the corresponding "xxx-supported" Printer
     attribute.  The "xxx-supported" attribute syntax type and attribute
     value(s) are obtained from a Get-Printer-Supported-Values response
     (see Appendix B: Attributes returned from Get-Printer-Supported-
     Values below).

    Table 5 - Validation rules for 'From Get-Printer-Supported-Values'

     Type of "xxx" value     Type of "xxx-     Validates if:
     "xxx"       supported" value
     value to
     be set            supported" value

     integer     rangeOfInteger    each 'integer' value is in one of
                                   the "xxx-
                                               supported" "xxx-supported" ranges

     uri         uriScheme         the uri scheme of each value
                                   matches one of the "xxx-supported"
                                   schemes

     any         boolean           if the boolean "xxx-
                                               supported" "xxx-supported" is
                                   'true'

     name        'admin-define' out-    any 'name' value
                           of-band value matches
                 out-of-band
                 value

     any         same type         each value matches an
                                               "xxx-supported" "xxx-
                                   supported" value of the same type

     For additional non-normative explanatory information see section
     3.1.2.3 of the "Internet Printing Protocol/1.1: Implementer's
     Guide" [ipp-iig]).

  4. Any value of the proper attribute syntax:  the Set-Printer-
     Attributes or Set-Job-Attributes operation accepts any value of the
     specified attribute syntax.  The attribute syntaxes supported are
     enumerated below.

     a.Any text(127)
     b.Any name(127)
     c.Any uri
     d.Any boolean
     e.Any positive integer
     f.Any dateTime
     g.1setOf any uri

  5. Combination of 'Any of "xxx-supported"' or 'Any name'.

   If a Printer implementation doesn't want to allow setting values
   indicated in this Appendix as "any xxx", it can make the value be not-
settable.
   not-settable.

   Table 6 - Values allowed for Job Template Attributes in the Set-Job-
                           Attributes Operation

    Job Template Attributes                      Values allowed for
                                                 Set

    job-priority (integer(1:100))                Any of  "xxx-supported"

                     Expires:  September 23, 2000

Job Template Attributes                      Values allowed for Set  "xxx-
                                                 supported"

    job-hold-until (type3 keyword | name (MAX))  Any of  "xxx-supported"  "xxx-
                                                 supported"

    job-sheets (type3 keyword | name(MAX))       Any of  "xxx-supported"  "xxx-
                                                 supported"

    multiple-document-handling (type2 keyword)   Any of  "xxx-supported"  "xxx-
                                                 supported"

    copies (integer(1:MAX))                      Any of  "xxx-supported"  "xxx-
                                                 supported"

    finishings (1setOf type2 enum)               Any of  "xxx-supported"  "xxx-
                                                 supported"

    page-ranges (1setOf rangeOfInteger (1:MAX))  Any of  "xxx-supported"  "xxx-
                                                 supported"

    sides (type2 keyword)                        Any of  "xxx-supported"  "xxx-
                                                 supported"

    number-up (integer(1:MAX))                   Any of  "xxx-supported"  "xxx-
                                                 supported"

    orientation-requested (type2 enum)           Any of  "xxx-supported"  "xxx-
                                                 supported"

    media (type3 keyword | name(MAX))            Any of  "xxx-supported"  "xxx-
                                                 supported"

    printer-resolution (resolution)              Any of  "xxx-supported"  "xxx-
                                                 supported"

    print-quality (type2 enum)                   Any of  "xxx-supported"  "xxx-
                                                 supported"
    Table 7 - Values allowed for Job Description Attributes in the Set-Job-
                          Attributes Set-
                         Job-Attributes Operation

    Job Description Attributes                   Values allowed for
                                                 Set

    job-uri (uri)                                READ-ONLY

    job-id (integer(1:MAX))                      READ-ONLY

    job-printer-uri (uri)                        READ-ONLY

    job-more-info (uri)                          READ-ONLY

    job-name (name(MAX))                         Any name(MAX)

    job-originating-user-name (name(MAX))        READ-ONLY

    job-state (type1 enum)                       READ-ONLY

    job-state-reasons (1setOf  type2 keyword)    READ-ONLY

    job-state-message (text(MAX))                READ-ONLY

    job-detailed-status-messages (1setOf text(MAX))         READ-ONLY
    text(MAX))

    job-document-access-errors (1setOf text(MAX))           READ-ONLY
    text(MAX))

    number-of-documents (integer(0:MAX))         READ-ONLY

    output-device-assigned (name(127))           READ-ONLY

    time-at-creation (integer(MIN:MAX))          READ-ONLY

    time-at-processing (integer(MIN:MAX))        READ-ONLY

    time-at-completed (integer(MIN:MAX))         READ-ONLY

    job-printer-up-time (integer(1:MAX))         READ-ONLY

    date-time-at-creation (dateTime)             READ-ONLY
    Job Description Attributes                   Values allowed for
                                                 Set

    date-time-at-processing (dateTime)           READ-ONLY

    date-time-at-completed (dateTime)            READ-ONLY

    number-of-intervening-jobs (integer(0:MAX))  READ-ONLY

    job-message-from-operator (text(127))        Any text(127)

    job-k-octets (integer(0:MAX))                READ-ONLY

    job-impressions (integer(0:MAX))             READ-ONLY

    job-media-sheets (integer(0:MAX))            READ-ONLY

    job-k-octets-processed (integer(0:MAX))      READ-ONLY

    job-impressions-completed (integer(0:MAX))   READ-ONLY

    job-media-sheets-completed (integer(0:MAX))  READ-ONLY

    attributes-charset (charset)                 READ-ONLY

    attributes-natural-language (naturalLanguage)                  READ-ONLY

                     Expires:  September 23, 2000
    (naturalLanguage)
    Table 8 - Values allowed for Printer Job Template Attributes in the Set-
                      Printer-Attributes
                     Set-Printer-Attributes Operation

    Printer Job Template Attributes                 Values allowed
                                                    for Set

    job-priority-default (integer(1:100))           Any of  "xxx-supported"  "xxx-
                                                    supported"

    job-hold-until-default (type3 keyword | name    Any of  "xxx-supported"
name  "xxx-
    (MAX))                                          supported"

    job-sheets-default (type3 keyword | name(MAX))  Any of  "xxx-supported"
name(MAX))  "xxx-
                                                    supported"

    multiple-document-handling-default (type2       Any of  "xxx-supported"  "xxx-
    keyword)                                        supported"

    copies-default (integer(1:MAX))                 Any of  "xxx-supported"  "xxx-
                                                    supported"

    finishings-default (1setOf type2 enum)          Any of  "xxx-supported"  "xxx-
                                                    supported"

    sides-default (type2 keyword)                   Any of  "xxx-supported"  "xxx-
                                                    supported"

    number-up-default (integer(1:MAX))              Any of  "xxx-supported"  "xxx-
                                                    supported"

    orientation-requested-default (type2 enum)      Any of  "xxx-supported"  "xxx-
                                                    supported"

    media-default (type3 keyword | name(MAX))       Any of  "xxx-supported"  "xxx-
                                                    supported"

    printer-resolution-default (resolution)         Any of  "xxx-supported"  "xxx-
                                                    supported"

    print-quality-default (type2 enum)              Any of  "xxx-supported"  "xxx-
                                                    supported"

    job-priority-supported (integer(1:100))         From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values
    Printer Job Template Attributes                 Values allowed
                                                    for Set

    job-hold-until-supported (1setOf(type3       From Get-Printer- keyword  From Get-
    | name (MAX)))                                  Printer-
                                                    Supported-Values

    job-sheets-supported (1setOf(type3 keyword   From Get-Printer- |    From Get-
    name(MAX)))                                     Printer-
                                                    Supported-Values

    multiple-document-handling-supported         From Get-Printer- (1setOf    From Get-
    type2 keyword)                                  Printer-
                                                    Supported-Values

    copies-supported (rangeOfInteger(1:MAX))        From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values

    finishings-supported (1setOf type2 enum)        From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values

    page-ranges-supported (boolean)                 From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values

    sides-supported (1setOf type2 keyword)          From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values

    number-up-supported (1setOf (integer(1:MAX)  From Get-Printer- |   From Get-
    rangeOfInteger(1:MAX)))                         Printer-
                                                    Supported-Values

    orientation-requested-supported (1setOf      From Get-Printer- type2   From Get-
    enum)                                           Printer-
                                                    Supported-Values

    media-supported (1setOf (type3 keyword |        From Get-Printer- Get-
    name(MAX)))                                     Printer-
                                                    Supported-Values

    printer-resolution-supported (1setOf            From Get-Printer- Get-
    resolution)                                     Printer-
                                                    Supported-Values
    Printer Job Template Attributes                 Values allowed
                                                    for Set

    print-quality-supported (1setOf type2 enum)     From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values

    media-ready (type3 keyword | name(MAX))         From Get-Printer- Get-
                                                    Printer-
                                                    Supported-Values
    Table 9 - Values allowed for Printer Description Attributes in the Set-
                      Printer-Attributes
                     Set-Printer-Attributes Operation

    Printer Description Attributes               Values allowed for
                                                 Set

                     Expires:  September 23, 2000

Printer Description Attributes                  Values allowed for
                                                 Set

    printer-uri-supported (1setOf uri)           READ-ONLY

    uri-authentication-supported (1setOf type2   READ-ONLY
    keyword)

    uri-security-supported (1setOf type2 keyword)         READ-ONLY
    keyword)

    printer-xri-supported (1setOf collection)
    member attributes:

      xri-uri (uri)                              any uriScheme of
                                                 "xri-uri-scheme-
                                                 supported" from Get-
                                                 Printer-Attributes
                                                 Get-Printer-
                                                 Attributes

      xri-authentication (1setOf type2 keyword)  any keyword of
                                                 "xri-
                                                 authentication-
                                                 supported" from Get-
                                                 Printer-Attributes
                                                 Get-Printer-
                                                 Attributes

      xri-security (1setOf type2 keyword)        any keyword of "xri-
                                                 security-supported"
                                                 "xri-security-
                                                 supported" from
                                                 Get-Printer-
                                                 Attributes

    xri-uri-scheme-supported (1setOf uriScheme)  READ-ONLY

    xri-authentication-supported (1setOf type2   READ-ONLY
    keyword)

    xri-security-supported (1setOf type2 keyword)         READ-ONLY
    keyword)

    printer-name (name(127))                     Any name(127)
    Printer Description Attributes               Values allowed for
                                                 Set

    printer-location (text(127))                 Any text(127)

    printer-info (text(127))                     Any text(127)

    printer-more-info (uri)                      Any uri

    printer-driver-installer (uri)               Any uri

    printer-make-and-model (text(127))           Any text(127)

    printer-more-info-manufacturer (uri)         Any uri

    printer-state (type1 enum)                   READ-ONLY

    printer-state-reasons (1setOf type2 keyword)          READ-ONLY
    keyword)

    printer-state-message (text(MAX))            READ-ONLY

    ipp-versions-supported (1setOf type2 keyword)         From Get-Printer-
    keyword)                                     Supported-Values

    operations-supported (1setOf type2 enum)     From Get-Printer-
                                                 Supported-Values

    multiple-document-jobs-supported (boolean)   From Get-Printer-
                                                 Supported-Values

    charset-configured (charset)                 Any of  "xxx-
                                                 supported", use
                                                 "charset-supported"

    charset-supported (1setOf charset)           From Get-Printer-
                                                 Supported-Values

    natural-language-configured (naturalLanguage)                  Any of  "xxx-
    (naturalLanguage)                            supported", use
                                                 "generated-natural-
                                                 language-supported"

    generated-natural-language-supported (1setOf         From Get-Printer-
    (1setOf naturalLanguage)                     Supported-Values
    Printer Description Attributes               Values allowed for
                                                 Set

    document-format-default (mimeMediaType)      Any of  "xxx-
                                                 supported"

    document-format-supported (1setOf            From Get-Printer-

                     Expires:  September 23, 2000

Printer Description Attributes                  Values allowed for
                                                 Set
    mimeMediaType)                               Supported-Values

    printer-is-accepting-jobs (boolean)          READ-ONLY

    queued-job-count (integer(0:MAX))            READ-ONLY

    printer-message-from-operator (text(127))    Any text(127)

    color-supported (boolean)                    From Get-Printer-
                                                 Supported-Values

    reference-uri-schemes-supported (1setOf      From Get-Printer-
    uriScheme)                                   Supported-Values

    pdl-override-supported (type2 keyword)       From Get-Printer-
                                                 Supported-Values

    printer-up-time (integer(1:MAX))             READ-ONLY

    printer-current-time (dateTime)              Any dateTime **

    multiple-operation-time-out (integer(1:MAX))                  any positive
    (integer(1:MAX))                             integer

    compression-supported (1setOf type3 keyword)          From Get-Printer-
    keyword)                                     Supported-Values

    job-k-octets-supported (rangeOfInteger(0:MAX))                       From Get-Printer-
    (rangeOfInteger(0:MAX))                      Supported-Values

    job-impressions-supported                    From Get-Printer-
    (rangeOfInteger(0:MAX))                      Supported-Values

    job-media-sheets-supported                   From Get-Printer-
    (rangeOfInteger(0:MAX))                      Supported-Values

    pages-per-minute (integer(0:MAX))            READ-ONLY

    pages-per-minute-color (integer(0:MAX))      READ-ONLY
    Printer Description Attributes               Values allowed for
                                                 Set

    printer-settable-attributes-supported (1setOf        From Get-Printer-
    (1setOf type2 keyword)                       Supported-Values

    job-settable-attributes-supported (1setOf type2    From Get-Printer-
    type2 keyword)                               Supported-Values

    document-format-varying-attributes (1setOf   READ-ONLY
    type2 keyword)

    printer-message-time (integer(MIN:MAX))      READ-ONLY

    printer-message-date-time(dateTime)          READ-ONLY

   ** - The "printer-current-time" (dateTime) attribute is settable in
   order to allow an administrator to correct an incorrect dateTime or
   time zone.

17

16 Appendix B: Attributes returned from Get-Printer-Supported-Values

   This Appendix is a normative part of this document and lists all the
   attributes that are possible for an implementation to return in a Get-
Printer-Supported-Values
   Get-Printer-Supported-Values response, i.e., all the "xxx-supported"
   attributes that can be supplied in a Set-Printer-Attributes request.
   READ-ONLY attributes MUST NOT be returned in a Get-Printer-Supported-
   Values response and are indicated in the tables as "READ-ONLY - MUST
   NOT be returned."

   For the following attributes, the value allowed by the Set-Printer-
   Attributes operation MUST be a single integer value in the range
   specified by the value returned by the Get-Printer-Supported-Values
   operation.

                     Expires:  September 23, 2000

   Table 10 - Printer Job Template Attributes returned from Get-Printer-
                             Supported-Values

    Printer Job Template Attributes            Values Returned

    job-priority-supported (integer(1:100))    rangeOfInteger(1:100)

   For the following attributes, the value allowed by the Set-Printer-
   Attributes operation MUST be a single rangeOfInteger value whose
   bounds do not exceed those of  the range specified by the value
   returned by the Get-Printer-Supported-Values operation.

   Table 11 - Printer Job Template Attributes returned from Get-Printer-
                             Supported-Values

    Printer Job Template Attributes             Values Returned

    copies-supported (rangeOfInteger(1:MAX))    rangeOfInteger(1:MAX)

   The following table has the same criteria as the last, but is for
   Printer Description attributes.

   Table 12 - Printer Description Attributes returned from Get-Printer-
                             Supported-Values

    Printer Description Attributes            Values allowed for Set

    job-k-octets-supported                    rangeOfInteger(0:MAX)
    (rangeOfInteger(0:MAX))

    job-impressions-supported                 rangeOfInteger(0:MAX)
    (rangeOfInteger(0:MAX))

    job-media-sheets-supported                rangeOfInteger(0:MAX)
    (rangeOfInteger(0:MAX))

   For the following attributes, the value allowed by the Set-Printer-
   Attributes operation MUST be one or more integers and rangeOfInteger
   values, such that the integer values described by these integers and
   rangeOfInteger is the same as or a subset of the integers described
   by the integers and rangeOf Integer of value returned by the Get-Printer-
Supported-Values Get-
   Printer-Supported-Values operation.

   Table 13 - Printer Job Template Attributes returned from Get-Printer-
                             Supported-Values

    Printer Job Template Attributes              Values Returned

    number-up-supported (1setOf (integer(1:MAX)  1setOf (integer(1:MAX) |
    | rangeOfInteger(1:MAX)))                    rangeOfInteger(1:MAX))                    (integer(1:MAX) |
                                                 rangeOfInteger(1:MA
                                                 X))

   For the following attributes, the value allowed by the Set-Printer-
   Attributes operation MUST be one or more values, where each such
   value matches a value returned by the Get-Printer-Supported-Values
   operation. A keyword, enum, boolean, charset, naturalLanguage,
   uriScheme,

                     Expires:  September 23, 2000 mimeMediaType or resolution value matches if it is equal.
   For Job Template attributes with the attribute syntax 'type3 keyword
   | name', any 'name' attribute syntax value matches the 'admin-define'
   out-of-band value, if the implementation allows the administrator to
   set any name values for the attribute.

   Table 14 - Printer Job Template Attributes returned from Get-Printer-
                             Supported-Values

    Printer Job Template Attributes              Values Returned

    job-hold-until-supported (1setOf(type3       1setOf (type3
    keyword |
keyword | name (MAX)))                       'admin-define')                       keyword | 'admin-
                                                 define')

    job-sheets-supported (1setOf(type3 keyword   1setOf (type3 keyword |
    | name(MAX)))                                'admin-define')                                keyword | 'admin-
                                                 define')

    multiple-document-handling-supported         1setOf type2 keyword
    (1setOf type2 keyword)                       keyword

    finishings-supported (1setOf type2 enum)     1setOf type2 enum

    page-ranges-supported (boolean)              1setOf boolean **

    sides-supported (1setOf type2 keyword)       1setOf type2
                                                 keyword

    orientation-requested-supported (1setOf      1setOf type2 enum
    type2 enum)

    media-supported (1setOf (type3 keyword |     1setOf (type3
    name(MAX)))                                  keyword |
name(MAX)))                                  'admin-define') 'admin-
                                                 define')

    printer-resolution-supported (1setOf         1setOf resolution
    resolution)

    print-quality-supported (1setOf type2 enum)  1setOf type2 enum

   ** Note:  the Get-Printer-Supported-Values returns a '1setOf boolean'
   so that all possible values are indicated, while Get-Printer-Attributes Get-Printer-
   Attributes returns only a single 'boolean' value.

   The following table has the same criteria as the last, but is for
   Printer Description attributes.

   Table 15 - Printer Description Attributes returned from Get-Printer-
                             Supported-Values

    Printer Description Attributes               Values allowed for
                                                 Set

    printer-uri-supported (1setOf uri)           READ-ONLY - MUST
                                                 NOT be returned

    uri-authentication-supported (1setOf type2   READ-ONLY - MUST
    keyword)                                     NOT be
keyword) returned

    uri-security-supported (1setOf type2         READ-ONLY - MUST
    keyword)                                     NOT be
keyword) returned

    xri-printer-supported (1setOf collection)    MUST NOT be
                                                 returned; see next
                                                 three attributes
                                                 returned with
                                             Get-Printer-Attributes: Get-
                                                 Printer-Attributes:

    xri-uri-scheme-supported (1setOf uriScheme)  READ-ONLY - MUST
                                                 NOT be returned

    xri-authentication-supported (1setOf type2   READ-ONLY - MUST
    keyword)                                     NOT be
keyword) returned

    xri-security-supported (1setOf type2         READ-ONLY - MUST
    keyword)                                     NOT be

                     Expires:  September 23, 2000

Printer Description Attributes               Values allowed for Set

keyword) returned

    ipp-versions-supported (1setOf type2         1setOf type2 keyword
    keyword)                                     keyword

    operations-supported (1setOf type2 enum)     1setOf type2
                                                 keyword

    multiple-document-jobs-supported (boolean)   1setOf boolean **

    charset-supported (1setOf charset)           1setOf charset

    generated-natural-language-supported         1setOf naturalLanguage
    (1setOf naturalLanguage)                     naturalLanguage

    document-format-supported (1setOf            1setOf mimeMediaType
    mimeMediaType)                               mimeMediaType
    Printer Description Attributes               Values allowed for
                                                 Set

    color-supported (boolean)                    1setOf boolean **

    reference-uri-schemes-supported (1setOf      1setOf uriScheme
    uriScheme)

    pdl-override-supported (type2 keyword)       1setOf type2
                                                 keyword **

    compression-supported (1setOf type3          1setOf type3 keyword
    keyword)                                     keyword

    printer-settable-attributes-supported        1setOf type2 keyword
    (1setOf type2 keyword)                       keyword

    job-settable-attributes-supported (1setOf    1setOf type2 keyword
    type2 keyword)                               keyword

   ** Note:  the Get-Printer-Supported-Values returns a '1setOf X' so
   that all possible values are indicated, while Get-Printer-Attributes
   returns only a single 'X' value.

18

17 Appendix C: Full Copyright Statement

   Copyright (C) The Internet Society (1998,1999). (1998,1999,2000,2001). All Rights
   Reserved

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT

                     Expires:  September 23, 2000 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

                     Expires:  September 23, 2000