Cite this STD: TXT
STD 92 contains the following RFCs:| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 8010, STD 92 | Internet Printing Protocol/1.1: Encoding and Transport | M. Sweet, I. McDonald | January 2017 | Obsoletes RFC 2910, RFC 3382 | Internet Standard (was published as Proposed Standard ) | |
| RFC 8011, STD 92 | Internet Printing Protocol/1.1: Model and Semantics | M. Sweet, I. McDonald | January 2017 | Obsoletes RFC 2911, RFC 3381, RFC 3382, Errata | Internet Standard (was published as Proposed Standard ) |
Abstract of RFC 8010
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 "Internet Printing Protocol/1.1: Model and Semantics" (RFC 8011).
Abstract of RFC 8011
The Internet Printing Protocol (IPP) is an application-level protocol for distributed printing using Internet tools and technologies. This document describes a simplified model consisting of abstract objects, attributes, and operations that is independent of encoding and transport. The model consists of several objects, including Printers and Jobs. Jobs optionally support multiple Documents.
IPP semantics allow End Users and Operators to query Printer capabilities; submit Print Jobs; inquire about the status of Print Jobs and Printers; and cancel, hold, and release Print Jobs. IPP semantics also allow Operators to pause and resume Jobs and Printers.
Security, internationalization, and directory issues are also addressed by the model and semantics. The IPP message encoding and transport are described in "Internet Printing Protocol/1.1: Encoding and Transport" (RFC 8010).
This document obsoletes RFCs 2911, 3381, and 3382.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.