RFC 3381: Internet Printing Protocol (IPP): Job Progress Attributes
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8011.
Current document in this lineage: RFC 8010 — Internet Printing Protocol/1.1: Encoding and Transport; RFC 8011 — Internet Printing Protocol/1.1: Model and Semantics
In plain English — editorial summary, not part of the RFC
This document defines four new Job Description attributes for monitoring job progress to be registered as OPTIONAL extensions to IPP/1.0 [RFC2566] and IPP/1.1 [RFC2911].
Document record
- Document ID
- RFC3381
- Published
- October 2002
- Authors
- T. Hastings; H. Lewis; R. Bergman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.
- RFC 2565 (1999)
- RFC 2566 (1999)
- RFC 2910 (2000)
- RFC 2911 (2000)
- RFC 3381 (2002)
- RFC 3382 (2002)
- RFC 8010 (2017)
- RFC 8011 (2017) ✓
Read the full history of Internet Printing Protocol/1.1: Model and Semantics →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3380Internet Printing Protocol (IPP): Job and Printer Set OperationsCurrent
October 2002
- RFC 3382Internet Printing Protocol (IPP): The 'collection' attribute syntaxObsoleted
October 2002
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 2003
- RFC 2911Internet Printing Protocol/1.1: Model and SemanticsObsoleted
September 2000
- RFC 2569Mapping between LPD and IPP ProtocolsCurrent
April 1999
- RFC 2568Rationale for the Structure of the Model and Protocol for the Internet Printing ProtocolCurrent
April 1999
- RFC 2567Design Goals for an Internet Printing ProtocolCurrent
April 1999
- RFC 2565Internet Printing Protocol/1.0: Encoding and TransportObsoleted
April 1999
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?