Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications
RFC 3996

 
Document
Type RFC - Proposed Standard (March 2005; No errata)
Updates RFC 2911
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG
IESG state RFC 3996 (Proposed Standard)
Telechat date
Responsible AD Scott Hollenbeck
Send notices to <carl@manros.com>

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                         R. Herriot
Request for Comments: 3996                     Global Workflow Solutions
Updates: 2911                                                T. Hastings
Category: Standards Track                                    Xerox Corp.
                                                                H. Lewis
                                                               IBM Corp.
                                                              March 2005

                   Internet Printing Protocol (IPP):
          The 'ippget' Delivery Method for Event Notifications

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 (2005).

Abstract

   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.

Table of Contents

   1.   Introduction. . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.   Terminology . . . . . . . . . . . . . . . . . . . . . . . . .  3
        2.1.  Conformance Terminology . . . . . . . . . . . . . . . .  4
        2.2.  Other Terminology . . . . . . . . . . . . . . . . . . .  4
   3.   Model and Operation . . . . . . . . . . . . . . . . . . . . .  4
   4.   General Information . . . . . . . . . . . . . . . . . . . . .  5
   5.   Get-Notifications Operation . . . . . . . . . . . . . . . . .  7
        5.1.  Get-Notifications Request . . . . . . . . . . . . . . .  8
              5.1.1.  notify-subscription-ids (1setOf integer(1:MAX))  8
              5.1.2.  notify-sequence-numbers (1setOf integer(1:MAX))  9

Herriot, et al.             Standards Track                     [Page 1]
RFC 3996           IPP: The 'ippget' Delivery Method          March 2005

              5.1.3.  notify-wait (boolean) . . . . . . . . . . . . . 10
        5.2.  Get-Notifications Response. . . . . . . . . . . . . . . 10
              5.2.1.  notify-get-interval (integer(0:MAX)). . . . . . 13
              5.2.2.  printer-up-time (integer(1:MAX)). . . . . . . . 14
   6.   Additional Information about Subscription Template Attributes 17
        6.1.  notify-pull-method (type2 keyword). . . . . . . . . . . 17
   7.   Subscription Description Attributes . . . . . . . . . . . . . 18
   8.   Additional Printer Description Attributes . . . . . . . . . . 18
        8.1.  ippget-event-life (integer(15:MAX)) . . . . . . . . . . 18
   9.   New Values for Existing Printer Description Attributes. . . . 19
        9.1.  notify-pull-method-supported (1setOf type2 keyword) . . 19
        9.2.  operations-supported (1setOf type2 enum). . . . . . . . 19
   10.  New Status Codes. . . . . . . . . . . . . . . . . . . . . . . 19
        10.1.  successful-ok-events-complete (0x0007) . . . . . . . . 20
   11.  Encoding and Transport. . . . . . . . . . . . . . . . . . . . 20
   12.  Conformance Requirements. . . . . . . . . . . . . . . . . . . 21
        12.1.  Conformance for IPP Printers . . . . . . . . . . . . . 21
        12.2.  Conformance for IPP Clients. . . . . . . . . . . . . . 22
   13.  Normative References. . . . . . . . . . . . . . . . . . . . . 23
   14.  Informative References. . . . . . . . . . . . . . . . . . . . 23
   15.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
        15.1.  Attribute Registrations. . . . . . . . . . . . . . . . 24
        15.2.  Delivery Method and Additional Keyword Attribute Value
               registrations for Existing Attributes. . . . . . . . . 24
        15.3.  Additional Enum Attribute Values . . . . . . . . . . . 25
        15.4.  Operation Registrations. . . . . . . . . . . . . . . . 25
        15.5.  Status Code Registrations. . . . . . . . . . . . . . . 25
   16.  Internationalization Considerations . . . . . . . . . . . . . 25
   17.  Security Considerations . . . . . . . . . . . . . . . . . . . 26
        17.1.  Notification Recipient Client Access Rights. . . . . . 26
        17.2.  Printer Security Threats . . . . . . . . . . . . . . . 27
        17.3.  Notification Recipient Security Threats. . . . . . . . 27
Show full document text