Apple Inc.

1 Infinite Loop MS 111-HOMC Cupertino CA 95014 US msweet@apple.com

High North, Inc.

PO Box 221 Grand Marais MI 49839 US +1 906-494-2434 blueroofmusic@gmail.com

Applications IPP WG The Internet Printing Protocol (IPP) is an application level protocol for distributed printing using Internet tools and technologies. This document defines the rules for encoding IPP operations, attributes, and values into the Internet MIME media type called "application/ipp". It also defines the rules for transporting a message body whose Content-Type is "application/ipp" over HTTP and/or HTTPS. The IPP data model and operation semantics are described in IPP/1.1: Model and Semantics . This document obsoletes RFCs 2910 and 3382. This draft is being submitted as an AD-sponsored replacement of RFCs 2910 and 3382, with drafts being reviewed and edited by the IEEE-ISTO's Printer Working Group IPP WG. The initial goal is to have an clean version of IPP/1.1 as an IETF Proposed Standard. The long-term goal is to advance IPP/1.1 to IETF Internet Standard.

This document contains the rules for encoding IPP operations and describes two layers: the transport layer and the operation layer. The transport layer consists of an HTTP request and response. All IPP implementations support HTTP/1.1, the relevant parts of which are described in the following RFCs: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests Hypertext Transfer Protocol (HTTP/1.1): Caching Hypertext Transfer Protocol (HTTP/1.1): Authentication The 'Basic' HTTP Authentication Scheme HTTP Digest Access Authentication IPP implementations can support HTTP/2 which is described in the following RFCs: Hypertext Transfer Protocol Version 2 (HTTP/2) HPACK - Header Compression for HTTP/2 This document specifies the HTTP headers that an IPP implementation supports. The operation layer consists of a message body in an HTTP request or response. The "Internet Printing Protocol/1.1: Model and Semantics" and subsequent extensions (collectively known as the IPP Model) define the semantics of such a message body and the supported values. This document specifies the encoding of an IPP request and response message.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

Client: Initiator of outgoing IPP session requests and sender of outgoing IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 User Agent). Document: An object created and managed by a Printer that contains description, processing, and status information. A Document object may have attached data and is bound to a single Job. 'ipp' URI: An IPP URI as defined in . 'ipps' URI: An IPPS URI as defined in . Job: An object created and managed by a Printer that contains description, processing, and status information. The Job also contains zero or more Document objects. Logical Device: A print server, software service, or gateway that processes Jobs and either forwards or stores the processed Job or uses one or more Physical Devices to render output. Model: The semantics of operations, attributes, values, and status codes used in the Internet Printing Protocol as defined in the Internet Printing Protocol/1.1: Model and Semantics and subsequent extensions. Output Device: A single Logical or Physical Device. Physical Device: A hardware implementation of an endpoint device, e.g., a marking engine, a fax modem, etc. Printer: Listener for incoming IPP session requests and receiver of incoming IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 Server) that represents one or more Physical Devices or a Logical Device.

ABNF: Augmented Backus-Naur Form ASCII: American Standard Code for Information Interchange HTTP: HyperText Transfer Protocol HTTPS: HTTP over TLS IANA: Internet Assigned Numbers Authority IEEE: Institute of Electrical and Electronics Engineers IESG: Internet Engineering Steering Group IPP: Internet Printing Protocol (this document and ) ISTO: IEEE Industry Standards and Technology Organization LPD: Line Printer Daemon Protocol PWG: IEEE-ISTO Printer Working Group RFC: Request for Comments TCP: Transmission Control Protocol TLS: Transport Layer Security URI: Uniform Resource Identifier URL: Uniform Resource Locator UTF-8: Unicode Transformation Format - 8-bit

The operation layer is the message body part of the HTTP request or response and it MUST contain a single IPP operation request or IPP operation response. Each request or response consists of a sequence of values and attribute groups. Attribute groups consist of a sequence of attributes each of which is a name and value. Names and values are ultimately sequences of octets. The encoding consists of octets as the most primitive type. There are several types built from octets, but three important types are integers, character strings and octet strings, on which most other data types are built. Every character string in this encoding MUST be a sequence of characters where the characters are associated with some charset and some natural language. A character string MUST be in "reading order" with the first character in the value (according to reading order) being the first character in the encoding. A character string whose associated charset is US-ASCII whose associated natural language is US English is henceforth called a US-ASCII-STRING. A character string whose associated charset and natural language are specified in a request or response as described in the Model is henceforth called a LOCALIZED-STRING. An octet string MUST be in "Model order" with the first octet in the value (according to the Model order) being the first octet in the encoding. Every integer in this encoding MUST 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 MUST be 1, 2 or 4, depending on usage in the protocol. Such one-octet integers, henceforth called SIGNED-BYTE, are used for the version-number and tag fields. Such two-byte integers, henceforth called SIGNED-SHORT are used for the operation-id, status-code and length fields. Four byte integers, henceforth called SIGNED-INTEGER, are used for value fields and the request-id. The following two sections present the encoding of the operation layer in two ways: informally through pictures and description formally through Augmented Backus-Naur Form (ABNF), as specified by RFC 5234 An operation request or response MUST use the encoding described in these two sections.

An operation request or response is encoded as follows:

----------------------------------------------- | version-number | 2 bytes - required ----------------------------------------------- | operation-id (request) | | or | 2 bytes - required | status-code (response) | ----------------------------------------------- | request-id | 4 bytes - required ----------------------------------------------- | attribute-group | n bytes - 0 or more ----------------------------------------------- | end-of-attributes-tag | 1 byte - required ----------------------------------------------- | data | q bytes - optional -----------------------------------------------

The first three fields in the above diagram contain the value of attributes described in Section 4.1.1 of the Model . The fourth field is the "attribute-group" field, and it occurs 0 or more times. Each "attribute-group" field represents a single group of attributes, such as an Operation Attributes group or a Job Attributes group (see the Model). The Model specifies the required attribute groups and their order for each operation request and response. The "end-of-attributes-tag" field is always present, even when the "data" is not present. The Model specifies whether the "data" field is present for each operation request and response.

Each "attribute-group" field is encoded as follows:

----------------------------------------------- | begin-attribute-group-tag | 1 byte ---------------------------------------------------------- | attribute | p bytes |- 0 or more ----------------------------------------------------------

An "attribute-group" field contains zero or more "attribute" fields. Note, the values of the "begin-attribute-group-tag" field and the "end-of-attributes-tag" field are called "delimiter-tags".

An "attribute" field is encoded as follows:

----------------------------------------------- | attribute-with-one-value | q bytes ---------------------------------------------------------- | additional-value | r bytes |- 0 or more ----------------------------------------------------------

When an attribute is single valued (e.g. "copies" with value of 10) or multi-valued with one value (e.g. "sides-supported" with just the value 'one-sided') it is encoded with just an "attribute-with-one-value" field. When an attribute is multi-valued with n values (e.g. "sides-supported" with the values 'one-sided' and 'two-sided-long-edge'), it is encoded with an "attribute-with-one-value" field followed by n-1 "additional-value" fields.

Each "attribute-with-one-value" field is encoded as follows:

----------------------------------------------- | value-tag | 1 byte ----------------------------------------------- | name-length (value is u) | 2 bytes ----------------------------------------------- | name | u bytes ----------------------------------------------- | value-length (value is v) | 2 bytes ----------------------------------------------- | value | v bytes -----------------------------------------------

An "attribute-with-one-value" field is encoded with five subfields: The "value-tag" field specifies the attribute syntax, e.g. 0x44 for the attribute syntax 'keyword'. The "name-length" field specifies the length of the "name" field in bytes, e.g. u in the above diagram or 15 for the name "sides-supported". The "name" field contains the textual name of the attribute, e.g. "sides-supported". The "value-length" field specifies the length of the "value" field in bytes, e.g. v in the above diagram or 9 for the (keyword) value 'one-sided'. The "value" field contains the value of the attribute, e.g. the textual value 'one-sided'.

Each "additional-value" field is encoded as follows:

----------------------------------------------- | value-tag | 1 byte ----------------------------------------------- | name-length (value is 0x0000) | 2 bytes ----------------------------------------------- | value-length (value is w) | 2 bytes ----------------------------------------------- | value | w bytes -----------------------------------------------

An "additional-value" is encoded with four subfields: The "value-tag" field specifies the attribute syntax, e.g. 0x44 for the attribute syntax 'keyword'. The "name-length" field has the value of 0 in order to signify that it is an "additional-value". The value of the "name-length" field distinguishes an "additional-value" field ("name-length" is 0) from an "attribute-with-one-value" field ("name-length" is not 0). The "value-length" field specifies the length of the "value" field in bytes, e.g. w in the above diagram or 19 for the (keyword) value 'two-sided-long-edge'. The "value" field contains the value of the attribute, e.g. the textual value 'two-sided-long-edge'.

Collection attributes create a named group containing related "member" attributes. The "attribute-with-one-value" field for a collection attribute is encoded as follows:

----------------------------------------------- | value-tag (value is 0x34) | 1 byte ----------------------------------------------- | name-length (value is u) | 2 bytes ----------------------------------------------- | name | u bytes ----------------------------------------------- | value-length (value is 0x0000) | 2 bytes ----------------------------------------------------------- | member-attribute | q bytes |-0 or more ----------------------------------------------------------- | end-value-tag (value is 0x37) | 1 byte ----------------------------------------------- | end-name-length (value is 0x0000) | 2 bytes ----------------------------------------------- | end-value-length (value is 0x0000) | 2 bytes -----------------------------------------------

Collection attribute is encoded with eight subfields: The "value-tag" field specifies the start attribute syntax: 0x34 for the attribute syntax 'begCollection'. The "name-length" field specifies the length of the "name" field in bytes, e.g. u in the above diagram or 9 for the name "media-col". Additional collection attribute values use a name length of 0x0000. The "name" field contains the textual name of the attribute, e.g. "media-col". The "value-length" field specifies a length of 0x0000. The "member-attribute" field contains member attributes encoded as defined in . The "end-value-tag" field specifies the end attribute syntax: 0x37 for the attribute syntax 'endCollection'. The "end-name-length" field specifies a length of 0x0000. The "end-value-length" field specifies a length of 0x0000.

Each "member-attribute" field is encoded as follows:

----------------------------------------------- | value-tag (value is 0x4A) | 1 byte ----------------------------------------------- | name-length (value is 0x0000) | 2 bytes ----------------------------------------------- | value-length (value is w) | 2 bytes ----------------------------------------------- | value (member-name) | w bytes ----------------------------------------------- | member-value-tag | 1 byte ----------------------------------------------- | name-length (value is 0x0000) | 2 bytes ----------------------------------------------- | member-value-length (value is x) | 2 bytes ----------------------------------------------- | member-value | x bytes -----------------------------------------------

A "member-attribute" is encoded with eight subfields: The "value-tag" field specifies 0x4A for the attribute syntax 'memberAttrName'. The "name-length" field has the value of 0 in order to signify that it is a "member-attribute" contained in the collection. The "value-length" field specifies the length of the "value" field in bytes, e.g. w in the above diagram or 10 for the member attribute name 'media-type'. Additional member attribute values are specifies using a value length of 0. The "value" field contains the name of the member attribute, e.g. the textual value 'media-type'. The "member-value-tag" field specifies the attribute syntax for the member attribute, e.g. 0x44 for the attribute syntax 'keyword'. The second "name-length" field has the value of 0 in order to signify that it is a "member-attribute" contained in the collection. The "member-value-length" field specifies the length of the member attribute value, e.g. x in the above diagram or 10 for the value 'stationery'. The "member-value" field contains the value of the attribute, e.g. the textual value 'stationery'.

From the standpoint of a parser that performs an action based on a "tag" value, the encoding consists of:

----------------------------------------------- | version-number | 2 bytes - required ----------------------------------------------- | operation-id (request) | | or | 2 bytes - required | status-code (response) | ----------------------------------------------- | request-id | 4 bytes - required ----------------------------------------------------------- | tag (delimiter-tag or value-tag) | 1 byte | ----------------------------------------------- |-0 or more | empty or rest of attribute | x bytes | ----------------------------------------------------------- | end-of-attributes-tag | 1 byte - required ----------------------------------------------- | data | y bytes - optional -----------------------------------------------

The following show what fields the parser would expect after each type of "tag": "begin-attribute-group-tag": expect zero or more "attribute" fields "value-tag": expect the remainder of an "attribute-with-one-value" or an "additional-value". "end-of-attributes-tag": expect that "attribute" fields are complete and there is optional "data"

The ABNF syntax for an IPP message is shown in .

ipp-message = ipp-request / ipp-response ipp-request = version-number operation-id request-id *attribute-group end-of-attributes-tag data ipp-response = version-number status-code request-id *attribute-group end-of-attributes-tag data version-number = major-version-number minor-version-number major-version-number = SIGNED-BYTE minor-version-number = SIGNED-BYTE operation-id = SIGNED-SHORT ; mapping from model status-code = SIGNED-SHORT ; mapping from model request-id = SIGNED-INTEGER ; whose value is > 0 attribute-group = begin-attribute-group-tag *attribute attribute = attribute-with-one-value *additional-value attribute-with-one-value = value-tag name-length name value-length value additional-value = value-tag zero-name-length value-length value name-length = SIGNED-SHORT ; number of octets of 'name' name = LALPHA *( LALPHA / DIGIT / "-" / "_" / "." ) value-length = SIGNED-SHORT ; number of octets of 'value' value = OCTET-STRING data = OCTET-STRING zero-name-length = %x00.00 ; name-length of 0 value-tag = %x10-FF ; see section 3.5.2 begin-attribute-group-tag = %x00-02 / %x04-0F ; see section 3.5.1 end-of-attributes-tag = %x03 ; tag of 3 ; see section 3.5.1 SIGNED-BYTE = BYTE SIGNED-SHORT = 2BYTE SIGNED-INTEGER = 4BYTE DIGIT = %x30-39 ; "0" to "9" LALPHA = %x61-7A ; "a" to "z" BYTE = %x00-FF OCTET-STRING = *BYTE

defines additional terms that are referenced in this document and provides an alternate grouping of the delimiter tags.

delimiter-tag = begin-attribute-group-tag / ; see section 3.5.1 end-of-attributes-tag begin-attribute-group-tag = %x00 / operation-attributes-tag / job-attributes-tag / printer-attributes-tag / unsupported-attributes-tag / future-group-tags operation-attributes-tag = %x01 ; tag of 1 job-attributes-tag = %x02 ; tag of 2 end-of-attributes-tag = %x03 ; tag of 3 printer-attributes-tag = %x04 ; tag of 4 unsupported-attributes-tag = %x05 ; tag of 5 future-group-tags = %x06-0F ; future extensions

Each "attribute-group" field MUST be encoded with the "begin-attribute-group-tag" field followed by zero or more "attribute" sub-fields. maps the Model group name to value of the "begin-attribute-group-tag" field: Model Document Group"begin-attribute-group-tag" field values Operation Attributes"operations-attributes-tag" Job Template Attributes"job-attributes-tag" Job Object Attributes"job-attributes-tag" Unsupported Attributes"unsupported-attributes-tag" Requested Attributes(Get-Job-Attributes) "job-attributes-tag" Requested Attributes(Get-Printer-Attributes)"printer-attributes-tag" Document Contentin a special position at the end of the message as described in . For each operation request and response, the Model prescribes the required and optional attribute groups, along with their order. Within each attribute group, the Model prescribes the required and optional attributes, along with their order. When the Model requires an attribute group in a request or response and the attribute group contains zero attributes, a request or response SHOULD encode the attribute group with the "begin-attribute-group-tag" field followed by zero "attribute" fields. For example, if the Client requests a single unsupported attribute with the Get-Printer-Attributes operation, the Printer MUST return no "attribute" fields, and it SHOULD return a "begin-attribute-group-tag" field for the Printer Attributes Group. The Unsupported Attributes group is not such an example. According to the Model, the Unsupported Attributes Group SHOULD be present only if the unsupported attributes group contains at least one attribute. A receiver of a request MUST be able to process the following as equivalent empty attribute groups: A "begin-attribute-group-tag" field with zero following "attribute" fields. An expected but missing "begin-attribute-group-tag" field. When the Model requires a sequence of an unknown number of attribute groups, each of the same type, the encoding MUST contain one "begin-attribute-group-tag" field for each attribute group even when an "attribute-group" field contains zero "attribute" sub-fields. For example, the Get-Jobs operation may return zero attributes for some jobs and not others. The "begin-attribute-group-tag" field followed by zero "attribute" fields tells the recipient that there is a Job in queue for which no information is available except that it is in the queue.

Some operation elements are called parameters in the Model. They MUST be encoded in a special position and they MUST NOT appear as operation attributes. These parameters are described in the subsections below.

The "version-number" field consists of a major and minor version-number, each of which is represented by a SIGNED-BYTE. The major version-number is the first byte of the encoding and the minor version-number is the second byte of the encoding. The protocol described in has a major version-number of 1 (0x01) and a minor version-number of 1 (0x01). The ABNF for these two bytes is %x01.01. Note: See for more information on the "version-number" field and IPP version numbers.

The "operation-id" field contains an operation-id value as defined in the Model. The value is encoded as a SIGNED-SHORT and is located in the third and fourth bytes of the encoding of an operation request.

The "status-code" field contains a status-code value as defined in the Model. The value is encoded as a SIGNED-SHORT and is located in the third and fourth bytes of the encoding of an operation response. If an IPP status-code is returned, then the HTTP status-code MUST be 200 (OK). With any other HTTP status-code value, the HTTP response MUST NOT contain an IPP message body, and thus no IPP status-code is returned.

The "request-id" field contains the request-id value as defined in the Model. The value is encoded as a SIGNED-INTEGER and is located in the fifth through eighth bytes of the encoding.

There are two kinds of tags: delimiter tags: delimit major sections of the protocol, namely attributes and data value tags: specify the type of each attribute value Tags are part of the IANA IPP registry

specifies the values for the delimiter tags defined in this document: Tag Value (Hex)Meaning 0x00reserved for future delimiters in standards track documents 0x01"operation-attributes-tag" 0x02"job-attributes-tag" 0x03"end-of-attributes-tag" 0x04"printer-attributes-tag" 0x05"unsupported-attributes-tag" 0x06-0x0freserved for future delimiters in standards track documents When a "begin-attribute-group-tag" field occurs in the protocol, it means that zero or more following attributes up to the next delimiter tag are attributes belonging to the attribute group specified by the value of the "begin-attribute-group-tag". For example, if the value of "begin-attribute-group-tag" is 0x01, the following attributes are members of the Operations Attributes group. The "end-of-attributes-tag" (value 0x03) MUST occur exactly once in an operation and MUST be the last "delimiter-tag". If the operation has a document-data group, the Document data in that group follows the "end-of-attributes-tag". The order and presence of "attribute-group" fields (whose beginning is marked by the "begin-attribute-group-tag" subfield) for each operation request and each operation response MUST be that defined in the Model. A Printer MUST treat a "delimiter-tag" (values from 0x00 through 0x0F) differently from a "value-tag" (values from 0x10 through 0xFF) so that the Printer knows there is an entire attribute group as opposed to a single value.

The remaining tables show values for the "value-tag" field, which is the first octet of an attribute. The "value-tag" field specifies the type of the value of the attribute. specifies the "out-of-band" values for the "value-tag" field defined in this document: Tag Value (Hex)Meaning 0x10unsupported 0x11reserved for "out-of-band" value definitions in future standards track documents 0x12unknown 0x13no-value 0x14-0x1Freserved for "out-of-band" value definitions in future standards track documents specifies the integer values for the "value-tag" field: Tag Value (Hex)Meaning 0x20reserved for integer type definitions in future standards track documents 0x21integer 0x22boolean 0x23enum 0x24-0x2Freserved for integer type definitions in future standards track documents specifies the octetString values for the "value-tag" field defined in this document: Tag Value (Hex)Meaning 0x30octetString with an unspecified format 0x31dateTime 0x32resolution 0x33rangeOfInteger 0x34begCollection 0x35textWithLanguage 0x36nameWithLanguage 0x37endCollection 0x38-0x3Freserved for octetString type definitions in future standards track documents specifies the character-string values for the "value-tag" field defined in this document: Tag Value (Hex)Meaning 0x40reserved for definition in a future standards track document 0x41textWithoutLanguage 0x42nameWithoutLanguage 0x43reserved for definition in a future standards track document 0x44keyword 0x45uri 0x46uriScheme 0x47charset 0x48naturalLanguage 0x49mimeMediaType 0x4AmemberAttrName 0x4B-0x5Freserved for character string type definitions in future standards track documents Note: An attribute value always has a type, which is explicitly specified by its tag; one such tag value is "nameWithoutLanguage". An attribute's name has an implicit type, which is keyword. The values 0x60-0xFF are reserved for future type definitions in standards track documents. The tag 0x7F is reserved for extending types beyond the 255 values available with a single byte. A tag value of 0x7F MUST signify that the first 4 bytes of the value field are interpreted as the tag value. Note this future extension doesn't affect parsers that are unaware of this special tag. The tag is like any other unknown tag, and the value length specifies the length of a value, which contains a value that the parser treats atomically. Values from 0x00000000 to 0x3FFFFFFF are reserved for definition in future standards track documents. The values 0x40000000 to 0x7FFFFFFF are reserved for vendor extensions.

The "name-length" field consists of a SIGNED-SHORT and specifies the number of octets in the immediately following "name" field. The value of this field excludes the two bytes of the "name-length" field. For example, if the "name" field contains 'sides', the value of this field is 5. If a "name-length" field has a value of zero, the following "name" field is empty and the following value is treated as an additional value for the attribute encoded in the nearest preceding "attribute-with-one-value" field. Within an attribute group, if two or more attributes have the same name, the attribute group is malformed (see ). The zero-length name is the only mechanism for multi-valued attributes.

The "name" field contains the name of an attribute. The Model specifies such names.

The "value-length" field consists of a SIGNED-SHORT which specifies the number of octets in the immediately following "value" field. The value of this field excludes the two bytes of the "value-length" field. For example, if the "value" field contains the keyword (string) value 'one-sided', the value of this field is 9. For any of the types represented by binary signed integers, the sender MUST encode the value in exactly four octets. For any of the types represented by binary signed bytes, e.g., the boolean type, the sender MUST encode the value in exactly one octet. 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 padding characters. For "out-of-band" "value-tag" fields defined in this document, such as 'unsupported', the "value-length" MUST be 0 and the "value" empty; the "value" has no meaning when the "value-tag" has one of these "out-of-band" values. For future "out-of-band" "value-tag" fields, the same rule holds unless the definition explicitly states that the "value-length" MAY be non-zero and the "value" non-empty

The syntax types (specified by the "value-tag" field) and most of the details of the representation of attribute values are defined in the Model. augments the information in the Model and defines the syntax types from the Model in terms of the 5 basic types defined in . The 5 types are US-ASCII-STRING, LOCALIZED-STRING, SIGNED-INTEGER, SIGNED-SHORT, SIGNED-BYTE, and OCTET-STRING. Syntax of Attribute ValueEncoding textWithoutLanguage, nameWithoutLanguageLOCALIZED-STRING textWithLanguageOCTET-STRING consisting of 4 fields: a SIGNED-SHORT which is the number of octets in the following field, a value of type natural-language, a SIGNED-SHORT which is the number of octets in the following field, and a value of type textWithoutLanguage. The length of a textWithLanguage value MUST be 4 + the value of field a + the value of field c. nameWithLanguageOCTET-STRING consisting of 4 fields: a SIGNED-SHORT which is the number of octets in the following field, a value of type natural-language, a SIGNED-SHORT which is the number of octets in the following field, and a value of type nameWithoutLanguage. The length of a nameWithLanguage value MUST be 4 + the value of field a + the value of field c. charset, naturalLanguage, mimeMediaType, keyword, uri, and uriSchemeUS-ASCII-STRING booleanSIGNED-BYTE where 0x00 is 'false' and 0x01 is 'true' integer and enuma SIGNED-INTEGER dateTimeOCTET-STRING consisting of eleven octets whose contents are defined by "DateAndTime" in RFC 2579 resolutionOCTET-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 units value. rangeOfIntegerEight octets consisting of 2 SIGNED-INTEGERs. The first SIGNED-INTEGER contains the lower bound and the second SIGNED-INTEGER contains the upper bound. 1setOf XEncoding according to the rules for an attribute with more than 1 value. Each value X is encoded according to the rules for encoding its type. octetStringOCTET-STRING collectionEncoding as defined in . The attribute syntax type of the value determines its encoding and the value of its "value-tag".

The "data" field MUST include any data required by the operation.

HTTP/1.1 is the REQUIRED transport layer for this protocol. HTTP/2 is an OPTIONAL transport layer for this protocol. The operation layer has been designed with the assumption that the transport layer contains the following information: the target URI for the operation the total length of the data in the operation layer, either as a single length or as a sequence of chunks each with a length. Printer implementations MUST support HTTP over the IANA assigned Well Known Port 631 (the IPP default port), although a Printer implementation can support HTTP over some other port as well. Each HTTP operation MUST use the POST method where the request-URI is the object target of the operation, and where the "Content-Type" of the message body in each request and response MUST be "application/ipp". The message body MUST contain the operation layer and MUST have the syntax described in "Syntax of Encoding". A Client implementation MUST adhere to the rules for a Client described for HTTP . A Printer (server) implementation MUST adhere the rules for an origin server described for HTTP . An IPP server sends a response for each request that it receives. If an IPP server detects an error, it MAY send a response before it has read the entire request. If the HTTP layer of the IPP server completes processing the HTTP headers successfully, it MAY send an intermediate response, such as "100 Continue", with no IPP data before sending the IPP response. A Client MUST expect such a variety of responses from an IPP server. For further information on HTTP, consult the HTTP documents . An HTTP/1.1 server MUST support chunking for IPP requests, and an IPP Client MUST support chunking for IPP responses according to HTTP/1.1 .

All Printer and Job objects are identified by a Uniform Resource Identifier (URI) so that they can be persistently and unambiguously referenced. Jobs can also be identified by a combination of Printer URI and Job ID. Some operation elements are encoded twice, once as the request-URI on the HTTP Request-Line and a second time as a REQUIRED operation attribute in the application/ipp entity. These attributes are the target for the operation and are called "printer-uri" and "job-uri". Note: The target URI is included twice in an operation referencing the same IPP object, but the two URIs can be different. For example, the HTTP request URI can be relative while the IPP request URI is absolute. HTTP allows Clients to generate and send a relative URI rather than an absolute URI. A relative URI identifies a resource with the scope of the HTTP server, but does not include scheme, host or port. The following statements characterize how URIs are used in the mapping of IPP onto HTTP: Although potentially redundant, a Client MUST supply the target of the operation both as an operation attribute and as a URI at the HTTP layer. The rationale for this decision is to maintain a consistent set of rules for mapping "application/ipp" to possibly many communication layers, even where URIs are not used as the addressing mechanism in the transport layer. Even though these two URIs might not be literally identical (one being relative and the other being absolute), they MUST both reference the same IPP object. The URI in the HTTP layer is either relative or absolute and is used by the HTTP server to route the HTTP request to the correct resource relative to that HTTP server. Once the HTTP server resource begins to process the HTTP request, it can get the reference to the appropriate IPP Printer object from either the HTTP URI (using to the context of the HTTP server for relative URIs) or from the URI within the operation request; the choice is up to the implementation. HTTP URIs can be relative or absolute, but the target URI in the IPP operation attribute MUST be an absolute URI.

The IPP URI schemes are 'ipp' and 'ipps' . Clients and Printers MUST support the ipp-URI value in the following IPP attributes: Job attributes: job-uri job-printer-uri Printer attributes: printer-uri-supported Operation attributes: job-uri printer-uri Each of the above attributes identifies a Printer or Job. The ipp-URI and ipps-URI are intended as the value of the attributes in this list. All of these attributes have a syntax type of 'uri', but there are attributes with a syntax type of 'uri' that do not use the 'ipp' scheme, e.g., "job-more-info". If a Printer registers its URI with a directory service, the Printer MUST register an ipp-URI or ipps-URI. When a Client sends a request, it MUST convert a target ipp-URI to a target http-URL (or ipps-URI to a target https-URI) for the HTTP layer according to the following steps: change the 'ipp' scheme to 'http' or 'ipps' scheme to 'https' add an explicit port 631 if the ipp-URL or ipps-URL does not contain an explicit port. Note: Port 631 is the IANA assigned Well Known Port for the 'ipp' and 'ipps' schemes. The Client MUST use the target http-URL or https-URL in both the HTTP Request-Line and HTTP headers, as specified by HTTP . However, the Client MUST use the target ipp-URI or ipps-URI for the value of the "printer-uri" or "job-uri" operation attribute within the application/ipp body of the request. The server MUST use the ipp-URI or ipps-URI for the value of the "printer-uri", "job-uri" or "printer-uri-supported" attributes within the application/ipp body of the response. For example, when an IPP Client sends a request directly, i.e., no proxy, to an ipp-URI "ipp://printer.example.com/ipp/print/myqueue", it opens a TCP connection to port 631 (the IPP implicit port) on the host "printer.example.com" and sends the following data:

POST /ipp/print/myqueue HTTP/1.1 Host: printer.example.com:631 Content-type: application/ipp Transfer-Encoding: chunked ... "printer-uri" 'ipp://printer.example.com/ipp/print/myqueue' (encoded in application/ipp message body) ...

As another example, when an IPP Client sends the same request as above via a proxy "myproxy.example.com", it opens a TCP connection to the proxy port 8080 on the proxy host "myproxy.example.com" and sends the following data:

POST http://printer.example.com:631/ipp/print/myqueue HTTP/1.1 Host: printer.example.com:631 Content-type: application/ipp Transfer-Encoding: chunked ... "printer-uri" 'ipp://printer.example.com/ipp/print/myqueue' (encoded in application/ipp message body) ...

The proxy then connects to the IPP origin server with headers that are the same as the "no-proxy" example above.

See the section on "IANA Considerations" in the document "Internet Printing Protocol/1.1: Model and Semantics" for information on IANA considerations for IPP extensions. The information following this paragraph will be forwarded to IANA to update the existing 'application/ipp' MIME media type registration whose contents are defined in "Encoding of the Operation Layer" in this document: Type name: application Subtype name: ipp Required parameters: N/A Optional parameters: N/A Encoding considerations: IPP protocol requests/responses MAY contain long lines and ALWAYS contain binary data (for example attribute value lengths). Security considerations: IPP protocol requests/responses do not introduce any security risks not already inherent in the underlying transport protocols. Protocol mixed-version interworking rules in as well as protocol encoding rules in this document are complete and unambiguous. See also the security considerations in this document and . Interoperability considerations: IPP requests (generated by clients) and responses (generated by servers) MUST comply with all conformance requirements imposed by the normative specifications and this document. Protocol encoding rules specified in [RFC2910bis] are comprehensive, so that interoperability between conforming implementations is guaranteed (although support for specific optional features is not ensured). Both the "charset" and "natural-language" of all IPP attribute values which are a LOCALIZED-STRING are explicit within IPP protocol requests/responses (without recourse to any external information in HTTP, SMTP, or other message transport headers). Published specifications: Sweet, M., McDonald, I., "Internet Printing Protocol/1.1: Model and Semantics" draft-sweet-rfc2911bis-10.txt, August 2016. [RFC2910bis] Sweet, M., McDonald, I., "Internet Printing Protocol/1.1: Encoding and Transport", draft-sweet-rfc2910bis-09.txt, August 2016. Applications which use this media type: Internet Printing Protocol (IPP) print clients and print servers, communicating using HTTP/HTTPS or other transport protocol. Messages of type "application/ipp" are self-contained and transport-independent, including "charset" and "natural-language" context for any LOCALIZED-STRING value. Fragment identifier considerations: N/A Additional information: Deprecated alias names for this type: N/A Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: ISTO PWG IPP Workgroup <ipp@pwg.org> Intended usage: COMMON Restrictions on usage: N/A Author: ISTO PWG IPP Workgroup <ipp@pwg.org> Change controller: ISTO PWG IPP Workgroup <ipp@pwg.org> Provisional registration? (standards tree only): No

See the section on "Internationalization Considerations" in the document "Internet Printing Protocol/1.1: Model and Semantics" for information on internationalization. This document adds no additional issues.

The IPP Model and Semantics document discusses high level security requirements (Client Authentication, Server Authentication and Operation Privacy). Client Authentication is the mechanism by which the Client proves its identity to the server in a secure manner. Server Authentication is the mechanism by which the server proves its identity to the Client in a secure manner. Operation Privacy is defined as a mechanism for protecting operations from eavesdropping. Message Integrity is addressed in the Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme .

This section defines the security requirements for IPP Clients and IPP objects.

IPP Clients and Printers SHOULD support Digest Authentication . Use of the Message Integrity feature (qop="auth-int") is OPTIONAL. Note: Previous versions of this document required support for the MD5 algorithms, however makes SHA2-256 mandatory to implement and deprecates MD5, allowing its use for backwards compatibility reasons. IPP implementations that support Digest Authentication MUST support SHA2-256 and SHOULD support MD5 for backwards-compatibility. Note: The reason that IPP Clients and Printers SHOULD (rather than MUST) support Digest Authentication is that there is a certain class of output devices where it does not make sense. Specifically, a low-end device with limited ROM space and low paper throughput may not need Client Authentication. This class of device typically requires firmware designers to make trade-offs between protocols and functionality to arrive at the lowest-cost solution possible. Factored into the designer's decisions is not just the size of the code, but also the testing, maintenance, usefulness, and time-to-market impact for each feature delivered to the customer. Forcing such low-end devices to provide security in order to claim IPP/1.1 conformance would not make business sense. Print devices that have high-volume throughput and have available ROM space will typically provide support for Client Authentication that safeguards the device from unauthorized access because these devices are prone to a high loss of consumables and paper if unauthorized access occurs.

IPP Clients and Printers SHOULD support Transport Layer Security (TLS) for Server Authentication and Operation Privacy. IPP Printers MAY also support TLS for Client Authentication. IPP Clients and Printers MAY support Basic Authentication for User Authentication if the channel is secure, e.g., IPP over HTTPS . IPP Clients and Printers SHOULD NOT support Basic Authentication over insecure channels. The IPP Model and Semantics document defines two Printer attributes ("uri-authentication-supported" and "uri-security-supported") that the Client can use to discover the security policy of a Printer. That document also outlines IPP-specific security considerations and is the primary reference for security implications with regard to the IPP protocol itself. Note: Because previous versions of this document did not require TLS support, this version cannot require it for IPP/1.1. However, since printing often involves a great deal of sensitive or private information (medical reports, performance reviews, banking information, etc.) and network monitoring is pervasive (), implementors are strongly encouraged to include TLS support. Note: Because IPP Printers typically use self-signed X.509 certificates, IPP Clients SHOULD support Trust On First Use (defined in ) in addition to traditional X.509 certificate validation.

IPP uses the "Upgrading to TLS Within HTTP/1.1" mechanism for 'ipp' URIs. The Client requests a secure TLS connection by using the HTTP "Upgrade" header, while the server agrees in the HTTP response. The switch to TLS occurs either because the server grants the Client's request to upgrade to TLS, or a server asks to switch to TLS in its response. Secure communication begins with a server's response to switch to TLS. IPP uses the "HTTPS: HTTP over TLS" mechanism for 'ipps' URIs. The Client and server negotiate a secure TLS connection immediately and unconditionally.

It is beyond the scope of this specification to mandate conformance with versions of IPP other than 1.1. IPP was deliberately designed, however, to make supporting other versions easy. IPP objects (Printers, Jobs, etc.) SHOULD: understand any valid request whose major "version-number" is greater than 0; respond appropriately with a response containing the same "version-number" parameter value used by the Client in the request (if the Client-supplied "version-number" is supported) or the highest "version-number" supported by the Printer (if the Client-supplied "version-number" is not supported.) IPP Clients SHOULD: understand any valid response whose major "version-number" is greater than 0.

The following are rules regarding the "version-number" parameter (see ): Clients MUST send requests containing a "version-number" parameter with the highest supported value, e.g., '1.1', '2.0', etc., and SHOULD try supplying alternate version numbers if they receive a 'server-error-version-not-supported' error return in a response. For example, if a Client sends an IPP/2.0 request that is rejected with the 'server-error-version-not-supported' error and an IPP/1.1 "version-number", it SHOULD retry by sending an IPP/1.1 request. IPP objects (Printers, Jobs, etc.) MUST accept requests containing a "version-number" parameter with a '1.1' value (or reject the request for reasons other than 'server-error-version-not-supported'). IPP objects SHOULD either accept requests whose major version is greater than 0 or reject such requests with the 'server-error-version-not-supported' status code. See "Versions" sub-section. In any case, security MUST NOT be compromised when a Client supplies a lower "version-number" parameter in a request. For example, if an IPP/2.0 conforming Printer accepts version '1.1' requests and is configured to enforce Digest Authentication, it MUST do the same for a version '1.1' request.

The following are rules regarding security, the "version-number" parameter, and the URI scheme supplied in target attributes and responses: When a Client supplies a request, the "printer-uri" or "job-uri" target operation attribute MUST have the same scheme as that indicated in one of the values of the "printer-uri-supported" Printer attribute. When the Printer returns the "job-printer-uri" or "job-uri" Job Description attributes, it SHOULD return the same scheme ('ipp', 'ipps', etc.) that the Client supplied in the "printer-uri" or "job-uri" target operation attributes in the Get-Job-Attributes or Get-Jobs request, rather than the scheme used when the Job was created. However, when a Client requests Job attributes using the Get-Job-Attributes or Get-Jobs operations, the Jobs and Job attributes that the Printer returns depends on: (1) the security in effect when the Job was created, (2) the security in effect in the query request, and (3) the security policy in force. The Printer MUST enforce its security and privacy policies based on the owner of the IPP object and the URI scheme and/or credentials supplied by the Client in the current request.

The following changes have been made since the publication of RFC 2910: Added references to current IPP extension specifications. Added optional support for HTTP/2. Added collection attribute syntax from RFC 3382. Fixed typographical errors. Now reference TLS/1.2 and no longer mandate the TLS/1.0 MTI cipher suites. Updated all references. Updated document organization to follow current style. Updated example ipp: URIs to follow RFC 7472 guidelines. Updated version compatibility for all versions of IPP. Updated HTTP Digest authentication to optional for Clients. Removed references to (experimental) IPP/1.0 and usage of http:/https: URLs.

This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged. This specification defines HPACK, a compression format for efficiently representing HTTP header fields, to be used in HTTP/2. Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations. The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation. The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false. The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages. The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework. This document defines the Internet Printing Protocol (IPP) over HTTPS transport binding and the corresponding 'ipps' URI scheme, which is used to designate the access to the network location of a secure IPP print service or a network resource managed by such a service. This document defines an alternate IPP transport binding to that defined in the original IPP URL Scheme (RFC 3510), but this document does not update or obsolete RFC 3510. Apple Inc. High North, Inc. University of Southern California (USC)/Information Sciences Institute

4676 Admiralty Way Marina del Rey CA 90291 US

ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. World Wide Web Consortium

Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge MA 02139 USA +1-617-253-5702 +1-617-258-5999 timbl@w3.org http://www.w3.org/People/Berners-Lee/

Day Software

5251 California Ave., Suite 110 Irvine CA 92617 USA +1-949-679-2960 +1-949-679-2972 fielding@gbiv.com http://roy.gbiv.com/

Adobe Systems Incorporated

345 Park Ave San Jose CA 95110 USA +1-408-536-3024 LMM@acm.org http://larry.masinter.net/

Applications uniform resource identifier URI URL URN WWW resource A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864 sob@harvard.edu

General keyword In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Note that the force of these words is modified by the requirement level of the document in which they are used. The Hypertext Transfer Protocol (HTTP) provides a simple challenge- response authentication mechanism that may be used by a server to challenge a client request and by a client to provide authentication information. This document defines the HTTP Digest Authentication scheme that can be used with the HTTP authentication mechanism. This document defines the "Basic" Hypertext Transfer Protocol (HTTP) authentication scheme, which transmits credentials as user-id/ password pairs, encoded using Base64. This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection. [STANDARDS-TRACK] This memo describes how to use Transport Layer Security (TLS) to secure Hypertext Transfer Protocol (HTTP) connections over the Internet. This memo provides information for the Internet community. Multipurpose Internet Mail Extensions (MIME) and various other Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This memo defines the "ipp" URL (Uniform Resource Locator) scheme. This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910. An "ipp" URL is used to specify the network location of a print service that supports the IPP Protocol (RFC 2910), or of a network resource (for example, a print job) managed by such a print service. [STANDARDS-TRACK] This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK] The Wollongong Group

1129 San Antonio Road Palo Alto CA 94303 US +1 415 962 7100 ljm@twg.com

Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible. This document defines the concept "Opportunistic Security" in the context of communications protocols. Protocol designs based on Opportunistic Security use encryption even when authentication is not available, and use authentication when possible, thereby removing barriers to the widespread use of encryption on the Internet. Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are widely used to protect data exchanged over application protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the last few years, several serious attacks on TLS have emerged, including attacks on its most commonly used cipher suites and their modes of operation. This document provides recommendations for improving the security of deployed services that use TLS and DTLS. The recommendations are applicable to the majority of use cases.

The following is an example of a Print-Job request with "job-name", "copies", and "sides" specified. The "ipp-attribute-fidelity" attribute is set to 'true' so that the print request will fail if the "copies" or the "sides" attribute are not supported or their values are not supported. OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0002Print-Joboperation-id 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x45uri typevalue-tag 0x000Bname-length printer-uriprinter-uriname 0x002Cvalue-length ipp://printer.example.com/ipp/print/pinetreeprinter pinetreevalue 0x42nameWithoutLanguage typevalue-tag 0x0008name-length job-namejob-namename 0x0006value-length foobarfoobarvalue 0x22boolean typevalue-tag 0x0016name-length ipp-attribute-fidelityipp-attribute-fidelityname 0x0001value-length 0x01truevalue 0x02start job-attributesjob-attributes-tag 0x21integer typevalue-tag 0x0006name-length copiescopiesname 0x0004value-length 0x0000001420value 0x44keyword typevalue-tag 0x0005name-length sidessidesname 0x0013value-length two-sided-long-edgetwo-sided-long-edgevalue 0x03end-of-attributesend-of-attributes-tag %!PDF...<PDF Document>data

Here is an example of a successful Print-Job response to the previous Print-Job request. The Printer supported the "copies" and "sides" attributes and their supplied values. The status code returned is 'successful-ok'. OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0000successful-okstatus-code 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x41textWithoutLanguage typevalue-tag 0x000Ename-length status-messagestatus-messagename 0x000Dvalue-length successful-oksuccessful-okvalue 0x02start job-attributesjob-attributes-tag 0x21integervalue-tag 0x0006name-length job-idjob-idname 0x0004value-length 147147value 0x45uri typevalue-tag 0x0007name-length job-urijob-uriname 0x0030value-length ipp://printer.example.com/ipp/print/pinetree/147job 147 on pinetreevalue 0x23enum typevalue-tag 0x0009name-length job-statejob-statename 0x0004value-length 0x0003pendingvalue 0x03end-of-attributesend-of-attributes-tag

Here is an example of an unsuccessful Print-Job response to the previous Print-Job request. It fails because, in this case, the Printer does not support the "sides" attribute and because the value '20' for the "copies" attribute is not supported. Therefore, no Job is created, and neither a "job-id" nor a "job-uri" operation attribute is returned. The error code returned is 'client-error-attributes-or-values-not-supported' (0x040B). OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x040Bclient-error-attributes-or-values-not-supportedstatus-code 0x000000011request-id 0x01start operation-attributesoperation-attributes tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x41textWithoutLanguage typevalue-tag 0x000Ename-length status-messagestatus-messagename 0x002Fvalue-length client-error-attributes-or-values-not-supportedclient-error-attributes-or-values-not-supportedvalue 0x05start unsupported-attributesunsupported-attributes tag 0x21integer typevalue-tag 0x0006name-length copiescopiesname 0x0004value-length 0x0000001420value 0x10unsupported (type)value-tag 0x0005name-length sidessidesname 0x0000value-length 0x03end-of-attributesend-of-attributes-tag

Here is an example of a successful Print-Job response to a Print-Job request like the previous Print-Job request, except that the value of "ipp-attribute-fidelity" is 'false'. The print request succeeds, even though, in this case, the Printer supports neither the "sides" attribute nor the value '20' for the "copies" attribute. Therefore, a Job is created, and both a "job-id" and a "job-uri" operation attribute are returned. The unsupported attributes are also returned in an Unsupported Attributes Group. The error code returned is 'successful-ok-ignored-or-substituted-attributes' (0x0001). OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0001successful-ok-ignored-or-substituted-attributesstatus-code 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x41textWithoutLanguage typevalue-tag 0x000Ename-length status-messagestatus-messagename 0x002Fvalue-length successful-ok-ignored-or-substituted-attributessuccessful-ok-ignored-or-substituted-attributesvalue 0x05start unsupported-attributesunsupported-attributes tag 0x21integer typevalue-tag 0x0006name-length copiescopiesname 0x0004value-length 0x0000001420value 0x10unsupported (type)value-tag 0x0005name-length sidessidesname 0x0000value-length 0x02start job-attributesjob-attributes-tag 0x21integervalue-tag 0x0006name-length job-idjob-idname 0x0004value-length 147147value 0x45uri typevalue-tag 0x0007name-length job-urijob-uriname 0x0030value-length ipp://printer.example.com/ipp/print/pinetree/147job 147 on pinetreevalue 0x23enum typevalue-tag 0x0009name-length job-statejob-statename 0x0004value-length 0x0003pendingvalue 0x03end-of-attributesend-of-attributes-tag

The following is an example of Print-URI request with "copies" and "job-name" parameters: OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0003Print-URIoperation-id 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x45uri typevalue-tag 0x000Bname-length printer-uriprinter-uriname 0x002Cvalue-length ipp://printer.example.com/ipp/print/pinetreeprinter pinetreevalue 0x45uri typevalue-tag 0x000Cname-length document-uridocument-uriname 0x0019value-length ftp://foo.example.com/fooftp://foo.example.com/foovalue 0x42nameWithoutLanguage typevalue-tag 0x0008name-length job-namejob-namename 0x0006value-length foobarfoobarvalue 0x02start job-attributesjob-attributes-tag 0x21integer typevalue-tag 0x0006name-length copiescopiesname 0x0004value-length 0x000000011value 0x03end-of-attributesend-of-attributes-tag

The following is an example of Create-Job request with no parameters and no attributes: OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0005Create-Joboperation-id 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x45uri typevalue-tag 0x000Bname-length printer-uriprinter-uriname 0x002Cvalue-length ipp://printer.example.com/ipp/print/pinetreeprinter pinetreevalue 0x03end-of-attributesend-of-attributes-tag

The following is an example of Create-Job request with the "media-col" collection attribute with the value "media-size={x-dimension=21000 y-dimension=29700} media-type='stationery'": OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0005Create-Joboperation-id 0x000000011request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x45uri typevalue-tag 0x000Bname-length printer-uriprinter-uriname 0x002Cvalue-length ipp://printer.example.com/ipp/print/pinetreeprinter pinetreevalue 0x34begCollectionvalue-tag 0x00099name-length media-colmedia-colname 0x00000value-length 0x4AmemberAttrNamevalue-tag 0x00000name-length 0x000A10value-length media-sizemedia-sizevalue (member-name) 0x34begCollectionmember-value-tag 0x00000name-length 0x00000member-value-length 0x4AmemberAttrNamevalue-tag 0x00000name-length 0x000B11value-length x-dimensionx-dimensionvalue (member-name) 0x21integermember-value-tag 0x00000name-length 0x00044member-value-length 0x0000520821000member-value 0x4AmemberAttrNamevalue-tag 0x00000name-length 0x000B11value-length y-dimensiony-dimensionvalue (member-name) 0x21integermember-value-tag 0x00000name-length 0x00044member-value-length 0x0000740429700member-value 0x37endCollectionend-value-tag 0x00000end-name-length 0x00000end-value-length 0x4AmemberAttrNamevalue-tag 0x00000name-length 0x000A10value-length media-typemedia-typevalue (member-name) 0x44keywordmember-value-tag 0x00000name-length 0x000A10member-value-length stationerystationerymember-value 0x37endCollectionend-value-tag 0x00000end-name-length 0x00000end-value-length 0x03end-of-attributesend-of-attributes-tag

The following is an example of Get-Jobs request with parameters but no attributes: OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x000AGet-Jobsoperation-id 0x0000007B123request-id 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x45uri typevalue-tag 0x000Bname-length printer-uriprinter-uriname 0x002Cvalue-length ipp://printer.example.com/ipp/print/pinetreeprinter pinetreevalue 0x21integer typevalue-tag 0x0005name-length limitlimitname 0x0004value-length 0x0000003250value 0x44keyword typevalue-tag 0x0014name-length requested-attributesrequested-attributesname 0x0006value-length job-idjob-idvalue 0x44keyword typevalue-tag 0x0000additional valuename-length 0x0008value-length job-namejob-namevalue 0x44keyword typevalue-tag 0x0000additional valuename-length 0x000Fvalue-length document-formatdocument-formatvalue 0x03end-of-attributesend-of-attributes-tag

The following is an of Get-Jobs response from previous request with 3 jobs. The Printer returns no information about the second Job (because of security reasons): OctetsSymbolic ValueProtocol field 0x01011.1version-number 0x0000successful-okstatus-code 0x0000007B123request-id (echoed back) 0x01start operation-attributesoperation-attributes-tag 0x47charset typevalue-tag 0x0012name-length attributes-charsetattributes-charsetname 0x0005value-length utf-8UTF-8value 0x48natural-language typevalue-tag 0x001Bname-length attributes-natural-languageattributes-natural-languagename 0x0005value-length en-usen-USvalue 0x41textWithoutLanguage typevalue-tag 0x000Ename-length status-messagestatus-messagename 0x000Dvalue-length successful-oksuccessful-okvalue 0x02start job-attributes (1st object)job-attributes-tag 0x21integer typevalue-tag 0x0006name-length job-idjob-idname 0x0004value-length 147147value 0x36nameWithLanguagevalue-tag 0x0008name-length job-namejob-namename 0x000Cvalue-length 0x0005sub-value-length fr-cafr-CAvalue 0x0003sub-value-length foufouname 0x02start job-attributes (2nd object)job-attributes-tag 0x02start job-attributes (3rd object)job-attributes-tag 0x21integer typevalue-tag 0x0006name-length job-idjob-idname 0x0004value-length 148149value 0x36nameWithLanguagevalue-tag 0x0008name-length job-namejob-namename 0x0012value-length 0x0005sub-value-length de-CHde-CHvalue 0x0009sub-value-length isch guetisch guetname 0x03end-of-attributesend-of-attributes-tag

The authors would like to acknowledge the following individuals for their contributions to the original IPP/1.1 specifications: Sylvan Butler, Roger deDry, Tom Hastings, Robert Herriot (original RFC 2910 editor), Paul Moore, Kirk Ocke, Randy Turner, John Wenn, and Peter Zehler

The following changes are in draft-sweet-rfc2910bis-10: Updated the acknowledgements to include authors from the original RFC 3382.

The following changes are in draft-sweet-rfc2910bis-09: Abstract: Mention that this document obsoletes RFC 2910 and 3382, and reword for clarity. Editor's Note: Add parenthetical note to RFC editor to remove before publication. Updated reference to ASCII to RFC 20/STD 80. Section 1: Removed redundant conformance terminology from the introduction. Section 3.2, Figure 10: Fixed ABNF syntax error. Section 3.4: Added reference to 3.1.1 for document content. Section 3.5.2: Reworded the (confusing) meanings for reserved values. Section 4: Reword "It is REQUIRED". Section 4.1: Reword example without conformance terminology. Section 5: Clarify URL rewriting rules. Section 6: Updated document pointers in MIME media type registration. Section 8: Mention message integrity, addressed by IPPS. Section 8.1.1: Reword and make SHA2-256 required if Digest is supported. Section 8.1.2: Add reference to RFC 7258 to encourage TLS support, RFC 7435 for TOFU. Section 8.2.1: SHOULD NOT support Basic over insecure channels. Section 9: Reworded to SHOULD allow version numbers > 0.0. Section 9.1: Reworded to SHOULD allow version numbers > 0.0, added example for client sending a 2.0 request and retrying with a 1.1 request.

The following changes are in draft-sweet-rfc2910bis-08: Section 3: Added reference to RFC 2978. Section 3.1.1: Fix reference to RFC 2910bis. Section 3.2: Fix ABNF for begin-attributes-group-tag. Section 3.8: Add examples for signed byte types (boolean). Section 8.1.2: Add reference to RFC 7472 (IPP over HTTPS) for example of secure channel. Section 9: Reference PWG 5100.12. Section 11.1: Added reference to RFC 2978. Section 11.2: Removed unused reference to IANA-CON. Appendix B: Updated MIME media type registration template and moved to section 6. Updated references to RFC 1903 to 2579.

The following changes are in draft-sweet-rfc2910bis-07: Global: Drop RFC2911bis references after "Model". Section 1.1: Fix typo. Section 4: Drop note about non-conforming HTTP/1.1 servers.

The following changes are in draft-sweet-rfc2910bis-06: Global: "Model" changed to just "Model". Global: "message-body" changed to "message body". Abstract: "MIME" instead of "mime" plus some minor rewording. Section 1: Updated references to HTTP Basic and Digest, clarify that the semantics/model are defined in both the Model and subsequent extensions. Section 2.2: Fixed some typos and added a definition of Model. Section 3.1.1: Reworded paragraph about the data field. Section 3.2: Reworded and now use figure references, and fixed section references in figures. Section 3.3: Added table reference, fix typo. Section 3.4.1: Replace "this document" with reference to 2911bis. Section 3.4.3: HTTP status-code (to be consistent with RFC 7230). Section 3.5.1: Add table references, capitalize Document, reword ordering requirements, reword printer requirements. Section 3.5.2: Add table references, dropped notes (15 years without needing it, we don't need the note...) Section 3.6: "mal-formed" changed to "malformed", fix RFC2911bis reference, single quotes around value. Section 3.8: "string" instead of "text", use single quotes for values. Section 3.9: Add table reference. Section 4: Fix HTTP references and put Note in a separate paragraph. Section 4.1: Mention the Job ID, clean up Note and get rid of "NEED NOT" language. Section 5: Clients and Printers MUST support, drop "object", use double quotes around attribute names, drop discussion of UI, fix typos. Section 6: Point to RFC2911bis. Section 8.1.1: Update references to HTTP Basic and Digest RFCs. Section 9: Allow 1.x and 2.x, fix typos. Section 11.1: Updated 5100.12, HTTP Basic and Digest references Appendix A: Examples now use UTF-8, fix job-uri to be consistent with job-id.

The following changes are in draft-sweet-rfc2910bis-05: Submission type is now IETF (AD-sponsored), clarify goals. Abstract: This document does not define the 'ipp' URI scheme. Section 5: drop reference to RFC 2617 Section 8.1.1: combine identical Client and Printer requirements Section 8.1.2: also applies to clients, HTTP Basic is User authentication, not Client authentication. References to RFC 2617 are updated to the updated drafts in the RFC editor's queue Global: Client, Printer, and Job are defined terms, capitalize

The following changes are in draft-sweet-rfc2910bis-04: Removed more references to IPP/1.0. Section 5: Be explicit about ipp/s-URI and http/s-URL Section 9.1: Reword SHOULD recommendation (avoid passive voice) Section 9.2: Reword item 3: the server MUST NOT compromise security... Make sure to use URI for generic schemes and URL for HTTP/HTTPS. Fixed incorrect usage of lowercase conformance words.

The following changes are in draft-sweet-rfc2910bis-03: New HTTP/2 RFCs: 7540, 7541 Added informative reference to UTA BCP (RFC 7525) Culled list of people in acknowledgements to the original RFC 2910 editors, per IPP F2F.

The following changes are in draft-sweet-rfc2910bis-02: Sections 3.1.x: Dropped "Picture of the encoding of" from titles Section 3.4.1: Added reference to IPP version interoperability section. Section 3.4.2: Removed paragraph on status-code as operation attribute (already covered in 3.4 intro) and updated HTTP status code 200 name (OK) Section 3.5: Added reference to IANA IPP registry for tags. Section 3.8: Mention SIGNED-BYTE is 1 octet. Section 4.1: Drop mention of URIs not being widely implemented, and that implementations will pass around URLs (not true). Also remove more "need not" text. Section 6: Fixed references. Section 8.1.1: Make Digest authentication a SHOULD for clients. Section 9: Reworked for generic IPP version compatibility. Section 9.1: Reworked for IPP 2.x compatibility. Section 9.2: Drop reference to IPP/1.0 and http/https URI schemes. Appendix A: Updated example URIs to follow IETF and IPP/IPPS URI examples Global: ipp-URL tp ipp-URI, URL to URI Global: Don't use conformance language for statements of fact. Global: Change "NOTE:" to "Note:" for consistency.

The following changes are in draft-sweet-rfc2910bis-01: Errata ID 4100: Cleaned up TLS references and recommendations - no longer include cipher suites. Errata ID 4172: Fixed range of standards-track value tags (to 0x3ffffff not 0x37777777) Updated RFC references. Added HTTP/2 references, made it clear that only HTTP/1.1 is required and HTTP/2 is optional. Added collection attribute encoding from RFC 3382.