Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 2911

Internet Printing Protocol/1.1: Model and Semantics

Pages: 224
Obsoletes:  2566
Obsoleted by:  8011
Updated by:  33803382399639957472
Part 8 of 9 – Pages 173 to 204
First   Prev   Next

ToP   noToC   RFC2911 - Page 173   prevText

12. APPENDIX A: Terminology

This specification document uses the terminology defined in this section.

12.1 Conformance Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

12.1.1 NEED NOT

This term is not included in RFC 2119. The verb "NEED NOT" indicates an action that the subject of the sentence does not have to implement in order to claim conformance to the standard. The verb "NEED NOT" is used instead of "MAY NOT" since "MAY NOT" sounds like a prohibition.

12.2 Model Terminology

12.2.1 Keyword

Keywords are used within this document as identifiers of semantic entities within the abstract model (see section 4.1.2.3). Attribute names, some attribute values, attribute syntaxes, and attribute group names are represented as keywords.

12.2.2 Attributes

An attribute is an item of information that is associated with an instance of an IPP object. An attribute consists of an attribute name and one or more attribute values. Each attribute has a specific attribute syntax. All object attributes are defined in section 4 and all operation attributes are defined in section 3. Job Template Attributes are described in section 4.2. The client optionally supplies Job Template attributes in a create request (operation requests that create Job objects). The Printer object has associated attributes which define supported and default values for the Printer.
12.2.2.1 Attribute Name
Each attribute is uniquely identified in this document by its attribute name. An attribute name is a keyword. The keyword attribute name is given in the section header describing that
ToP   noToC   RFC2911 - Page 174
   attribute.  In running text in this document, attribute names are
   indicated inside double quotation marks (") where the quotation marks
   are not part of the keyword itself.

12.2.2.2 Attribute Group Name
Related attributes are grouped into named groups. The name of the group is a keyword. The group name may be used in place of naming all the attributes in the group explicitly. Attribute groups are defined in section 3.
12.2.2.3 Attribute Value
Each attribute has one or more values. Attribute values are represented in the syntax type specified for that attribute. In running text in this document, attribute values are indicated inside single quotation marks ('), whether their attribute syntax is keyword, integer, text, etc. where the quotation marks are not part of the value itself.
12.2.2.4 Attribute Syntax
Each attribute is defined using an explicit syntax type. In this document, each syntax type is defined as a keyword with specific meaning. The "Encoding and Transport" document [RFC2910] indicates the actual "on-the-wire" encoding rules for each syntax type. Attribute syntax types are defined in section 4.1.

12.2.3 Supports

By definition, a Printer object supports an attribute only if that Printer object responds with the corresponding attribute populated with some value(s) in a response to a query for that attribute. A Printer object supports an attribute value if the value is one of the Printer object's "supported values" attributes. The device behind a Printer object may exhibit a behavior that corresponds to some IPP attribute, but if the Printer object, when queried for that attribute, doesn't respond with the attribute, then as far as IPP is concerned, that implementation does not support that feature. If the Printer object's "xxx-supported" attribute is not populated with a particular value (even if that value is a legal value for that attribute), then that Printer object does not support that particular value.
ToP   noToC   RFC2911 - Page 175
   A conforming implementation MUST support all REQUIRED attributes.
   However, even for REQUIRED attributes, conformance to IPP does not
   mandate that all implementations support all possible values
   representing all possible job processing behaviors and features.  For
   example, if a given instance of a Printer supports only certain
   document formats, then that Printer responds with the "document-
   format-supported" attribute populated with a set of values, possibly
   only one, taken from the entire set of possible values defined for
   that attribute. This limited set of values represents the Printer's
   set of supported document formats.  Supporting an attribute and some
   set of values for that attribute enables IPP end users to be aware of
   and make use of those features associated with that attribute and
   those values.  If an implementation chooses to not support an
   attribute or some specific value, then IPP end users would have no
   ability to make use of that feature within the context of IPP itself.
   However, due to existing practice and legacy systems which are not
   IPP aware, there might be some other mechanism outside the scope of
   IPP to control or request the "unsupported" feature (such as embedded
   instructions within the document data itself).

   For example, consider the "finishings-supported" attribute.

      1) If a Printer object is not physically capable of stapling, the
         "finishings-supported" attribute MUST NOT be populated with the
         value of 'staple'.
      2) A Printer object is physically capable of stapling, however an
         implementation chooses not to support stapling in the IPP
         "finishings" attribute.  In this case, 'staple' MUST NOT be a
         value in the "finishings-supported" Printer object attribute.
         Without support for the value 'staple', an IPP end user would
         have no means within the protocol itself to request that a Job
         be stapled.  However, an existing document data formatter might
         be able to request that the document be stapled directly with
         an embedded instruction within the document data.  In this
         case, the IPP implementation does not "support" stapling,
         however the end user is still able to have some control over
         the stapling of the completed job.
      3) A Printer object is physically capable of stapling, and an
         implementation chooses to support stapling in the IPP
         "finishings" attribute. In this case, 'staple' MUST be a value
         in the "finishings-supported" Printer object attribute. Doing
         so, would enable end users to be aware of and make use of the
         stapling feature using IPP attributes.
ToP   noToC   RFC2911 - Page 176
   Even though support for Job Template attributes by a Printer object
   is OPTIONAL, it is RECOMMENDED that if the device behind a Printer
   object is capable of realizing any feature or function that
   corresponds to an IPP attribute and some associated value, then that
   implementation SHOULD support that IPP attribute and value.

   The set of values in any of the supported value attributes is set
   (populated) by some administrative process or automatic sensing
   mechanism that is outside the scope of this IPP/1.1 document.  For
   administrative policy and control reasons, an administrator may
   choose to make only a subset of possible values visible to the end
   user.  In this case, the real output device behind the IPP Printer
   abstraction may be capable of a certain feature, however an
   administrator is specifying that access to that feature not be
   exposed to the end user through the IPP protocol.  Also, since a
   Printer object may represent a logical print device (not just a
   physical device) the actual process for supporting a value is
   undefined and left up to the implementation.  However, if a Printer
   object supports a value, some manual human action may be needed to
   realize the semantic action associated with the value, but no end
   user action is required.

   For example, if one of the values in the "finishings-supported"
   attribute is 'staple', the actual process might be an automatic
   staple action by a physical device controlled by some command sent to
   the device.  Or, the actual process of stapling might be a manual
   action by an operator at an operator attended Printer object.

   For another example of how supported attributes function, consider a
   system administrator who desires to control all print jobs so that no
   job sheets are printed in order to conserve paper.  To force no job
   sheets, the system administrator sets the only supported value for
   the "job-sheets-supported" attribute to 'none'.  In this case, if a
   client requests anything except 'none', the create request is
   rejected or the "job-sheets" value is ignored (depending on the value
   of "ipp-attribute-fidelity").  To force the use of job start/end
   sheets on all jobs, the administrator does not include the value
   'none' in the "job-sheets- supported" attribute.  In this case, if a
   client requests 'none', the create request is rejected or the "job-
   sheets" value is ignored (again depending on the value of "ipp-
   attribute-fidelity").

12.2.4 print-stream page

A "print-stream page" is a page according to the definition of pages in the language used to express the document data.
ToP   noToC   RFC2911 - Page 177

12.2.5 impression

An "impression" is the image (possibly many print-stream pages in different configurations) imposed onto a single media page.

13. APPENDIX B: Status Codes and Suggested Status Code Messages

This section defines status code enum keywords and values that are used to provide semantic information on the results of an operation request. Each operation response MUST include a status code. The response MAY also contain a status message that provides a short textual description of the status. The status code is intended for use by automata, and the status message is intended for the human end user. Since the status message is an OPTIONAL component of the operation response, an IPP application (i.e., a browser, GUI, print driver or gateway) is NOT REQUIRED to examine or display the status message, since it MAY not be returned to the application. The prefix of the status keyword defines the class of response as follows: "informational" - Request received, continuing process "successful" - The action was successfully received, understood, and accepted "redirection" - Further action must be taken in order to complete the request "client-error" - The request contains bad syntax or cannot be fulfilled "server-error" - The IPP object failed to fulfill an apparently valid request As with type2 enums, IPP status codes are extensible. IPP clients are NOT REQUIRED to understand the meaning of all registered status codes, though such understanding is obviously desirable. However, IPP clients MUST understand the class of any status code, as indicated by the prefix, and treat any unrecognized response as being equivalent to the first status code of that class, with the exception that an unrecognized response MUST NOT be cached. For example, if an unrecognized status code of "client-error-xxx-yyy" is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a "client- error-bad-request" status code. In such cases, IPP applications SHOULD present the OPTIONAL message (if present) to the end user since the message is likely to contain human readable information which will help to explain the unusual status. The name of the enum is the suggested status message for US English.
ToP   noToC   RFC2911 - Page 178
   The status code values range from 0x0000 to 0x7FFF.  The value ranges
   for each status code class are as follows:

      "successful" - 0x0000 to 0x00FF
      "informational" - 0x0100 to 0x01FF
      "redirection" - 0x0200 to 0x02FF
      "client-error" - 0x0400 to 0x04FF
      "server-error" - 0x0500 to 0x05FF

   The top half (128 values) of each range (0x0n40 to 0x0nFF, for n = 0
   to 5) is reserved for vendor use within each status code class.
   Values 0x0600 to 0x7FFF are reserved for future assignment by IETF
   standards track documents and MUST NOT be used.

13.1 Status Codes

Each status code is described below. Section 13.1.5.9 contains a table that indicates which status codes apply to which operations. The Implementer's Guide [IPP-IIG] describe the suggested steps for processing IPP attributes for all operations, including returning status codes.

13.1.1 Informational

This class of status code indicates a provisional response and is to be used for informational purposes only. There are no status codes defined in IPP/1.1 for this class of status code.

13.1.2 Successful Status Codes

This class of status code indicates that the client's request was successfully received, understood, and accepted.
13.1.2.1 successful-ok (0x0000)
The request has succeeded and no request attributes were substituted or ignored. In the case of a response to a create request, the 'successful-ok' status code indicates that the request was successfully received and validated, and that the Job object has been created; it does not indicate that the job has been processed. The transition of the Job object into the 'completed' state is the only indicator that the job has been printed.
ToP   noToC   RFC2911 - Page 179
13.1.2.2 successful-ok-ignored-or-substituted-attributes (0x0001)
The request has succeeded, but some supplied (1) attributes were ignored or (2) unsupported values were substituted with supported values or were ignored in order to perform the operation without rejecting it. Unsupported attributes, attribute syntaxes, or values MUST be returned in the Unsupported Attributes group of the response for all operations. There is an exception to this rule for the query operations: Get-Printer-Attributes, Get-Jobs, and Get-Job-Attributes for the "requested-attributes" operation attribute only. When the supplied values of the "requested-attributes" operation attribute are requesting attributes that are not supported, the IPP object MAY, but is NOT REQUIRED to, return the "requested-attributes" attribute in the Unsupported Attribute response group (with the unsupported values only). See sections 3.1.7 and 3.2.1.2.
13.1.2.3 successful-ok-conflicting-attributes (0x0002)
The request has succeeded, but some supplied attribute values conflicted with the values of other supplied attributes. These conflicting values were either (1) substituted with (supported) values or (2) the attributes were removed in order to process the job without rejecting it. Attributes or values which conflict with other attributes and have been substituted or ignored MUST be returned in the Unsupported Attributes group of the response for all operations as supplied by the client. See sections 3.1.7 and 3.2.1.2.

13.1.3 Redirection Status Codes

This class of status code indicates that further action needs to be taken to fulfill the request. There are no status codes defined in IPP/1.1 for this class of status code.

13.1.4 Client Error Status Codes

This class of status code is intended for cases in which the client seems to have erred. The IPP object SHOULD return a message containing an explanation of the error situation and whether it is a temporary or permanent condition.
ToP   noToC   RFC2911 - Page 180
13.1.4.1 client-error-bad-request (0x0400)
The request could not be understood by the IPP object due to malformed syntax (such as the value of a fixed length attribute whose length does not match the prescribed length for that attribute - see the Implementer's Guide [IPP-IIG] ). The IPP application SHOULD NOT repeat the request without modifications.
13.1.4.2 client-error-forbidden (0x0401)
The IPP object understood the request, but is refusing to fulfill it. Additional authentication information or authorization credentials will not help and the request SHOULD NOT be repeated. This status code is commonly used when the IPP object does not wish to reveal exactly why the request has been refused or when no other response is applicable.
13.1.4.3 client-error-not-authenticated (0x0402)
The request requires user authentication. The IPP client may repeat the request with suitable authentication information. If the request already included authentication information, then this status code indicates that authorization has been refused for those credentials. If this response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the response message may contain relevant diagnostic information. This status codes reveals more information than "client-error-forbidden".
13.1.4.4 client-error-not-authorized (0x0403)
The requester is not authorized to perform the request. Additional authentication information or authorization credentials will not help and the request SHOULD NOT be repeated. This status code is used when the IPP object wishes to reveal that the authentication information is understandable, however, the requester is explicitly not authorized to perform the request. This status codes reveals more information than "client-error-forbidden" and "client-error- not-authenticated".
13.1.4.5 client-error-not-possible (0x0404)
This status code is used when the request is for something that can not happen. For example, there might be a request to cancel a job that has already been canceled or aborted by the system. The IPP client SHOULD NOT repeat the request.
ToP   noToC   RFC2911 - Page 181
13.1.4.6 client-error-timeout (0x0405)
The client did not produce a request within the time that the IPP object was prepared to wait. For example, a client issued a Create- Job operation and then, after a long period of time, issued a Send- Document operation and this error status code was returned in response to the Send-Document request (see section 3.3.1). The IPP object might have been forced to clean up resources that had been held for the waiting additional Documents. The IPP object was forced to close the Job since the client took too long. The client SHOULD NOT repeat the request without modifications.
13.1.4.7 client-error-not-found (0x0406)
The IPP object has not found anything matching the request URI. No indication is given of whether the condition is temporary or permanent. For example, a client with an old reference to a Job (a URI) tries to cancel the Job, however in the mean time the Job might have been completed and all record of it at the Printer has been deleted. This status code, 'client-error-not-found' is returned indicating that the referenced Job can not be found. This error status code is also used when a client supplies a URI as a reference to the document data in either a Print-URI or Send-URI operation, but the document can not be found. In practice, an IPP application should avoid a not found situation by first querying and presenting a list of valid Printer URIs and Job URIs to the end-user.
13.1.4.8 client-error-gone (0x0407)
The requested object is no longer available and no forwarding address is known. This condition should be considered permanent. Clients with link editing capabilities should delete references to the request URI after user approval. If the IPP object does not know or has no facility to determine, whether or not the condition is permanent, the status code "client-error-not-found" should be used instead. This response is primarily intended to assist the task of maintenance by notifying the recipient that the resource is intentionally unavailable and that the IPP object administrator desires that remote links to that resource be removed. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the IPP object administrator and/or Printer implementation.
ToP   noToC   RFC2911 - Page 182
13.1.4.9 client-error-request-entity-too-large (0x0408)
The IPP object is refusing to process a request because the request entity is larger than the IPP object is willing or able to process. An IPP Printer returns this status code when it limits the size of print jobs and it receives a print job that exceeds that limit or when the attributes are so many that their encoding causes the request entity to exceed IPP object capacity.
13.1.4.10 client-error-request-value-too-long (0x0409)
The IPP object is refusing to service the request because one or more of the client-supplied attributes has a variable length value that is longer than the maximum length specified for that attribute. The IPP object might not have sufficient resources (memory, buffers, etc.) to process (even temporarily), interpret, and/or ignore a value larger than the maximum length. Another use of this error code is when the IPP object supports the processing of a large value that is less than the maximum length, but during the processing of the request as a whole, the object may pass the value onto some other system component which is not able to accept the large value. For more details, see the Implementer's Guide [IPP-IIG] . Note: For attribute values that are URIs, this rare condition is only likely to occur when a client has improperly submitted a request with long query information (e.g. an IPP application allows an end- user to enter an invalid URI), when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the IPP object is under attack by a client attempting to exploit security holes present in some IPP objects using fixed-length buffers for reading or manipulating the Request-URI.
13.1.4.11 client-error-document-format-not-supported (0x040A)
The IPP object is refusing to service the request because the document data is in a format, as specified in the "document-format" operation attribute, that is not supported by the Printer object. This error is returned independent of the client-supplied "ipp- attribute-fidelity". The Printer object MUST return this status code, even if there are other Job Template attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes. See sections 3.1.6.1, 3.1.7, and 3.2.1.1.
ToP   noToC   RFC2911 - Page 183
13.1.4.12 client-error-attributes-or-values-not-supported (0x040B)
In a create request, if the Printer object does not support one or more attributes, attribute syntaxes, or attribute values supplied in the request and the client supplied the "ipp-attribute-fidelity" operation attribute with the 'true' value, the Printer object MUST return this status code. The Printer object MUST also return in the Unsupported Attributes Group all the attributes and/or values supplied by the client that are not supported. See section 3.1.7. For example, if the request indicates 'iso-a4' media, but that media type is not supported by the Printer object. Or, if the client supplies a Job Template attribute and the attribute itself is not even supported by the Printer. If the "ipp-attribute-fidelity" attribute is 'false', the Printer MUST ignore or substitute values for unsupported Job Template attributes and values rather than reject the request and return this status code. For any operation where a client requests attributes (such as a Get- Jobs, Get-Printer-Attributes, or Get-Job-Attributes operation), if the IPP object does not support one or more of the requested attributes, the IPP object simply ignores the unsupported requested attributes and processes the request as if they had not been supplied, rather than returning this status code. In this case, the IPP object MUST return the 'successful-ok-ignored-or-substituted- attributes' status code and MAY return the unsupported attributes as values of the "requested-attributes" in the Unsupported Attributes Group (see section 13.1.2.2).
13.1.4.13 client-error-uri-scheme-not-supported (0x040C)
The scheme of the client-supplied URI in a Print-URI or a Send-URI operation is not supported. See sections 3.1.6.1 and 3.1.7.
13.1.4.14 client-error-charset-not-supported (0x040D)
For any operation, if the IPP Printer does not support the charset supplied by the client in the "attributes-charset" operation attribute, the Printer MUST reject the operation and return this status and any 'text' or 'name' attributes using the 'utf-8' charset (see Section 3.1.4.1). See sections 3.1.6.1 and 3.1.7.
13.1.4.15 client-error-conflicting-attributes (0x040E)
The request is rejected because some attribute values conflicted with the values of other attributes which this document does not permit to be substituted or ignored. The Printer object MUST also return in the Unsupported Attributes Group the conflicting attributes supplied by the client. See sections 3.1.7 and 3.2.1.2.
ToP   noToC   RFC2911 - Page 184
13.1.4.16 client-error-compression-not-supported (0x040F)
The IPP object is refusing to service the request because the document data, as specified in the "compression" operation attribute, is compressed in a way that is not supported by the Printer object. This error is returned independent of the client-supplied "ipp- attribute-fidelity". The Printer object MUST return this status code, even if there are other Job Template attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes. See sections 3.1.6.1, 3.1.7, and 3.2.1.1.
13.1.4.17 client-error-compression-error (0x0410)
The IPP object is refusing to service the request because the document data cannot be decompressed when using the algorithm specified by the "compression" operation attribute. This error is returned independent of the client-supplied "ipp-attribute-fidelity". The Printer object MUST return this status code, even if there are Job Template attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes. See sections 3.1.7 and 3.2.1.1.
13.1.4.18 client-error-document-format-error (0x0411)
The IPP object is refusing to service the request because Printer encountered an error in the document data while interpreting it. This error is returned independent of the client-supplied "ipp- attribute-fidelity". The Printer object MUST return this status code, even if there are Job Template attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes. See sections 3.1.7 and 3.2.1.1.
13.1.4.19 client-error-document-access-error (0x0412)
The IPP object is refusing to service the Print-URI or Send-URI request because Printer encountered an access error while attempting to validate the accessibility or access the document data specified in the "document-uri" operation attribute. The Printer MAY also return a specific document access error code using the "document- access-error" operation attribute (see section 3.1.6.4). This error is returned independent of the client-supplied "ipp-attribute- fidelity". The Printer object MUST return this status code, even if there are Job Template attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes. See sections 3.1.6.1 and 3.1.7.
ToP   noToC   RFC2911 - Page 185

13.1.5 Server Error Status Codes

This class of status codes indicates cases in which the IPP object is aware that it has erred or is incapable of performing the request. The IPP object SHOULD include a message containing an explanation of the error situation, and whether it is a temporary or permanent condition.
13.1.5.1 server-error-internal-error (0x0500)
The IPP object encountered an unexpected condition that prevented it from fulfilling the request. This error status code differs from "server-error-temporary-error" in that it implies a more permanent type of internal error. It also differs from "server-error-device- error" in that it implies an unexpected condition (unlike a paper-jam or out-of-toner problem which is undesirable but expected). This error status code indicates that probably some knowledgeable human intervention is required.
13.1.5.2 server-error-operation-not-supported (0x0501)
The IPP object does not support the functionality required to fulfill the request. This is the appropriate response when the IPP object does not recognize an operation or is not capable of supporting it. See sections 3.1.6.1 and 3.1.7.
13.1.5.3 server-error-service-unavailable (0x0502)
The IPP object is currently unable to handle the request due to a temporary overloading or maintenance of the IPP object. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in the message. If no delay is given, the IPP application should handle the response as it would for a "server-error- temporary-error" response. If the condition is more permanent, the error status codes "client-error-gone" or "client-error-not-found" could be used.
13.1.5.4 server-error-version-not-supported (0x0503)
The IPP object does not support, or refuses to support, the IPP protocol version that was supplied as the value of the "version- number" operation parameter in the request. The IPP object is indicating that it is unable or unwilling to complete the request using the same major and minor version number as supplied in the request other than with this error message. The error response SHOULD contain a "status-message" attribute (see section 3.1.6.2) describing
ToP   noToC   RFC2911 - Page 186
   why that version is not supported and what other versions are
   supported by that IPP object.  See sections 3.1.6.1, 3.1.7, and
   3.1.8.

   The error response MUST identify in the "version-number" operation
   parameter the closest version number that the IPP object does
   support.  For example, if a client supplies version '1.0' and an
   IPP/1.1 object supports version '1.0', then it responds with version
   '1.0' in all responses to such a request.  If the IPP/1.1 object does
   not support version '1.0', then it should accept the request and
   respond with version '1.1' or may reject the request and respond with
   this error code and version
   '1.1'.  If a client supplies a version '1.2', the IPP/1.1 object
   should accept the request and return version '1.1' or may reject the
   request and respond with this error code and version '1.1'.  See
   sections 3.1.8 and 4.4.14.

13.1.5.5 server-error-device-error (0x0504)
A printer error, such as a paper jam, occurs while the IPP object processes a Print or Send operation. The response contains the true Job Status (the values of the "job-state" and "job-state-reasons" attributes). Additional information can be returned in the OPTIONAL "job-state-message" attribute value or in the OPTIONAL status message that describes the error in more detail. This error status code is only returned in situations where the Printer is unable to accept the create request because of such a device error. For example, if the Printer is unable to spool, and can only accept one job at a time, the reason it might reject a create request is that the printer currently has a paper jam. In many cases however, where the Printer object can accept the request even though the Printer has some error condition, the 'successful-ok' status code will be returned. In such a case, the client would look at the returned Job Object Attributes or later query the Printer to determine its state and state reasons.
13.1.5.6 server-error-temporary-error (0x0505)
A temporary error such as a buffer full write error, a memory overflow (i.e. the document data exceeds the memory of the Printer), or a disk full condition, occurs while the IPP Printer processes an operation. The client MAY try the unmodified request again at some later point in time with an expectation that the temporary internal error condition may have been cleared. Alternatively, as an implementation option, a Printer object MAY delay the response until the temporary condition is cleared so that no error is returned.
ToP   noToC   RFC2911 - Page 187
13.1.5.7 server-error-not-accepting-jobs (0x0506)
A temporary error indicating that the Printer is not currently accepting jobs, because the administrator has set the value of the Printer's "printer-is-accepting-jobs" attribute to 'false' (by means outside the scope of this IPP/1.1 document).
13.1.5.8 server-error-busy (0x0507)
A temporary error indicating that the Printer is too busy processing jobs and/or other requests. The client SHOULD try the unmodified request again at some later point in time with an expectation that the temporary busy condition will have been cleared.
13.1.5.9 server-error-job-canceled (0x0508)
An error indicating that the job has been canceled by an operator or the system while the client was transmitting the data to the IPP Printer. If a job-id and job-uri had been created, then they are returned in the Print-Job, Send-Document, or Send-URI response as usual; otherwise, no job-id and job-uri are returned in the response.
13.1.5.10 server-error-multiple-document-jobs-not-supported (0x0509)
The IPP object does not support multiple documents per job and a client attempted to supply document data with a second Send-Document or Send-URI operation.

13.2 Status Codes for IPP Operations

PJ = Print-Job, PU = Print-URI, CJ = Create-Job, SD = Send-Document SU = Send-URI, V = Validate-Job, GA = Get-Job-Attributes and Get-Printer-Attributes, GJ = Get-Jobs, C = Cancel-Job
ToP   noToC   RFC2911 - Page 188
                                                  IPP Operations
   IPP Status Keyword                       PJ PU CJ SD SU V GA GJ C
   ------------------                       -- -- -- -- -- - -- -- -
   successful-ok                            x  x  x  x  x  x x  x  x
   successful-ok-ignored-or-substituted-    x  x  x  x  x  x x  x  x
        attributes
   successful-ok-conflicting-attributes     x  x  x  x  x  x x  x  x
   client-error-bad-request                 x  x  x  x  x  x x  x  x
   client-error-forbidden                   x  x  x  x  x  x x  x  x
   client-error-not-authenticated           x  x  x  x  x  x x  x  x
   client-error-not-authorized              x  x  x  x  x  x x  x  x
   client-error-not-possible                x  x  x  x  x  x x  x  x
   client-error-timeout                              x  x
   client-error-not-found                   x  x  x  x  x  x x  x  x
   client-error-gone                        x  x  x  x  x  x x  x  x
   client-error-request-entity-too-large    x  x  x  x  x  x x  x  x
   client-error-request-value-too-long      x  x  x  x  x  x x  x  x
   client-error-document-format-not-        x  x     x  x  x x
        supported
   client-error-attributes-or-values-not-   x  x  x  x  x  x x  x  x
        supported
   client-error-uri-scheme-not-supported       x        x
   client-error-charset-not-supported       x  x  x  x  x  x x  x  x
   client-error-conflicting-attributes      x  x  x  x  x  x x  x  x
   client-error-compression-not-supported   x  x     x  x  x
   client-error-compression-error           x  x     x  x
   client-error-document-format-error       x  x     x  x
   client-error-document-access-error          x        x
   server-error-internal-error              x  x  x  x  x  x x  x  x
   server-error-operation-not-supported        x  x  x  x
   server-error-service-unavailable         x  x  x  x  x  x x  x  x
   server-error-version-not-supported       x  x  x  x  x  x x  x  x
   server-error-device-error                x  x  x  x  x
   server-error-temporary-error             x  x  x  x  x
   server-error-not-accepting-jobs          x  x  x        x
   server-error-busy                        x  x  x  x  x  x x  x  x
   server-error-job-canceled                x        x  x
   server-error-multiple-document-jobs-              x  x
          not-supported

   HJ = Hold-Job, RJ = Release-Job, RS = Restart-Job
   PP = Pause-Printer, RP = Resume-Printer, PJ = Purge-Jobs
ToP   noToC   RFC2911 - Page 189
                                            IPP Operations (cont.)
   IPP Status Keyword                       HJ RJ RS PP RP PJ
   ------------------                       -- -- -- -- -- --
   successful-ok                            x  x  x  x  x  x
   successful-ok-ignored-or-substituted-    x  x  x  x  x  x
        attributes
   successful-ok-conflicting-attributes     x  x  x  x  x  x
   client-error-bad-request                 x  x  x  x  x  x
   client-error-forbidden                   x  x  x  x  x  x
   client-error-not-authenticated           x  x  x  x  x  x
   client-error-not-authorized              x  x  x  x  x  x
   client-error-not-possible                x  x  x  x  x  x
   client-error-timeout
   client-error-not-found                   x  x  x  x  x  x
   client-error-gone                        x  x  x  x  x  x
   client-error-request-entity-too-large    x  x  x  x  x  x
   client-error-request-value-too-long      x  x  x  x  x  x
   client-error-document-format-not-
        supported
   client-error-attributes-or-values-not-   x  x  x  x  x  x
        supported
   client-error-uri-scheme-not-supported
   client-error-charset-not-supported       x  x  x  x  x  x
   client-error-conflicting-attributes      x  x  x  x  x  x
   client-error-compression-not-supported
   client-error-compression-error
   client-error-document-format-error
   client-error-document-access-error
   server-error-internal-error              x  x  x  x  x  x
   server-error-operation-not-supported     x  x  x  x  x  x
   server-error-service-unavailable         x  x  x  x  x  x
   server-error-version-not-supported       x  x  x  x  x  x
   server-error-device-error
   server-error-temporary-error             x  x  x  x  x  x
   server-error-not-accepting-jobs
   server-error-busy                        x  x  x  x  x  x
   server-error-job-canceled
   server-error-multiple-document-jobs-
          not-supported
ToP   noToC   RFC2911 - Page 190

14. APPENDIX C: "media" keyword values

Standard keyword values are taken from several sources. Standard values are defined (taken from DPA[ISO10175] and the Printer MIB[RFC1759]): 'default': The default medium for the output device 'iso-a4-white': Specifies the ISO A4 white medium: 210 mm x 297 mm 'iso-a4-colored': Specifies the ISO A4 colored medium: 210 mm x 297 mm 'iso-a4-transparent' Specifies the ISO A4 transparent medium: 210 mm x 297 mm 'iso-a3-white': Specifies the ISO A3 white medium: 297 mm x 420 mm 'iso-a3-colored': Specifies the ISO A3 colored medium: 297 mm x 420 mm 'iso-a5-white': Specifies the ISO A5 white medium: 148 mm x 210 mm 'iso-a5-colored': Specifies the ISO A5 colored medium: 148 mm x 210 mm 'iso-b4-white': Specifies the ISO B4 white medium: 250 mm x 353 mm 'iso-b4-colored': Specifies the ISO B4 colored medium: 250 mm x 353 mm 'iso-b5-white': Specifies the ISO B5 white medium: 176 mm x 250 mm 'iso-b5-colored': Specifies the ISO B5 colored medium: 176 mm x 250 mm 'jis-b4-white': Specifies the JIS B4 white medium: 257 mm x 364 mm 'jis-b4-colored': Specifies the JIS B4 colored medium: 257 mm x 364 mm 'jis-b5-white': Specifies the JIS B5 white medium: 182 mm x 257 mm 'jis-b5-colored': Specifies the JIS B5 colored medium: 182 mm x 257 mm The following standard values are defined for North American media: 'na-letter-white': Specifies the North American letter white medium 'na-letter-colored': Specifies the North American letter colored medium 'na-letter-transparent': Specifies the North American letter transparent medium 'na-legal-white': Specifies the North American legal white medium 'na-legal-colored': Specifies the North American legal colored medium
ToP   noToC   RFC2911 - Page 191
   The following standard values are defined for envelopes:

    'iso-b4-envelope': Specifies the ISO B4 envelope medium
    'iso-b5-envelope': Specifies the ISO B5 envelope medium
    'iso-c3-envelope': Specifies the ISO C3 envelope medium
    'iso-c4-envelope': Specifies the ISO C4 envelope medium
    'iso-c5-envelope': Specifies the ISO C5 envelope medium
    'iso-c6-envelope': Specifies the ISO C6 envelope medium
    'iso-designated-long-envelope': Specifies the ISO Designated Long
       envelope medium
    'na-10x13-envelope': Specifies the North American 10x13 envelope
       medium
    'na-9x12-envelope': Specifies the North American 9x12 envelope
       medium
    'monarch-envelope': Specifies the Monarch envelope
    'na-number-10-envelope': Specifies the North American number 10
       business envelope medium
    'na-7x9-envelope': Specifies the North American 7x9 inch envelope
    'na-9x11-envelope': Specifies the North American 9x11 inch
       envelope
    'na-10x14-envelope': Specifies the North American 10x14 inch
       envelope
    'na-number-9-envelope': Specifies the North American number 9
       business envelope
    'na-6x9-envelope': Specifies the North American 6x9 inch envelope
    'na-10x15-envelope': Specifies the North American 10x15 inch
       envelope

   The following standard values are defined for the less commonly used
   media:

 'executive-white': Specifies the white executive medium
 'folio-white': Specifies the folio white medium
 'invoice-white': Specifies the white invoice medium
 'ledger-white': Specifies the white ledger medium
 'quarto-white': Specified the white quarto medium
 'iso-a0-white': Specifies the ISO A0 white medium: 841 mm x 1189 mm
 'iso-a0-transparent': Specifies the ISO A0 transparent medium: 841 mm
    x 1189 mm
 'iso-a0-translucent': Specifies the ISO A0 translucent medium: 841 mm
    x 1189 mm
 'iso-a1-white': Specifies the ISO A1 white medium: 594 mm x 841 mm
 'iso-a1-transparent': Specifies the ISO A1 transparent medium: 594 mm
    x 841 mm
 'iso-a1-translucent': Specifies the ISO A1 translucent medium: 594 mm
    x 841 mm
 'iso-a2-white': Specifies the ISO A2 white medium: 420 mm x 594 mm
ToP   noToC   RFC2911 - Page 192
 'iso-a2-transparent': Specifies the ISO A2 transparent medium: 420 mm
    x 594 mm
 'iso-a2-translucent': Specifies the ISO A2 translucent medium: 420 mm
    x 594 mm
 'iso-a3-transparent': Specifies the ISO A3 transparent medium: 297 mm
    x 420 mm
 'iso-a3-translucent': Specifies the ISO A3 translucent medium: 297 mm
    x 420 mm
 'iso-a4-translucent': Specifies the ISO A4 translucent medium: 210 mm
    x 297 mm
 'iso-a5-transparent': Specifies the ISO A5 transparent medium: 148 mm
    x 210 mm
 'iso-a5-translucent': Specifies the ISO A5 translucent medium: 148 mm
    x 210 mm
 'iso-a6-white': Specifies the ISO A6 white medium: 105 mm x 148 mm
 'iso-a7-white': Specifies the ISO A7 white medium: 74 mm x 105 mm
 'iso-a8-white': Specifies the ISO A8 white medium: 52 mm x 74 mm
 'iso-a9-white': Specifies the ISO A9 white medium: 37 mm x 52 mm
 'iso-a10-white': Specifies the ISO A10 white medium: 26 mm x 37 mm
 'iso-b0-white': Specifies the ISO B0 white medium: 1000 mm x 1414 mm
 'iso-b1-white': Specifies the ISO B1 white medium: 707 mm x 1000 mm
 'iso-b2-white': Specifies the ISO B2 white medium: 500 mm x 707 mm
 'iso-b3-white': Specifies the ISO B3 white medium: 353 mm x 500 mm
 'iso-b6-white': Specifies the ISO B6 white medium: 125 mm x 176 mm
 'iso-b7-white': Specifies the ISO B7 white medium: 88 mm x 125 mm
 'iso-b8-white': Specifies the ISO B8 white medium: 62 mm x 88 mm
 'iso-b9-white': Specifies the ISO B9 white medium: 44 mm x 62 mm
 'iso-b10-white': Specifies the ISO B10 white medium: 31 mm x 44 mm
 'jis-b0-white': Specifies the JIS B0 white medium: 1030 mm x 1456 mm
 'jis-b0-transparent': Specifies the JIS B0 transparent medium: 1030
    mm x 1456 mm
 'jis-b0-translucent': Specifies the JIS B0 translucent medium: 1030
    mm x 1456 mm
 'jis-b1-white': Specifies the JIS B1 white medium: 728 mm x 1030 mm
 'jis-b1-transparent': Specifies the JIS B1 transparent medium: 728 mm
    x 1030 mm
 'jis-b1-translucent': Specifies the JIS B1 translucent medium: 728 mm
    x 1030 mm
 'jis-b2-white': Specifies the JIS B2 white medium: 515 mm x 728 mm
 'jis-b2-transparent': Specifies the JIS B2 transparent medium: 515 mm
    x 728 mm
 'jis-b2-translucent': Specifies the JIS B2 translucent medium: 515 mm
    x 728 mm
 'jis-b3-white': Specifies the JIS B3 white medium: 364 mm x 515 mm
 'jis-b3-transparent': Specifies the JIS B3 transparent medium: 364 mm
    x 515 mm
 'jis-b3-translucent': Specifies the JIS B3 translucent medium: 364 mm
    x 515 mm
ToP   noToC   RFC2911 - Page 193
 'jis-b4-transparent': Specifies the JIS B4 transparent medium: 257 mm
    x 364 mm
 'jis-b4-translucent': Specifies the JIS B4 translucent medium: 257 mm
    x 364 mm
 'jis-b5-transparent': Specifies the JIS B5 transparent medium: 182 mm
    x 257 mm
 'jis-b5-translucent': Specifies the JIS B5 translucent medium: 182 mm
    x 257 mm
 'jis-b6-white': Specifies the JIS B6 white medium: 128 mm x 182 mm
 'jis-b7-white': Specifies the JIS B7 white medium: 91 mm x 128 mm
 'jis-b8-white': Specifies the JIS B8 white medium: 64 mm x 91 mm
 'jis-b9-white': Specifies the JIS B9 white medium: 45 mm x 64 mm
 'jis-b10-white': Specifies the JIS B10 white medium: 32 mm x 45 mm

   The following standard values are defined for American Standard (i.e.
   ANSI) engineering media:

    'a-white': Specifies the engineering ANSI A size white medium: 8.5
       inches x 11 inches
    'a-transparent': Specifies the engineering ANSI A size transparent
       medium: 8.5 inches x 11 inches
    'a-translucent': Specifies the engineering ANSI A size translucent
       medium: 8.5 inches x 11 inches
    'b-white': Specifies the engineering ANSI B size white medium: 11
       inches x 17 inches
    'b-transparent': Specifies the engineering ANSI B size transparent
       medium: 11 inches x 17 inches)
    'b-translucent': Specifies the engineering ANSI B size translucent
       medium: 11 inches x 17 inches
    'c-white': Specifies the engineering ANSI C size white medium: 17
       inches x 22 inches
    'c-transparent': Specifies the engineering ANSI C size transparent
       medium: 17 inches x 22 inches
    'c-translucent': Specifies the engineering ANSI C size translucent
       medium: 17 inches x 22 inches
    'd-white': Specifies the engineering ANSI D size white medium: 22
       inches x 34 inches
    'd-transparent': Specifies the engineering ANSI D size transparent
       medium: 22 inches x 34 inches
    'd-translucent': Specifies the engineering ANSI D size translucent
       medium: 22 inches x 34 inches
    'e-white': Specifies the engineering ANSI E size white medium: 34
       inches x 44 inches
    'e-transparent': Specifies the engineering ANSI E size transparent
       medium: 34 inches x 44 inches
    'e-translucent': Specifies the engineering ANSI E size translucent
       medium: 34 inches x 44 inches
ToP   noToC   RFC2911 - Page 194
   The following standard values are defined for American Standard (i.e.
   ANSI) engineering media for devices that provide the "synchro-cut"
   feature (see section 14.1):

 'axsynchro-white': Specifies the roll paper having the width of the
    longer edge (11 inches) of the engineering ANSI A size white medium
    and cuts synchronizing with data.
 'axsynchro-transparent': Specifies the roll paper having the width of
    the longer edge (11 inches) of the engineering ANSI A size
    transparent medium and cuts synchronizing with data.
 'axsynchro-translucent': Specifies the roll paper having the width of
    the longer edge (11 inches) of the engineering ANSI A size
    translucent medium and cuts synchronizing with data.
 'bxsynchro-white': Specifies the roll paper having the width of the
    longer edge (17 inches) of the engineering ANSI B size white medium
    and cuts synchronizing with data.
 'bxsynchro-transparent': Specifies the roll paper having the width of
    the longer edge (17 inches) of the engineering ANSI B size
    transparent medium and cuts synchronizing with data.
 'bxsynchro-translucent': Specifies the roll paper having the width of
    the longer edge (17 inches) of the engineering ANSI B size
    translucent medium and cuts synchronizing with data.
 'cxsynchro-white': Specifies the roll paper having the width of the
    longer edge (22 inches) of the engineering ANSI C size white medium
    and cuts synchronizing with data.
 'cxsynchro-transparent': Specifies the roll paper having the width of
    the longer edge (22 inches) of the engineering ANSI C size
    transparent medium and cuts synchronizing with data.
 'cxsynchro-translucent': Specifies the roll paper having the width of
    the longer edge (22 inches) of the engineering ANSI C size
    translucent medium and cuts synchronizing with data.
 'dxsynchro-white': Specifies the roll paper having the width of the
    longer edge (34 inches) of the engineering ANSI D size white medium
    and cuts synchronizing with data.
 'dxsynchro-transparent': Specifies the roll paper having the width of
    the longer edge (34 inches) of the engineering ANSI D size
    transparent medium and cuts synchronizing with data.
 'dxsynchro-translucent': Specifies the roll paper having the width of
    the longer edge (34 inches) of the engineering ANSI D size
    translucent medium and cuts synchronizing with data.
 'exsynchro-white': Specifies the roll paper having the width of the
    longer edge (44 inches) of the engineering ANSI E size white medium
    and cuts synchronizing with data.
 'exsynchro-transparent': Specifies the roll paper having the width of
    the longer edge (44 inches) of the engineering ANSI E size
    transparent medium and cuts synchronizing with data.
ToP   noToC   RFC2911 - Page 195
 'exsynchro-translucent': Specifies the roll paper having the width of
    the longer edge (44 inches) of the engineering ANSI E size
    translucent medium and cuts synchronizing with data.

   The following standard values are defined for American Architectural
   engineering media:

 'arch-a-white': Specifies the Architectural A size white medium: 9
    inches x 12 inches
 'arch-a-transparent': Specifies the Architectural A size transparent
    medium: 9 inches x 12 inches
 'arch-a-translucent': Specifies the Architectural A size translucent
    medium: 9 inches x 12 inches
 'arch-b-white': Specifies the Architectural B size white medium: 12
    inches x 18 inches
 'arch-b-transparent': Specifies the Architectural B size transparent
    medium: 12 inches x 18 inches
 'arch-b-translucent': Specifies the Architectural B size translucent
    medium: 12 inches x 18 inches
 'arch-c-white': Specifies the Architectural C size white medium: 18
    inches x 24 inches
 'arch-c-transparent': Specifies the Architectural C size transparent
    medium: 18 inches x 24 inches
 'arch-c-translucent': Specifies the Architectural C size translucent
    medium: 18 inches x 24 inches
 'arch-d-white': Specifies the Architectural D size white medium: 24
    inches x 36 inches
 'arch-d-transparent': Specifies the Architectural D size transparent
    medium: 24 inches x 36 inches
 'arch-d-translucent': Specifies the Architectural D size translucent
    medium: 24 inches x 36 inches
 'arch-e-white': Specifies the Architectural E size white medium: 36
    inches x 48 inches
 'arch-e-transparent': Specifies the Architectural E size transparent
    medium: 36 inches x 48 inches
 'arch-e-translucent': Specifies the Architectural E size translucent
    medium: 36 inches x 48 inches

   The following standard values are defined for American Architectural
   engineering media for devices that provide the "synchro-cut" feature
   (see section 14.1):

 'arch-axsynchro-white': Specifies the roll paper having the width of
    the longer edge (12 inches) of the Architectural A size white
    medium and cuts synchronizing with data.
 'arch-axsynchro-transparent': Specifies the roll paper having the
    width of the longer edge (12 inches) of the Architectural A size
    transparent medium and cuts synchronizing with data.
ToP   noToC   RFC2911 - Page 196
 'arch-axsynchro-translucent': Specifies the roll paper having the
    width of the longer edge (12 inches) of the Architectural A size
    translucent medium and cuts synchronizing with data.
 'arch-bxsynchro-white': Specifies the roll paper having the width of
    the longer edge (18 inches) of the Architectural B size white
    medium and cuts synchronizing with data.
 'arch-bxsynchro-transparent': Specifies the roll paper having the
    width of the longer edge (18 inches) of the Architectural B size
    transparent medium and cuts synchronizing with data.
 'arch-bxsynchro-translucent': Specifies the roll paper having the
    width of the longer edge (18 inches) of the Architectural B size
    translucent medium and cuts synchronizing with data.
 'arch-cxsynchro-white': Specifies the roll paper having the width of
    the longer edge (24 inches) of the Architectural C size white
    medium and cuts synchronizing with data.
 'arch-cxsynchro-transparent': Specifies the roll paper having the
    width of the longer edge (24 inches) of the Architectural C size
    transparent medium and cuts synchronizing with data.
 'arch-cxsynchro-translucent': Specifies the roll paper having the
    width of the longer edge (24 inches) of the Architectural C size
    translucent medium and cuts synchronizing with data.
 'arch-dxsynchro-white': Specifies the roll paper having the width of
    the longer edge (36 inches) of the Architectural D size white
    medium and cuts synchronizing with data.
 'arch-dxsynchro-transparent': Specifies the roll paper having the
    width of the longer edge (36 inches) of the Architectural D size
    transparent medium and cuts synchronizing with data.
 'arch-dxsynchro-translucent': Specifies the roll paper having the
    width of the longer edge (36 inches) of the Architectural D size
    translucent medium and cuts synchronizing with data.
 'arch-exsynchro-white': Specifies the roll paper having the width of
    the longer edge (48 inches) of the Architectural E size white
    medium and cuts synchronizing with data.
 'arch-exsynchro-transparent': Specifies the roll paper having the
    width of the longer edge (48 inches) of the Architectural E size
    transparent medium and cuts synchronizing with data.
 'arch-exsynchro-translucent': Specifies the roll paper having the
    width of the longer edge (48 inches) of the Architectural E size
    translucent medium and cuts synchronizing with data.

   The following standard values are defined for Japanese and European
   Standard (i.e. ISO) engineering media, which are of a long fixed size
   [ASME-Y14.1M]:

 'iso-a1x3-white': Specifies the ISO A1X3 white medium having the
      width of the longer edge (841 mm) of the ISO A1 medium
ToP   noToC   RFC2911 - Page 197
 'iso-a1x3-transparent': Specifies the ISO A1X3 transparent medium
      having the width of the longer edge (841 mm) of the ISO A1
      medium
 'iso-a1x3-translucent': Specifies the ISO A1X3 translucent medium
      having the width of the longer edge (841 mm) of the ISO A1
      medium
 'iso-a1x4-white': Specifies the ISO A1X4 white medium having the
      width of the longer edge (841 mm) of the ISO A1 medium
 'iso-a1x4-transparent': Specifies the ISO A1X4 transparent medium
      having the width of the longer edge (841 mm) of the ISO A1
      medium
 'iso-a1x4- translucent': Specifies the ISO A1X4 translucent medium
      having the width of the longer edge (841 mm) of the ISO A1
      medium
 'iso-a2x3-white': Specifies the ISO A2X3 white medium having the
      width of the longer edge (594 mm) of the ISO A2 medium
 'iso-a2x3-transparent': Specifies the ISO A2X3 transparent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a2x3-translucent': Specifies the ISO A2X3 translucent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a2x4-white': Specifies the ISO A2X4 white medium having the
      width of the longer edge (594 mm) of the ISO A2 medium
 'iso-a2x4-transparent': Specifies the ISO A2X4 transparent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a2x4-translucent': Specifies the ISO A2X4 translucent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a2x5-white': Specifies the ISO A2X5 white medium having the
      width of the longer edge (594 mm) of the ISO A2 medium
 'iso-a2x5-transparent': Specifies the ISO A2X5 transparent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a2x5-translucent': Specifies the ISO A2X5 translucent medium
      having the width of the longer edge (594 mm) of the ISO A2
      medium
 'iso-a3x3-white': Specifies the ISO A3X3 white medium having the
      width of the longer edge (420 mm) of the ISO A3 medium
 'iso-a3x3-transparent': Specifies the ISO A3X3 transparent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x3-translucent': Specifies the ISO A3X3 translucent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x4-white': Specifies the ISO A3X4 white medium having the
      width of the longer edge (420 mm) of the ISO A3 medium
ToP   noToC   RFC2911 - Page 198
 'iso-a3x4-transparent': Specifies the ISO A3X4 transparent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x4-translucent': Specifies the ISO A3X4 translucent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x5-white': Specifies the ISO A3X5 white medium having the
      width of the longer edge (420 mm) of the ISO A3 medium
 'iso-a3x5-transparent': Specifies the ISO A3X5 transparent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x5-translucent': Specifies the ISO A3X5 translucent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x6-white': Specifies the ISO A3X6 white medium having the
      width of the longer edge (420 mm) of the ISO A3 medium
 'iso-a3x6-transparent': Specifies the ISO A3X6 transparent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x6-translucent': Specifies the ISO A3X6 translucent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x7-white': Specifies the ISO A3X7 white medium having the
      width of the longer edge (420 mm) of the ISO A3 medium
 'iso-a3x7-transparent': Specifies the ISO A3X7 transparent medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a3x7-translucent'': Specifies the ISO A3X7 translucent' medium
      having the width of the longer edge (420 mm) of the ISO A3
      medium
 'iso-a4x3-white': Specifies the ISO A4X3 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x3-transparent': Specifies the ISO A4X3 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x3-translucent'': Specifies the ISO A4X3 translucent' medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x4-white': Specifies the ISO A4X4 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x4-transparent': Specifies the ISO A4X4 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x4-translucent': Specifies the ISO A4X4 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x5-white': Specifies the ISO A4X5 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
ToP   noToC   RFC2911 - Page 199
 'iso-a4x5-transparent': Specifies the ISO A4X5 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x5-translucent': Specifies the ISO A4X5 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x6-white': Specifies the ISO A4X6 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x6-transparent': Specifies the ISO A4X6 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x6-translucent': Specifies the ISO A4X6 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x7-white': Specifies the ISO A4X7 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x7-transparent': Specifies the ISO A4X7 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x7-translucent': Specifies the ISO A4X7 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x8-white': Specifies the ISO A4X8 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x8-transparent': Specifies the ISO A4X8 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x8-translucent': Specifies the ISO A4X8 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x9-white': Specifies the ISO A4X9 white medium having the
      width of the longer edge (297 mm) of the ISO A4 medium
 'iso-a4x9-transparent': Specifies the ISO A4X9 transparent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium
 'iso-a4x9-translucent': Specifies the ISO A4X9 translucent medium
      having the width of the longer edge (297 mm) of the ISO A4
      medium

   The following standard values are defined for Japanese and European
   Standard (i.e. ISO) engineering media, which are either a long fixed
   size [ASME-Y14.1M] or roll feed, for devices that provide the
   "synchro-cut" feature (see section 14.1):

 'iso-a0xsynchro-white': Specifies the paper having the width of the
      longer edge (1189 mm) of the ISO A0 white medium and cuts
      synchronizing with data.
ToP   noToC   RFC2911 - Page 200
 'iso-a0xsynchro-transparent': Specifies the paper having the width of
      the longer edge (1189 mm) of the ISO A0 transparent medium and
      cuts synchronizing with data.
 'iso-a0xsynchro-translucent': Specifies the paper having the width of
      the longer edge (1189 mm) of the ISO A0 translucent medium and
      cuts synchronizing with data.
 'iso-a1xsynchro-white': Specifies the paper having the width of the
      longer edge (841 mm) of the ISO A1 white medium and cuts
      synchronizing with data.
 'iso-a1xsynchro-transparent': Specifies the paper having the width of
      the longer edge (841 mm) of the ISO A1 transparent medium and
      cuts synchronizing with data.
 'iso-a1xsynchro-translucent': Specifies the paper having the width of
      the longer edge (841 mm) of the ISO A1 translucent medium and
      cuts synchronizing with data.
 'iso-a2xsynchro-white': Specifies the paper having the width of the
      longer edge (594 mm) of the ISO A2 white medium and cuts
      synchronizing with data.
 'iso-a2xsynchro-transparent': Specifies the paper having the width of
      the longer edge (594 mm) of the ISO A2 transparent medium and
      cuts synchronizing with data.
 'iso-a2xsynchro-translucent': Specifies the paper having the width of
      the longer edge (594 mm) of the ISO A2 translucent medium and
      cuts synchronizing with data.
 'iso-a3xsynchro-white': Specifies the paper having the width of the
      longer edge (420 mm) of the ISO A3 white medium and cuts
      synchronizing with data.
 'iso-a3xsynchro-transparent': Specifies the paper having the width of
      the longer edge (420 mm) of the ISO A3 transparent medium and
      cuts synchronizing with data.
 'iso-a3xsynchro-translucent': Specifies the paper having the width of
      the longer edge (420 mm) of the ISO A3 translucent medium and
      cuts synchronizing with data.
 'iso-a4xsynchro-white': Specifies the paper having the width of the
      longer edge (297 mm) of the ISO A4 white medium and cuts
      synchronizing with data.
 'iso-a4xsynchro-transparent': Specifies the paper having the width of
      the longer edge (297 mm) of the ISO A4 transparent medium and
      cuts synchronizing with data.
 'iso-a4xsynchro-translucent': Specifies the paper having the width of
      the longer edge (297 mm) of the ISO A4 transparent medium and
      cuts synchronizing with data.

   The following standard values are defined for American Standard (i.e.
   ANSI) engineering media, American Architectural engineering media,
   and Japanese and European Standard (i.e. ISO) engineering media,
ToP   noToC   RFC2911 - Page 201
   which are either a long fixed size [ASME-Y14.1M] or roll feed, for
   devices that provide the "synchro-cut" feature and/or the "auto-
   select" feature (see section 14.1):

 'auto-white': Specifies that the printer selects the white medium
      with the appropriate fixed size (e.g. a1, a2, etc.) or data-
      synchro size, and the selection is implementation-defined.
 'auto-transparent': Specifies that the printer selects the
      transparent medium with the appropriate fixed size (e.g. a1, a2,
      etc.) or data-synchro size, and the selection is implementation-
      defined.
 'auto-translucent': Specifies that the printer selects the
      translucent medium with the appropriate fixed size (e.g. a1, a2,
      etc.) or data-synchro size, and the selection is implementation-
      defined.
 'auto-fixed-size-white': Specifies that the printer selects the white
      medium with the appropriate fixed size (e.g. a1, a2, etc.) or
      the appropriate long fixed size listed above.
 'auto-fixed-size-transparent': Specifies that the printer selects the
      transparent medium with the appropriate fixed size (e.g. a1, a2,
      etc.) or the appropriate long fixed size listed above.
 'auto-fixed-size-translucent': Specifies that the printer selects the
      translucent medium with the appropriate fixed size (e.g. a1, a2,
      etc.) or the appropriate long fixed size listed above.
 'auto-synchro-white': Specifies that the printer selects the white
      paper with the appropriate width and cuts it synchronizing with
      data.
 'auto-synchro-transparent': Specifies that the printer selects the
      transparent paper with the appropriate width and cuts it
      synchronizing with data.
 'auto-synchro-translucent': Specifies that the printer selects the
      translucent paper with the appropriate width and cuts it
      synchronizing with data.

   The following standard values are defined for input-trays (from ISO
   DPA and the Printer MIB):

    'top': The top input tray in the printer.
    'middle': The middle input tray in the printer.
    'bottom': The bottom input tray in the printer.
    'envelope': The envelope input tray in the printer.
    'manual': The manual feed input tray in the printer.
    'large-capacity': The large capacity input tray in the printer.
    'main': The main input tray
    'side': The side input tray
ToP   noToC   RFC2911 - Page 202
   The following standard values are defined for media sizes (from ISO
   DPA):

 'iso-a0': Specifies the ISO A0 size: 841 mm by 1189 mm as defined in
    ISO 216
 'iso-a1': Specifies the ISO A1 size: 594 mm by 841 mm as defined in
    ISO 216
 'iso-a2': Specifies the ISO A2 size: 420 mm by 594 mm as defined in
    ISO 216
 'iso-a3': Specifies the ISO A3 size: 297 mm by 420 mm as defined in
    ISO 216
 'iso-a4': Specifies the ISO A4 size: 210 mm by 297 mm as defined in
    ISO 216
 'iso-a5': Specifies the ISO A5 size: 148 mm by 210 mm as defined in
    ISO 216
 'iso-a6': Specifies the ISO A6 size: 105 mm by 148 mm as defined in
    ISO 216
 'iso-a7': Specifies the ISO A7 size: 74 mm by 105 mm as defined in
    ISO 216
 'iso-a8': Specifies the ISO A8 size: 52 mm by 74 mm as defined in ISO
    216
 'iso-a9': Specifies the ISO A9 size: 37 mm by 52 mm as defined in ISO
    216
 'iso-a10': Specifies the ISO A10 size: 26 mm by 37 mm as defined in
    ISO 216
 'iso-b0': Specifies the ISO B0 size: 1000 mm by 1414 mm as defined in
    ISO 216
 'iso-b1': Specifies the ISO B1 size: 707 mm by 1000 mm as defined in
    ISO 216
 'iso-b2': Specifies the ISO B2 size: 500 mm by 707 mm as defined in
    ISO 216
 'iso-b3': Specifies the ISO B3 size: 353 mm by 500 mm as defined in
    ISO 216
 'iso-b4': Specifies the ISO B4 size: 250 mm by 353 mm as defined in
    ISO 216
 'iso-b5': Specifies the ISO B5 size: 176 mm by 250 mm as defined in
    ISO 216
 'iso-b6': Specifies the ISO B6 size: 125 mm by 176 mm as defined in
    ISO 216
 'iso-b7': Specifies the ISO B7 size: 88 mm by 125 mm as defined in
    ISO 216
 'iso-b8': Specifies the ISO B8 size: 62 mm by 88 mm as defined in ISO
    216
 'iso-b9': Specifies the ISO B9 size: 44 mm by 62 mm as defined in ISO
    216
 'iso-b10': Specifies the ISO B10 size: 31 mm by 44 mm as defined in
    ISO 216
ToP   noToC   RFC2911 - Page 203
 'na-letter': Specifies the North American letter size: 8.5 inches by
    11 inches
 'na-legal': Specifies the North American legal size: 8.5 inches by 14
    inches
 'na-8x10': Specifies the North American 8 inches by 10 inches
 'na-5x7': Specifies the North American 5 inches by 7 inches
 'executive': Specifies the executive size (7.25 X 10.5 in)
 'folio': Specifies the folio size (8.5 X 13 in)
 'invoice': Specifies the invoice size (5.5 X 8.5 in)
 'ledger': Specifies the ledger size (11 X 17 in)
 'quarto': Specifies the quarto size (8.5 X 10.83 in)
 'iso-c3': Specifies the ISO C3 size: 324 mm by 458 mm as defined in
    ISO 269
 'iso-c4': Specifies the ISO C4 size: 229 mm by 324 mm as defined in
    ISO 269
 'iso-c5': Specifies the ISO C5 size: 162 mm by 229 mm as defined in
    ISO 269
 'iso-c6': Specifies the ISO C6 size: 114 mm by 162 mm as defined in
    ISO 269
 'iso-designated-long': Specifies the ISO Designated Long size: 110 mm
    by 220 mm as defined in ISO 269
 'na-10x13-envelope': Specifies the North American 10x13 size: 10
    inches by 13 inches
 'na-9x12-envelope': Specifies the North American 9x12 size: 9 inches
    by 12 inches
 'na-number-10-envelope': Specifies the North American number 10
    business envelope size: 4.125 inches by 9.5 inches
 'na-7x9-envelope': Specifies the North American 7x9 inch envelope
    size
 'na-9x11-envelope': Specifies the North American 9x11 inch envelope
    size
 'na-10x14-envelope': Specifies the North American 10x14 inch envelope
    size
 'na-number-9-envelope': Specifies the North American number 9
    business envelope size
 'na-6x9-envelope': Specifies the North American 6x9 envelope size
 'na-10x15-envelope': Specifies the North American 10x15 envelope size
 'monarch-envelope': Specifies the Monarch envelope size (3.87 x 7.5
    in)
 'jis-b0': Specifies the JIS B0 size: 1030mm x 1456mm
 'jis-b1': Specifies the JIS B1 size: 728mm x 1030mm
 'jis-b2': Specifies the JIS B2 size: 515mm x 728mm
 'jis-b3': Specifies the JIS B3 size: 364mm x 515mm
 'jis-b4': Specifies the JIS B4 size: 257mm x 364mm
 'jis-b5': Specifies the JIS B5 size: 182mm x 257mm
 'jis-b6': Specifies the JIS B6 size: 128mm x 182mm
 'jis-b7': Specifies the JIS B7 size: 91mm x 128mm
 'jis-b8': Specifies the JIS B8 size: 64mm x 91mm
ToP   noToC   RFC2911 - Page 204
 'jis-b9': Specifies the JIS B9 size: 45mm x 64mm
 'jis-b10': Specifies the JIS B10 size: 32mm x 45mm

   The following standard values are defined for American Standard (i.e.
   ANSI) engineering media sizes:

    'a': Specifies the engineering ANSI A size medium: 8.5 inches x 11
       inches
    'b': Specifies the engineering ANSI B size medium: 11 inches x 17
       inches
    'c': Specifies the engineering ANSI C size medium: 17 inches x 22
       inches
    'd': Specifies the engineering ANSI D size medium: 22 inches x 34
       inches
    'e': Specifies the engineering ANSI E size medium: 34 inches x 44
       inches

   The following standard values are defined for American Architectural
   engineering media sizes:

    'arch-a': Specifies the Architectural A size medium: 9 inches x 12
       inches
    'arch-b': Specifies the Architectural B size medium: 12 inches x 18
       inches
    'arch-c': Specifies the Architectural C size medium: 18 inches x 24
       inches
    'arch-d': Specifies the Architectural D size medium: 24 inches x 36
       inches
    'arch-e': Specifies the Architectural E size medium: 36 inches x 48
       inches


(next page on part 9)

Next Section