draft-ietf-ipp-protocol-02.txt   draft-ietf-ipp-protocol-03.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
INTERNET-DRAFT INTERNET-DRAFT
Robert Herriot (editor) Robert Herriot (editor)
Sun Microsystems Sun Microsystems
Sylvan Butler Sylvan Butler
Hewlett-Packard Hewlett-Packard
Paul Moore Paul Moore
Microsoft. Microsoft.
Randy Turner Randy Turner
Sharp Labs Sharp Labs
October 23, 1997 November 7, 1997
Internet Printing Protocol/1.0: Protocol Specification Internet Printing Protocol/1.0: Protocol Specification
draft-ietf-ipp-protocol-02.txt draft-ietf-ipp-protocol-03.txt
Copyright c The Internet Society (date). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 49 skipping to change at page 1, line 50
aspects of a new Internet Printing Protocol (IPP). IPP is an aspects of a new Internet Printing Protocol (IPP). IPP is an
application level protocol that can be used for distributed printing application level protocol that can be used for distributed printing
using Internet tools and technology. The protocol is heavily influenced using Internet tools and technology. The protocol is heavily influenced
by the printing model introduced in the Document Printing Application by the printing model introduced in the Document Printing Application
(ISO/IEC 10175 DPA) standard [dpa]. Although DPA specifies both end (ISO/IEC 10175 DPA) standard [dpa]. Although DPA specifies both end
user and administrative features, IPP version 1.0 is focused only on end user and administrative features, IPP version 1.0 is focused only on end
user functionality. user functionality.
The full set of IPP documents includes: The full set of IPP documents includes:
Internet Printing Protocol: Requirements Requirements for an Internet Printing Protocol [ipp-req]
Internet Printing Protocol/1.0: Model and Semantics Internet Printing Protocol/1.0: Model and Semantics [ipp-mod]
Internet Printing Protocol/1.0: Protocol Specification Internet Printing Protocol/1.0: Protocol Specification (this
document)
The requirements document takes a broad look at distributed printing The requirements document takes a broad look at distributed printing
functionality, and it enumerates real-life scenarios that help to functionality, and it enumerates real-life scenarios that help to
clarify the features that need to be included in a printing protocol for clarify the features that need to be included in a printing protocol for
the Internet. It identifies requirements for three types of users: end the Internet. It identifies requirements for three types of users: end
Moore and Turner Expires May 7, 1998
users, operators, and administrators. The requirements document calls users, operators, and administrators. The requirements document calls
out a subset of end user requirements that MUST be satisfied in the out a subset of end user requirements that MUST be satisfied in the
Moore and Turner Expires April 23, 1998
first version of IPP. Operator and administrator requirements are out first version of IPP. Operator and administrator requirements are out
of scope for v1.0. The model and semantics document describes a of scope for v1.0. The model and semantics document describes a
simplified model with abstract objects, their attributes, and their simplified model with abstract objects, their attributes, and their
operations. The model introduces a Printer object and a Job object. The operations. The model introduces a Printer object and a Job object. The
Job object supports multiple documents per job. The protocol Job object supports multiple documents per job. The protocol
specification is formal document which incorporates the ideas in all the specification is formal document which incorporates the ideas in all the
other documents into a concrete mapping using clearly defined data other documents into a concrete mapping using clearly defined data
representations and transport protocol mappings that real implementers representations and transport protocol mappings that real implementers
can use to develop interoperable client and printer (server) side can use to develop interoperable client and printer (server) side
components. components.
skipping to change at page 2, line 28 skipping to change at page 3, line 5
Specification'' document. Specification'' document.
Notice Notice
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. Director.
Copyright c The Internet Society (date). All Rights Reserved. Moore and Turner Expires May 7, 1998
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 implmentation 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
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Moore and Turner Expires April 23, 1998
Table of Contents Table of Contents
1. Introduction........................................................4 1. Introduction........................................................4
2. Conformance Terminology.............................................4 2. Conformance Terminology.............................................4
3. Encoding of the Operation Layer....................................4 3. Encoding of the Operation Layer....................................4
3.1 Picture of the Encoding.........................................5 3.1 Picture of the Encoding.........................................5
3.2 Syntax of Encoding..............................................6 3.2 Syntax of Encoding..............................................6
3.3 Version.........................................................8 3.3 Version.........................................................8
3.4 Mapping of Operations...........................................8 3.4 Mapping of Operations...........................................8
3.5 Mapping of Status-code..........................................8 3.5 Mapping of Status-code..........................................8
3.6 Tags............................................................. 8 3.6 Tags.............................................................
3.6.1 Delimiter Tags.............................................8 3.6.1 Delimiter Tags.............................................8
3.6.2 Value Tags.................................................9 3.6.2 Value Tags.................................................9
3.7 Name-Lengths...................................................11 3.7 Name-Lengths...................................................11
3.8 Mapping of Attribute Names....................................11 3.8 Mapping of Attribute Names....................................11
3.9 Value Lengths..................................................12 3.9 Value Lengths..................................................12
3.10 Mapping of Attribute Values...................................13 3.10 Mapping of Attribute Values...................................12
3.11 Data............................................................ 15 3.11 Data............................................................
4. Encoding of Transport Layer........................................15 4. Encoding of Transport Layer........................................14
4.1 General Headers................................................16 4.1 General Headers................................................15
4.2 Request Headers...............................................17 4.2 Request Headers...............................................16
4.3 Response Headers...............................................18 4.3 Response Headers...............................................16
4.4 Entity Headers................................................18 4.4 Entity Headers................................................17
5. Security Considerations............................................19 5. Security Considerations............................................17
6. References.........................................................20 6. Copyright..........................................................18
7. Author's Address...................................................21 7. References.........................................................19
8. Other Participants:................................................22 8. Author's Address...................................................20
9. Appendix A: Protocol Examples......................................22 9. Other Participants:................................................20
9.1 Print-Job Request..............................................22 10. Appendix A: Protocol Examples.....................................21
9.2 Print-Job Response (successful)................................23 10.1 Print-Job Request.............................................21
9.3 Print-Job Response (failure)...................................24 10.2 Print-Job Response (successful)...............................22
9.4 Print-URI Request..............................................25 10.3 Print-Job Response (failure)..................................23
9.5 Create-Job Request.............................................26 10.4 Print-URI Request.............................................24
9.6 Get-Jobs Request...............................................26 10.5 Create-Job Request............................................25
9.7 Get-Jobs Response..............................................27 10.6 Get-Jobs Request..............................................25
10. Appendix B: Mapping of Each Operation in the Encoding.............28 10.7 Get-Jobs Response.............................................26
11. Appendix C: Hints to implementors using IPP with SSL3.............32 11. Appendix B: Mapping of Each Operation in the Encoding.............27
12. Appendix C: Hints to implementors using IPP with SSL3.............32
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
1. Introduction 1. Introduction
This document contains the rules for encoding IPP operations and This document contains the rules for encoding IPP operations and
describes two layers: the transport layer and the operation layer. describes two layers: the transport layer and the operation layer.
The transport layer consists of an HTTP/1.1 request or response. RFC The transport layer consists of an HTTP/1.1 request or response. RFC
2068 [r2068] describes HTTP/1.1. This document specifies the HTTP 2068 [rfc2068] describes HTTP/1.1. This document specifies the HTTP
headers that an IPP implementation supports. headers that an IPP implementation supports.
The operation layer consists of a message body in an HTTP request or The operation layer consists of a message body in an HTTP request or
response. The document "Internet Printing Protocol/1.0: Model and response. The document "Internet Printing Protocol/1.0: Model and
Semantics" [ipp-m] defines the semantics of such a message body and the Semantics" [ipp-mod] defines the semantics of such a message body and
supported values. This document specifies the encoding of an IPP the supported values. This document specifies the encoding of an IPP
operation. The aforementioned document [ipp-m] is henceforth referred to operation. The aforementioned document [ipp-mod] is henceforth referred
as the "IPP model document" to as the "IPP model document"
2. Conformance Terminology 2. Conformance Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [r2119]. document are to be interpreted as described in RFC 2119 [rfc2119].
3. Encoding of the Operation Layer 3. Encoding of the Operation Layer
The operation layer SHALL contain a single operation request or The operation layer SHALL contain a single operation request or
operation response. operation response.
The encoding consists of octets as the most primitive type. There are The encoding consists of octets as the most primitive type. There are
several types built from octets, but two important types are integers several types built from octets, but three important types are
and characters, on which most other data types are built. Every integers, character strings and octet strings, on which most other
character in this encoding SHALL be a member of the UCS-2 coded data types are built. Every character string in this encoding SHALL be a
character set and SHALL be encoded using UTF-8 which uses 1 to 3 octets sequence of characters where the characters are associated with some
per character. Every integer in this encoding SHALL be encoded as a charset and some natural language. . A character string MUST be in
signed integer using two's-complement binary encoding with big-endian "network byte order" with the first character in the value (according to
format (also known as "network order" and "most significant byte reading order) being the first character in the encoding. A character
first"). The number of octets for an integer SHALL be 1, 2 or 4, string whose associated charset is US-ASCII whose associated natural
depending on usage in the protocol. Such one-octet integers, henceforth language is US English is henceforth called a US-ASCII-STRING. A
called SIGNED-BYTE, are used for the version and tag fields. Such two- character string whose associated charset and natural language are
byte integers, henceforth called SIGNED-SHORT are used for the specified in a request or response as described in the model document is
operation, status-code and length fields. Four byte integers, henceforth henceforth called a LOCALIZED-STRING. . An octet string MUST be in
called SIGNED-INTEGER, are used for values fields. "network byte order" with the first octet in the value (according to
reading order) being the first octet in the encoding Every integer in
this encoding SHALL be encoded as a signed integer using two's-
complement binary encoding with big-endian format (also known as
"network order" and "most significant byte first"). The number of octets
for an integer SHALL be 1, 2 or 4, depending on usage in the protocol.
Such one-octet integers, henceforth called SIGNED-BYTE, are used for the
version and tag fields. Such two-byte integers, henceforth called
SIGNED-SHORT are used for the operation, status-code and length fields.
Four byte integers, henceforth called SIGNED-INTEGER, are used for
values fields.
Moore and Turner Expires May 7, 1998
The following two sections present the operation layer in two ways The following two sections present the operation layer in two ways
. informally through pictures and description . informally through pictures and description
. formally through Augmented Backus-Naur Form (ABNF), as specified by . formally through Augmented Backus-Naur Form (ABNF), as specified by
draft-ietf-drums-abnf-02.txt [abnf] draft-ietf-drums-abnf-02.txt [abnf]
Moore and Turner Expires April 23, 1998
3.1 Picture of the Encoding 3.1 Picture of the Encoding
The encoding for an operation request or response consists of: The encoding for an operation request or response consists of:
----------------------------------------------- -----------------------------------------------
| version | 2 bytes - required | version | 2 bytes - required
----------------------------------------------- -----------------------------------------------
|operation (request) or status-code (response)| 2 bytes - required |operation (request) or status-code (response)| 2 bytes - required
----------------------------------------------------------- -----------------------------------------------------------
| xxx-attributes-tag | 1 byte | | xxx-attributes-tag | 1 byte |
skipping to change at page 5, line 31 skipping to change at page 5, line 37
----------------------------------------------- -----------------------------------------------
| data | q bytes - optional | data | q bytes - optional
----------------------------------------------- -----------------------------------------------
The xxx-attributes-tag and xxx-attribute-sequence represents four The xxx-attributes-tag and xxx-attribute-sequence represents four
different values of "xxx", namely, operation, job, printer and different values of "xxx", namely, operation, job, printer and
unsupported-job. The xxx-attributes-tag and xxx-attribute-sequence may unsupported-job. The xxx-attributes-tag and xxx-attribute-sequence may
be omitted if the operation has no attributes or it may be repeated with be omitted if the operation has no attributes or it may be repeated with
the same or different values of "xxx" in ways that are specific to each the same or different values of "xxx" in ways that are specific to each
operation. The data is omitted from some operations, but the data-tag is operation. The data is omitted from some operations, but the data-tag is
present even when the data is omitted. Note, the xxx-attributestags and present even when the data is omitted. Note, the xxx-attributes-tags and
data-tag are called `delimiter-tags'. data-tag are called `delimiter-tags'.
Note: the xxx-attribute-sequence, shown above may consist of 0 bytes, Note: the xxx-attribute-sequence, shown above may consist of 0 bytes,
according to the rule below. according to the rule below.
An xxx-attributes-sequence consists of zero or more compound-attributes. An xxx-attributes-sequence consists of zero or more compound-attributes.
----------------------------------------------- -----------------------------------------------
| compound-attribute | s bytes - 0 or more | compound-attribute | s bytes - 0 or more
----------------------------------------------- -----------------------------------------------
A compound-attribute consists an attribute with a single value followed A compound-attribute consists of an attribute with a single value
by zero or more additional values. followed by zero or more additional values.
Note: a `compound-attribute' represents a single attribute in the model Note: a `compound-attribute' represents a single attribute in the model
document. The `additional value' syntax is for attributes with 2 or document. The `additional value' syntax is for attributes with 2 or
more values. more values.
Each attribute consists of: Each attribute consists of:
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
----------------------------------------------- -----------------------------------------------
| value-tag | 1 byte | value-tag | 1 byte
----------------------------------------------- -----------------------------------------------
| name-length (value is u) | 2 bytes | name-length (value is u) | 2 bytes
----------------------------------------------- -----------------------------------------------
| name | u bytes | name | u bytes
----------------------------------------------- -----------------------------------------------
| value-length (value is v) | 2 bytes | value-length (value is v) | 2 bytes
----------------------------------------------- -----------------------------------------------
| value | v bytes | value | v bytes
skipping to change at page 7, line 5 skipping to change at page 7, line 5
. attributes . attributes
. data . data
. the remainder of a single attribute where the tag specifies the . the remainder of a single attribute where the tag specifies the
type of the value. type of the value.
3.2 Syntax of Encoding 3.2 Syntax of Encoding
The syntax below is ABNF [abnf] except `strings of literals' SHALL be The syntax below is ABNF [abnf] except `strings of literals' SHALL be
case sensitive. For example `a' means lower case `a' and not upper case case sensitive. For example `a' means lower case `a' and not upper case
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
`A'. In addition, SIGNED-BYTE and SIGNED-SHORT fields are represented `A'. In addition, SIGNED-BYTE and SIGNED-SHORT fields are represented
as `%x' values which show their range of values. as `%x' values which show their range of values.
ipp-message = ipp-request / ipp-response ipp-message = ipp-request / ipp-response
ipp-request = version operation ipp-request = version operation
*(xxx-attributes-tag xxx-attribute-sequence) data-tag data *(xxx-attributes-tag xxx-attribute-sequence) data-tag data
ipp-response = version status-code ipp-response = version status-code
*(xxx-attributes-tag xxx-attribute-sequence) data-tag data *(xxx-attributes-tag xxx-attribute-sequence) data-tag data
xxx-attribute-sequence = *compound-attribute xxx-attribute-sequence = *compound-attribute
skipping to change at page 7, line 44 skipping to change at page 7, line 44
value-length = SIGNED-SHORT ; number of octets of `value' value-length = SIGNED-SHORT ; number of octets of `value'
value = OCTET-STRING value = OCTET-STRING
data = OCTET-STRING data = OCTET-STRING
zero-name-length = %x00.00 ; name-length of 0 zero-name-length = %x00.00 ; name-length of 0
operation-attributes-tag= %x01 ; tag of 1 operation-attributes-tag= %x01 ; tag of 1
job-attributes-tag = %x02 ; tag of 2 job-attributes-tag = %x02 ; tag of 2
printer-attributes-tag = %x04 ; tag of 4 printer-attributes-tag = %x04 ; tag of 4
unsupported-job-attributes-tag = %x05 ; tag of 5 unsupported-job-attributes-tag = %x05 ; tag of 5
data-tag = %x03 ; tag of data-tag = %x03 ;
3 tag of 3
value-tag = %x10-FF value-tag = %x10-FF
SIGNED-BYTE = BYTE SIGNED-BYTE = BYTE
SIGNED-SHORT = 2BYTE SIGNED-SHORT = 2BYTE
DIGIT = %x30-39 ; "0" to "9" DIGIT = %x30-39 ; "0" to "9"
LALPHA = %x61-7A ; "a" to "z" LALPHA = %x61-7A ; "a" to "z"
BYTE = %x00-FF BYTE = %x00-FF
OCTET-STRING = *BYTE OCTET-STRING = *BYTE
The syntax allows an xxx-attributestag to be present when the xxx- The syntax allows an xxx-attributes-tag to be present when the xxx-
attribute-sequence that follows is empty. The syntax is defined this way attribute-sequence that follows is empty. The syntax is defined this way
to allow for the response of Get-Jobs where no attributes are returned to allow for the response of Get-Jobs where no attributes are returned
for some job-objects. Although it is RECOMMENDED that the sender not for some job-objects. Although it is RECOMMENDED that the sender not
send an xxx-attributestag if there are no attributes (except in the Get- send an xxx-attributes-tag if there are no attributes (except in the
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
Jobs response just mentioned), the receiver MUST be able to decode such Get-Jobs response just mentioned), the receiver MUST be able to decode
syntax. such syntax.
3.3 Version 3.3 Version
The version SHALL consist of a major and minor version, each of which The version SHALL consist of a major and minor version, each of which
SHALL be represented by a SIGNED-BYTE. The protocol described in this SHALL be represented by a SIGNED-BYTE. The protocol described in this
document SHALL have a major version of 1 (0x01) and a minor version of document SHALL have a major version of 1 (0x01) and a minor version of
0 (0x00). The ABNF for these two bytes SHALL be %x01.00. 0 (0x00). The ABNF for these two bytes SHALL be %x01.00.
3.4 Mapping of Operations 3.4 Mapping of Operations
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Tag Value (Hex) Delimiter Tag Value (Hex) Delimiter
0x00 reserved 0x00 reserved
0x01 operation-attributes-tag 0x01 operation-attributes-tag
0x02 job-attributes-tag 0x02 job-attributes-tag
0x03 data-tag 0x03 data-tag
0x04 printer-attributes-tag 0x04 printer-attributes-tag
0x05 unsupported-job-attributes-tag 0x05 unsupported-job-attributes-tag
0x06-0x0F reserved for future delimiters 0x06-0x0F reserved for future delimiters
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
When an xxx-attributes-tag occurs in the protocol, it SHALL mean that When an xxx-attributes-tag occurs in the protocol, it SHALL mean that
the zero or more following attributes up to the next delimiter tag are the zero or more following attributes up to the next delimiter tag are
xxx attributes as defined in the model document, where xxx is operation, xxx attributes as defined in the model document, where xxx is operation,
job, printer, unsupported-job. job, printer, unsupported-job.
Doing substitution for xxx in the above paragraph, this means the Doing substitution for xxx in the above paragraph, this means the
following. When an operation-attributes-tag occurs in the protocol, it following. When an operation-attributes-tag occurs in the protocol, it
SHALL mean that the zero or more following attributes up to the next SHALL mean that the zero or more following attributes up to the next
delimiter tag are operation attributes as defined in the model document. delimiter tag are operation attributes as defined in the model document.
When an job-attributes-tag occurs in the protocol, it SHALL mean that When an job-attributes-tag occurs in the protocol, it SHALL mean that
the zero or more following attributes up to the next delimiter tag are the zero or more following attributes up to the next delimiter tag are
job attributes as defined in the model document. When an printer- job attributes as defined in the model document. When an printer-
attributes-tag occurs in the protocol, it SHALL mean that the zero or attributes-tag occurs in the protocol, it SHALL mean that the zero or
more following attributes up to the next delimiter tag are printer more following attributes up to the next delimiter tag are printer
attributes as defined in the model document. When an unsupported-job- attributes as defined in the model document. When an unsupported-job-
attributes-tag occurs in the protocol, it SHALL mean that the zero or attributes-tag occurs in the protocol, it SHALL mean that the zero or
more following attributes up to the next delimiter tag are unsupported- more following attributes up to the next delimiter tag are unsupported-
job attributes as defined in the model document. job attributes as defined in the model document.
Each of the four xxx-attributes-tags defined above is OPTIONAL in an The operation-attributes-tag and data-tag SHALL each occur exactly once
operation and each SHALL occur at most once in an operation, except for in an operation. The operation-attributes-tag SHALL be the first tag
job-attributes-tag in a Get-Jobs response which may occur zero or more delimiter, and the data-tag SHALL be the last tag delimiter.
times. The data-tag SHALL occur exactly once in an operation.
If an operation contains an operations-attribute-tag, it SHALL be the Each of the other three xxx-attributes-tags defined above is OPTIONAL
first tag delimiter. The data-tag SHALL be the last tag delimiter. in an operation and each SHALL occur at most once in an operation,
except for job-attributes-tag in a Get-Jobs response which may occur
zero or more times.
The order and presence of delimiter tags for each operation request and The order and presence of delimiter tags for each operation request and
each operation response SHALL be that defined in the model document. For each operation response SHALL be that defined in the model document. For
further details, see Section 3.8 Mapping of Attribute Names and further details, see Section 3.8 Mapping of Attribute Names and
Appendix B: Mapping of Each Operation in the Encoding. Appendix B: Mapping of Each Operation in the Encoding.
3.6.2 Value Tags 3.6.2 Value Tags
The remaining tables show values for the value-tag, which is the first The remaining tables show values for the value-tag, which is the first
octet of an attribute. The value-tag specifies the type of the value of octet of an attribute. The value-tag specifies the type of the value of
the attribute. The value of the value-tag of an attribute SHALL either the attribute. If the value-tag specifies a type of compoundValue, it
be a type value specified in the model document or an "out-of-band" represents a compound value whose type is the that of the last member of
value, such as "unsupported" or "default". If the value of value-tag the compound value. The following table specifies the "out-of-band"
for an attribute is not "out-of-band" and differs from the value type values for the value-tag.
specified by the model document, then a printer receiving such a request
MAY reject the attribute or just the value. A client receiving such a
response MAY ignore the attribute or just the value.
If ipp-attribute-fidelity is true and a printer rejects a value, it is
the same as rejecting the attribute. If ipp-attribute-fidelity is false
and a printer rejects a value, or it a client rejects a value, then it
is as if the attribute didn't have that value. If after rejecting
values, the attribute no longer has any values the attribute is
rejected.
Moore and Turner Expires April 23, 1998
Note: the intent of the above rule is for servers to be able to
understand text and name values when they don't support the
naturalLanguage override for the value.
The following table specifies the "out-of-band" values for the value-
tag.
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x10 unsupported 0x10 unsupported
0x11 default 0x11 reserved for future `default'
0x12 no-value 0x12 unknown
0x13 compoundValue 0x13 compoundValue
0x14-0x1F reserved for future "out-of-band" values. 0x14-0x1F reserved for future "out-of-band" values.
The "unsupported" value SHALL be used in the attribute-sequence of an The "unsupported" value SHALL be used in the attribute-sequence of an
error response for those attributes which the printer does not support. error response for those attributes which the printer does not support.
Moore and Turner Expires May 7, 1998
The "default" value is reserved for future use of setting value back to The "default" value is reserved for future use of setting value back to
their default value. The "no-value" value is used for the "no-value" their default value. The "unknown" value is used for the value of a
value in model, e.g. when a document-attribute is returned as a set of supported attribute when its value is temporarily unknown. . The
values and an attribute has no specified value for one or more of the "compoundValue" SHALL be used to form a single value from a collection
documents. The "compoundValue" SHALL be used to form a single value of values, and its value is the number of members forming the compound
from a collection of values, and its value is the number of members value, excluding the compoundValue. For example, a text value with a
forming the compound value, excluding the compoundValue. For example, a naturalLanguage override consists of 3 "values": a compoundValue with
text value with a naturalLanguage override consists of 3 "values": a value 2, a naturalLanguage value and a text value.
compoundValue with value 2, a naturalLanguage value and a text value.
The following table specifies the integer values for the value-tag The following table specifies the integer values for the value-tag
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x20 reserved 0x20 reserved
0x21 integer 0x21 integer
0x22 boolean 0x22 boolean
0x23 enum 0x23 enum
0x24-0x2F reserved for future integer types 0x24-0x2F reserved for future integer types
skipping to change at page 11, line 5 skipping to change at page 10, line 39
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x30 octetString with an unspecified format 0x30 octetString with an unspecified format
0x31 dateTime 0x31 dateTime
0x32 resolution 0x32 resolution
0x33 rangeOfInteger 0x33 rangeOfInteger
0x34 reserved for dictionary (in the future) 0x34 reserved for dictionary (in the future)
0x35-0x3F reserved for future octetString types 0x35-0x3F reserved for future octetString types
Moore and Turner Expires April 23, 1998
The following table specifies the character-string values for the value- The following table specifies the character-string values for the value-
tag tag
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x40 reserved 0x40 reserved
0x41 text 0x41 text
0x42 name 0x42 name
0x43 reserved 0x43 reserved
0x44 keyword 0x44 keyword
0x45 uri 0x45 uri
0x46 uriScheme 0x46 uriScheme
0x47 charSet 0x47 charset
0x48 naturalLanguage 0x48 naturalLanguage
0x49 mediaType 0x49 mimeMediaType
0x4A-0x5F reserved for future character string types 0x4A-0x5F reserved for future character string types
NOTE: 0x40 is reserved for "generic character-string" if should ever be NOTE: 0x40 is reserved for "generic character-string" if should ever be
needed. needed.
Moore and Turner Expires May 7, 1998
The values 0x60-0xFF are reserved for future types. There are no values The values 0x60-0xFF are reserved for future types. There are no values
allocated for private extensions. A new type must be registered via the allocated for private extensions. A new type must be registered via the
type 2 process. type 2 process.
3.7 Name-Lengths 3.7 Name-Lengths
The name-length field SHALL consist of a SIGNED-SHORT. This field SHALL The name-length field SHALL consist of a SIGNED-SHORT. This field SHALL
specify the number of octets in the name field which follows the name- specify the number of octets in the name field which follows the name-
length field, excluding the two bytes of the name-length field. length field, excluding the two bytes of the name-length field.
skipping to change at page 12, line 4 skipping to change at page 11, line 36
Some attributes are encoded in a special position. These attribute are: Some attributes are encoded in a special position. These attribute are:
. "printer-uri": The target printer-uri of each operation in the IPP . "printer-uri": The target printer-uri of each operation in the IPP
model document SHALL be specified outside of the operation layer model document SHALL be specified outside of the operation layer
as the request-URI on the Request-Line at the HTTP level. as the request-URI on the Request-Line at the HTTP level.
. "job-uri": The target job-uri of each operation in the IPP model . "job-uri": The target job-uri of each operation in the IPP model
document SHALL be specified outside of the operation layer as the document SHALL be specified outside of the operation layer as the
request-URI on the Request-Line at the HTTP level. request-URI on the Request-Line at the HTTP level.
. "document-content": The attribute named "document-content" in the . "document-content": The attribute named "document-content" in the
IPP model document SHALL become the "data" in the operation layer. IPP model document SHALL become the "data" in the operation layer.
Moore and Turner Expires April 23, 1998
. "status-code": The attribute named "status-code" in the IPP model . "status-code": The attribute named "status-code" in the IPP model
document SHALL become the "status-code" field in the operation document SHALL become the "status-code" field in the operation
layer response. layer response.
The model document arranges the remaining attributes into groups for The model document arranges the remaining attributes into groups for
each operation request and response. Each such group SHALL be each operation request and response. Each such group SHALL be
represented in the protocol by an xxx-attribute-sequence preceded by the represented in the protocol by an xxx-attribute-sequence preceded by the
appropriate xxx-attributes-tag (See the table below and Appendix B: appropriate xxx-attributes-tag (See the table below and Appendix B:
Mapping of Each Operation in the Encoding). In addition, the order of Mapping of Each Operation in the Encoding). In addition, the order of
these xxx-attributes-tags and xxx-attribute-sequences in the protocol these xxx-attributes-tags and xxx-attribute-sequences in the protocol
skipping to change at page 12, line 28 skipping to change at page 12, line 4
maps the model document group name to xxx-attributes-sequence maps the model document group name to xxx-attributes-sequence
Model Document Group xxx-attributes-sequence Model Document Group xxx-attributes-sequence
Operation Attributes operations-attributes-sequence Operation Attributes operations-attributes-sequence
Job Template Attributes job-attributes-sequence Job Template Attributes job-attributes-sequence
Job Object Attributes job-attributes-sequence Job Object Attributes job-attributes-sequence
Unsupported Attributes unsupported-job-attributes-sequence Unsupported Attributes unsupported-job-attributes-sequence
Requested Attributes (Get- job-attributes-sequence Requested Attributes (Get- job-attributes-sequence
Attributes of job object) Attributes of job object)
Moore and Turner Expires May 7, 1998
Requested Attributes (Get- printer-attributes-sequence Requested Attributes (Get- printer-attributes-sequence
Attributes of printer object) Attributes of printer object)
Document Content in a special position as described above Document Content in a special position as described above
ISSUE: coordinate this with the model document. ISSUE: coordinate this with the model document.
If an operation contains attributes from more than one job object (e.g. If an operation contains attributes from more than one job object (e.g.
Get-Jobs response), the attributes from each job object SHALL be in a Get-Jobs response), the attributes from each job object SHALL be in a
separate job-attribute-sequence, such that the attributes from the ith separate job-attribute-sequence, such that the attributes from the ith
job object are in the ith job-attribute-sequence. See Section 10 job object are in the ith job-attribute-sequence. See Section 11
"Appendix B: Mapping of Each Operation in the Encoding" for table "Appendix B: Mapping of Each Operation in the Encoding" for table
showing the application of the rules above. showing the application of the rules above.
3.9 Value Lengths 3.9 Value Lengths
Each attribute value SHALL be preceded by a SIGNED-SHORT which SHALL Each attribute value SHALL be preceded by a SIGNED-SHORT which SHALL
specify the number of octets in the value which follows this length, specify the number of octets in the value which follows this length,
exclusive of the two bytes specifying the length. exclusive of the two bytes specifying the length.
For any of the types represented by binary signed integers, the sender For any of the types represented by binary signed integers, the sender
MUST encode the value in exactly four octets.. MUST encode the value in exactly four octets..
For any of the types represented by character-strings, the sender MUST For any of the types represented by character-strings, the sender MUST
encode the value with all the characters of the string and without any encode the value with all the characters of the string and without any
padding characters. padding characters.
If a value-tag contains an "out-of-band" value, such as "unsupported", If a value-tag contains an "out-of-band" value which is not
the value-length SHALL be 0 and the value empty " the value has no compoundValue, such as "unsupported", the value-length SHALL be 0 and
meaning when the value-tag has an "out-of-band" value. If a printer or the value empty " the value has no meaning when the value-tag has an
client receives an operation with a nonzero value-length in this case, "out-of-band" value. If a printer or client receives an operation with a
it SHALL ignore the value field. nonzero value-length in this case, it SHALL ignore the value field.
Moore and Turner Expires April 23, 1998
3.10 Mapping of Attribute Values 3.10 Mapping of Attribute Values
The following SHALL be the mapping of attribute values to their IPP The syntax types and most of the details of their representation are
encoding in the value field. The syntax types are defined in the IPP defined in the IPP model document. The table below augments the
model document. information in the model document, and defines the syntax types from the
model document in terms of the 5 basic types defined in section 3
Syntax of Encoding Encoding of the Operation Layer. The 5 types are US-ASCII-STRING,
Attribute Value LOCALIZED-STRING, SIGNED-INTEGER, SIGNED-SHORT, SIGNED-BYTE, and OCTET-
STRING.
text an octet string whose charset and language is
that specified within the operation request or
response.
The attributes-charset attribute with a value of
type `charset' MUST be in the operations-
attribute sequence unless the request or response
contains no attributes. It specifies the charset
for all text and name values of attributes.
The attributes-natural-language attribute with a
value of type `naturalLanguage' MUST be in the
operations-attribute sequence unless the request
or response contains no attributes. It specifies
the language for all text and name values of
attributes unless overridden. The language can
be overridden on a per-object or a per-value
basis.
The language can be overridden on a per-object
basis only for a job-sequence within a Get-Jobs
response. If the attributes-natural-language
attribute is present within such a context, it
must have a value of type `naturalLanguage' and
it overrides the language for all text and name
attributes within the job-attributes sequence
containing it, but not for attributes in any
other xxx-attribute-sequence.
The language can be overridden on a per-value
basis by syntactically preceding the text or name
value by two values: a value of type
compoundValue whose value is 2 and a value of
type naturalLanguage whose value is the language
override. From a protocol syntax view, the
compoundValue, the naturalLanguage value and the
text or name value appear as three separate
values of a single attribute, but from a semantic
view, the Printer treats them as a single value
where the naturalLanguage value overrides the
language of the immediately following text or
name value in the attribute. Any text or name
values in the same or other attributes are not
affected by the override. If an attribute
consists of a single text or name value, the
language value turns it into an attribute with
two values from a syntactic view.
The text is encoded in "network byte order" with
Moore and Turner Expires April 23, 1998
Syntax of Encoding Syntax of Encoding
Attribute Value Attribute Value
the first character in the text (according to text, name LOCALIZED-STRING.
reading order) being the first character in the The override natural language mechanism is
encoding. encoded by syntactically preceding the text or
name same as text name value by two values: first a value of type
charset an octet string of US-ASCII encoded characters compoundValue whose value is 2 and second a value
specified in RFC 2046 [r2046] and contained in of type naturalLanguage whose value is the
the IANA character-set Registry [iana] according language override. From a protocol syntax view,
to the IANA procedures [char].
naturalLanguage an octet string of US-ASCII encoded characters
and with a syntax specified by RFC 1766 [r1766]
mediaType an octet string of US-ASCII encoded characters
defined by RFC 2046 [r2046] and registered
according to the procedures of RFC 2048 [r2048]
for identifying a document format. The value MAY
include a charset parameter, depending on the
specification of the Media Type in the IANA
Registry [iana]. Examples:
keyword an octet string of US-ASCII encoded characters. .
Allowed values are defined in the IPP model
document
uri as specified by RFC 1630 [r1630]
uriScheme same as keyword
boolean one binary octet where 0x00 is `false' and 0x01
is `true'
integer a SIGNED-INTEGER, defined previously as a signed
integer using two's-complement binary encoding in
four octets with big-endian format (also known as
"network order" and "most significant byte
first").
enum same as integer. Allowed integer values are
defined in the IPP model document
compoundValue has the same representation as an integer, but
with a different meaning. If the value of a
compoundValue is n, then the n following values
of the attribute form a single value. For
example, if an attribute has 3 successive values:
compoundValue of 2, naturalLanuage of `fr-CA' and
name of `bete', then these three "values" form a
single value which is a name of `bete' in
Canadian French.
dateTime eleven octets whose contents are defined by
"DateAndTime" in RFC 1903 [r1903]. Although RFC
1903 also defines an eight octet format which
omits the time zone, a value of this type in the
IPP protocol MUST use the eleven octet format.
resolution nine octets consisting of 2 SIGNED-INTEGERs
followed by a SIGNED-BYTE. The values are the
same as those specified in RFC 1759 (Printer MIB)
[r1759]. The first SIGNED-INTEGER contains the
value of prtMarkerAddressabilityXFeedDir. The
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
Syntax of Encoding Syntax of Encoding
Attribute Value Attribute Value
second SIGNED-INTEGER contains the value of there are three separate values: the
prtMarkerAddressabilityFeedDir. The SIGNED-BYTE compoundValue, the naturalLanguage value and the
contains the value of text or name value, but from a semantic view, the
prtMarkerAddressabilityUnit. Note: the latter Printer treats them as a single value where the
value is either 3 (tenThousandsOfInches) or 4 naturalLanguage value overrides the language of
(micrometers) and the addressability is in 10,000 the immediately following text or name value in
units of measure. Thus the SIGNED-INTEGERS the attribute. The override applies to just the
represent integral values in either dots-per-inch text or name within the compound value. Other
or dots-per-centimeter. text or name values needing an override must be
rangeOf integer Eight octets consisting of 2 SIGNED-INTEGERs. The overridden with additional compoundValues.
first SIGNED-INTEGERs contains the lowest value charset, US-ASCII-STRING
of the range and the second SIGNED-INTEGERs naturalLanguage,
contains the highest value of the range mimeMediaType,
keyword, uri,
and uriScheme
boolean SIGNED-BYTE where 0x00 is `false' and 0x01 is
`true'
integer and enum a SIGNED-INTEGER
compoundValue a SIGNED-INTEGER with a special meaning.
If the value of a compoundValue is n, then the n
following values of the attribute form a single
value whose type is that of the last member of
the compound value. For example, if an attribute
has 3 successive values: compoundValue of 2,
naturalLanguage of `fr-CA' and name of `chien',
then these three "values" form a single value
which is a name of `chien' in Canadian French..
dateTime OCTET-STRING consisting of eleven octets whose
contents are defined by "DateAndTime" in RFC 1903
[rfc1903]. Although RFC 1903 also defines an
eight octet format which omits the time zone, a
value of this type in the IPP protocol MUST use
the eleven octet format. [ transfer to model].
resolution OCTET"STRING consisting of nine octets of 2
SIGNED-INTEGERs followed by a SIGNED-BYTE. The
first SIGNED-INTEGER contains the value of cross
feed direction resolution . The second SIGNED-
INTEGER contains the value of feed direction
resolution. The SIGNED-BYTE contains the unts
value.
rangeOfInteger Eight octets consisting of 2 SIGNED-INTEGERs. The
first SIGNED-INTEGERs contains the lower bound
and the second SIGNED-INTEGERs contains the upper
bound
1setOf X encoding according to the rules for an attribute 1setOf X encoding according to the rules for an attribute
with more than more value. Each value X is with more than 1 value. Each value X is encoded
encoded according to the rules for encoding its according to the rules for encoding its type.
type. octetString OCTET-STRING
Moore and Turner Expires May 7, 1998
The type of the value in the model document determines the encoding in The type of the value in the model document determines the encoding in
the value and the value of the value-tag. the value and the value of the value-tag.
3.11 Data 3.11 Data
The data part SHALL include any data required by the operation The data part SHALL include any data required by the operation
4. Encoding of Transport Layer 4. Encoding of Transport Layer
skipping to change at page 16, line 4 skipping to change at page 14, line 37
Note: Consistent with RFC 2068 (HTTP/1.1), HTTP URI's for IPP implicitly Note: Consistent with RFC 2068 (HTTP/1.1), HTTP URI's for IPP implicitly
reference port 80. If a URI references some other port, the port number reference port 80. If a URI references some other port, the port number
must be explicitly specified in the URI. must be explicitly specified in the URI.
Each HTTP operation shall use the POST method where the request-URI is Each HTTP operation shall use the POST method where the request-URI is
the object target of the operation, and where the "Content-Type" of the the object target of the operation, and where the "Content-Type" of the
message-body in each request and response shall be "application/ipp". message-body in each request and response shall be "application/ipp".
The message-body shall contain the operation layer and shall have the The message-body shall contain the operation layer and shall have the
syntax described in section 3.2 "Syntax of Encoding". A client syntax described in section 3.2 "Syntax of Encoding". A client
Moore and Turner Expires April 23, 1998
implementation SHALL adhere to the rules for a client described in RFC implementation SHALL adhere to the rules for a client described in RFC
2068 [r2068]. A printer (server) implementation SHALL adhere the rules 2068 [rfc2068]. A printer (server) implementation SHALL adhere the rules
for an origin server described in RFC 2068.In the following sections, for an origin server described in RFC 2068.In the following sections,
there are a tables of all HTTP headers which describe their use in an there are a tables of all HTTP headers which describe their use in an
IPP client or server. The following is an explanation of each column in IPP client or server. The following is an explanation of each column in
these tables. these tables.
. the "header" column contains the name of a header . the "header" column contains the name of a header
. the "request/client" column indicates whether a client sends the . the "request/client" column indicates whether a client sends the
header. header.
. the "request/ server" column indicates whether a server supports . the "request/ server" column indicates whether a server supports
the header when received. the header when received.
skipping to change at page 16, line 30 skipping to change at page 15, line 5
header. header.
. the "response /client" column indicates whether a client supports . the "response /client" column indicates whether a client supports
the header when received. the header when received.
. the "values and conditions" column specifies the allowed header . the "values and conditions" column specifies the allowed header
values and the conditions for the header to be present in a values and the conditions for the header to be present in a
request/response. request/response.
The table for "request headers" does not have columns for responses, and The table for "request headers" does not have columns for responses, and
the table for "response headers" does not have columns for requests. the table for "response headers" does not have columns for requests.
Moore and Turner Expires May 7, 1998
The following is an explanation of the values in the "request/client" The following is an explanation of the values in the "request/client"
and "response/ server" columns. and "response/ server" columns.
. must: the client or server MUST send the header, . must: the client or server MUST send the header,
. must-if: the client or server MUST send the header when the . must-if: the client or server MUST send the header when the
condition described in the "values and conditions" column is met, condition described in the "values and conditions" column is met,
. may: the client or server MAY send the header . may: the client or server MAY send the header
. not: the client or server SHOULD NOT send the header. It is not . not: the client or server SHOULD NOT send the header. It is not
relevant to an IPP implementation. relevant to an IPP implementation.
skipping to change at page 17, line 5 skipping to change at page 15, line 36
The following is a table for the general headers. The following is a table for the general headers.
ISSUE: an HTTP expert should review these tables for accuracy. ISSUE: an HTTP expert should review these tables for accuracy.
General- Request Response Values and Conditions General- Request Response Values and Conditions
Header Header
Client Server Server Client Client Server Server Client
Moore and Turner Expires April 23, 1998
General- Request Response Values and Conditions
Header
Client Server Server Client
Cache- must not must not "no-cache" only Cache- must not must not "no-cache" only
Control Control
Connection must-if must must- must "close" only. Both Connection must-if must must- must "close" only. Both
if client and server if client and server
SHOULD keep a SHOULD keep a
connection for the connection for the
duration of a sequence duration of a sequence
of operations. The of operations. The
client and server MUST client and server MUST
include this header include this header
for the last operation for the last operation
in such a sequence. in such a sequence.
Date may may must may per RFC 1123 [r1123] Date may may must may per RFC 1123 [rfc1123]
Pragma` must not must not "no-cache" only Pragma` must not must not "no-cache" only
Transfer- must-if must must- must "chunked" only . Transfer- must-if must must- must "chunked" only .
Encoding if Header MUST be present Encoding if Header MUST be present
if Content-Length is if Content-Length is
absent. absent.
Upgrade not not not not Upgrade not not not not
Via not not not not Via not not not not
Moore and Turner Expires May 7, 1998
4.2 Request Headers 4.2 Request Headers
The following is a table for the request headers. The following is a table for the request headers.
Request-Header Client Server Request Values and Conditions Request-Header Client Server Request Values and Conditions
Accept may must "application/ipp" only. This Accept may must "application/ipp" only. This
value is the default if the value is the default if the
client omits it client omits it
Accept-Charset not not Charset information is within Accept-Charset not not Charset information is within
the application/ipp entity the application/ipp entity
Accept-Encoding may must empty and per RFC 2068 [r2068] Accept-Encoding may must empty and per RFC 2068 [rfc2068]
and IANA registry for content- and IANA registry for content-
codings codings
Accept-Language not not . language information is within Accept-Language not not . language information is within
the application/ipp entity the application/ipp entity
Authorization must-if must per RFC 2068. A client MUST send Authorization must-if must per RFC 2068. A client MUST send
this header when it receives a this header when it receives a
401 "Unauthorized" response and 401 "Unauthorized" response and
does not receive a "Proxy- does not receive a "Proxy-
Authenticate" header. Authenticate" header.
From not not per RFC 2068. Because RFC From not not per RFC 2068. Because RFC
recommends sending this header recommends sending this header
only with the user's approval, it only with the user's approval, it
Moore and Turner Expires April 23, 1998
Request-Header Client Server Request Values and Conditions
is not very useful is not very useful
Host must must per RFC 2068 Host must must per RFC 2068
If-Match not not If-Match not not
If-Modified- not not If-Modified- not not
Since Since
If-None-Match not not If-None-Match not not
If-Range not not If-Range not not
If-Unmodified- not not If-Unmodified- not not
Since Since
Max-Forwards not not Max-Forwards not not
skipping to change at page 18, line 37 skipping to change at page 17, line 4
4.3 Response Headers 4.3 Response Headers
The following is a table for the request headers. The following is a table for the request headers.
Response- Server Client Response Values and Conditions Response- Server Client Response Values and Conditions
Header Header
Accept-Ranges not not Accept-Ranges not not
Age not not Age not not
Location must-if may per RFC 2068. When URI needs Location must-if may per RFC 2068. When URI needs
Moore and Turner Expires May 7, 1998
Response- Server Client Response Values and Conditions
Header
redirection. redirection.
Proxy- not must per RFC 2068 Proxy- not must per RFC 2068
Authenticate Authenticate
Public may may per RFC 2068 Public may may per RFC 2068
Retry-After may may per RFC 2068 Retry-After may may per RFC 2068
Server not not Server not not
Vary not not Vary not not
Warning may may per RFC 2068 Warning may may per RFC 2068
WWW- must-if must per RFC 2068. When a server needs to WWW- must-if must per RFC 2068. When a server needs to
Authenticate authenticate a client. Authenticate authenticate a client.
4.4 Entity Headers 4.4 Entity Headers
The following is a table for the entity headers. The following is a table for the entity headers.
Entity-Header Request Response Values and Conditions Entity-Header Request Response Values and Conditions
Client Server Server Client Client Server Server Client
Allow not not not not Allow not not not not
Moore and Turner Expires April 23, 1998
Entity-Header Request Response Values and Conditions
Client Server Server Client
Content-Base not not not not Content-Base not not not not
Content- may must must must per RFC 2068 and IANA Content- may must must must per RFC 2068 and IANA
Encoding registry for content Encoding registry for content
codings. codings.
Content- not not not not Application/ipp Content- not not not not Application/ipp
Language handles language Language handles language
Content- must-if must must-if must the length of the Content- must-if must must-if must the length of the
Length message-body per RFC Length message-body per RFC
2068. Header MUST be 2068. Header MUST be
present if Transfer- present if Transfer-
skipping to change at page 19, line 35 skipping to change at page 17, line 54
Content-Range not not not not Content-Range not not not not
Content-Type must must must must "application/ipp" Content-Type must must must must "application/ipp"
only only
ETag not not not not ETag not not not not
Expires not not not not Expires not not not not
Last-Modified not not not not Last-Modified not not not not
5. Security Considerations 5. Security Considerations
When utilizing HTTP 1.1 as a transport of IPP, the security When utilizing HTTP 1.1 as a transport of IPP, the security
considerations outlined in RFC 2068 [r2068] apply. Specifically, IPP considerations outlined in RFC 2068 [rfc2068] apply. Specifically, IPP
servers can generate a 401 "Unauthorized" response code to request servers can generate a 401 "Unauthorized" response code to request
client authentication and IPP clients should correctly respond with the client authentication and IPP clients should correctly respond with the
proper "Authorization" header. Both Basic Authentication (RFC 2068) and proper "Authorization" header. Both Basic Authentication (RFC 2068) and
Digest Authentication (RFC 2069) [r2069] flavors of authentication SHALL
be supported. The server chooses which type(s) of authentication to Moore and Turner Expires May 7, 1998
accept. Digest Authentication is a more secure method, and is always
Digest Authentication (RFC 2069) [rfc2069] flavors of authentication
SHALL be supported. The server chooses which type(s) of authentication
to accept. Digest Authentication is a more secure method, and is always
preferred to Basic Authentication. preferred to Basic Authentication.
For secure communication (privacy in particular), IPP SHOULD be run For secure communication (privacy in particular), IPP SHOULD be run
using a secure communications channel. For this purpose it is the using a secure communications channel. For this purpose it is the
intention to define standardization of IPP in combination with Transport intention to define standardization of IPP in combination with Transport
Layer Security (TLS), currently under development in the IETF, when the Layer Security (TLS), currently under development in the IETF, when the
TLS specifications are agreed and on the IETF standards track. TLS specifications are agreed and on the IETF standards track.
As an intercept solution for secure communication, the Secure Socket As an intercept solution for secure communication, the Secure Socket
Layer 3.0 (SSL3) could be used, but be warned that such implementations Layer 3.0 (SSL3) could be used, but be warned that such implementations
may not be able to interoperate with a future standardized IPP and TLS may not be able to interoperate with a future standardized IPP and TLS
solution. Appendix C gives some hints to implementors wanting to use solution. Appendix C gives some hints to implementors wanting to use
SSL3 as intercept solution. SSL3 as intercept solution.
It is possible to combine the techniques, HTTP 1.1 client authentication It is possible to combine the techniques, HTTP 1.1 client authentication
(either basic or digest) with a secure communications channel. Together (either basic or digest) with a secure communications channel. Together
Moore and Turner Expires April 23, 1998
the two are more secure than client authentication and they perform user the two are more secure than client authentication and they perform user
authentication. authentication.
See further discussion of IPP security concepts in the model document See further discussion of IPP security concepts in the model document
[ipp-m]. [ipp-mod].
6. References 6. Copyright
[822] Crocker, D., "Standard for the Format of ARPA Internet Text This document and translations of it may be copied and furnished to
Messages", RFC 822, August 1982. 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.
[r1123] Braden, S., "Requirements for Internet Hosts - Application and The limited permissions granted above are perpetual and will not be
Support", RFC 1123, October, 1989, revoked by the Internet Society or its successors or assigns.
[r1179] McLaughlin, L. III, (editor), "Line Printer Daemon Protocol" This document and the information contained herein is provided on an "AS
RFC 1179, August 1990. 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
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
[r1630] T. Berners-Lee, "Universal Resource Identifiers in WWW: A Moore and Turner Expires May 7, 1998
Unifying Syntax for the Expression of Names and Addresses of
7. References
[rfc822] Crocker, D., "Standard for the Format of ARPA
Internet Text Messages", RFC 822, August 1982.
[rfc1123] Braden, S., "Requirements for Internet Hosts -
Application and Support", RFC 1123, October, 1989,
[rfc1179] McLaughlin, L. III, (editor), "Line Printer Daemon
Protocol" RFC 1179, August 1990.
[rfc1630] T. Berners-Lee, "Universal Resource Identifiers in WWW:
A Unifying Syntax for the Expression of Names and Addresses of
Objects on the Network as used in the Word-Wide Web", RFC 1630, Objects on the Network as used in the Word-Wide Web", RFC 1630,
June 1994. June 1994.
[r1759] Smith, R., Wright, F., Hastings, T., Zilles, S., and [rfc1759] Smith, R., Wright, F., Hastings, T., Zilles, S., and
Gyllenskog, J., "Printer MIB", RFC 1759, March 1995. Gyllenskog, J., "Printer MIB", RFC 1759, March 1995.
[r1738] Berners-Lee, T., Masinter, L., McCahill, M. , "Uniform [rfc1738] Berners-Lee, T., Masinter, L., McCahill, M. , "Uniform
Resource Locators (URL)", RFC 1738, December, 1994. Resource Locators (URL)", RFC 1738, December, 1994.
[r1543] Postel, J., "Instructions to RFC Authors", RFC 1543, October [rfc1543] Postel, J., "Instructions to RFC Authors", RFC 1543,
1993. October 1993.
[r1766] H. Alvestrand, " Tags for the Identification of Languages", [rfc1766] H. Alvestrand, " Tags for the Identification of
RFC 1766, March 1995. Languages", RFC 1766, March 1995.
[r1903} J. Case, et al. "Textual Conventions for Version 2 of the [rfc1903} J. Case, et al. "Textual Conventions for Version 2 of
Simple Network Managment Protocol (SNMPv2)", RFC 1903, January the Simple Network Management Protocol (SNMPv2)", RFC 1903,
1996. January 1996.
[r2046] N. Freed & N. Borenstein, Multipurpose Internet Mail [rfc2046] N. Freed & N. Borenstein, Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types. November 1996. (Obsoletes Extensions (MIME) Part Two: Media Types. November 1996.
RFC1521, RFC1522, RFC1590), RFC 2046. (Obsoletes RFC1521, RFC1522, RFC1590), RFC 2046.
[r2048] N. Freed, J. Klensin & J. Postel. Multipurpose Internet Mail [rfc2048] N. Freed, J. Klensin & J. Postel. Multipurpose Internet
Extension (MIME) Part Four: Registration Procedures. November 1996. Mail Extension (MIME) Part Four: Registration Procedures.
(Format: TXT=45033 bytes) (Obsoletes RFC1521, RFC1522, RFC1590) November 1996. (Format: TXT=45033 bytes) (Obsoletes RFC1521,
(Also BCP0013), RFC 2048. RFC1522, RFC1590) (Also BCP0013), RFC 2048.
[r2068] R Fielding, et al, "Hypertext Transfer Protocol " HTTP/1.1" [rfc2068] R Fielding, et al, "Hypertext Transfer Protocol "
RFC 2068, January 1997 HTTP/1.1" RFC 2068, January 1997
[r2069] J. Franks, et al, "An Extension to HTTP: Digest Access [rfc2069] J. Franks, et al, "An Extension to HTTP: Digest Access
Authentication" RFC 2069, January 1997 Authentication" RFC 2069, January 1997
Moore and Turner Expires April 23, 1998 [rfc2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119 , March 1997
[r2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement [rfc2184] N. Freed, K. Moore, "MIME Parameter Value and Encoded
Levels", RFC 2119 , March 1997 Word Extensions: Character Sets, Languages, and Continuations",
RFC 2184, August 1997,
[r2184] N. Freed, K. Moore, "MIME Parameter Value and Encoded Word Moore and Turner Expires May 7, 1998
Extensions: Character Sets, Languages, and Continuations", RFC
2184, August 1997,
[abnf] D. Crocker et al., "Augmented BNF for Syntax Specifications: [abnf] D. Crocker et al., "Augmented BNF for Syntax Specifications:
ABNF", draft-ietf-drums-abnf-04.txt. ABNF", draft-ietf-drums-abnf-04.txt.
[char] N. Freed, J. Postel: IANA CharSet Registration Procedures, [char] N. Freed, J. Postel: IANA Charset Registration Procedures, Work
Work in Progress (draft-freed-charset-reg-02.txt). in Progress (draft-freed-charset-reg-02.txt).
[dpa] ISO/IEC 10175 Document Printing Application (DPA), June 1996. [dpa] ISO/IEC 10175 Document Printing Application (DPA), June 1996.
[iana] IANA Registry of Coded Character Sets: ftp://ftp.isi.edu/in- [iana] IANA Registry of Coded Character Sets: ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets notes/iana/assignments/character-sets
[ipp-r] Wright, F. D., "Requirements for an Internet Printing [ipp-req] Wright, F. D., "Requirements for an Internet Printing
Protocol:" Protocol:"
[ipp-m] Isaacson, S, deBry, R, Hasting, T, Herriot, R, Powell, P, [ipp-mod] Isaacson, S, deBry, R, Hastings, T, Herriot, R, Powell,
"Internet Printing Protocol/1.0: Model and Semantics" P, "Internet Printing Protocol/1.0: Model and Semantics"
[ssl] Netscape, The SSL Protocol, Version 3, (Text version 3.02) [ssl] Netscape, The SSL Protocol, Version 3, (Text version 3.02)
November 1996. November 1996.
7. Author's Address 8. Author's Address
Robert Herriot (editor) Paul Moore Robert Herriot (editor) Paul Moore
Sun Microsystems Inc. Microsoft Sun Microsystems Inc. Microsoft
901 San Antonio.Road, MPK-17 One Microsoft Way 901 San Antonio Road, MPK-17 One Microsoft Way
Palo Alto, CA 94303 Redmond, WA 98053 Palo Alto, CA 94303 Redmond, WA 98053
Phone: 650-786-8995 Phone: 425-936-0908 Phone: 650-786-8995 Phone: 425-936-0908
Fax: 650-786-7077 Fax: 425-93MS-FAX Fax: 650-786-7077 Fax: 425-93MS-FAX
Email: robert.herriot@eng.sun.com Email: paulmo@microsoft.com Email: robert.herriot@eng.sun.com Email: paulmo@microsoft.com
Sylvan Butler Randy Turner Sylvan Butler Randy Turner
Hewlett-Packard Sharp Laboratories Hewlett-Packard Sharp Laboratories
11311 Chinden Blvd. 5750 NW Pacific Rim Blvd 11311 Chinden Blvd. 5750 NW Pacific Rim Blvd
Boise, ID 83714 Camas, WA 98607 Boise, ID 83714 Camas, WA 98607
Phone: 208-396-6000 Phone: 360-817-8456 Phone: 208-396-6000 Phone: 360-817-8456
Fax: 208-396-3457 Fax: : 360-817-8436 Fax: 208-396-3457 Fax: : 360-817-8436
Email: sbutler@boi.hp.com Email: rturner@sharplabs.com Email: sbutler@boi.hp.com Email: rturner@sharplabs.com
IPP Mailing List: ipp@pwg.org IPP Mailing List: ipp@pwg.org
IPP Mailing List Subscription: ipp-request@pwg.org IPP Mailing List Subscription: ipp-request@pwg.org
IPP Web Page: http://www.pwg.org/ipp/ IPP Web Page: http://www.pwg.org/ipp/
Moore and Turner Expires April 23, 1998 9. Other Participants:
8. Other Participants:
Chuck Adams - Tektronix Harry Lewis - IBM Chuck Adams - Tektronix Harry Lewis - IBM
Ron Bergman - Data Products Tony Liao - Vivid Image Ron Bergman - Data Products Tony Liao - Vivid Image
Keith Carter - IBM David Manchala - Xerox Keith Carter - IBM David Manchala - Xerox
Angelo Caruso - Xerox Carl-Uno Manros - Xerox Angelo Caruso - Xerox Carl-Uno Manros - Xerox
Moore and Turner Expires May 7, 1998
Jeff Copeland - QMS Jay Martin - Underscore Jeff Copeland - QMS Jay Martin - Underscore
Roger Debry - IBM Larry Masinter - Xerox Roger Debry - IBM Larry Masinter - Xerox
Lee Farrell - Canon Bob Pentecost - Hewlett-Packard Lee Farrell - Canon Ira McDonald, Xerox
Sue Gleeson - Digital Patrick Powell - SDSU Sue Gleeson - Digital Bob Pentecost - Hewlett-Packard
Charles Gordon - Osicom Jeff Rackowitz - Intermec Charles Gordon - Osicom Patrick Powell - SDSU
Brian Grimshaw - Apple Xavier Riley - Xerox Brian Grimshaw - Apple Jeff Rackowitz - Intermec
Jerry Hadsell - IBM Gary Roberts - Ricoh Jerry Hadsell - IBM Xavier Riley - Xerox
Richard Hart - Digital Stuart Rowley - Kyocera Richard Hart - Digital Gary Roberts - Ricoh
Tom Hastings - Xerox Richard Schneider - Epson Tom Hastings - Xerox Stuart Rowley - Kyocera
Stephen Holmstead Shigern Ueda - Canon Stephen Holmstead Richard Schneider - Epson
Zhi-Hong Huang - Zenographics Bob Von Andel - Allegro Software Zhi-Hong Huang - Zenographics Shigern Ueda - Canon
Scott Isaacson - Novell William Wagner - Digital Products Scott Isaacson - Novell Bob Von Andel - Allegro Software
Rich Lomicka - Digital Jasper Wong - Xionics Rich Lomicka - Digital William Wagner - Digital Products
David Kellerman - Northlake Don Wright - Lexmark David Kellerman - Northlake Jasper Wong - Xionics
Software Software
Robert Kline - TrueSpectra Rick Yardumian - Xerox Robert Kline - TrueSpectra Don Wright - Lexmark
Dave Kuntz - Hewlett-Packard Lloyd Young - Lexmark Dave Kuntz - Hewlett-Packard Rick Yardumian - Xerox
Takami Kurono - Brother Peter Zehler - Xerox Takami Kurono - Brother Lloyd Young - Lexmark
Rich Landau - Digital Frank Zhao - Panasonic Rich Landau - Digital Peter Zehler - Xerox
Greg LeClair - Epson Steve Zilles - Adobe Greg LeClair - Epson Frank Zhao - Panasonic
Steve Zilles - Adobe
9. Appendix A: Protocol Examples 10. Appendix A: Protocol Examples
9.1 Print-Job Request 10.1 Print-Job Request
The following is an example of a Print-Job request with job-name, The following is an example of a Print-Job request with job-name,
copies, and sides specified. copies, and sides specified.
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x0002 PrintJob operation 0x0002 PrintJob operation
0x01 start operation- operation-attributes tag 0x01 start operation- operation-attributes tag
attributes attributes
skipping to change at page 23, line 4 skipping to change at page 21, line 54
attributes-charset attributes-charset name attributes-charset attributes-charset name
0x0008 value-length 0x0008 value-length
US-ASCII US-ASCII value US-ASCII US-ASCII value
0x48 natural-language value-tag 0x48 natural-language value-tag
type type
0x001B name-length 0x001B name-length
attributes-natural- attributes-natural- name attributes-natural- attributes-natural- name
language language language language
0x0005 value-length 0x0005 value-length
en-US en-US value en-US en-US value
Moore and Turner Expires April 23, 1998
Octets Symbolic Value Protocol field
0x42 name type value-tag 0x42 name type value-tag
0x0008 name-length 0x0008 name-length
job-name job-name name job-name job-name name
0x0006 value-length 0x0006 value-length
foobar foobar value foobar foobar value
0x02 start job- job-attributes tag
Moore and Turner Expires May 7, 1998
Octets Symbolic Value Protocol field
0x02 start job- job-attributes-tag
attributes attributes
0x21 integer type value-tag 0x21 integer type value-tag
0x0005 name-length 0x0005 name-length
copies copies name copies copies name
0x0004 value-length 0x0004 value-length
0x00000014 20 value 0x00000014 20 value
0x44 keyword type value-tag 0x44 keyword type value-tag
0x0005 name-length 0x0005 name-length
sides sides name sides sides name
0x0013 value-length 0x0013 value-length
two-sided-long-edge two-sided-long-edge value two-sided-long-edge two-sided-long-edge value
0x03 start-data data-tag 0x03 start-data data-tag
%!PS... <PostScript> data %!PS... <PostScript> data
9.2 Print-Job Response (successful) 10.2 Print-Job Response (successful)
Here is an example of a Print-Job response which is successful: Here is an example of a Print-Job response which is successful:
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x0000 OK (successful) status-code 0x0000 OK (successful) status-code
0x01 start operation- operation-attributes tag 0x01 start operation- operation-attributes-tag
attributes attributes
0x47 charset type value-tag 0x47 charset type value-tag
0x0012 name-length 0x0012 name-length
attributes- attributes- name attributes- attributes- name
charset charset charset charset
0x0008 value-length 0x0008 value-length
US-ASCII US-ASCII value US-ASCII US-ASCII value
0x48 natural-language value-tag 0x48 natural-language value-tag
type type
0x001B name-length 0x001B name-length
attributes- attributes- name attributes- attributes- name
natural- natural-language natural- natural-language
language language
0x0005 value-length 0x0005 value-length
en-US en-US value en-US en-US value
0x41 text type value-tag 0x41 text type value-tag
0x000E name-length 0x000E name-length
status-message status-message name status-message status-message name
0x0002 value-length 0x0002 value-length
OK OK value OK OK value
0x02 start job- job-attributes tag 0x02 start job- job-attributes-tag
Moore and Turner Expires April 23, 1998
Octets Symbolic Value Protocol field
attributes attributes
0x21 integer value-tag 0x21 integer value-tag
0x0007 name-length 0x0007 name-length
job-id job-id name job-id job-id name
0x0004 value-length 0x0004 value-length
Moore and Turner Expires May 7, 1998
Octets Symbolic Value Protocol field
147 147 value 147 147 value
0x45 uri type value-tag 0x45 uri type value-tag
0x0008 name-length 0x0008 name-length
job-uri job-uri name job-uri job-uri name
0x000E value-length 0x000E value-length
http://foo/123 http://foo/123 value http://foo/123 http://foo/123 value
0x25 name type value-tag 0x25 name type value-tag
0x0008 name-length 0x0008 name-length
job-state job-state name job-state job-state name
0x0001 value-length 0x0001 value-length
0x03 pending value 0x03 pending value
0x03 start-data data-tag 0x03 start-data data-tag
9.3 Print-Job Response (failure) 10.3 Print-Job Response (failure)
Here is an example of a Print-Job response which fails because the Here is an example of a Print-Job response which fails because the
printer does not support sides and because the value 20 for copies is printer does not support sides and because the value 20 for copies is
not supported: not supported:
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x0400 client-error-bad-request status-code 0x0400 client-error-bad-request status-code
0x01 start operation- operation-attribute tag 0x01 start operation- operation-attribute tag
attribures attributes
0x47 charset type value-tag 0x47 charset type value-tag
0x0012 name-length 0x0012 name-length
attributes- attributes-charset name attributes- attributes-charset name
charset charset
0x0008 value-length 0x0008 value-length
US-ASCII US-ASCII value US-ASCII US-ASCII value
0x48 natural-language type value-tag 0x48 natural-language type value-tag
0x001B name-length 0x001B name-length
attributes- attributes-natural- name attributes- attributes-natural- name
natural- language natural- language
language language
0x0005 value-length 0x0005 value-length
en-US en-US value en-US en-US value
0x41 text type value-tag 0x41 text type value-tag
0x000E name-length 0x000E name-length
status-message status-message name status-message status-message name
0x000D value-length 0x000D value-length
bad-request bad-request value bad-request bad-request value
0x04 start unsupported-job- unsupported-job- 0x04 start unsupported-job- unsupported-job-
attributes attributes tag attributes attributes-tag
Moore and Turner Expires April 23, 1998
Octets Symbolic Value Protocol field
0x21 integer type value-tag 0x21 integer type value-tag
0x0005 name-length 0x0005 name-length
copies copies name copies copies name
0x0004 value-length 0x0004 value-length
0x00000014 20 value 0x00000014 20 value
Moore and Turner Expires May 7, 1998
Octets Symbolic Value Protocol field
0x10 unsupported (type) value-tag 0x10 unsupported (type) value-tag
0x0005 name-length 0x0005 name-length
sides sides name sides sides name
0x0000 value-length 0x0000 value-length
0x03 start-data data-tag 0x03 start-data data-tag
9.4 Print-URI Request 10.4 Print-URI Request
The following is an example of Print-URI request with copies and job- The following is an example of Print-URI request with copies and job-
name parameters. name parameters.
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x0003 Print-URI operation 0x0003 Print-URI operation
0x01 start operation- operation-attributes tag 0x01 start operation- operation-attributes-tag
attributes attributes
0x47 charset type value-tag 0x47 charset type value-tag
0x0012 name-length 0x0012 name-length
attributes-charset attributes-charset name attributes-charset attributes-charset name
0x0008 value-length 0x0008 value-length
US-ASCII US-ASCII value US-ASCII US-ASCII value
0x48 natural-language value-tag 0x48 natural-language value-tag
type type
0x001B name-length 0x001B name-length
attributes-natural- attributes- name attributes-natural- attributes- name
skipping to change at page 25, line 52 skipping to change at page 24, line 47
0x45 uri type value-tag 0x45 uri type value-tag
0x000A name-length 0x000A name-length
document-uri document-uri name document-uri document-uri name
0x11 value-length 0x11 value-length
ftp://foo.com/foo ftp://foo.com/foo value ftp://foo.com/foo ftp://foo.com/foo value
0x42 name type value-tag 0x42 name type value-tag
0x0008 name-length 0x0008 name-length
job-name job-name name job-name job-name name
0x0006 value-length 0x0006 value-length
foobar foobar value foobar foobar value
0x02 start job- job-attributes tag 0x02 start job- job-attributes-tag
attributes attributes
0x21 integer type value-tag 0x21 integer type value-tag
0x0005 name-length 0x0005 name-length
copies copies name copies copies name
0x0004 value-length 0x0004 value-length
0x00000001 1 value 0x00000001 1 value
0x03 start-data data-tag 0x03 start-data data-tag
Moore and Turner Expires April 23, 1998
Octets Symbolic Value Protocol field
%!PS... <PostScript> data %!PS... <PostScript> data
9.5 Create-Job Request Moore and Turner Expires May 7, 1998
10.5 Create-Job Request
The following is an example of Create-Job request with no parameters and The following is an example of Create-Job request with no parameters and
no attributes no attributes
Octets Symbolic Protocol field Octets Symbolic Value Protocol field
Value
0x0100 1.0 version 0x0100 1.0 version
0x0005 Create-Job operation 0x0005 Create-Job operation
0x01 start operation-attributes-tag
operation-
attributes
0x47 charset type value-tag
0x0012 name-length
attributes- attributes- name
charset charset
0x0008 value-length
US-ASCII US-ASCII value
0x48 natural- value-tag
language type
0x001B name-length
attributes- attributes- name
natural- natural-
language language
0x0005 value-length
en-US en-US value
0x03 start-data data-tag 0x03 start-data data-tag
9.6 Get-Jobs Request 10.6 Get-Jobs Request
The following is an example of Get-Jobs request with parameters but no The following is an example of Get-Jobs request with parameters but no
attributes. attributes.
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x000A Get-Jobs operation 0x000A Get-Jobs operation
0x01 start operation- operation-attributes- 0x01 start operation- operation-attributes-
attributes tag attributes tag
0x47 charset type value-tag 0x47 charset type value-tag
skipping to change at page 26, line 48 skipping to change at page 26, line 4
0x001B name-length 0x001B name-length
attributes-natural- attributes-natural- name attributes-natural- attributes-natural- name
language language language language
0x0005 value-length 0x0005 value-length
en-US en-US value en-US en-US value
0x21 integer type value-tag 0x21 integer type value-tag
0x0005 name-length 0x0005 name-length
limit limit name limit limit name
0x0004 value-length 0x0004 value-length
0x00000032 50 value 0x00000032 50 value
Moore and Turner Expires May 7, 1998
Octets Symbolic Value Protocol field
0x44 keyword type value-tag 0x44 keyword type value-tag
0x0014 name-length 0x0014 name-length
requested-attributes requested-attributes name requested-attributes requested-attributes name
0x0006 value-length 0x0006 value-length
job-id job-id value job-id job-id value
0x44 keyword type value-tag 0x44 keyword type value-tag
0x0000 additional value name-length 0x0000 additional value name-length
0x0008 value-length 0x0008 value-length
job-name job-name value job-name job-name value
0x03 start-data data-tag 0x03 start-data data-tag
Moore and Turner Expires April 23, 1998 10.7 Get-Jobs Response
9.7 Get-Jobs Response
The following is an of Get-Jobs response from previous request with 3 The following is an of Get-Jobs response from previous request with 3
jobs. The Printer returns no information about the second job. jobs. The Printer returns no information about the second job.
Octets Symbolic Value Protocol field Octets Symbolic Value Protocol field
0x0100 1.0 version 0x0100 1.0 version
0x0000 OK (successful) status-code 0x0000 OK (successful) status-code
0x01 start operation- operation-attribute-tag 0x01 start operation- operation-attribute-tag
attributes attributes
0x47 charset type value-tag 0x47 charset type value-tag
skipping to change at page 27, line 49 skipping to change at page 27, line 4
0x001B name-length 0x001B name-length
attributes- attributes-natural- name attributes- attributes-natural- name
natural-language language natural-language language
0x0005 value-length 0x0005 value-length
fr-CA fr-CA value fr-CA fr-CA value
0x21 integer type value-tag 0x21 integer type value-tag
0x0006 name-length 0x0006 name-length
job-id job-id name job-id job-id name
0x0004 value-length 0x0004 value-length
147 147 value 147 147 value
Moore and Turner Expires May 7, 1998
Octets Symbolic Value Protocol field
0x42 name type value-tag 0x42 name type value-tag
0x0008 name-length 0x0008 name-length
job-name job-name name job-name job-name name
0x0003 name-length 0x0003 name-length
fou fou name fou fou name
0x02 start job-attributes job-attributes-tag 0x02 start job-attributes job-attributes-tag
(2nd object) (2nd object)
0x02 start job-attributes job-attributes-tag 0x02 start job-attributes job-attributes-tag
(3rd object) (3rd object)
0x21 interger type value-tag 0x21 integer type value-tag
0x0006 name-length 0x0006 name-length
job-id job-id name job-id job-id name
Moore and Turner Expires April 23, 1998
Octets Symbolic Value Protocol field
0x0004 value-length 0x0004 value-length
148 148 value 148 148 value
0x13 compoundValue value-tag 0x13 compoundValue value-tag
0x0008 name-length 0x0008 name-length
job-name job-name name job-name job-name name
0x0004 value-length 0x0004 value-length
0x0002 2 value (number of values) 0x0002 2 value (number of values)
0x48 naturalLanguage value-tag 0x48 naturalLanguage value-tag
0x0000 muli-value marker name-length 0x0000 multi-value marker name-length
0x0005 value-length 0x0005 value-length
de-CH de-CH value de-CH de-CH value
0x42 name type value-tag 0x42 name type value-tag
0x0000 muli-value marker name-length 0x0000 multi-value marker name-length
0x0003 name-length 0x0003 name-length
bar bar name isch guet isch guet name
0x03 start-data data-tag 0x03 start-data data-tag
10. Appendix B: Mapping of Each Operation in the Encoding 11. Appendix B: Mapping of Each Operation in the Encoding
The next three tables show the results of applying the rules above to The next three tables show the results of applying the rules above to
the operations defined in the IPP model document. There is no the operations defined in the IPP model document. There is no
information in these tables that cannot be derived from the rules information in these tables that cannot be derived from the rules
presented in Section 3.8 "Mapping of Attribute Names". presented in Section 3.8 "Mapping of Attribute Names".
The following table shows the mapping of all IPP model-document request The following table shows the mapping of all IPP model-document request
attributes to an appropriate xxx-attribute-sequence or special position attributes to an appropriate xxx-attribute-sequence or special position
in the protocol. in the protocol.
skipping to change at page 28, line 48 skipping to change at page 28, line 4
Operation operation job attributes special position Operation operation job attributes special position
attributes attributes
Print-Job attributes- job-template document-content Print-Job attributes- job-template document-content
charset attributes charset attributes
attributes- attributes-
natural- natural-
language language
job-name job-name
Moore and Turner Expires May 7, 1998
Operation operation job attributes special position
attributes
document-name document-name
ipp-attribute- ipp-attribute-
fidelity fidelity
document-
charset
document- document-
natural- natural-
language language
Create-Job or attributes- job-template Create-Job or attributes- job-template
Validate-Job charset attributes Validate-Job charset attributes
attributes- attributes-
natural- natural-
Moore and Turner Expires April 23, 1998
Operation operation job attributes special position
attributes
language job- language job-
name name
ipp-attribute- ipp-attribute-
fidelity fidelity
Print-URI attributes- job-template Print-URI attributes- job-template
charset attributes charset attributes
attributes- attributes-
natural- natural-
language job- language job-
name name
ipp-attribute- ipp-attribute-
fidelity fidelity
document-uri document-uri
document-
charset
document- document-
natural- natural-
language language
Send-Document attributes- Send-Document attributes- document-content
charset charset
attributes- attributes-
natural- natural-
language job-id language job-id
last-document last-document
document-name document-name
document- document-
charset natural-
document-
natural- document-content
language language
Send-URI attributes- Send-URI attributes-
charset charset
attributes- attributes-
natural- natural-
language job-id language job-id
last-document last-document
document-name document-name
document-uri document-uri
document-
charset
document- document-
natural- natural-
Moore and Turner Expires May 7, 1998
Operation operation job attributes special position
attributes
language language
Cancel-Job attributes- Cancel-Job attributes-
charset charset
attributes- attributes-
natural- natural-
language job-id language job-id
message message
Get-Attributes attributes- Get-Attributes attributes-
Moore and Turner Expires April 23, 1998
Operation operation job attributes special position
attributes
(for a Printer) charset (for a Printer) charset
attributes- attributes-
natural- natural-
language language
requested- requested-
attributes attributes
document-format document-format
Get-Attributes attributes- Get-Attributes attributes-
(for a Job) charset (for a Job) charset
attributes- attributes-
skipping to change at page 30, line 45 skipping to change at page 29, line 53
Operation operation job attributes special position Operation operation job attributes special position
attributes attributes
Send-Document attributes- document-content Send-Document attributes- document-content
charset charset
attributes- attributes-
natural- natural-
language last- language last-
document document
document-name document-name
document-
charset
document- document-
natural- natural-
language language
Send-URI attributes- Send-URI attributes-
charset charset
Moore and Turner Expires May 7, 1998
Operation operation job attributes special position
attributes
attributes- attributes-
natural- natural-
language last- language last-
document document
document-name document-name
document-uri document-uri
document-
Moore and Turner Expires April 23, 1998
Operation operation job attributes special position
attributes
charset
document- document-
natural- natural-
language language
Cancel-Job attributes- Cancel-Job attributes-
charset charset
attributes- attributes-
natural- natural-
language language
message message
Get-Attributes attributes- Get-Attributes attributes-
skipping to change at page 31, line 52 skipping to change at page 31, line 4
number-of- number-of-
intervening intervening
-jobs -jobs
Validate-Job attributes- unsupported status- Validate-Job attributes- unsupported status-
charset attributes code charset attributes code
attributes- attributes-
natural- natural-
language language
status- status-
Moore and Turner Expires May 7, 1998
Operation operation job- unsupported-job- special
attributes attributes attributes position
message message
Note: the unsupported-job-attributes are present only if the client Note: the unsupported-job-attributes are present only if the client
included some job attributes that the Printer doesn't support. included some job attributes that the Printer doesn't support.
Moore and Turner Expires April 23, 1998
Note: the job-attributes are present only if the server returns the Note: the job-attributes are present only if the server returns the
status code of successful-ok or successful-ok-ignored-or-substituted- status code of successful-ok or successful-ok-ignored-or-substituted-
attributes. attributes.
Operation operation job- printer- special Operation operation job- printer- special
attributes attributes attributes position attributes attributes attributes position
Cancel-Job attributes- Cancel-Job attributes-
charset charset
attributes- attributes-
skipping to change at page 32, line 49 skipping to change at page 32, line 5
charset attributes charset attributes
attributes- (see the attributes- (see the
natural- Note below) natural- Note below)
language language
status- status-
message message
Note for Get-Jobs: there is a separate job-attribute-sequence containing Note for Get-Jobs: there is a separate job-attribute-sequence containing
requested-attributes for each job object in the response requested-attributes for each job object in the response
11. Appendix C: Hints to implementors using IPP with SSL3 Moore and Turner Expires May 7, 1998
12. Appendix C: Hints to implementors using IPP with SSL3
WARNING: Clients and IPP objects using intermediate secure connection WARNING: Clients and IPP objects using intermediate secure connection
protocol solutions such as IPP in combination with Secure Socket Layer protocol solutions such as IPP in combination with Secure Socket Layer
Version 3 (SSL3), which are developed in advance of IPP and TLS Version 3 (SSL3), which are developed in advance of IPP and TLS
standardization, might not be interoperable with IPP and TLS standards- standardization, might not be interoperable with IPP and TLS standards-
conforming clients and IPP objects. conforming clients and IPP objects.
Moore and Turner Expires April 23, 1998
An assumption is that the URI for a secure IPP Printer object has been An assumption is that the URI for a secure IPP Printer object has been
found by means outside the IPP printing protocol, via a directory found by means outside the IPP printing protocol, via a directory
service, web site or other means. service, web site or other means.
IPP provides a transparent connection to SSL by calling the IPP provides a transparent connection to SSL by calling the
corresponding URL (a https URI connects by default to port 443). corresponding URL (a https URI connects by default to port 443).
However, the following functions can be provided to ease the integration However, the following functions can be provided to ease the integration
of IPP with SSL during implementation. of IPP with SSL during implementation.
connect (URI), returns a status. connect (URI), returns a status.
skipping to change at line 1741 skipping to change at line 1688
The session-id available from the "connect" could be used. The session-id available from the "connect" could be used.
resume (session) resume (session)
to reconnect using a previous session-id. to reconnect using a previous session-id.
The availability of this information as administration features are left The availability of this information as administration features are left
for implementors, and need not be standardized at this time for implementors, and need not be standardized at this time
Moore and Turner Expires April 23, 1998 Moore and Turner Expires May 7, 1998
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/