Internet Printing Protocol (IPP): Requirements for IPP Notifications
RFC 3997

 
Document Type RFC - Informational (March 2005; No errata)
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 3997 (Informational)
Telechat date
Responsible AD Scott Hollenbeck
Send notices to <carl@manros.com>
Network Working Group                                   T. Hastings, Ed.
Request for Comments: 3997                             Xerox Corporation
Category: Informational                                      R. K. deBry
                                               Utah Valley State College
                                                                H. Lewis
                                                         IBM Corporation
                                                              March 2005

                   Internet Printing Protocol (IPP):
                   Requirements for IPP Notifications

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document is one of a set of documents that together describe all
   aspects of the Internet Printing Protocol (IPP).  IPP is an
   application-level protocol that can be used for distributed printing
   on the Internet.  There are multiple parts to IPP, but the primary
   architectural components are the Model, the Protocol, and an
   interface to Directory Services.  This document provides a statement
   of the requirements for notifications as an optional part of an IPP
   Service.

Table of Contents

   1.   Introduction. . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.   Terminology . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3.   Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.   Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.   Security Considerations for IPP Notifications Requirements. . 12
   6.   Internationalization Considerations . . . . . . . . . . . . . 13
   7.   IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
   8.   References. . . . . . . . . . . . . . . . . . . . . . . . . . 14
        8.1.  Normative References. . . . . . . . . . . . . . . . . . 14
        8.2.  Informative References. . . . . . . . . . . . . . . . . 14
   9.   Appendix A: Description of the Base IPP Documents . . . . . . 15
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
   Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 17

Hastings, et al.             Informational                      [Page 1]
RFC 3997             IPP: Notification Requirements           March 2005

1.  Introduction

   This document is one of a set of documents that together describe all
   aspects of the Internet Printing Protocol (IPP).  IPP is an
   application level protocol that can be used for distributed printing
   on the Internet.  There are multiple parts to IPP, but the primary
   architectural components are the Model, the Protocol, and an
   interface to Directory Services.  This document provides a statement
   of the requirements for notifications as an optional part of an IPP
   Service.  See section 10 for a description of the base IPP documents.

   The scope of this requirements document covers functionality used by
   the following kinds of IPP Users: End Users, Print Administrators,
   and Operators.  See [RFC3995] for the extensions to the Internet
   Printing Protocol/1.0 (IPP) [RFC2565], [RFC2566], IPP/1.1 [RFC2911],
   [RFC2910], and future versions.

2.  Terminology

   It is necessary to define a set of terms to be able to clearly
   express the requirements for notification services in an IPP System.

2.1.  Job-Submitting End User

   A human end user who submits a print job to an IPP Printer.  This
   person may or may not be within the same security domain as the
   Printer.  This person may or may not be geographically near the
   printer.

2.2.  Administrator

   A human user who established policy for and configures the print
   system.

2.3.  Operator

   A human user who carries out the policy established by the
   Administrator and controls the day-to-day running of the print
   system.

2.4.  Job-Submitting Application

   An application (for example, a batch application), acting on behalf
   of a Job Submitting End User, that submits a print job to an IPP
   Printer.  The application may or may not be within the same security
   domain as the Printer.  This application may or may not be
   geographically near the printer.

Hastings, et al.             Informational                      [Page 2]
RFC 3997             IPP: Notification Requirements           March 2005

2.5.  Security Domain

   For the purposes of this discussion, the set of network components
Show full document text