draft-ietf-ipp-indp-method-01.txt   draft-ietf-ipp-indp-method-02.txt 
INTERNET-DRAFT There are 4 issues INTERNET-DRAFT
<draft-ietf-ipp-indp-method-01.txt> <draft-ietf-ipp-indp-method-02.txt>
Hugo Parra Hugo Parra
Novell, Inc. Novell, Inc.
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
July 6, 2000 July 14, 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'indp' Notification Delivery Method The 'indp' Notification Delivery Method and Protocol/1.0
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of [rfc2026]. Internet-Drafts are working provisions of Section 10 of [rfc2026]. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
or to cite them other than as "work in progress". or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed as The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
The IPP Event Notification specification [ipp-ntfy] is an OPTIONAL The IPP notification extension document [ipp-ntfy] defines operations
extension to IPP/1.0, IPP/1.1, and future versions. [ipp-ntfy] requires that a client can perform in order to create Subscription Objects in a
the definition of one or more Delivery Methods in separate Delivery Printer and carry out other operations on them. The Subscription Object
Method Documents for the Printer to dispatch Event Notifications to specifies that when one of the specified Events occurs, the Printer
Notification Recipients. This Delivery Method Document defines the sends an asynchronous Event Notification to the specified Notification
semantics and syntax of the 'indp' Notification Delivery Method. For Recipient via the specified Delivery Method (i.e., protocol).
this Delivery Method, an IPP Printer sends (pushes) an IPP Event
Notifications request to the Notification Recipients using the Send-
Notifications operation defined in this document. 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, 2001 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 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 this Delivery Method, when an Event occurs, the Printer immediately
sends (pushes) an Event Notification via the Send-Notifications
operation to the Notification Recipient specified in 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.
Expires: January 14, 2001
The full set of IPP documents includes: The full set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567] Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568] Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [ipp-mod] 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: Encoding and Transport [ipp-pro]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
Mapping between LPD and IPP Protocols [RFC2569] Mapping between LPD and IPP Protocols [RFC2569]
skipping to change at page 2, line 34 skipping to change at page 3, line 34
administrators. It calls out a subset of end user requirements that are administrators. It calls out a subset of end user requirements that are
satisfied in IPP/1.0. A few OPTIONAL operator operations have been satisfied in IPP/1.0. A few OPTIONAL operator operations have been
added to IPP/1.1. added to IPP/1.1.
The "Rationale for the Structure and Model and Protocol for the Internet The "Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol" document describes IPP from a high level view, Printing Protocol" document describes IPP from a high level view,
defines a roadmap for the various documents that form the suite of IPP defines a roadmap for the various documents that form the suite of IPP
specification documents, and gives background and rationale for the IETF specification documents, and gives background and rationale for the IETF
working group's major decisions. 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 The "Internet Printing Protocol/1.1: Encoding and Transport" document is
a formal mapping of the abstract operations and attributes defined in a formal mapping of the abstract operations and attributes defined in
the model document onto HTTP/1.1 [RFC2616]. It defines the encoding the model document onto HTTP/1.1 [RFC2616]. It defines the encoding
rules for a new Internet MIME media type called "application/ipp". This rules for a new Internet MIME media type called "application/ipp". This
document also defines the rules for transporting a message body over document also defines the rules for transporting a message body over
HTTP whose Content-Type is "application/ipp". This document defines a HTTP whose Content-Type is "application/ipp". This document defines a
new scheme named 'ipp' for identifying IPP printers and jobs. new scheme named 'ipp' for identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document gives The "Internet Printing Protocol/1.1: Implementer's Guide" document gives
insight and advice to implementers of IPP clients and IPP objects. It 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 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 considerations that may assist them in the design of their client and/or
IPP object implementations. For example, a typical order of processing IPP object implementations. For example, a typical order of processing
requests is given, including error checking. Motivation for some of the requests is given, including error checking. Motivation for some of the
specification decisions is also included. specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some advice The "Mapping between LPD and IPP Protocols" document gives some advice
to implementers of gateways between IPP and LPD (Line Printer Daemon) to implementers of gateways between IPP and LPD (Line Printer Daemon)
implementations. implementations.
Expires: January 14, 2001
The "Internet Printing Protocol (IPP): IPP Event Notification The "Internet Printing Protocol (IPP): IPP Event Notification
Specification" document defines the semantics for Subscription Creation Specification" document defines the semantics for Subscription Creation
Operations and the requirements for other Delivery Method documents to Operations and the requirements for other Delivery Method documents to
define a Delivery Method to carry an Event Notifications to a define a Delivery Method to carry an Event Notifications to a
Notification Recipient. Notification Recipient.
Expires: January 6, 2001 Expires: January 14, 2001
Table of Contents Table of Contents
1 Introduction......................................................5 1 Introduction......................................................7
2 Terminology.......................................................5 2 Terminology.......................................................7
3 Model and Operation...............................................5 3 Model and Operation...............................................8
4 Summary of the 'indp' Delivery Method.............................6 4 General Information...............................................8
5 Subscription object attributes....................................8 5 Subscription object attributes...................................10
5.1SUBSCRIPTION TEMPLATE ATTRIBUTE CONFORMANCE......................8 5.1Subscription Template Attribute Conformance.....................10
5.2SUBSCRIPTION DESCRIPTION ATTRIBUTE CONFORMANCE...................8 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 Attribute Conformance.........................9 6 Printer Description Attributes...................................11
6.1Printer Description Attribute Conformance.......................11
6.2New Values for Existing Printer Description Attributes..........11
6.2.1 notify-schemes-supported (1setOf uriScheme)...............11
6.2.2 operations-supported (1setOf type2 enum)..................11
7 New Values for Existing Printer Description Attributes............9 7 Attributes Only in Event Notifications...........................12
7.1NOTIFY-SCHEMES-SUPPORTED (1SETOF URISCHEME)......................9
7.2OPERATIONS-SUPPORTED (1SETOF TYPE2 ENUM).........................9
0X001D..............................................................9
8 Attributes Only in Event Notifications............................9 8 Operations for Notification......................................12
8.1Send-Notifications operation....................................12
8.1.1 Send-Notifications Request................................13
8.1.2 Send-Notifications Response...............................15
9 Operations for Notification.......................................9 9 Status Codes.....................................................17
9.1SEND-NOTIFICATIONS OPERATION....................................10 9.1Additional Status Codes.........................................17
9.1.1 Send-Notifications Request.................................10 9.1.1 successful-ok-ignored-notifications (0x0004)..............17
9.1.2 Send-Notifications Response................................13 9.2Status Codes returned in Event Notification Attributes Groups...17
9.2NOTIFICATION PROTOCOL URI SCHEME................................14 9.2.1 client-error-not-found (0x0406)...........................18
9.2.2 successful-ok-but-cancel-subscription (0x0006)............18
10 Status Codes.....................................................15 10 Encoding and Transport...........................................18
10.1 ADDITIONAL STATUS CODES.......................................15 10.1 Encoding of the Operation Layer...............................18
10.1.1 successful-ok-ignored-notifications (0x0004)..............15 10.2 Encoding of Transport Layer...................................18
10.2 STATUS CODES RETURNED IN EVENT NOTIFICATION ATTRIBUTES GROUPS.15
10.2.1 client-error-not-found (0x0406)...........................15
10.2.2 successful-ok-but-cancel-subscription (0x0006)............16
11 Encoding and Transport...........................................16 11 Conformance Requirements.........................................18
11.1 ENCODING OF THE OPERATION LAYER...............................16 11.1 Printer Conformance Requirements..............................19
11.2 ENCODING OF TRANSPORT LAYER...................................16 11.2 Notification Recipient Requirements...........................19
12 IANA Considerations..............................................16 12 IANA Considerations..............................................19
13 Internationalization Considerations..............................16 13 Internationalization Considerations..............................19
14 Security Considerations..........................................17 14 Security Considerations..........................................19
14.1 SECURITY CONFORMANCE..........................................17
15 References.......................................................17 Expires: January 14, 2001
14.1 Security Conformance..........................................20
16 Author's Addresses...............................................18 15 References.......................................................20
Expires: January 6, 2001 16 Author's Addresses...............................................21
17 Full Copyright Statement.........................................18 17 Full Copyright Statement.........................................21
Tables Tables
Table 1 - Summary of the 'indp' Delivery Method.......................6 Table 1 - Information about the Delivery Method.......................8
Table 2 . Operation-id assignments....................................9 Table 2 . Operation-id assignments...................................12
Table 3 . Attributes in Event Notification Content...................11 Table 3 . Attributes in Event Notification Content...................13
Table 4 . Additional Attributes in Event Notification Content for Job Table 4 . Additional Attributes in Event Notification Content for Job
Events............................................................12 Events...........................................................14
Table 5 . Combinations of Events and Subscribed Events for .job- Table 5 . Combinations of Events and Subscribed Events for "job-
impressions-completed............................................13 impressions-completed"...........................................15
Table 6 . Additional Attributes in Event Notification Content for Table 6 . Additional Attributes in Event Notification Content for
Printer Events...................................................13 Printer Events...................................................15
Expires: January 6, 2001 Expires: January 14, 2001
1 Introduction 1 Introduction
The notification extension document [ipp-ntfy] defines operations that a The notification extension document [ipp-ntfy] defines operations that a
client can perform in order to create Subscription Objects in a Printer client can perform in order to create Subscription Objects in a Printer
and carry out other operations on them. A Subscription Object represents and carry out other operations on them. A Subscription Object represents
a Subscription abstraction. The Subscription Object specifies that when a Subscription abstraction. The Subscription Object specifies that when
one of the specified Events occurs, the Printer sends an asynchronous one of the specified Events occurs, the Printer sends an asynchronous
Event Notification to the specified Notification Recipient via the Event Notification to the specified Notification Recipient via the
specified Delivery Method (i.e., protocol). specified Delivery Method (i.e., protocol).
The notification extension document [ipp-ntfy] specifies that each The notification extension document [ipp-ntfy] specifies that each
Delivery Method is defined in another document. This document is one Delivery Method is defined in another document. This document is one
such document, and it specifies the .indp. Delivery Method. such document, and it specifies the '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. Delivery Method, an IPP Printer sends (pushes) a Send- For the 'indp' Delivery Method, an IPP Printer sends (pushes) a Send-
Notifications operation request containing one or more Event Notifications operation request containing one or more Event
Notifications to a Notification Recipient. The Notification Recipient Notifications to the Notification Recipient specified in the
returns a response to the Printer. The Send-Notifications operation Subscription Object. The Event Notification content consists of Machine
uses the same Encoding and Transport as IPP itself. Consumable attributes and a Human Consumable "notify-text" attribute.
The Notification 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.
2 Terminology 2 Terminology
This document uses terms such as "attributes", "keywords", and This section defines the following terms that are used throughout this
"support". These terms have special meaning and are defined in the document:
model terminology [ipp-mod] section 12.2.
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, Terms such as attributes, keywords, and support. These terms have
MAY, NEED NOT, and OPTIONAL, have special meaning relating to special meaning and are defined in the model terminology [ipp-mod]
conformance. These terms are defined in [ipp-mod] section 12.1 on section 12.2.
conformance terminology, most of which is taken from RFC 2119 [RFC2119].
This document uses the capitalized terms, such as Notification Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
Recipient, Event Notification, Printer, etc., that are defined in [ipp- NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
ntfy] with the same meanings and are not reproduced here. conformance as specified in RFC 2119 [RFC2119] and [ipp-mod]
section 12.1. These terms refer to conformance to this document,
if this document is implemented.
This section defines the following additional terms that are used Capitalized terms, such as Notification Recipient, Event
throughout this document: Notification, Printer, etc., that are defined in [ipp-ntfy] with
the same meanings and are not reproduced here.
Event Notification Attributes Group . The attributes group in a Event Notification Attributes Group . The attributes group in a
request that contains Event Notification Attributes in a request or request that contains Event Notification Attributes in a request or
response. response.
Expires: January 14, 2001
3 Model and Operation 3 Model and Operation
See [ipp-ntfy] for the description of the Event Notification Model and See [ipp-ntfy] for the description of the Event Notification Model and
Operation. This Delivery Method takes advantage of combining several Operation. This Delivery Method takes advantage of combining several
Event Notifications into a single Compound Event Notification that is Event Notifications into a single Compound Event Notification that is
delivery by a single Send-Notification operation to a single delivery by a single Send-Notification operation to a single
Notification Recipient. Notification Recipient.
Expires: January 6, 2001
When creating each Subscription object, the client supplies the "notify- When creating each Subscription object, the client supplies the "notify-
recipient" (uri) Subscription Template attribute. The "notify- recipient" (uri) Subscription Template attribute. The "notify-
recipient" attribute specifies both a single Notification Recipient that recipient" attribute specifies both a single Notification Recipient that
is to receive the Notifications when subsequent events occur and the is to receive the Notifications when subsequent events occur and the
method for notification delivery that the IPP Printer is to use. For method for notification delivery that the IPP Printer is to use. For
the Notification Delivery Method defined in this document, the the Notification Delivery Method defined in this document, the
notification method is 'indp' and the rest of the URI is the address of 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- the Notification Recipient to which the IPP Printer will send the Send-
Notifications operation. Notifications operation.
skipping to change at page 6, line 29 skipping to change at page 8, line 37
the Printer described in [ipp-ntfy] while the "server" is the the Printer described in [ipp-ntfy] while the "server" is the
Notification Recipient. The Printer invokes the Send-Notifications Notification Recipient. The Printer invokes the Send-Notifications
operation to communicate IPP Event Notification contents to the operation to communicate IPP Event Notification contents to the
Notification Recipient. The Notification Recipient only conveys Notification Recipient. The Notification Recipient only conveys
information to the Printer in the form of responses to the operations information to the Printer in the form of responses to the operations
initiated by the Printer. initiated by the Printer.
Printers that implement the 'indp' Notification Delivery Method will Printers that implement the 'indp' Notification Delivery Method will
need to include an HTTP client stack while Notification Recipients that need to include an HTTP client stack while Notification Recipients that
implement this Delivery Method will need to support an HTTP server implement this Delivery Method will need to support an HTTP server
stack. See section 11.2 for more details. stack. See section 10.2 for more details.
4 Summary of the 'indp' Delivery Method 4 General Information
Column 1 of Table 1 lists the conformance requirements for Delivery If a Printer supports this Delivery Method, Table 1 lists its
Method Documents as specified in [ipp-ntfy]. Column 2 indicates how characteristics.
this Delivery Method Document meets each requirement:
Table 1 - Summary of the 'indp' Delivery Method Table 1 - Information about the Delivery Method
Document Method conformance 'indp' realization Document Method conformance 'indp' realization
requirement requirement
1.MUST define a URL scheme indp 1.What is the URL scheme name indp
name for the Delivery Method. for the Delivery Method?
2.MUST indicate whether the OPTIONAL 2.Is the Delivery Method is RECOMMENDED
delivery method is REQUIRED or REQUIRED, RECOMMENDED, or
OPTIONAL for an IPP Printer to OPTIONAL for an IPP Printer to
support if it supports Event support?
Notification.
3.MUST define the transport a complete HTTP stack [rfc2616]
and delivery protocol for the
Event Notification content that
a Printer MUST use, i.e., the
entire network stack.
4.MUST indicate whether or not yes, see section 9.1.1 3.What transport and delivery A Printer MUST support a
several Event Notifications can protocol does the Printer use complete HTTP/1.1 stack
to deliver the Event
Expires: January 6, 2001 Expires: January 14, 2001
Document Method conformance 'indp' realization Document Method conformance 'indp' realization
requirement requirement
be combined into a compound Notification content, i.e., [rfc2616]
Event Notification. what is the entire network
stack?
5.MUST describe how the initiated by the Printer (push)
Delivery Method is initiated,
i.e., is it initiated by the
receiving user (pull), or is it
initiated by the Printer
(push).
6.MUST indicate whether the Machine Consumable with the 4.Can several Event A Printer implementation MAY
Delivery Method is Machine "notify-text" attribute being Notifications be combined into combine several Event
Consumable or Human Consumable. Human Consumable a Compound Event Notification? Notifications into a single
Event Notifications request as
separate Event Notification
Attributes Groups, see section
8.1.1
7.MUST define the The representation and encoding 5.Is the Delivery Method This Delivery Method is a push.
representation and encoding is the same as IPP. See initiated by the Notification
that a Printer MUST use for section 9.1.1 Recipient (pull), or by the
each value or piece of Printer (push)?
information listed in [ipp-
ntfy] section 9 (9.1 for
Machine Consumable Event
Notification and/or section 9.2
for Human Consumable Event
Notification).
8.MUST specify for each See the Send-Notifications 6.Is the Event Notification Machine Consumable with the
attribute in [ipp-ntfy] section Request defined in section content Machine Consumable or "notify-text" attribute being
9 whether a Printer MUST, 9.1.1 Human Consumable? Human Consumable
SHOULD, MAY, MUST NOT, SHOULD
NOT or NEED NOT send the
attribute in an Event
Notification content.
9.MUST define what frequently Frequently occurring Events 7.What section in this The representation and encoding
occurring Events MUST be NEED NOT be moderated because document answers the following is the same as IPP. See
moderated, if any, and whether the Delivery Method is an question? For a Machine section 8.1.1
the moderation mechanism is efficient one and because the Consumable Event Notification,
configurable. Also whether Printer can group multiple what is the representation and
Events are moderated by sending Event Notifications for the encoding of values defined in
one per time unit or one per same Notification Recipient section 9.1 of [ipp-ntfy] and
number of Events. into a single Send- the conformance requirements
Notifications operations. thereof? For a Human Consumable
Event Notification, what is the
representation and encoding of
pieces of information defined
in section 9.2 of [ipp-ntfy]
and the conformance
requirements thereof?
10. MUST discuss the latency Same as for IPP/1.0 or IPP/1.1 8.What are the latency and Same as for IPP/1.0 or IPP/1.1
and reliability of the itself (see [ipp-mod]). reliability of the transport itself (see [ipp-mod]).
transport and delivery and delivery protocol?
protocol.
11. MUST discuss the security See section 14 9.What are the security See section 14
aspects of the transport and aspects of the transport and
delivery protocol, e.g., how it
is handled in firewalls?
Expires: January 6, 2001 10. What are the content They are the same as for
length restrictions? IPP/1.0 and IPP/1.1 itself (see
[ipp-mod]).
Expires: January 14, 2001
Document Method conformance 'indp' realization Document Method conformance 'indp' realization
requirement requirement
delivery protocol, e.g., how it 11. What are the additional A new Event Notifications
is handled in firewalls.
12. MUST identify content They are the same as for
length restrictions, if any. IPP/1.0 and IPP/1.1 itself (see
[ipp-mod]).
13. MAY define additional A new Event Notifications
values or pieces of information attribute group (see section values or pieces of information attribute group (see section
that a Printer MUST, SHOULD or 11.1) and additional status that a Printer sends in an 10.1) and additional status
MAY send in a Notification codes for use in the response Event Notification and the codes for use in the response
content. (see section 10) conformance requirements (see section 9)
thereof?
14. MAY define additional none defined 12. What are the additional None
Subscription Template and/or Subscription Template and/or
Subscription Description Subscription Description
attributes and the conformance attributes and the conformance
requirements thereof. requirements thereof?
15. MAY define additional none defined 13. What are the additional None
Printer Description attributes Printer Description attributes
and the conformance and the conformance
requirements thereof. requirements thereof?
The remaining sections of this document parallel the sections of [ipp- The remaining sections of this document parallel the sections of [ipp-
ntfy]. ntfy].
5 Subscription object attributes 5 Subscription object attributes
This section defines the Subscription object conformance requirements This section defines the Subscription object conformance requirements
for Printers. for Printers.
5.1 Subscription Template Attribute Conformance 5.1 Subscription Template Attribute Conformance
The 'indp' Delivery Method has the same conformance requirements for The 'indp' Delivery Method has the same conformance requirements for
Subscription Template attributes as defined in [ipp-ntfy]. The 'indp' Subscription Template attributes as defined in [ipp-ntfy]. The 'indp'
Delivery Method does not define any addition Subscription Template Delivery Method does not define any addition Subscription Template
attributes. attributes.
5.2 Subscription Description Attribute Conformance 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 The 'indp' Delivery Method has the same conformance requirements for
Subscription Description attributes as defined in [ipp-ntfy]. The Subscription Description attributes as defined in [ipp-ntfy]. The
'indp' Delivery Method does not define any addition Subscription 'indp' Delivery Method does not define any addition Subscription
Description attributes. Description attributes.
Expires: January 6, 2001 6 Printer Description Attributes
6 Printer Description Attribute Conformance 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 The 'indp' Delivery Method has the same conformance requirements for
Printer Description attributes as defined in [ipp-ntfy]. The 'indp' Printer Description attributes as defined in [ipp-ntfy]. The 'indp'
Delivery Method does not define any addition Printer Description Delivery Method does not define any addition Printer Description
attributes. attributes.
7 New Values for Existing Printer Description Attributes 6.2 New Values for Existing Printer Description Attributes
This section defines additional values for existing Printer Description This section defines additional values for existing Printer Description
attributes. attributes.
7.1 notify-schemes-supported (1setOf uriScheme) 6.2.1 notify-schemes-supported (1setOf uriScheme)
The following .notify-schemes-supported. value is added in order to The following "notify-schemes-supported" value is added in order to
support the new Delivery Method defined in this document: support the new Delivery Method defined in this document:
'indp': - The IPP Notification Delivery Method defined in this 'indp': - The IPP Notification Delivery Method defined in this
document. document.
7.2 operations-supported (1setOf type2 enum) 6.2.2 operations-supported (1setOf type2 enum)
Table 2 lists the .operation-id. value added in order to support the new Table 2 lists the "operation-id" value added in order to support the new
operation defined in this document. The operation-id is assigned in the operation defined in this document. The operation-id is assigned in the
same name space as other operations that a Printer supports. However, a same name space as other operations that a Printer supports. However, a
Printer MUST NOT include this value in its "operations-supported" Printer MUST NOT include this value in its "operations-supported"
attribute unless it can accept the Send-Notifications request. attribute unless it can accept the Send-Notifications request.
Expires: January 14, 2001
Table 2 . Operation-id assignments Table 2 . Operation-id assignments
Value Operation Name Value Operation Name
0x001D Send-Notifications 0x001D Send-Notifications
8 Attributes Only in Event Notifications 7 Attributes Only in Event Notifications
No additional attributes are defined only for use in Event Notifications No additional attributes are defined only for use in Event Notifications
besides those defined in [ipp-ntfy]. besides those defined in [ipp-ntfy].
9 Operations for Notification 8 Operations for Notification
This section defines the operation for Event Notification using the This section defines the operation for Event Notification using the
'indp' Delivery Method. 'indp' Delivery Method.
There is only one operation defined: Send-Notifications. Section 7.2 There is only one operation defined: Send-Notifications. Section 6.2.2
assigns of the .operation-id. for the Send-Notifications operation and assigns of the "operation-id" for the Send-Notifications operation and
the following section defined the operation. the following section defined the operation.
Expires: January 6, 2001 8.1 Send-Notifications operation
9.1 Send-Notifications operation
This REQUIRED operation allows a Printer to send one or more Event This REQUIRED operation allows a Printer to send one or more Event
Notifications to a Notification Recipient using HTTP. Notifications to a Notification Recipient using HTTP.
The Printer composes the information defined for an IPP Notification The Printer composes the information defined for an IPP Notification
[ipp-ntfy] and sends it using the Sent-Notifications operation to the [ipp-ntfy] and sends it using the Sent-Notifications operation to the
Notification Recipient supplied in the Subscription object. Notification Recipient supplied in the Subscription object.
The Send-Notifications operations uses the operations model defined by The Send-Notifications operations uses the operations model defined by
IPP [rfc2566]. This includes, the use of a URI as the identifier for IPP [rfc2566]. This includes, the use of a URI as the identifier for
skipping to change at page 10, line 30 skipping to change at page 12, line 49
attribute groups. The Send-Notifications operation uses the Operation attribute groups. The Send-Notifications operation uses the Operation
Attributes group, but currently has no need for the Unsupported Attributes group, but currently has no need for the Unsupported
Attributes, Printer Object Attributes, and Job-Object Attributes groups. Attributes, Printer Object Attributes, and Job-Object Attributes groups.
However, it uses a new attribute group, the Event Notification However, it uses a new attribute group, the Event Notification
Attributes group. Attributes group.
The Notification Recipient MUST accept the request in any state. There The Notification Recipient MUST accept the request in any state. There
is no state defined for the Notification Recipient for this Delivery is no state defined for the Notification Recipient for this Delivery
Method. Method.
Access Rights: To send Event Notifications to a Notification Recipient, Access Rights: Notification Recipient MAY enforce access rights. If
the authenticated user (see [IPP-MOD] section 8.3) performing this the Printer receives a rejection with these status codes: 'client-error-
operation MUST be the Printer that accepted a previous Subscription forbidden', 'client-error-not-authenticated', or 'client-error-not-
Creation operation (see [ipp-ntfy]). Otherwise the Notification authorized' status code , the Printer SHOULD cancel the subscription.
Recipient MUST reject the operation and return: the .client-error-
forbidden., .client-error-not-authenticated., or .client-error-not-
authorized. status code as appropriate.
ISSUE 01: Is this what the Access Rights section should say for a Send- Expires: January 14, 2001
Notifications request?
9.1.1 Send-Notifications Request 8.1.1 Send-Notifications Request
Every operation request MUST contains the following parameters (see Every operation request MUST contains the following parameters (see
[ipp-mod] section 3.1.1): [ipp-mod] section 3.1.1):
- a "version-number" ISSUE 02: What version number goes here? - a "version-number" '1.0' . the version of the 'indp'
protocol is '1.0'.
- an "operation-id" - the value defined in Table 2 - an "operation-id" - the value defined in Table 2
- a "request-id" - the contents of the Subscription object's - a "request-id" - the contents of the Subscription object's
"notify-sequence-number" after incrementing for the first try "notify-sequence-number" after incrementing for the first try
(see [ipp-ntfy]). (see [ipp-ntfy]).
The following groups of attributes MUST be part of the Send- The following groups of attributes MUST be part of the Send-
Notifications Request: Notifications Request:
Group 1: Operation Attributes Group 1: Operation Attributes
Natural Language and Character Set: Natural Language and Character Set:
Expires: January 6, 2001
The "attributes-charset" and "attributes-natural-language" The "attributes-charset" and "attributes-natural-language"
attributes as defined in [ipp-mod] section 3.1.4.1. attributes as defined in [ipp-mod] section 3.1.4.1.
Target: Target:
A copy of the Subscription object's "notification-recipient- A copy of the Subscription object's "notification-recipient-
uri" (uri) attribute which is the target of this operation as 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 described in [ipp-mod] section 3.1.5, i.e., the URI of the
'indp' Notification Recipient (see section 9.2). 'indp' Notification Recipient (see section 5.2.1).
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?
Group 2 to N: Event Notification Attributes Group 2 to N: Event Notification Attributes
In each group 2 to N, each attribute is encoded using the IPP rules 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. 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 Note: the Get-Jobs response in [ipp-mod] acts as a model for
encoding multiple groups of attributes. encoding multiple groups of attributes.
Each Event Notification Group MUST contain all of attributes Each Event Notification Group MUST contain all of attributes
specified in [ipp-ntfy] section 9.1 (.Content of Machine Consumable specified in [ipp-ntfy] section 9.1 ("Content of Machine Consumable
Event Notifications.) with exceptions denoted by asterisks in the Event Notifications") with exceptions denoted by asterisks in the
tables below. tables below.
The tables below are copies of the tables in [ipp-ntfy] section 9.1 The tables below are copies of the tables in [ipp-ntfy] section 9.1
(.Content of Machine Consumable Event Notifications.) except that ("Content of Machine Consumable Event Notifications") except that
each cell in the .Sends. column is a .MUST.. each cell in the "Sends" column is a "MUST".
For an Event Notification for all Events, the Printer sends the For an Event Notification for all Events, the Printer sends the
following attributes. following attributes.
Table 3 . Attributes in Event Notification Content Table 3 . Attributes in Event Notification Content
Source Value Sends Source Object Source Value Sends Source Object
notify-subscription-id (integer(1:MAX)) MUST Subscription notify-subscription-id (integer(1:MAX)) MUST Subscription
notify-printer-uri (uri) MUST Subscription notify-printer-uri (uri) MUST Subscription
notify-subscribed-event (type2 keyword) MUST Event notify-subscribed-event (type2 keyword) MUST Event
Expires: January 14, 2001
Source Value Sends Source Object
Notification Notification
printer-up-time (integer(MIN:MAX)) MUST Printer printer-up-time (integer(MIN:MAX)) MUST Printer
printer-current-time (dateTime) * MUST Printer printer-current-time (dateTime) * MUST Printer
notify-sequence-number (integer (0:MAX)) MUST Subscription notify-sequence-number (integer (0:MAX)) MUST Subscription
notify-charset (charset) MUST Subscription notify-charset (charset) MUST Subscription
Expires: January 6, 2001
Source Value Sends Source Object
notify-natural-language (naturalLanguage) MUST Subscription notify-natural-language (naturalLanguage) MUST Subscription
notify-user-data (octetString(63)) ** MUST Subscription notify-user-data (octetString(63)) ** MUST Subscription
notify-text (text) MUST Event notify-text (text (MAX)) MUST Event
Notification Notification
attributes from the .notify-attributes. MUST Printer attributes from the "notify-attributes" MUST Printer
attribute *** attribute ***
attributes from the .notify-attributes. MUST Job attributes from the "notify-attributes" MUST Job
attribute *** attribute ***
attributes from the .notify-attributes. MUST Subscription attributes from the "notify-attributes" MUST Subscription
attribute *** attribute ***
ISSUE 04: Ok that "notify-text" has been changed from MAY to MUST? * The Printer MUST send "printer-current-time" if and only if it
supports the "printer-current-time" attribute on the Printer
* The Printer MUST send .printer-current-time. if and only if it
supports the .printer-current-time. attribute on the Printer
object. object.
** If the associated Subscription Object does not contain a ** If the associated Subscription Object does not contain a
.notify-user-data. attribute, the Printer MUST send an octet-string "notify-user-data" attribute, the Printer MUST send an octet-string
of length 0. of length 0.
*** If the .notify-attributes. attribute is present on the *** If the "notify-attributes" attribute is present on the
Subscription Object, the Printer MUST send all attributes specified Subscription Object, the Printer MUST send all attributes specified
by the .notify-attributes. attribute. Note: if the Printer doesn.t by the "notify-attributes" attribute. Note: if the Printer doesn't
support the .notify-attributes. attribute, it is not present on the support the "notify-attributes" attribute, it is not present on the
associated Subscription Object. associated Subscription Object.
For Event Notifications for Job Events, the Printer sends the For Event Notifications for Job Events, the Printer sends the
following additional attributes shown in Table 4. following additional attributes shown in Table 4.
Table 4 . Additional Attributes in Event Notification Content for Table 4 . Additional Attributes in Event Notification Content for
Job Events Job Events
Source Value Sends Source Object 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 (type1 enum) MUST Job
job-state-reasons (1setOf type2 keyword) MUST Job job-state-reasons (1setOf type2 keyword) MUST Job
job-impressions-completed MUST Job job-impressions-completed MUST Job
(integer(0:MAX)) * (integer(0:MAX)) *
Expires: January 6, 2001 * The Printer MUST send the "job-impressions-completed" attribute
* The Printer MUST send the .job-impressions-completed. attribute
in an Event Notification only for the combinations of Events and in an Event Notification only for the combinations of Events and
Subscribed Events shown in Table 5. Subscribed Events shown in Table 5.
Table 5 . Combinations of Events and Subscribed Events for .job- Table 5 . Combinations of Events and Subscribed Events for "job-
impressions-completed. impressions-completed"
Job Event Subscribed Job Event Job Event Subscribed Job Event
.job-progress. .job-progress. 'job-progress' 'job-progress'
.job-completed. .job-completed. 'job-completed' 'job-completed'
.job-completed. .job-state-changed. 'job-completed' 'job-state-changed'
For Event Notification for Printer Events, the Printer sends the For Event Notification for Printer Events, the Printer sends the
following additional attributes shown in Table 6. following additional attributes shown in Table 6.
Table 6 . Additional Attributes in Event Notification Content for Table 6 . Additional Attributes in Event Notification Content for
Printer Events Printer Events
Source Value Sends Source Object Source Value Sends Source Object
printer-state (type1 enum) MUST Printer printer-state (type1 enum) MUST Printer
printer-state-reasons (1setOf type2 MUST Printer printer-state-reasons (1setOf type2 MUST Printer
keyword) keyword)
printer-is-accepting-jobs (boolean) MUST Printer printer-is-accepting-jobs (boolean) MUST Printer
9.1.2 Send-Notifications Response 8.1.2 Send-Notifications Response
The Notification Recipient MUST return (to the client which is the The Notification Recipient MUST return (to the client which is the
Printer) the following sets of attributes as part of a Send- Printer) the following sets of attributes as part of a Send-
Notifications response: Notifications response:
Every operation response contains the following REQUIRED parameters (see Every operation response contains the following REQUIRED parameters (see
[ipp-mod] section 3.1.1}: [ipp-mod] section 3.1.1}:
Expires: January 14, 2001
- a "version-number" - a "version-number"
- a "status-code" - a "status-code"
- the "request-id" that was supplied in the corresponding request - the "request-id" that was supplied in the corresponding request
Group 1: Operation Attributes Group 1: Operation Attributes
Status Message: Status Message:
As defined in [ipp-mod]. As defined in [ipp-mod].
Expires: January 6, 2001
The Notification Recipient can return any status codes defined in The Notification Recipient can return any status codes defined in
[ipp-mod] and section 10.1 that applies to all of the Event [ipp-mod] and section 9.1 that applies to all of the Event
Notification Attribute groups. The following is a description of Notification Attribute groups. The following is a description of
the important status codes: the important status codes:
'successful-ok': the Notification Recipient received all of the 'successful-ok': the Notification Recipient received all of the
Event Notification Attribute Groups and was expecting each of Event Notification Attribute Groups and was expecting each of
them. them.
'successful-ok-ignored-notifications': the Notification 'successful-ok-ignored-notifications': the Notification
Recipient was able to consume some, but not all of the Event Recipient was able to consume some, but not all of the Event
Notification Attributes Groups sent. The Event Notification Notification Attributes Groups sent. The Event Notification
Attributes Groups with a .notify-status-code. attribute are Attributes Groups with a "notify-status-code" attribute are
the ones that were ignored or are to be canceled. the ones that were ignored or are to be canceled.
'client-error-ignored-all-notifications': the Notification 'client-error-ignored-all-notifications': the Notification
Recipient was unable to consume any of the Event Notification Recipient was unable to consume any of the Event Notification
Attributes Groups sent. The Event Notification Attributes Attributes Groups sent. The Event Notification Attributes
Groups with a .notify-status-code. attribute are the ones that Groups with a "notify-status-code" attribute are the ones that
were ignored or are to be canceled. were ignored or are to be canceled.
Natural Language and Character Set: Natural Language and Character Set:
The "attributes-charset" and "attributes-natural-language" The "attributes-charset" and "attributes-natural-language"
attributes as defined in [ipp-mod] section 3.1.4.1. attributes as defined in [ipp-mod] section 3.1.4.1.
Group 2 to N: Notification Attributes Group 2 to N: Notification Attributes
These groups MUST be returned if and only if the "status-code" These groups MUST be returned if and only if the "status-code"
parameter returned in Group 1 is anything but the 'successful-ok' parameter returned in Group 1 is anything but the 'successful-ok'
status code. status code.
"notification-status-code" (type2 enum) "notification-status-code" (type2 enum)
Indicates whether the Notification Recipient was able to consume Indicates whether the Notification Recipient was able to consume
the n-th Notification Report as follows: the n-th Notification Report as follows:
Expires: January 14, 2001
'successful-ok' - this Event Notification Attribute Group was 'successful-ok' - this Event Notification Attribute Group was
consumed consumed
'client-error-not-found' - this Event Notification Attribute Group 'client-error-not-found' - this Event Notification Attribute Group
was not able to be consumed. The Printer MUST cancel the was not able to be consumed. The Printer MUST cancel the
Subscription and MUST NOT attempt to send any further Event Subscription and MUST NOT attempt to send any further Event
Notifications from the associated Subscription object. Notifications from the associated Subscription object.
'successful-ok-but-cancel-subscription' - the Event Notification 'successful-ok-but-cancel-subscription' - the Event Notification
Attribute Group was consumed, but the Notification Recipient Attribute Group was consumed, but the Notification Recipient
wishes to cancel the Subscription object. The Printer MUST wishes to cancel the Subscription object. The Printer MUST
cancel the Subscription and MUST NOT attempt to send any further cancel the Subscription and MUST NOT attempt to send any further
Event Notifications from the associated Subscription object. Event Notifications from the associated Subscription object.
9.2 Notification Protocol URI Scheme 9 Status Codes
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 Status Codes
This section lists status codes whose meaning have been extended and/or This section lists status codes whose meaning have been extended and/or
defined for returning in Event Notification Attribute Groups as the defined for returning in Event Notification Attribute Groups as the
value of the "notification-status-code" operation attribute. The code value of the "notification-status-code" operation attribute. The code
values are allocated in the same space as the status codes in [ipp-mod]. values are allocated in the same space as the status codes in [ipp-mod].
10.1 Additional Status Codes 9.1 Additional Status Codes
The following status codes are defined as extensions for Notification The following status codes are defined as extensions for Notification
and are returned as the value of the .status-code. parameter in the and are returned as the value of the "status-code" parameter in the
Operation Attributes Group of a response (see [ipp-mod] section Operation Attributes Group of a response (see [ipp-mod] section
3.1.6.1). Operations in this document can also return the status codes 3.1.6.1). Operations in this document can also return the status codes
defined in section 13 of [ipp-mod]. The .successful-ok. status code is defined in section 13 of [ipp-mod]. The 'successful-ok' status code is
an example of such a status code. an example of such a status code.
10.1.1 successful-ok-ignored-notifications (0x0004) 9.1.1 successful-ok-ignored-notifications (0x0004)
The Notification Recipient was able to consume some, but not all, of the The Notification Recipient was able to consume some, but not all, of the
Event Notifications Attributes Groups sent by the Printer in the Send- Event Notifications Attributes Groups sent by the Printer in the Send-
Notifications request. See section 9.1.2 for further details. Notifications request. See section 8.1.2 for further details.
10.2 Status Codes returned in Event Notification Attributes Groups 9.2 Status Codes returned in Event Notification Attributes Groups
This section contains values of the .notify-status-code. attribute that This section contains values of the "notify-status-code" attribute that
the Notification Recipient returns in a Event Notification Attributes the Notification Recipient returns in a Event Notification Attributes
Group in a response when the corresponding Event Notification Attributes Group in a response when the corresponding Event Notification Attributes
Group in the request: Group in the request:
1. was not consumed OR 1. was not consumed OR
2. was consumed, but the Notification Recipient wants to cancel the 2. was consumed, but the Notification Recipient wants to cancel the
corresponding Subscription object corresponding Subscription object
The following sections are ordered in decreasing order of importance of The following sections are ordered in decreasing order of importance of
the status-codes. the status-codes.
10.2.1 client-error-not-found (0x0406) Expires: January 14, 2001
9.2.1 client-error-not-found (0x0406)
This status code is defined in [ipp-mod]. This document extends its This status code is defined in [ipp-mod]. This document extends its
meaning and allows it to be returned in an Event Notification Attributes meaning and allows it to be returned in an Event Notification Attributes
Group of a response. Group of a response.
The Notification Recipient was unable to consume this Event Notification The Notification Recipient was unable to consume this Event Notification
Attributes Group because it was not expected. See section 9.1.2 for Attributes Group because it was not expected. See section 8.1.2 for
further details. further details.
Expires: January 6, 2001 9.2.2 successful-ok-but-cancel-subscription (0x0006)
10.2.2 successful-ok-but-cancel-subscription (0x0006)
The Notification Recipient was able to consume this Event Notification The Notification Recipient was able to consume this Event Notification
Attributes Group that the Printer sent, but wants the corresponding Attributes Group that the Printer sent, but wants the corresponding
Subscription object to be canceled none-the-less. See section 9.1.2 for Subscription object to be canceled none-the-less. See section 8.1.2 for
further details. further details.
11 Encoding and Transport 10 Encoding and Transport
This section defines the encoding and transport used by the 'indp' This section defines the encoding and transport used by the 'indp'
Delivery Method. Delivery Method.
11.1 Encoding of the Operation Layer 10.1 Encoding of the Operation Layer
The 'indp' Delivery Method uses the IPP operation layer encoding The 'indp' Delivery Method uses the IPP operation layer encoding
described in [ipp-pro] and the following Event Notification Attributes described in [ipp-pro] and the following Event Notification Attributes
Group tag allocated by [ipp-ntfy]: Group tag allocated by [ipp-ntfy]:
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x07 .event-notification-attributes-tag. 0x07 "event-notification-attributes-tag"
11.2 Encoding of Transport Layer 10.2 Encoding of Transport Layer
The 'indp' Notification Delivery Method uses the IPP transport layer The 'indp' Notification Delivery Method uses the IPP transport layer
encoding described in [ipp-pro]. encoding described in [ipp-pro].
It is REQUIRED that an 'indp' Notification Recipient implementation It is REQUIRED that an 'indp' Notification Recipient implementation
support HTTP over the IANA assigned Well Known Port assigned to the support HTTP over the IANA assigned Well Known Port assigned to the
'indp' Delivery Method as its default port by IANA (see section 12), 'indp' Delivery Method as its default port by IANA (see section 12),
though a Notification Recipient implementation MAY support HTTP over though a Notification Recipient implementation MAY support HTTP over
some other port as well. 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 12 IANA Considerations
The 'indp://' URL scheme for the 'indp' Delivery Method will be The 'indp' URL scheme for the 'indp' Delivery Method and Protocol will
registered with IANA. IANA will assign a default port to use with the be registered with IANA. IANA will assign a default port to use with
'indp' Delivery Method. the 'indp' Delivery Method and Protocol.
13 Internationalization Considerations 13 Internationalization Considerations
When the client requests Human Consumable form by supplying the "notify- When the client requests Human Consumable form by supplying the "notify-
text-format" operation attribute (see [ipp-ntfy]), the IPP Printer (or text-format" operation attribute (see [ipp-ntfy]), the IPP Printer (or
any Notification Service that the IPP Printer might be configured to any Notification Service that the IPP Printer might be configured to
use) supplies and localizes the text value of the "human-readable- use) supplies and localizes the text value of the "human-readable-
report" attribute in the Notification according to the charset and report" attribute in the Notification according to the charset and
natural language requested in the notification subscription. natural language requested in the notification subscription.
Expires: January 6, 2001
14 Security Considerations 14 Security Considerations
The IPP Model and Semantics document [ipp-mod] discusses high level The IPP Model and Semantics document [ipp-mod] discusses high level
security requirements (Client Authentication, Server Authentication and security requirements (Client Authentication, Server Authentication and
Operation Privacy). Client Authentication is the mechanism by which the Operation Privacy). Client Authentication is the mechanism by which the
client proves its identity to the server in a secure manner. Server client proves its identity to the server in a secure manner. Server
Authentication is the mechanism by which the server proves its identity 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 to the client in a secure manner. Operation Privacy is defined as a
mechanism for protecting operations from eavesdropping. mechanism for protecting operations from eavesdropping.
The Notification Recipient can cancel unwanted Subscriptions created by The Notification Recipient can cancel unwanted Subscriptions created by
other parties without having to be the owner of the subscription by other parties without having to be the owner of the subscription by
returning the 'successful-ok-but-cancel-subscription' status code in the returning the 'successful-ok-but-cancel-subscription' status code in the
Send-Notifications response returned to the Printer. Send-Notifications response returned to the Printer.
14.1 Security Conformance 14.1 Security Conformance
skipping to change at page 17, line 44 skipping to change at page 20, line 37
server authentication and operation privacy. If a Notification Recipient server authentication and operation privacy. If a Notification Recipient
supports TLS, it MUST support the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA 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 cipher suite as mandated by RFC 2246 [rfc2246]. All other cipher suites
are OPTIONAL. Notification recipients MAY support Basic Authentication are OPTIONAL. Notification recipients MAY support Basic Authentication
(described in HTTP/1.1 [rfc2616]) for client authentication if the (described in HTTP/1.1 [rfc2616]) for client authentication if the
channel is secure. TLS with the above mandated cipher suite can provide channel is secure. TLS with the above mandated cipher suite can provide
such a secure channel. such a secure channel.
15 References 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] [ipp-mod]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf- "Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf-
ipp-model-v11-07.txt>, May 22, 2000. ipp-model-v11-07.txt>, May 22, 2000.
[ipp-ntfy] [ipp-ntfy]
Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M., Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,
Bergman, R., "Internet Printing Protocol/1.1: IPP Event Bergman, R., "Internet Printing Protocol/1.1: IPP Event
Notification Specification", <draft-ietf-ipp-not-spec-03.txt>, June Notification Specification", <draft-ietf-ipp-not-spec-04.txt>, July
30, 2000. 13, 2000.
Expires: January 6, 2001
[ipp-pro] [ipp-pro]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11- Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
06.txt, May 30, 2000. 06.txt, May 30, 2000.
[rfc2026] [rfc2026]
S. Bradner, "The Internet Standards Process -- Revision 3", RFC S. Bradner, "The Internet Standards Process -- Revision 3", RFC
2026, October 1996. 2026, October 1996.
Expires: January 14, 2001
[rfc2616] [rfc2616]
R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
RFC 2616, June 1999. RFC 2616, June 1999.
[rfc2617] [rfc2617]
J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A.
Luotonen, L. Stewart, "HTTP Authentication: Basic and Digest Access Luotonen, L. Stewart, "HTTP Authentication: Basic and Digest Access
Authentication", RFC 2617, June 1999. Authentication", RFC 2617, June 1999.
skipping to change at page 19, line 4 skipping to change at page 21, line 50
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself 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 may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in 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 which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into Standards process must be followed, or as required to translate it into
languages other than English. languages other than English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 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 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
Expires: January 6, 2001 Expires: January 14, 2001
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/