INTERNET-DRAFT         There are 4 issues
<draft-ietf-ipp-indp-method-01.txt>
<draft-ietf-ipp-indp-method-02.txt>
                                                              Hugo Parra
                                                            Novell, Inc.
                                                            Tom Hastings
                                                             Xerox Corp.
                                                           July 6, 14, 2000

                   Internet Printing Protocol (IPP):

        The 'indp' Notification Delivery Method and Protocol/1.0

    Copyright (C) The Internet Society (2000). All Rights Reserved.

Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of [rfc2026].  Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups.  Note that other groups may also distribute working
documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress".

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html.

Abstract

The IPP Event Notification specification [ipp-ntfy] is an OPTIONAL notification extension document [ipp-ntfy] defines operations
that a client can perform in order to IPP/1.0, IPP/1.1, create Subscription Objects in a
Printer and future versions.  [ipp-ntfy] requires
the definition of carry out other operations on them. The Subscription Object
specifies that when one or more Delivery Methods in separate Delivery
Method Documents for of the specified Events occurs, the Printer to dispatch
sends an asynchronous Event Notifications Notification to the specified Notification Recipients.
Recipient via the specified Delivery Method (i.e., protocol).

The notification extension document [ipp-ntfy] specifies that each
Delivery Method is defined in another document. This document is one
such document, and it specifies the 'indp' Delivery Method and Protocol.
This Delivery Method Document defines is a simple protocol consisting of a single
operation: the
semantics Send-Notifications operation which uses the same encoding
and syntax transport as IPP.  This document defines version '1.0' of the 'indp' Notification Delivery Method.
protocol.

For this Delivery Method, when an IPP Event occurs, the Printer immediately
sends (pushes) an IPP Event
Notifications request to the Notification Recipients using via the Send-
Notifications Send-Notifications
operation defined to the Notification Recipient specified in this document. the Subscription

                      Expires: January 14, 2001

Object. The Event Notification content consists of Machine Consumable
attributes and a Human Consumable "notify-text" attribute.  The
Notification Recipient returns a response to the Printer.  The Send-Notifications
operation uses the same Encoding and Transport as IPP itself.

                      Expires: January 6, 14, 2001

The full set of IPP documents includes:

  Design Goals for an Internet Printing Protocol [RFC2567]
  Rationale for the Structure and Model and Protocol for the Internet
     Printing Protocol [RFC2568]
  Internet Printing Protocol/1.1: Model and Semantics [ipp-mod]
  Internet Printing Protocol/1.1: Encoding and Transport [ipp-pro]
  Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
  Mapping between LPD and IPP Protocols [RFC2569]
  Internet Printing Protocol (IPP):  IPP Event Notification
     Specification [ipp-ntfy]

The "Design Goals for an Internet Printing Protocol" 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.  It calls out a subset of end user requirements that are
satisfied in IPP/1.0.  A few OPTIONAL operator operations have been
added to IPP/1.1.

The "Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol" document describes IPP from a high level view,
defines a roadmap for the various documents that form the suite of IPP
specification documents, and gives background and rationale for the IETF
working group's major decisions.

The "Internet Printing Protocol/1.1: Model and Semantics" document
describes a simplified model with abstract objects, their attributes,
and their operations that are independent of encoding and transport.  It
introduces a Printer and a Job object.  The Job object optionally
supports multiple documents per Job.  It also addresses security,
internationalization, and directory issues.

The "Internet Printing Protocol/1.1: Encoding and Transport" document is
a formal mapping of the abstract operations and attributes defined in
the model document onto HTTP/1.1 [RFC2616].  It defines the encoding
rules for a new Internet MIME media type called "application/ipp".  This
document also defines the rules for transporting a message body over
HTTP whose Content-Type is "application/ipp".  This document defines a
new scheme named 'ipp' for identifying IPP printers and jobs.

The "Internet Printing Protocol/1.1: Implementer's Guide" document gives
insight and advice to implementers of IPP clients and IPP objects.  It
is intended to help them understand IPP/1.1 and some of the
considerations that may assist them in the design of their client and/or
IPP object implementations.  For example, a typical order of processing
requests is given, including error checking.  Motivation for some of the
specification decisions is also included.

The "Mapping between LPD and IPP Protocols" document gives some advice
to implementers of gateways between IPP and LPD (Line Printer Daemon)
implementations.

                      Expires: January 14, 2001

The "Internet Printing Protocol (IPP):  IPP Event Notification
Specification" document defines the semantics for Subscription Creation
Operations and the requirements for other Delivery Method documents to
define a Delivery Method to carry an Event Notifications to a
Notification Recipient.

                      Expires: January 6, 14, 2001
                           Table of Contents

1  Introduction......................................................5  Introduction......................................................7

2  Terminology.......................................................5  Terminology.......................................................7

3  Model and Operation...............................................5 Operation...............................................8

4  Summary of the 'indp' Delivery Method.............................6  General Information...............................................8

5  Subscription object attributes....................................8
 5.1SUBSCRIPTION TEMPLATE ATTRIBUTE CONFORMANCE......................8
 5.2SUBSCRIPTION DESCRIPTION ATTRIBUTE CONFORMANCE...................8 attributes...................................10
 5.1Subscription Template Attribute Conformance.....................10
 5.2Additional Information about Subscription Template Attributes...10
   5.2.1  notify-recipient-uri (uri)................................10
 5.3Subscription Description Attribute Conformance..................11

6  Printer Description Attributes...................................11
 6.1Printer Description Attribute Conformance.........................9

7  New Conformance.......................11
 6.2New Values for Existing Printer Description Attributes............9
 7.1NOTIFY-SCHEMES-SUPPORTED (1SETOF URISCHEME)......................9
 7.2OPERATIONS-SUPPORTED (1SETOF TYPE2 ENUM).........................9
 0X001D..............................................................9

8 Attributes..........11
   6.2.1  notify-schemes-supported (1setOf uriScheme)...............11
   6.2.2  operations-supported (1setOf type2 enum)..................11

7  Attributes Only in Event Notifications............................9

9 Notifications...........................12

8  Operations for Notification.......................................9
 9.1SEND-NOTIFICATIONS OPERATION....................................10
   9.1.1 Notification......................................12
 8.1Send-Notifications operation....................................12
   8.1.1  Send-Notifications Request.................................10
   9.1.2 Request................................13
   8.1.2  Send-Notifications Response................................13
 9.2NOTIFICATION PROTOCOL URI SCHEME................................14

10 Response...............................15

9  Status Codes.....................................................15
 10.1 ADDITIONAL STATUS CODES.......................................15
   10.1.1 Codes.....................................................17
 9.1Additional Status Codes.........................................17
   9.1.1  successful-ok-ignored-notifications (0x0004)..............15
 10.2 STATUS CODES RETURNED IN EVENT NOTIFICATION ATTRIBUTES GROUPS.15
   10.2.1 (0x0004)..............17
 9.2Status Codes returned in Event Notification Attributes Groups...17
   9.2.1  client-error-not-found (0x0406)...........................15
   10.2.2 (0x0406)...........................18
   9.2.2  successful-ok-but-cancel-subscription (0x0006)............16

11 (0x0006)............18

10 Encoding and Transport...........................................16 Transport...........................................18
 10.1 Encoding of the Operation Layer...............................18
 10.2 Encoding of Transport Layer...................................18

11 Conformance Requirements.........................................18
 11.1 ENCODING OF THE OPERATION LAYER...............................16 Printer Conformance Requirements..............................19
 11.2 ENCODING OF TRANSPORT LAYER...................................16 Notification Recipient Requirements...........................19

12 IANA Considerations..............................................16 Considerations..............................................19

13 Internationalization Considerations..............................16 Considerations..............................19

14 Security Considerations..........................................17 Considerations..........................................19

                      Expires: January 14, 2001
 14.1 SECURITY CONFORMANCE..........................................17 Security Conformance..........................................20

15 References.......................................................17 References.......................................................20

16 Author's Addresses...............................................18

                       Expires: January 6, 2001 Addresses...............................................21

17 Full Copyright Statement.........................................18 Statement.........................................21

                                 Tables

Table 1 - Summary of Information about the 'indp' Delivery Method.......................6 Method.......................8

Table 2 . Operation-id assignments....................................9 assignments...................................12

Table 3 . Attributes in Event Notification Content...................11 Content...................13

Table 4 . Additional Attributes in Event Notification Content for Job
   Events............................................................12
   Events...........................................................14

Table 5 . Combinations of Events and Subscribed Events for .job-
   impressions-completed............................................13 "job-
   impressions-completed"...........................................15

Table 6 . Additional Attributes in Event Notification Content for
   Printer Events...................................................13 Events...................................................15

                      Expires: January 6, 14, 2001

1  Introduction

The notification extension document [ipp-ntfy] defines operations that a
client can perform in order to create Subscription Objects in a Printer
and carry out other operations on them. A Subscription Object represents
a Subscription abstraction. The Subscription Object specifies that when
one of the specified Events occurs, the Printer sends an asynchronous
Event Notification to the specified Notification Recipient via the
specified Delivery Method (i.e., protocol).

The notification extension document [ipp-ntfy] specifies that each
Delivery Method is defined in another document. This document is one
such document, and it specifies the .indp. 'indp' Delivery Method.  This
Delivery Method is a simple protocol consisting of a single operation:
the Send-Notifications operation which uses the same encoding and
transport as IPP.  This document defines version '1.0' of the protocol.

For the .indp. 'indp' Delivery Method, an IPP Printer sends (pushes) a Send-
Notifications operation request containing one or more Event
Notifications to  the Notification Recipient specified in the
Subscription Object.  The Event Notification content consists of Machine
Consumable attributes and a Human Consumable "notify-text" attribute.

The Notification Recipient. Recipient receives the Event Notification as a Send-
Notifications operation, in the same way as an IPP Printer receives IPP
operations.  The Notification Recipient returns a response to the
Printer.  The Send-Notifications operation
uses the same Encoding and Transport as IPP itself.

2  Terminology

This document uses section defines the following terms that are used throughout this
document:

  Terms such as "attributes", "keywords", attributes, keywords, and
"support". support.  These terms have
     special meaning and are defined in the model terminology [ipp-mod]
     section 12.2.

  Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
     NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
conformance.  These terms are defined
     conformance as specified in RFC 2119 [RFC2119] and [ipp-mod]
     section 12.1 on 12.1.  These terms refer to conformance terminology, most of which is taken from RFC 2119 [RFC2119].

This to this document,
     if this document uses the capitalized is implemented.

  Capitalized terms, such as Notification Recipient, Event
     Notification, Printer, etc.,  that are defined in [ipp-
ntfy] [ipp-ntfy] with
     the same meanings and are not reproduced here.

This section defines the following additional terms that are used
throughout this document:

  Event Notification Attributes Group . The attributes group in a
     request that contains Event Notification Attributes in a request or
     response.

                      Expires: January 14, 2001

3  Model and Operation

See [ipp-ntfy] for the description of the Event Notification Model and
Operation.  This Delivery Method takes advantage of combining several
Event Notifications into a single Compound Event Notification that is
delivery by a single Send-Notification operation to a single
Notification Recipient.

                       Expires: January 6, 2001

When creating each Subscription object, the client supplies the "notify-
recipient" (uri) Subscription Template attribute.  The "notify-
recipient" attribute specifies both a single Notification Recipient that
is to receive the Notifications when subsequent events occur and the
method for notification delivery that the IPP Printer is to use.  For
the Notification Delivery Method defined in this document, the
notification method is 'indp' and the rest of the URI is the address of
the Notification Recipient to which the IPP Printer will send the Send-
Notifications operation.

The 'indp' Notification Delivery Method defined in this document uses a
client/server protocol paradigm.  The "client" in this relationship is
the Printer described in [ipp-ntfy] while the "server" is the
Notification Recipient. The Printer invokes the Send-Notifications
operation to communicate IPP Event Notification contents to the
Notification Recipient. The Notification Recipient only conveys
information to the Printer in the form of responses to the operations
initiated by the Printer.

Printers that implement the 'indp' Notification Delivery Method will
need to include an HTTP client stack while Notification Recipients that
implement this Delivery Method will need to support an HTTP server
stack.  See section 11.2 10.2 for more details.

4  Summary of the 'indp'  General Information

If a Printer supports this Delivery Method

Column 1 of Method, Table 1 lists the conformance requirements for Delivery
Method Documents as specified in [ipp-ntfy].  Column 2 indicates how
this Delivery Method Document meets each requirement: its
characteristics.

            Table 1 - Summary of Information about the 'indp' Delivery Method

Document Method conformance     'indp' realization
requirement

1.MUST define a

1.What is the URL scheme      indp name   indp
for the Delivery Method.

2.MUST indicate whether Method?

2.Is the     OPTIONAL
delivery method Delivery Method is REQUIRED     RECOMMENDED
REQUIRED, RECOMMENDED, or
OPTIONAL for an IPP Printer to
support if it supports Event
Notification.

3.MUST define the
support?

3.What transport     a complete HTTP stack [rfc2616] and delivery protocol for the
Event Notification content that
a   A Printer MUST use, i.e., the
entire network stack.

4.MUST indicate whether or not  yes, see section 9.1.1
several support a
protocol does the Printer use   complete HTTP/1.1 stack
to deliver the Event Notifications can

                      Expires: January 6, 14, 2001

Document Method conformance     'indp' realization
requirement

Notification content, i.e.,     [rfc2616]
what is the entire network
stack?

4.Can several Event             A Printer implementation MAY
Notifications be combined into  combine several Event
a compound Compound Event Notification.

5.MUST describe how the         initiated by Notification?  Notifications into a single
                                Event Notifications request as
                                separate Event Notification
                                Attributes Groups, see section
                                8.1.1

5.Is the Printer (push) Delivery Method        This Delivery Method is initiated,
i.e., is it a push.
initiated by the
receiving user Notification
Recipient (pull), or is it
initiated by the
Printer
(push).

6.MUST indicate whether (push)?

6.Is the Event Notification     Machine Consumable with the
Delivery Method is
content Machine Consumable or   "notify-text" attribute being
Consumable or
Human Consumable. Consumable?               Human Consumable

7.MUST define the

7.What section in this          The representation and encoding
representation and encoding
document answers the following  is the same as IPP.  See
that
question? For a Printer MUST use for     section 9.1.1
each value or piece of
information listed in [ipp-
ntfy] section 9 (9.1 for Machine Consumable Event
Notification and/or         section 9.2
for Human 8.1.1
Consumable Event
Notification).

8.MUST specify for each         See Notification,
what is the Send-Notifications
attribute in [ipp-ntfy] section Request representation and
encoding of values defined in
section
9 whether a Printer MUST,       9.1.1
SHOULD, MAY, MUST NOT, SHOULD
NOT or NEED NOT send 9.1 of [ipp-ntfy] and
the
attribute in an conformance requirements
thereof? For a Human Consumable
Event
Notification content.

9.MUST define Notification, what frequently   Frequently occurring Events
occurring Events MUST be        NEED NOT be moderated because
moderated, if any, and whether  the Delivery Method is an the moderation mechanism is     efficient one
representation and encoding of
pieces of information defined
in section 9.2 of [ipp-ntfy]
and because the
configurable. Also whether      Printer can group multiple
Events conformance
requirements thereof?

8.What are moderated by sending Event Notifications for the
one per time unit or one per    same Notification Recipient
number of Events.               into a single Send-
                                Notifications operations.

10.  MUST discuss the latency and      Same as for IPP/1.0 or IPP/1.1
and
reliability of the transport    itself (see [ipp-mod]).
transport
and delivery
protocol.

11.  MUST discuss protocol?

9.What are the security         See section 14
aspects of the transport and

                       Expires: January 6, 2001

Document Method conformance     'indp' realization
requirement
delivery protocol, e.g., how it
is handled in firewalls.

12.  MUST identify firewalls?

10.  What are the content       They are the same as for
length restrictions, if any. restrictions?            IPP/1.0 and IPP/1.1 itself (see
                                [ipp-mod]).

13.  MAY define

                      Expires: January 14, 2001

Document Method conformance     'indp' realization
requirement

11.  What are the additional    A new Event Notifications
values or pieces of information attribute group (see section
that a Printer MUST, SHOULD or  11.1) sends in an      10.1) and additional status
MAY send in a
Event Notification and the      codes for use in the response
content.
conformance requirements        (see section 10)

14.  MAY define 9)
thereof?

12.  What are the additional      none defined    None
Subscription Template and/or
Subscription Description
attributes and the conformance
requirements thereof.

15.  MAY define thereof?

13.  What are the additional      none defined    None
Printer Description attributes
and the conformance
requirements thereof. thereof?

The remaining sections of this document parallel the sections of [ipp-
ntfy].

5  Subscription object attributes

This section defines the Subscription object conformance requirements
for Printers.

5.1 Subscription Template Attribute Conformance

The 'indp' Delivery Method has the same conformance requirements for
Subscription Template attributes as defined in [ipp-ntfy].  The 'indp'
Delivery Method does not define any addition Subscription Template
attributes.

5.2 Additional Information about Subscription Template Attributes

This section defines additional information about Subscription Template
attributes defined in [ipp-ntfy].

5.2.1 notify-recipient-uri (uri)

This section describes the syntax of the value of this attribute for the
'indp' Delivery Method. The syntax for values of this attribute for
other Delivery Method is defined in other Delivery Method Documents.

In order to support the 'indp' Delivery Method and Protocol, the Printer
MUST support the following syntax:

                      Expires: January 14, 2001
    The 'indp://' URI scheme.  The remainder of the URI indicates the
    host and address of the Notification Recipient that is to receive
    the Send-Notification operation.

5.3 Subscription Description Attribute Conformance

The 'indp' Delivery Method has the same conformance requirements for
Subscription Description attributes as defined in [ipp-ntfy].  The
'indp' Delivery Method does not define any addition Subscription
Description attributes.

                       Expires: January 6, 2001

6  Printer Description Attributes

This section defines the Printer Description Attributes conformance
requirements for Printers.

6.1 Printer Description Attribute Conformance

The 'indp' Delivery Method has the same conformance requirements for
Printer Description attributes as defined in [ipp-ntfy].  The 'indp'
Delivery Method does not define any addition Printer Description
attributes.

7

6.2 New Values for Existing Printer Description Attributes

This section defines additional values for existing Printer Description
attributes.

7.1

6.2.1 notify-schemes-supported (1setOf uriScheme)

The following .notify-schemes-supported. "notify-schemes-supported" value is added in order to
support the new Delivery Method defined in this document:

  'indp':  - The IPP Notification Delivery Method defined in this
     document.

7.2

6.2.2 operations-supported (1setOf type2 enum)

Table 2 lists the .operation-id. "operation-id" value added in order to support the new
operation defined in this document.  The operation-id is assigned in the
same name space as other operations that a Printer supports.  However, a
Printer MUST NOT include this value in its "operations-supported"
attribute unless it can accept the Send-Notifications request.

                      Expires: January 14, 2001
                   Table 2 . Operation-id assignments

     Value       Operation Name

     0x001D      Send-Notifications

8

7  Attributes Only in Event Notifications

No additional attributes are defined only for use in Event Notifications
besides those defined in [ipp-ntfy].

9

8  Operations for Notification

This section defines the operation for Event Notification using the
'indp' Delivery Method.

There is only one operation defined:  Send-Notifications.  Section 7.2 6.2.2
assigns of the .operation-id. "operation-id" for the Send-Notifications operation and
the following section defined the operation.

                       Expires: January 6, 2001

9.1

8.1 Send-Notifications operation

This REQUIRED operation allows a Printer to send one or more Event
Notifications to a Notification Recipient using HTTP.

The Printer composes the information defined for an IPP Notification
[ipp-ntfy] and sends it using the Sent-Notifications operation to the
Notification Recipient supplied in the Subscription object.

The Send-Notifications operations uses the operations model defined by
IPP [rfc2566].  This includes, the use of a URI as the identifier for
the target of each operation, the inclusion of a version number,
operation-id, and request-id in each request, and the definition of
attribute groups. The Send-Notifications operation uses the Operation
Attributes group, but currently has no need for the Unsupported
Attributes, Printer Object Attributes, and Job-Object Attributes groups.
However, it uses a new attribute group, the Event Notification
Attributes group.

The Notification Recipient MUST accept the request in any state. There
is no state defined for the Notification Recipient for this Delivery
Method.

Access Rights:  To send Event Notifications to a  Notification Recipient,
the authenticated user (see [IPP-MOD] section 8.3) performing this
operation MUST be Recipient MAY enforce access rights.  If
the Printer that accepted receives a previous Subscription
Creation operation (see [ipp-ntfy]).  Otherwise the Notification
Recipient MUST reject the operation and return: the .client-error-
forbidden., .client-error-not-authenticated., rejection with these status codes: 'client-error-
forbidden', 'client-error-not-authenticated', or .client-error-not-
authorized. 'client-error-not-
authorized' status code as appropriate.

ISSUE 01:  Is this what , the Access Rights section should say for a Send-
Notifications request?

9.1.1 Printer SHOULD cancel the subscription.

                      Expires: January 14, 2001

8.1.1 Send-Notifications Request

Every operation request MUST contains the following parameters (see
[ipp-mod] section 3.1.1):

     - a "version-number"    ISSUE 02:  What     '1.0' . the version number goes here? of the 'indp'
       protocol is '1.0'.
     - an "operation-id" - the value defined in Table 2
     - a "request-id" - the contents of the Subscription object's
       "notify-sequence-number" after incrementing for the first try
       (see [ipp-ntfy]).

The following groups of attributes MUST be part of the Send-
Notifications Request:

Group 1: Operation Attributes
     Natural Language and Character Set:

                       Expires: January 6, 2001
          The "attributes-charset" and "attributes-natural-language"
          attributes as defined in [ipp-mod] section 3.1.4.1.

     Target:
          A copy of the Subscription object's "notification-recipient-
          uri" (uri) attribute which is the target of this operation as
          described in [ipp-mod] section 3.1.5, i.e., the URI of the
          'indp' Notification Recipient (see section 9.2).

  Requesting User Name:
     Unlike the other IPP operations, the .requesting-user-name.
     attribute SHOULD NOT be supplied by the client as described in
     [ipp-mod] section 8.3.
          ISSUE 03:  Ok that "requesting-user-name" SHOULD NOT be send
          in Send-Notifications? 5.2.1).

Group 2 to N: Event Notification Attributes

     In each group 2 to N, each attribute is encoded using the IPP rules
     for encoding attributes [ipp-pro] and may be encoded in any order.
     Note: the Get-Jobs response in [ipp-mod] acts as a model for
     encoding multiple groups of attributes.

     Each Event Notification Group MUST contain all of attributes
     specified in [ipp-ntfy] section 9.1 (.Content ("Content of Machine Consumable
     Event Notifications.) Notifications") with exceptions denoted by asterisks in the
     tables below.

     The tables below are copies of the tables in [ipp-ntfy] section 9.1
     (.Content
     ("Content of Machine Consumable Event Notifications.) Notifications") except that
     each cell in the .Sends. "Sends" column is a  .MUST..  "MUST".

     For an Event Notification for all Events, the Printer sends the
     following attributes.

             Table 3 . Attributes in Event Notification Content

                    Source Value                 Sends   Source Object

     notify-subscription-id (integer(1:MAX))     MUST   Subscription

     notify-printer-uri (uri)                    MUST   Subscription

     notify-subscribed-event (type2 keyword)     MUST   Event

                      Expires: January 14, 2001
                    Source Value                 Sends   Source Object

                                                          Notification

     printer-up-time (integer(MIN:MAX))          MUST   Printer

     printer-current-time (dateTime) *           MUST   Printer

     notify-sequence-number (integer (0:MAX))    MUST   Subscription

     notify-charset (charset)                    MUST   Subscription

                       Expires: January 6, 2001
                    Source Value                 Sends   Source Object

     notify-natural-language (naturalLanguage)   MUST   Subscription

     notify-user-data (octetString(63)) **       MUST   Subscription

     notify-text (text) (text (MAX))                    MUST   Event
                                                          Notification

     attributes from the .notify-attributes. "notify-attributes"     MUST   Printer
     attribute ***

     attributes from the .notify-attributes. "notify-attributes"     MUST   Job
     attribute ***

     attributes from the .notify-attributes. "notify-attributes"     MUST   Subscription
     attribute ***

     ISSUE 04: Ok that "notify-text" has been changed from MAY to MUST?

     * The Printer MUST send .printer-current-time. "printer-current-time" if and only if it
     supports the .printer-current-time. "printer-current-time" attribute on the Printer
     object.

     ** If the associated Subscription Object does not contain a
     .notify-user-data.
     "notify-user-data" attribute, the Printer MUST send an octet-string
     of length 0.

     *** If the .notify-attributes. "notify-attributes" attribute is present on the
     Subscription Object, the Printer MUST send all attributes specified
     by the .notify-attributes. "notify-attributes" attribute. Note: if the Printer doesn.t doesn't
     support the .notify-attributes. "notify-attributes" attribute, it is not present on the
     associated Subscription Object.

     For Event Notifications for Job Events, the Printer sends the
     following additional attributes shown in Table 4.

      Table 4 . Additional Attributes in Event Notification Content for
                                 Job Events

                    Source Value                 Sends   Source Object

     job-id (integer(1:MAX))                     MUST   Job

     job-id (integer(1:MAX))                     MUST   Job

                      Expires: January 14, 2001
                    Source Value                 Sends   Source Object

     job-state (type1 enum)                      MUST   Job

     job-state-reasons (1setOf type2 keyword)    MUST   Job

     job-impressions-completed                   MUST   Job
     (integer(0:MAX)) *

                       Expires: January 6, 2001

     *  The Printer MUST send the .job-impressions-completed. "job-impressions-completed" attribute
     in an Event Notification only for the combinations of Events and
     Subscribed Events shown in Table 5.

      Table 5 . Combinations of Events and Subscribed Events for .job-
                           impressions-completed. "job-
                           impressions-completed"

     Job Event                 Subscribed Job Event

     .job-progress.            .job-progress.

     .job-completed.           .job-completed.

     .job-completed.           .job-state-changed.

     'job-progress'            'job-progress'

     'job-completed'           'job-completed'

     'job-completed'           'job-state-changed'

     For Event Notification for Printer Events, the Printer sends the
     following additional attributes shown in Table 6.

      Table 6 . Additional Attributes in Event Notification Content for
                               Printer Events

                    Source Value                 Sends   Source Object

     printer-state (type1 enum)                  MUST   Printer

     printer-state-reasons (1setOf type2         MUST   Printer
     keyword)

     printer-is-accepting-jobs (boolean)         MUST   Printer

9.1.2

8.1.2 Send-Notifications Response

The Notification Recipient MUST return (to the client which is the
Printer) the following sets of attributes as part of a Send-
Notifications response:

Every operation response contains the following REQUIRED parameters (see
[ipp-mod] section 3.1.1}:

                      Expires: January 14, 2001
     - a "version-number"
     - a "status-code"
     - the "request-id" that was supplied in the corresponding request

Group 1: Operation Attributes

  Status Message:
     As defined in [ipp-mod].

                       Expires: January 6, 2001

     The Notification Recipient can return any status codes defined in
     [ipp-mod] and section 10.1 9.1 that applies to all of the Event
     Notification Attribute groups. The following is a description of
     the important status codes:

       'successful-ok': the Notification Recipient received all of the
          Event Notification Attribute Groups and was expecting each of
          them.
       'successful-ok-ignored-notifications': the Notification
          Recipient was able to consume some, but not all of the Event
          Notification Attributes Groups sent. The Event Notification
          Attributes Groups with a .notify-status-code. "notify-status-code" attribute are
          the ones that were ignored or are to be canceled.
       'client-error-ignored-all-notifications': the Notification
          Recipient was unable to consume any of the Event Notification
          Attributes Groups sent. The Event Notification Attributes
          Groups with a .notify-status-code. "notify-status-code" attribute are the ones that
          were ignored or are to be canceled.

  Natural Language and Character Set:
     The "attributes-charset" and "attributes-natural-language"
     attributes as defined in [ipp-mod] section 3.1.4.1.

Group 2 to N: Notification Attributes

  These groups MUST be returned if and only if the "status-code"
  parameter returned in Group 1 is anything but the 'successful-ok'
  status code.

  "notification-status-code" (type2 enum)
     Indicates whether the Notification Recipient was able to consume
     the n-th Notification Report as follows:

                      Expires: January 14, 2001
     'successful-ok' - this Event Notification Attribute Group was
       consumed
     'client-error-not-found' - this Event Notification Attribute Group
       was not able to be consumed.  The Printer MUST cancel the
       Subscription and MUST NOT attempt to send any further Event
       Notifications from the associated Subscription object.
     'successful-ok-but-cancel-subscription' - the Event Notification
       Attribute Group was consumed, but the Notification Recipient
       wishes to cancel the Subscription object.  The Printer MUST
       cancel the Subscription and MUST NOT attempt to send any further
       Event Notifications from the associated Subscription object.

9.2  Notification Protocol URI Scheme

The INDP Notification Delivery Method uses the 'indp://' URI scheme in
the "notify-recipients" attribute in the Subscription object in order to
indicate the notification Delivery Method defined in this document.  The
remainder of the URI indicates the host and address of the Notification
Recipient that is to receive the Send-Notification operation.

                       Expires: January 6, 2001

10

9  Status Codes

This section lists status codes whose meaning have been extended and/or
defined for returning in Event Notification Attribute Groups as the
value of the "notification-status-code" operation attribute.  The code
values are allocated in the same space as the status codes in [ipp-mod].

10.1

9.1 Additional Status Codes

The following status codes are defined as extensions for Notification
and are returned as the value of the .status-code. "status-code" parameter in the
Operation Attributes Group of a response (see [ipp-mod] section
3.1.6.1). Operations in this document can also return the status codes
defined in section 13 of [ipp-mod]. The .successful-ok. 'successful-ok' status code is
an example of such a status code.

10.1.1

9.1.1 successful-ok-ignored-notifications (0x0004)

The Notification Recipient was able to consume some, but not all, of the
Event Notifications Attributes Groups sent by the Printer in the Send-
Notifications request.  See section 9.1.2 8.1.2 for further details.

10.2

9.2 Status Codes returned in Event Notification Attributes Groups

This section contains values of the .notify-status-code. "notify-status-code" attribute that
the Notification Recipient returns in a Event Notification Attributes
Group in a response when the corresponding Event Notification Attributes
Group in the request:

  1. was not consumed OR

  2. was consumed, but the Notification Recipient wants to cancel the
     corresponding Subscription object

The following sections are ordered in decreasing order of importance of
the status-codes.

10.2.1

                      Expires: January 14, 2001

9.2.1 client-error-not-found (0x0406)

This status code is defined in [ipp-mod]. This document extends its
meaning and allows it to be returned in an Event Notification Attributes
Group of a response.

The Notification Recipient was unable to consume this Event Notification
Attributes Group because it was not expected.  See section 9.1.2 8.1.2 for
further details.

                       Expires: January 6, 2001

10.2.2

9.2.2 successful-ok-but-cancel-subscription (0x0006)

The Notification Recipient was able to consume this Event Notification
Attributes Group that the Printer sent, but wants the corresponding
Subscription object to be canceled none-the-less.  See section 9.1.2 8.1.2 for
further details.

11

10 Encoding and Transport

This section defines the encoding and transport used by the 'indp'
Delivery Method.

11.1

10.1 Encoding of the Operation Layer

The 'indp' Delivery Method uses the IPP operation layer encoding
described in [ipp-pro] and the following Event Notification Attributes
Group tag allocated by [ipp-ntfy]:

   Tag Value (Hex)   Meaning

   0x07              .event-notification-attributes-tag.

11.2              "event-notification-attributes-tag"

10.2 Encoding of Transport Layer

The 'indp' Notification Delivery Method uses the IPP transport layer
encoding described in [ipp-pro].

It is REQUIRED that an 'indp' Notification Recipient implementation
support HTTP over the IANA assigned Well Known Port assigned to the
'indp' Delivery Method as its default port by IANA (see section 12),
though a Notification Recipient implementation MAY support HTTP over
some other port as well.

11 Conformance Requirements

This section defines conformance requirements for Printers and
Notification Recipients.

                      Expires: January 14, 2001

11.1 Printer Conformance Requirements

The 'indp' Delivery Method is RECOMMENDED for a Printer to support.

If the Printer supports the 'indp' Delivery Method, the Printer MUST:

1.meet the conformance requirements defined in [ipp-ntfy].

2.support the conformance requirements for Subscription object
  attributes defined in section 5, including the syntax for the
  "notify-recipient-uri" Subscription Object attribute defined in
  section 5.2.1.

3.support the conformance requirements for Printer Description object
  attributes defined in section 6.

4.support the 'indp' protocol by sending Event Notifications using the
  Send-Notifications operation defined in section 8.1.

5.support sending Event Notification via email with the content
  specified in section 8.1.1.

11.2 Notification Recipient Requirements

A Notification Recipient MUST accept Send-Notifications requests and
return Send-Notifications responses as defined in sections 8 and 9.

12 IANA Considerations

The 'indp://' 'indp' URL scheme for the 'indp' Delivery Method and Protocol will
be registered with IANA.  IANA will assign a default port to use with
the 'indp' Delivery Method. Method and Protocol.

13 Internationalization Considerations

When the client requests Human Consumable form by supplying the "notify-
text-format" operation attribute (see [ipp-ntfy]), the IPP Printer (or
any Notification Service that the IPP Printer might be configured to
use) supplies and localizes the text value of the "human-readable-
report" attribute in the Notification according to the charset and
natural language requested in the notification subscription.

                       Expires: January 6, 2001

14 Security Considerations

The IPP Model and Semantics document [ipp-mod] discusses high level
security requirements (Client Authentication, Server Authentication and
Operation Privacy). Client Authentication is the mechanism by which the
client proves its identity to the server in a secure manner. Server
Authentication is the mechanism by which the server proves its identity

                      Expires: January 14, 2001

to the client in a secure manner. Operation Privacy is defined as a
mechanism for protecting operations from eavesdropping.

The Notification Recipient can cancel unwanted Subscriptions created by
other parties without having to be the owner of the subscription by
returning the 'successful-ok-but-cancel-subscription' status code in the
Send-Notifications response returned to the Printer.

14.1 Security Conformance

Printers (client) MAY support Digest Authentication [rfc2617].  If
Digest Authentication is supported, then MD5 and MD5-sess MUST be
supported, but the Message Integrity feature NEED NOT be supported.

Notification Recipient (server) MAY support Digest Authentication
[rfc2617].  If Digest Authentication is supported, then MD5 and MD5-sess
MUST be supported, but the Message Integrity feature NEED NOT be
supported.

Notification Recipients MAY support TLS for client authentication,
server authentication and operation privacy. If a Notification Recipient
supports TLS, it MUST support the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
cipher suite as mandated by RFC 2246 [rfc2246]. All other cipher suites
are OPTIONAL. Notification recipients MAY support Basic Authentication
(described in HTTP/1.1 [rfc2616]) for client authentication if the
channel is secure. TLS with the above mandated cipher suite can provide
such a secure channel.

15 References

[indp]
     Parra, H., T. Hastings,  "Internet Printing Protocol (IPP): IPP
     Notification Delivery Protocol (INDP)", <draft-ietf-indp-00.txt>,
     February 29, 2000.

[ipp-mod]
     R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
     "Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf-
     ipp-model-v11-07.txt>, May 22, 2000.

[ipp-ntfy]
     Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,
     Bergman, R., "Internet Printing Protocol/1.1: IPP Event
     Notification Specification", <draft-ietf-ipp-not-spec-03.txt>, June
     30, <draft-ietf-ipp-not-spec-04.txt>, July
     13, 2000.

                       Expires: January 6, 2001

[ipp-pro]
     Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
     Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
     06.txt, May 30, 2000.

[rfc2026]
     S. Bradner, "The Internet Standards Process -- Revision 3", RFC
     2026, October 1996.

                      Expires: January 14, 2001

[rfc2616]
     R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
     Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
     RFC 2616, June 1999.

[rfc2617]
     J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A.
     Luotonen, L. Stewart, "HTTP Authentication: Basic and Digest Access
     Authentication", RFC 2617, June 1999.

16 Author's Addresses

     Hugo Parra
     Novell, Inc.
     1800 South Novell Place
     Provo, UT   84606

     Phone: 801-861-3307
     Fax:   801-861-2517
     e-mail: hparra@novell.com

     Tom Hastings
     Xerox Corporation
     737 Hawaii St.  ESAE 231
     El Segundo, CA   90245

     Phone: 310-333-6413
     Fax:   310-333-5514
     e-mail: hastings@cp10.es.xerox.com

17 Full Copyright Statement

Copyright (C) The Internet Society (2000). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works.  However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the  purpose of developing Internet standards in

                       Expires: January 6, 2001
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK

                      Expires: January 14, 2001

FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.

                      Expires: January 6, 14, 2001