Internet Printing Protocol/1.1: Encoding and Transport
RFC 2910
Document | Type |
RFC - Proposed Standard
(September 2000; Errata)
Obsoleted by RFC 8010
Obsoletes RFC 2565
|
|
---|---|---|---|
Authors | Paul Moore , Robert Herriot , John Wenn , Sylvan Butler | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 2910 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group R. Herriot, Editor Request for Comments: 2910 Xerox Corporation Obsoletes: 2565 S. Butler Category: Standards Track Hewlett-Packard P. Moore Peerless Systems Networking R. Turner 2wire.com J. Wenn Xerox Corporation September 2000 Internet Printing Protocol/1.1: Encoding and Transport Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document defines the rules for encoding IPP operations and IPP attributes into a new Internet mime media type called "application/ipp". This document also defines the rules for transporting over Hypertext Transfer Protocol (HTTP) a message body whose Content-Type is "application/ipp". This document defines a new scheme named 'ipp' for identifying IPP printers and jobs. Herriot, et al. Standards Track [Page 1] RFC 2910 IPP/1.1: Encoding and Transport September 2000 The full set of IPP documents includes: Design Goals for an Internet Printing Protocol [RFC2567] Rationale for the Structure and Model and Protocol for the Internet Printing Protocol [RFC2568] Internet Printing Protocol/1.1: Model and Semantics [RFC2911] Internet Printing Protocol/1.1: Encoding and Transport (this document) Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] Mapping between LPD and IPP Protocols [RFC2569] The document, "Design Goals for an Internet Printing Protocol", takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help to clarify the features that need to be included in a printing protocol for the Internet. It identifies requirements for three types of users: end users, operators, and administrators. It calls out a subset of end user requirements that are satisfied in IPP/1.1. A few OPTIONAL operator operations have been added to IPP/1.1. The document, "Rationale for the Structure and Model and Protocol for the Internet Printing Protocol", describes IPP from a high level view, defines a roadmap for the various documents that form the suite of IPP specification documents, and gives background and rationale for the IETF working group's major decisions. The document, "Internet Printing Protocol/1.1: Model and Semantics", describes a simplified model with abstract objects, their attributes, and their operations that are independent of encoding and transport. It introduces a Printer and a Job object. The Job object optionally supports multiple documents per Job. It also addresses security, internationalization, and directory issues. The document "Internet Printing Protocol/1.1: Implementer's Guide", gives advice to implementers of IPP clients and IPP objects. The document "Mapping between LPD and IPP Protocols", gives some advice to implementers of gateways between IPP and LPD (Line Printer Daemon) implementations. Herriot, et al. Standards Track [Page 2] RFC 2910 IPP/1.1: Encoding and Transport September 2000 Table of Contents 1. Introduction ...................................................4 2. Conformance Terminology ........................................4 3. Encoding of the Operation Layer ...............................4 3.1 Picture of the Encoding ...................................6 3.1.1 Request and Response...................................6 3.1.2 Attribute Group........................................6 3.1.3 Attribute..............................................7 3.1.4 Picture of the Encoding of an Attribute-with-one-value.7 3.1.5 Additional-value.......................................8Show full document text