RFC 3996: Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications
In plain English — editorial summary, not part of the RFC
This document describes an extension to the Internet Printing Protocol1.1: Model and Semantics (RFC 2911, RFC 2910). This document specifies the 'ippget' Pull Delivery Method for use with the "Internet Printing Protocol (IPP): Event Notifications and Subscriptions" specification (RFC 3995). This IPPGET Delivery Method is REQUIRED for all clients and Printers that support RFC 3995. The Notification Recipient, acting as a client, fetches (pulls) Event Notifications by using the Get-Notifications operation defined in this document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3996
- Published
- March 2005
- Authors
- R. Herriot; T. Hastings; H. Lewis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 31
- Also known as
- —
- Updates:
- RFC 2911
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3997Internet Printing Protocol (IPP): Requirements for IPP NotificationsCurrent
March 2005
- RFC 3995Internet Printing Protocol (IPP): Event Notifications and SubscriptionsCurrent
March 2005
- RFC 3998Internet Printing Protocol (IPP): Job and Printer Administrative OperationsCurrent
March 2005
- RFC 3983Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)Updated
January 2005
- RFC 3982IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)Current
January 2005
- RFC 3981IRIS: The Internet Registry Information Service (IRIS) Core ProtocolUpdated
January 2005
- RFC 3977Network News Transfer Protocol (NNTP)Updated
October 2006
- RFC 3965A Simple Mode of Facsimile Using Internet MailCurrent
December 2004
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?