RFC 2567: Design Goals for an Internet Printing Protocol
In plain English — editorial summary, not part of the RFC
This document 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. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2567
- Published
- April 1999
- Authors
- F. Wright
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2568Rationale for the Structure of the Model and Protocol for the Internet Printing ProtocolCurrent
April 1999
- RFC 2569Mapping between LPD and IPP ProtocolsCurrent
April 1999
- RFC 2910Internet Printing Protocol/1.1: Encoding and TransportObsoleted
September 2000
- RFC 2911Internet Printing Protocol/1.1: Model and SemanticsObsoleted
September 2000
- RFC 3380Internet Printing Protocol (IPP): Job and Printer Set OperationsCurrent
October 2002
- RFC 3381Internet Printing Protocol (IPP): Job Progress AttributesObsoleted
October 2002
- RFC 3382Internet Printing Protocol (IPP): The 'collection' attribute syntaxObsoleted
October 2002
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?