IPP Mail Archive: IPP> OPS - Updated IPP "Job and Print

IPP Mail Archive: IPP> OPS - Updated IPP "Job and Print

IPP> OPS - Updated IPP "Job and Printer Set Operations" spec down load ed

From: Hastings, Tom N (hastings@cp10.es.xerox.com)
Date: Wed Mar 29 2000 - 22:39:51 EST

  • Next message: Michael Sweet: "Re: IPP> New CUPS 1.1 beta and set-job-attributes extension [why not use "job-sheets"?]"

    I've made an Internet-Draft too and put them all in the usual place, plus
    replacing the older version in the meetings directories. There are no
    issues. It is ready for IPP WG Last Call.





    Here is the 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], 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)
                    printer-xri-supported (1setOf collection)
                    xri-uri-scheme-supported (1setOf uriScheme)
                    xri-authentication-supported (1setOf type2 keyword)
                    xri-security-supported (1setOf type2 keyword)

    Here is the change history:

    1.1 Changes to the March 21, 2000 version to make the March 23, 2000
    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
    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
    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.
    1.2 Changes to the March 8, 2000 version to make the March 21, 2000
    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.

    This archive was generated by hypermail 2b29 : Wed Mar 29 2000 - 22:46:26 EST