draft-ietf-ipp-indp-method-03.txt   draft-ietf-ipp-indp-method-04.txt 
INTERNET-DRAFT INTERNET-DRAFT Hugo Parra
<draft-ietf-ipp-indp-method-03.txt> <draft-ietf-ipp-indp-method-04.txt> Novell, Inc.
Category: standards track Hugo Parra [Target Category: standards track] Tom Hastings
Novell, Inc.
Tom Hastings
Xerox Corp. Xerox Corp.
August 29, 2000 February 28, 2001
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'indp' Delivery Method for Event Notifications and Protocol/1.0 The 'indp' Delivery Method for Event Notifications and Protocol/1.0
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). 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
provisions of Section 10 of [rfc2026]. Internet-Drafts are working all provisions of Section 10 of [RFC2026]. Internet-Drafts are
documents of the Internet Engineering Task Force (IETF), its areas, and working documents of the Internet Engineering Task Force (IETF), its
its working groups. Note that other groups may also distribute working areas, and its working groups. Note that other groups may also
documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference
or to cite them other than as "work in progress". material 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 notification extension document [ipp-ntfy] defines operations The IPP notification extension document [ipp-ntfy] defines operations
that a client can perform in order to create Subscription Objects in a that a client can perform in order to create Subscription Objects in
Printer and carry out other operations on them. The Subscription Object a Printer and carry out other operations on them. The Subscription
specifies that when one of the specified Events occurs, the Printer Object specifies that when one of the specified Events occurs, the
sends an asynchronous Event Notification to the specified Notification Printer sends an asynchronous Event Notification to the specified
Recipient via the specified Delivery Method (i.e., protocol). Notification Recipient via the specified Delivery Method (i.e.,
protocol).
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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 and Protocol. such document, and it specifies the 'indp' Delivery Method and
This Delivery Method is a simple protocol consisting of a single Protocol. This Delivery Method is a simple protocol consisting of a
operation: the Send-Notifications operation which uses the same encoding single operation: the Send-Notifications operation which uses the
and transport as IPP. This document defines version '1.0' of the same encoding and transport as IPP. This document defines version
protocol. '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
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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol For this Delivery Method, when an Event occurs, the Printer
August 29, 2000 immediately sends (pushes) an Event Notification via the Send-
Notifications operation 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 returns a response to the
Printer.
The basic 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
Printing Protocol [RFC2568] Internet Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [ipp-mod] Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [ipp-pro] Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
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]
Internet Printing Protocol (IPP): IPP Event Notification Internet Printing Protocol (IPP): IPP Event Notification
Specification [ipp-ntfy] Specification [ipp-ntfy]
The "Design Goals for an Internet Printing Protocol" document takes a The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that are administrators. It calls out a subset of end user requirements that
satisfied in IPP/1.0. A few OPTIONAL operator operations have been are satisfied in IPP/1.0. A few OPTIONAL operator operations have
added to IPP/1.1. been 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
Printing Protocol" document describes IPP from a high level view, Internet Printing Protocol" document describes IPP from a high level
defines a roadmap for the various documents that form the suite of IPP view, defines a roadmap for the various documents that form the suite
specification documents, and gives background and rationale for the IETF of IPP specification documents, and gives background and rationale
working group's major decisions. for the IETF working group's major decisions.
The "Internet Printing Protocol/1.1: Model and Semantics" document The "Internet Printing Protocol/1.1: Model and Semantics" document
describes a simplified model with abstract objects, their attributes, describes a simplified model with abstract objects, their attributes,
and their operations that are independent of encoding and transport. It and their operations that are independent of encoding and transport.
introduces a Printer and a Job object. The Job object optionally It introduces a Printer and a Job object. The Job object optionally
supports multiple documents per Job. It also addresses security, supports multiple documents per Job. It also addresses security,
internationalization, and directory issues. 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
a formal mapping of the abstract operations and attributes defined in is a formal mapping of the abstract operations and attributes defined
the model document onto HTTP/1.1 [RFC2616]. It defines the encoding in the model document onto HTTP/1.1 [RFC2616]. It defines the
rules for a new Internet MIME media type called "application/ipp". This encoding rules for a new Internet MIME media type called
document also defines the rules for transporting a message body over "application/ipp". This document also defines the rules for
HTTP whose Content-Type is "application/ipp". This document defines a transporting a message body over HTTP whose Content-Type is
new scheme named 'ipp' for identifying IPP printers and jobs. "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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
considerations that may assist them in the design of their client and/or The "Internet Printing Protocol/1.1: Implementer's Guide" document
IPP object implementations. For example, a typical order of processing gives insight and advice to implementers of IPP clients and IPP
requests is given, including error checking. Motivation for some of the objects. It is intended to help them understand IPP/1.1 and some of
specification decisions is also included. 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 The "Mapping between LPD and IPP Protocols" document gives some
to implementers of gateways between IPP and LPD (Line Printer Daemon) advice to implementers of gateways between IPP and LPD (Line Printer
implementations. Daemon) implementations.
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
Operations and the requirements for other Delivery Method documents to Creation Operations and the requirements for other Delivery Method
define a Delivery Method to carry an Event Notifications to a documents to define a Delivery Method to carry an Event Notifications
Notification Recipient. to a Notification Recipient.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
Table of Contents Table of Contents
1 Introduction ......................................................7 1 Introduction....................................................7
2 Terminology .......................................................7
3 Model and Operation ...............................................8 2 Terminology.....................................................7
4 General Information ...............................................9 3 Model and Operation.............................................8
5 Subscription object attributes ...................................12 4 General Information.............................................9
5.1 SUBSCRIPTION TEMPLATE ATTRIBUTE CONFORMANCE.....................12
5.2 ADDITIONAL INFORMATION ABOUT SUBSCRIPTION TEMPLATE ATTRIBUTES...13
5.2.1 ....................................notify-recipient-uri (uri)
13
5.3 SUBSCRIPTION DESCRIPTION ATTRIBUTE CONFORMANCE..................13
6 Printer Description Attributes ...................................13 5 Subscription object attributes.................................12
6.1 PRINTER DESCRIPTION ATTRIBUTE CONFORMANCE.......................13 5.1 Subscription Template Attribute Conformance.................12
6.2 NEW VALUES FOR EXISTING PRINTER DESCRIPTION ATTRIBUTES..........14 5.2 Additional Information about Subscription Template Attributes12
6.2.1 ...................notify-schemes-supported (1setOf uriScheme) 5.2.1 notify-recipient-uri (uri)................................12
14 5.3 Subscription Description Attribute Conformance..............12
6.2.2 ......................operations-supported (1setOf type2 enum)
14
7 Attributes Only in Event Notifications ...........................14 6 Printer Description Attributes.................................12
6.1 Printer Description Attribute Conformance...................13
6.2 New Values for Existing Printer Description Attributes......13
6.2.1 notify-schemes-supported (1setOf uriScheme)...............13
6.2.2 operations-supported (1setOf type2 enum)..................13
8 Operations for Notification ......................................15 7 Attributes Only in Event Notifications.........................13
8.1 SEND-NOTIFICATIONS OPERATION....................................15
8.1.1 ....................................Send-Notifications Request
16
8.1.2 ...................................Send-Notifications Response
20
9 Status Codes .....................................................22 8 Operations for Notification....................................14
9.1 ADDITIONAL STATUS CODES.........................................22 8.1 Send-Notifications operation................................14
9.1.1 ..................successful-ok-ignored-notifications (0x0004) 8.1.1 Send-Notifications Request................................14
22 8.1.2 Send-Notifications Response...............................18
9.2 STATUS CODES RETURNED IN EVENT NOTIFICATION ATTRIBUTES GROUPS...22
9.2.1 ...............................client-error-not-found (0x0406)
23
9.2.2 ................successful-ok-but-cancel-subscription (0x0006)
23
10 Encoding and Transport ...........................................23 9 Status Codes...................................................19
9.1 Additional Status Codes.....................................19
9.1.1 successful-ok-ignored-notifications (0x0004)..............20
9.1.2 client-error-ignored-all-notifications (0x0416)...........20
9.2 Status Codes returned in Event Notification Attributes Groups20
9.2.1 client-error-not-found (0x0406)...........................20
9.2.2 successful-ok-but-cancel-subscription (0x0006)............20
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol 10 Encoding and Transport.........................................21
August 29, 2000 10.1 Encoding of the Operation Layer.............................21
10.2 Encoding of Transport Layer.................................21
10.1 ENCODING OF THE OPERATION LAYER ...............................23 11 Conformance Requirements.......................................21
10.2 ENCODING OF TRANSPORT LAYER ...................................24 11.1 Conformance Requirements for Printers.......................21
11.2 Conformance Requirements for INDP Notification Recipients...22
11 Conformance Requirements .........................................24 12 INDP URL Scheme................................................23
11.1 PRINTER CONFORMANCE REQUIREMENTS ..............................24 12.1 INDP URL Scheme Applicability and Intended Usage............23
11.2 NOTIFICATION RECIPIENT REQUIREMENTS ...........................25 12.2 INDP URL Scheme Associated INDP Port........................23
12.3 INDP URL Scheme Associated MIME Type........................23
12.4 INDP URL Scheme Character Encoding..........................23
12.5 INDP URL Scheme Syntax in ABNF..............................23
12.5.1 INDP URL Examples.........................................24
12.5.2 INDP URL Comparisons......................................25
12 IANA Considerations ..............................................25 13 IANA Considerations............................................26
13.1 Operation Registrations.....................................26
13.2 Additional values of existing attributes....................26
13.2.1 Additional values for the "notify-schemes-supported" Printer
attribute..............................................26
13.2.2 Additional values for the "operations-supported" Printer
attribute..............................................27
13.3 Status code Registrations...................................27
13 Internationalization Considerations ..............................25 14 Internationalization Considerations............................27
14 Security Considerations ..........................................25 15 Security Considerations........................................28
14.1 SECURITY CONFORMANCE ..........................................25 15.1 Security Conformance........................................28
15 References .......................................................26 16 References.....................................................28
16 Author's Addresses ...............................................27 17 Author's Addresses.............................................30
17 Full Copyright Statement .........................................27 18 Full Copyright Statement.......................................30
Tables Tables
Table 1 - Information about the Delivery Method.......................9 Table 1 - Information about the Delivery Method...................10
Table 2 - Operation-id assignments................................13
Table 2 - Operation-id assignments...................................14 Table 3 - Attributes in Event Notification Content................16
Table 3 - Attributes in Event Notification Content...................17
Table 4 - Additional Attributes in Event Notification Content for Job Table 4 - Additional Attributes in Event Notification Content for Job
Events ...........................................................19 Events ........................................................17
Table 5 - Combinations of Events and Subscribed Events for "job- Table 5 - Combinations of Events and Subscribed Events for "job-
impressions-completed" ...........................................19 impressions-completed" ........................................17
Table 6 - Additional Attributes in Event Notification Content for Table 6 - Additional Attributes in Event Notification Content for
Printer Events ...................................................20 Printer Events ................................................18
Table 7 - The "event-notification-attributes-tag" value...........21
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
1 Introduction 1 Introduction
The notification extension document [ipp-ntfy] defines operations that a The notification extension document [ipp-ntfy] defines operations
client can perform in order to create Subscription Objects in a Printer that a client can perform in order to create Subscription Objects in
and carry out other operations on them. A Subscription Object represents a Printer and carry out other operations on them. A Subscription
a Subscription abstraction. The Subscription Object specifies that when Object represents a Subscription abstraction. The Subscription Object
one of the specified Events occurs, the Printer sends an asynchronous specifies that when one of the specified Events occurs, the Printer
Event Notification to the specified Notification Recipient via the sends an asynchronous Event Notification to the specified
specified Delivery Method (i.e., protocol). Notification Recipient via the 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. This such document, and it specifies the 'indp' Delivery Method. This
Delivery Method is a simple protocol consisting of a single operation: Delivery Method is a simple protocol consisting of a single
the Send-Notifications operation which uses the same encoding and operation: the Send-Notifications operation which uses the same
transport as IPP. This document defines version '1.0' of the protocol. 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 the Notification Recipient specified in the Notifications to the Notification Recipient specified in the
Subscription Object. The Event Notification content consists of Machine Subscription Object. The Event Notification content consists of
Consumable attributes and a Human Consumable "notify-text" attribute. Machine Consumable attributes and a Human Consumable "notify-text"
attribute.
The Notification Recipient receives the Event Notification as a Send- The Notification Recipient receives the Event Notification as a Send-
Notifications operation, in the same way as an IPP Printer receives IPP Notifications operation, in the same way as an IPP Printer receives
operations. The Notification Recipient returns a response to the IPP operations. The Notification Recipient returns a response to the
Printer. Printer.
2 Terminology 2 Terminology
This section defines the following terms that are used throughout this This section defines the following terms that are used throughout
document: this document:
Terms such as attributes, keywords, and support. These terms have Terms such as attributes, keywords, and support. These terms have
special meaning and are defined in the model terminology [ipp-mod] special meaning and are defined in the model terminology
section 12.2. [RFC2911] 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 as specified in RFC 2119 [RFC2119] and [ipp-mod]
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
section 12.1. These terms refer to conformance to this document, Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD,
if this document is implemented. SHOULD NOT, MAY, NEED NOT, and OPTIONAL, have special
meaning relating to conformance as specified in RFC 2119
[RFC2119] and [RFC2911] section 12.1. These terms refer to
conformance to this document, if this document is
implemented.
Capitalized terms, such as Notification Recipient, Event Capitalized terms, such as Notification Recipient, Event
Notification, Printer, etc., that are defined in [ipp-ntfy] with Notification, Printer, etc., that are defined in [ipp-ntfy]
the same meanings and are not reproduced here. 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
response. request or response.
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
Operation. This Delivery Method takes advantage of combining several and Operation. This Delivery Method takes advantage of combining
Event Notifications into a single Compound Event Notification that is several Event Notifications into a single Compound Event Notification
delivery by a single Send-Notification operation to a single that is delivery by a single Send-Notification operation to a single
Notification Recipient. Notification Recipient.
When creating each Subscription object, the client supplies the "notify- When creating each Subscription object, the client supplies the
recipient" (uri) Subscription Template attribute. The "notify- "notify-recipient" (uri) Subscription Template attribute. The
recipient" attribute specifies both a single Notification Recipient that "notify-recipient" attribute specifies both a single Notification
is to receive the Notifications when subsequent events occur and the Recipient that is to receive the Notifications when subsequent events
method for notification delivery that the IPP Printer is to use. For occur and the method for notification delivery that the IPP Printer
the Notification Delivery Method defined in this document, the is to use. For the Notification Delivery Method defined in this
notification method is 'indp' and the rest of the URI is the address of document, the notification method is 'indp' and the rest of the URI
the Notification Recipient to which the IPP Printer will send the Send- is the address of the Notification Recipient to which the IPP Printer
Notifications operation. will send the Send-Notifications operation.
The 'indp' Notification Delivery Method defined in this document uses a The 'indp' Notification Delivery Method defined in this document uses
client/server protocol paradigm. The "client" in this relationship is a client/server protocol paradigm. The "client" in this relationship
the Printer described in [ipp-ntfy] while the "server" is the is 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
implement this Delivery Method will need to support an HTTP server that implement this Delivery Method will need to support an HTTP
stack. See section 10.2 for more details. server stack. See section 10.2 for more details.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
If the client wants the Printer to send Event Notifications via the If the client wants the Printer to send Event Notifications via the
'indp' Delivery Method, the client MUST choose a value for "notify- 'indp' Delivery Method, the client MUST choose a value for "notify-
recipient-uri" attribute which conforms to the rules of section 5.2.1. recipient-uri" attribute which conforms to the rules of section
5.2.1.
When an Event occurs, the Printer MUST immediately: When an Event occurs, the Printer MUST immediately:
1. Find all pertinent Subscription Objects P according to the rules of 1. Find all pertinent Subscription Objects P according to the rules of
section 9 of [ipp-ntfy], AND section 9 of [ipp-ntfy], AND
2. Find the subset M of these Subscription Objects P whose "notify- 2. Find the subset M of these Subscription Objects P whose "notify-
recipient-uri" attribute has a scheme value of 'indp', AND recipient-uri" attribute has a scheme value of 'indp', AND
3. For each Subscription Object in M, the Printer MUST 3. For each Subscription Object in M, the Printer MUST
a)generate a Send-Notifications request as specified in section a)generate a Send-Notifications request as specified in section
8.1.1 AND 8.1.1 AND
b)send the Send-Notifications request to the Notification b)send the Send-Notifications request to the Notification
Recipient specified by the address part of the "notify- Recipient specified by the address part of the "notify-
skipping to change at page 9, line 29 skipping to change at page 9, line 16
3. For each Subscription Object in M, the Printer MUST 3. For each Subscription Object in M, the Printer MUST
a)generate a Send-Notifications request as specified in section a)generate a Send-Notifications request as specified in section
8.1.1 AND 8.1.1 AND
b)send the Send-Notifications request to the Notification b)send the Send-Notifications request to the Notification
Recipient specified by the address part of the "notify- Recipient specified by the address part of the "notify-
recipient-uri" attribute value (see section 5.2.1). recipient-uri" attribute value (see section 5.2.1).
If several events occur sufficiently close to one another for the same If several events occur sufficiently close to one another for the
or different Subscription objects, but with the same Notification same or different Subscription objects, but with the same
Recipient, the Printer MAY combine them into a single Send-Notifications Notification Recipient, the Printer MAY combine them into a single
request using a separate Event Notification Attributes group for each Send-Notifications request using a separate Event Notification
event (see section 8.1.1). Attributes group for each event (see section 8.1.1).
4 General Information 4 General Information
If a Printer supports this Delivery Method, Table 1 lists its If a Printer supports this Delivery Method, Table 1 lists its
characteristics. characteristics.
Table 1 - Information about the Delivery Method Table 1 - Information about the Delivery Method
Document Method conformance 'indp' realization Document Method conformance 'indp' realization
requirement requirement
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
Document Method conformance 'indp' realization
requirement
1.What is the URL scheme name indp 1.What is the URL scheme name indp
for the Delivery Method? for the Delivery Method?
2.Is the Delivery Method is 2. Is the Delivery Method is RECOMMENDED
REQUIRED, RECOMMENDED, or REQUIRED, RECOMMENDED, or
OPTIONAL for an IPP Printer to RECOMMENDED OPTIONAL for an IPP Printer to
support? support?
3.What transport and delivery A Printer MUST support a 3.What transport and delivery A Printer MUST support a
protocol does the Printer use complete HTTP/1.1 stack protocol does the Printer use complete HTTP/1.1 stack
to deliver the Event [rfc2616] to deliver the Event [RFC2616]
Notification content, i.e., Notification content, i.e.,
what is the entire network what is the entire network
stack? stack?
4.Can several Event A Printer implementation MAY 4.Can several Event A Printer implementation MAY
Notifications be combined into combine several Event Notifications be combined into combine several Event
a Compound Event Notification? Notifications into a single a Compound Event Notification? Notifications into a single
Event Notifications request as Event Notifications request as
separate Event Notification separate Event Notification
Attributes Groups, see section Attributes Groups, see section
skipping to change at page 11, line 5 skipping to change at page 10, line 42
5.Is the Delivery Method This Delivery Method is a push. 5.Is the Delivery Method This Delivery Method is a push.
initiated by the Notification initiated by the Notification
Recipient (pull), or by the Recipient (pull), or by the
Printer (push)? Printer (push)?
6.Is the Event Notification Machine Consumable with the 6.Is the Event Notification Machine Consumable with the
content Machine Consumable or "notify-text" attribute being content Machine Consumable or "notify-text" attribute being
Human Consumable? Human Consumable Human Consumable? Human Consumable
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol 7. What section in this document The representation and encoding
August 29, 2000 answers the following is the same as IPP. See
Document Method conformance 'indp' realization
requirement
7.What section in this The representation and encoding
document answers the following is the same as IPP. See
question? For a Machine section 8.1.1 question? For a Machine section 8.1.1
Consumable Event Notification, Consumable Event Notification,
what is the representation and what is the representation and
encoding of values defined in encoding of values defined in
section 9.1 of [ipp-ntfy] and section 9.1 of [ipp-ntfy] and
the conformance requirements the conformance requirements
thereof? For a Human Consumable thereof? For a Human
Event Notification, what is the Consumable Event Notification,
representation and encoding of Document Method conformance 'indp' realization
pieces of information defined requirement
in section 9.2 of [ipp-ntfy]
and the conformance
requirements thereof?
8.What are the latency and Same as for IPP/1.0 or IPP/1.1
reliability of the transport itself (see [ipp-mod]).
and delivery protocol?
9.What are the security See section 14
aspects of the transport and
delivery protocol, e.g., how it
is handled in firewalls?
10. What are the content They are the same as for what is the representation and
length restrictions? IPP/1.0 and IPP/1.1 itself (see encoding of pieces of
[ipp-mod]). information defined in section
9.2 of [ipp-ntfy] and the
conformance requirements
thereof?
11. What are the additional A new Event Notifications 8. What are the latency and
values or pieces of information attribute group (see section reliability of the transport itselfs(see [RFC2911]).IPP/1.1
that a Printer sends in an 10.1) and additional status and delivery protocol?
Event Notification and the codes for use in the response
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol 9. What are the security aspects 15
August 29, 2000 of the transport and delivery
protocol, e.g., how it is See section
handled in firewalls?
Document Method conformance 'indp' realization 10. What are the content length They are the same as for
requirement restrictions? IPP/1.0 and IPP/1.1 itself (see
[RFC2911]).
11. What are the additional values A new Event Notifications
or pieces of information that attribute group (see section
a Printer sends in an Event 10.1) and additional status
Notification and the codes for use in the response
conformance requirements (see section 9) conformance requirements (see section 9)
thereof? thereof?
12. What are the additional None 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?
13. What are the additional 13. What are the additional None
Printer Description attributes Printer Description attributes
and the conformance None 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
ntfy]. [ipp-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
Delivery Method does not define any addition Subscription Template 'indp' Delivery Method does not define any addition Subscription
attributes. Template attributes.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
5.2 Additional Information about Subscription Template Attributes 5.2 Additional Information about Subscription Template Attributes
This section defines additional information about Subscription Template This section defines additional information about Subscription
attributes defined in [ipp-ntfy]. Template attributes defined in [ipp-ntfy].
5.2.1notify-recipient-uri (uri) 5.2.1notify-recipient-uri (uri)
This section describes the syntax of the value of this attribute for the This section describes the syntax of the value of this attribute for
'indp' Delivery Method. The syntax for values of this attribute for the 'indp' Delivery Method. The syntax for values of this attribute
other Delivery Method is defined in other Delivery Method Documents. for other Delivery Method is defined in other Delivery Method
Documents.
In order to support the 'indp' Delivery Method and Protocol, the Printer In order to support the 'indp' Delivery Method and Protocol, the
MUST support the following syntax: Printer MUST support the following syntax:
The 'indp://' URI scheme. The remainder of the URI indicates the The 'indp://' URI scheme. The remainder of the URI indicates
host and address of the Notification Recipient that is to receive the host name or host address (and optional path) of the
the Send-Notification operation. Notification Recipient that is to receive the Send-
Notification operation.
5.3 Subscription Description Attribute Conformance 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.
6 Printer Description Attributes 6 Printer Description Attributes
This section defines the Printer Description Attributes conformance This section defines the Printer Description Attributes conformance
requirements for Printers. requirements for Printers.
6.1 Printer Description Attribute Conformance 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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
6.2 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
attributes. Description attributes.
6.2.1notify-schemes-supported (1setOf uriScheme) 6.2.1notify-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.
6.2.2operations-supported (1setOf type2 enum) 6.2.2operations-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
operation defined in this document. The operation-id is assigned in the new operation defined in this document. The operation-id is assigned
same name space as other operations that a Printer supports. However, a in the same name space as other operations that a Printer supports.
Printer MUST NOT include this value in its "operations-supported" However, a Printer MUST NOT include this value in its "operations-
attribute unless it can accept the Send-Notifications request. supported" attribute unless it can accept the Send-Notifications
request.
Table 2 - Operation-id assignments Table 2 - Operation-id assignments
Value Operation Name Value Operation Name
0x001D Send-Notifications 0x001D Send-Notifications
7 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
besides those defined in [ipp-ntfy]. Notifications besides those defined in [ipp-ntfy].
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
8 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 6.2.2 There is only one operation defined: Send-Notifications. Section
assigns of the "operation-id" for the Send-Notifications operation and 6.2.2 assigns of the "operation-id" for the Send-Notifications
the following section defined the operation. operation and the following section defined the operation.
8.1 Send-Notifications operation 8.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
IPP [rfc2566]. This includes, the use of a URI as the identifier for by IPP [RFC2566]. This includes, the use of a URI as the identifier
the target of each operation, the inclusion of a version number, for the target of each operation, the inclusion of a version number,
operation-id, and request-id in each request, and the definition of operation-id, and request-id in each request, and the definition of
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
However, it uses a new attribute group, the Event Notification groups. However, it uses a new attribute group, the Event
Attributes group. Notification Attributes group.
The Notification Recipient MUST accept the request in any state. There The Notification Recipient MUST accept the request in any state.
is no state defined for the Notification Recipient for this Delivery There is no state defined for the Notification Recipient for this
Method. Delivery Method.
Access Rights: Notification Recipient MAY enforce access rights. If Access Rights: Notification Recipient MAY enforce access rights. If
the Printer receives a rejection with these status codes: 'client-error- the Printer receives a rejection with these status codes: 'client-
forbidden', 'client-error-not-authenticated', or 'client-error-not- error-forbidden', 'client-error-not-authenticated', or 'client-error-
authorized' status code , the Printer SHOULD cancel the subscription. not-authorized' status code , the Printer SHOULD cancel the
subscription.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
8.1.1Send-Notifications Request 8.1.1Send-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): [RFC2911] section 3.1.1):
- a "version-number" '1.0' - the version of the 'indp' - a "version-number" '1.0' - the version of the 'indp'
protocol is '1.0'. 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 request id (see [ipp-mod] section 3.1.2). - a "request-id" - the request id (see [RFC2911] section 3.1.2).
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:
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 [RFC2911] section 3.1.4.1.
The Printer MUST use the values of "notify-charset" and "notify- The Printer MUST use the values of "notify-charset" and
natural-language", respectively, from one Subscription Object "notify-natural-language", respectively, from one Subscription
associated with the Event Notifications in this request. Object associated with the Event Notifications in this request.
Normally, there is only one matched Subscription Object, or the Normally, there is only one matched Subscription Object, or the
value of the "notify-charset" and "notify-natural-language" value of the "notify-charset" and "notify-natural-language"
attributes is the same in all Subscription Objects. If not, the attributes is the same in all Subscription Objects. If not, the
Printer MUST pick one Subscription Object from which to obtain the Printer MUST pick one Subscription Object from which to obtain
value of these attributes. The algorithm for picking the the value of these attributes. The algorithm for picking the
Subscription Object is implementation dependent. The choice of Subscription Object is implementation dependent. The choice of
natural language is not critical because 'text' and 'name' values natural language is not critical because 'text' and 'name'
can override the "attributes-natural-language" Operation attribute. values can override the "attributes-natural-language" Operation
The Printer's choice of charset is critical because a bad choice attribute. The Printer's choice of charset is critical because
may leave it unable to send some 'text' and 'name' values a bad choice may leave it unable to send some 'text' and 'name'
accurately. values accurately.
Target: Target:
A copy of the Subscription object's "notification-recipient- A copy of the Subscription object's "notify-recipient-uri"
uri" (uri) attribute which is the target of this operation as (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 [RFC2911] section 3.1.5, i.e., the URI of the
'indp' Notification Recipient (see section 5.2.1). 'indp' Notification Recipient (see section 5.2.1).
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
for encoding attributes [ipp-pro] and may be encoded in any order. rules for encoding attributes [RFC2910] and may be encoded in
Note: the Get-Jobs response in [ipp-mod] acts as a model for any order. Note: the Get-Jobs response in [RFC2911] acts as a
encoding multiple groups of attributes. model for encoding multiple groups of attributes.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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
Event Notifications") with exceptions denoted by asterisks in the Consumable Event Notifications") with exceptions denoted by
tables below. asterisks in the 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
("Content of Machine Consumable Event Notifications") except that 9.1 ("Content of Machine Consumable Event Notifications")
each cell in the "Sends" column is a "MUST". except that 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
skipping to change at page 18, line 5 skipping to change at page 16, line 24
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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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 (MAX)) 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, if any *** attribute, if any ***
attributes from the "notify-attributes" MUST *** Job attributes from the "notify-attributes" MUST *** Job
attribute, if any *** attribute, if any ***
attributes from the "notify-attributes" MUST *** Subscription attributes from the "notify-attributes" MUST *** Subscription
attribute, if any *** attribute, if any ***
* The Printer MUST send "printer-current-time" if and only if it * The Printer MUST send "printer-current-time" if and only if
supports the "printer-current-time" attribute on the Printer 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-
of length 0. string 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
by the "notify-attributes" attribute. Note: if the Printer doesn't specified by the "notify-attributes" attribute. Note: if the
support the "notify-attributes" attribute, it is not present on the Printer doesn't support the "notify-attributes" attribute, it
associated Subscription Object and the Printer does not send any is not present on the associated Subscription Object and the
client-requested attributes. Printer does not send any client-requested attributes.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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
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)) *
* The Printer MUST send the "job-impressions-completed" attribute * The Printer MUST send the "job-impressions-completed"
in an Event Notification only for the combinations of Events and attribute in an Event Notification only for the combinations of
Subscribed Events shown in Table 5. Events and 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'
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
'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
following additional attributes shown in Table 6. the 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 keyword) MUST Printer
keyword)
printer-is-accepting-jobs (boolean) MUST Printer printer-is-accepting-jobs (boolean) MUST Printer
8.1.2Send-Notifications Response 8.1.2Send-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
[ipp-mod] section 3.1.1}: (see [RFC2911] section 3.1.1}:
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
- 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 [RFC2911].
The Notification Recipient can return any status codes defined in The Notification Recipient can return any status codes defined
[ipp-mod] and section 9.1 that applies to all of the Event in [RFC2911] 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
the important status codes: 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': the Notification Recipient received all of the
Event Notification Attribute Groups and was expecting each of
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
Notification Attributes Groups sent. The Event Notification Event Notification Attributes Groups sent. The Event
Attributes Groups with a "notify-status-code" attribute are Notification Attributes Groups with a "notify-status-
the ones that were ignored or are to be canceled. code" attribute are 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
Attributes Groups sent. The Event Notification Attributes Notification Attributes Groups sent. The Event
Groups with a "notify-status-code" attribute are the ones that Notification Attributes Groups with a "notify-status-
were ignored or are to be canceled. code" attribute are the ones that 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 [RFC2911] 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) "notify-status-code" (type2 enum)
Indicates whether the Notification Recipient was able to consume Indicates whether the Notification Recipient was able to
the n-th Notification Report as follows: consume the n-th Notification Report as follows:
'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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
Subscription and MUST NOT attempt to send any further Event 'successful-ok' - this Event Notification Attribute Group
Notifications from the associated Subscription object. was consumed
'successful-ok-but-cancel-subscription' - the Event Notification 'client-error-not-found' - this Event Notification
Attribute Group was consumed, but the Notification Recipient Attribute Group was not able to be consumed. The Printer
wishes to cancel the Subscription object. The Printer MUST MUST cancel the Subscription and MUST NOT attempt to send
cancel the Subscription and MUST NOT attempt to send any further any further Event Notifications from the associated
Event Notifications from the associated Subscription object. 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 Status Codes 9 Status Codes
This section lists status codes whose meaning have been extended and/or This section lists status codes whose meaning have been extended
defined for returning in Event Notification Attribute Groups as the and/or defined for returning in Event Notification Attribute Groups
value of the "notification-status-code" operation attribute. The code as the value of the "notify-status-code" operation attribute. The
values are allocated in the same space as the status codes in [ipp-mod]. code values are allocated in the same space as the status codes in
[RFC2911].
9.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 [RFC2911] 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
defined in section 13 of [ipp-mod]. The 'successful-ok' status code is codes defined in section 13 of [RFC2911]. The 'successful-ok' status
an example of such a status code. code is an example of such a status code.
9.1.1successful-ok-ignored-notifications (0x0004) 9.1.1successful-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
Event Notifications Attributes Groups sent by the Printer in the Send- the Event Notifications Attributes Groups sent by the Printer in the
Notifications request. See section 8.1.2 for further details. Send-Notifications request. See section 8.1.2 for further details.
9.1.2 client-error-ignored-all-notifications (0x0416)
The Notification Recipient was unable to consume any of the Event
Notification Attributes Groups sent by the Printer. The Event
Notification Attributes Groups with a "notify-status-code" attribute
are the ones that were ignored or are to be canceled.
9.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
the Notification Recipient returns in a Event Notification Attributes that the Notification Recipient returns in a Event Notification
Group in a response when the corresponding Event Notification Attributes Attributes Group in a response when the corresponding Event
Group in the request: Notification Attributes Group in the request:
4. was not consumed OR 1.was not consumed OR
5. 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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol The following sections are ordered in decreasing order of importance
August 29, 2000 of the status-codes.
The following sections are ordered in decreasing order of importance of
the status-codes.
9.2.1client-error-not-found (0x0406) 9.2.1client-error-not-found (0x0406)
This status code is defined in [ipp-mod]. This document extends its This status code is defined in [RFC2911]. 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
Group of a response. Attributes Group of a response.
The Notification Recipient was unable to consume this Event Notification The Notification Recipient was unable to consume this Event
Attributes Group because it was not expected. See section 8.1.2 for Notification Attributes Group because it was not expected. See
further details. section 8.1.2 for further details.
9.2.2successful-ok-but-cancel-subscription (0x0006) 9.2.2successful-ok-but-cancel-subscription (0x0006)
The Notification Recipient was able to consume this Event Notification The Notification Recipient was able to consume this Event
Attributes Group that the Printer sent, but wants the corresponding Notification Attributes Group that the Printer sent, but wants the
Subscription object to be canceled none-the-less. See section 8.1.2 for corresponding Subscription object to be canceled none-the-less. See
further details. section 8.1.2 for further details.
10 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.
10.1Encoding of the Operation Layer 10.1Encoding 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 [RFC2910] and the Event Notification Attributes Group
Group tag allocated by [ipp-ntfy]: tag allocated by [ipp-ntfy] as shown in Table 7:
Table 7 - The "event-notification-attributes-tag" value
Tag Value (Hex) Meaning Tag Value (Hex) Meaning
0x07 "event-notification-attributes-tag" 0x07 "event-notification-attributes-tag"
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
10.2Encoding of Transport Layer 10.2Encoding 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 [RFC2910].
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 13),
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 11 Conformance Requirements
This section defines conformance requirements for Printers and This section defines conformance requirements for Printers and
Notification Recipients. Notification Recipients.
11.1Printer Conformance Requirements 11.1 Conformance Requirements for Printers
The 'indp' Delivery Method is RECOMMENDED for a Printer to support. The 'indp' Delivery Method is RECOMMENDED for a Printer to support.
If the Printer supports the 'indp' Delivery Method, the Printer MUST: IPP Printers that conform to this specification:
1.meet the conformance requirements defined in [ipp-ntfy]. 1.MUST meet the conformance requirements defined in [ipp-ntfy].
2.support the conformance requirements for Subscription object 2.MUST support the conformance requirements for Subscription object
attributes defined in section 5, including the syntax for the attributes defined in section 5, including the syntax for the
"notify-recipient-uri" Subscription Object attribute defined in "notify-recipient-uri" Subscription Object attribute defined in
section 5.2.1. section 5.2.1.
3.support the conformance requirements for Printer Description object 3.MUST support the conformance requirements for Printer Description
attributes defined in section 6. object attributes defined in section 6.
4.support the 'indp' protocol by sending Event Notifications using the 4.MUST support the 'indp' protocol by sending Event Notifications
Send-Notifications operation defined in section 8.1. using the Send-Notifications operation defined in section 8.1.
5.support sending Event Notification via email with the content 5.MUST send INDP URLs (e.g., in the "notify-recipient-uri" attribute
specified in section 8.1.1. in 'Send-Notifications') that conform to the ABNF specified in
section 12.5 of this document;
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol 6.MUST send INDP operations via the port specified in the INDP URL
August 29, 2000 (if present) or otherwise via IANA assigned well-known port [TBD];
11.2Notification Recipient Requirements 7.MUST convert INDP URLs to their corresponding HTTP URL forms by
the same rules used to convert IPP URLs to their corresponding
HTTP URL forms (see section 5 'IPP URL Scheme' in [RFC2910]).
A Notification Recipient MUST accept Send-Notifications requests and 11.2 Conformance Requirements for INDP Notification Recipients
return Send-Notifications responses as defined in sections 8 and 9.
12 IANA Considerations INDP Notification Recipients that conform to this specification:
The 'indp' URL scheme for the 'indp' Delivery Method and Protocol will 1.MUST accept Send-Notifications requests and return Send-
be registered with IANA. IANA will assign a default port to use with Notifications responses as defined in sections 8 and 9.
the 'indp' Delivery Method and Protocol.
13 Internationalization Considerations 2.SHOULD reject received INDP URLs in "application/ipp" request
bodies (e.g., in the "notify-recipient-uri" attribute in 'Send-
Notifications') that do not conform to the ABNF for INDP URLs
specified in section 12.5 of this document;
When the client requests Human Consumable form by supplying the "notify- 3.MUST listen for INDP operations on IANA-assigned well-known port
text-format" operation attribute (see [ipp-ntfy]), the IPP Printer (or [TBD], unless explicitly configured by system administrators or
any Notification Service that the IPP Printer might be configured to site policies;
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.
14 Security Considerations 4.SHOULD NOT listen for INDP operations on any other port, unless
explicitly configured by system administrators or site policies.
The IPP Model and Semantics document [ipp-mod] discusses high level 12 INDP URL Scheme
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
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 12.1 INDP URL Scheme Applicability and Intended Usage
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.1Security Conformance This section is intended for use in registering the "indp" URL scheme
with IANA and fully conforms to the requirements in [RFC2717]. This
document defines the "indp" URL (Uniform Resource Locator) scheme for
specifying the location of an INDP Notification Recipient object
which implements IPP Notification Delivery Protocol (INDP) specified
in this document.
Printers (client) MAY support Digest Authentication [rfc2617]. If The intended usage of the "indp" URL scheme is COMMON.
12.2 INDP URL Scheme Associated INDP Port
All INDP URLs which do NOT explicitly specify a port MUST be used
over IANA-assigned well-known port [TBD] for the INDP protocol.
See: IANA Port Numbers Registry [IANA-PORTREG].
12.3 INDP URL Scheme Associated MIME Type
All INDP protocol operations (requests and responses) MUST be
conveyed in an "application/ipp" MIME media type as registered in
[IANA-MIMEREG]. INDP URLs MUST refer to INDP Notification Recipient
objects which support this "application/ipp" MIME media type.
See: IANA MIME Media Types Registry [IANA-MIMEREG].
12.4 INDP URL Scheme Character Encoding
The INDP URL scheme defined in this document is based on the ABNF for
the HTTP URL scheme defined in HTTP/1.1 [RFC2616], which is derived
from the URI Generic Syntax [RFC2396] and further updated by
[RFC2732] and [RFC2373] (for IPv6 addresses in URLs). The INDP URL
scheme is case-insensitive in the host name or host address part;
however the path part is case-sensitive, as in [RFC2396]. Code
points outside [US-ASCII] MUST be hex escaped by the mechanism
specified in [RFC2396].
12.5 INDP URL Scheme Syntax in ABNF
This section is intended for use in registering the "indp" URL scheme
with IANA and fully conforms to the requirements in [RFC2717]. This
document defines the "indp" URL (Uniform Resource Locator) scheme for
specifying the location of an INDP Notification Recipient object
which implements IPP Notification Delivery Protocol (INDP) specified
in this document.
The intended usage of the "indp" URL scheme is COMMON.
The IPP protocol places a limit of 1023 octets (NOT characters) on
the length of a URI (see section 4.1.5 'uri' in [RFC2911]). An INDP
Notification Recipient MUST return 'client-error-request-value-too-
long' (see section 13.1.4.10 in [RFC2911]) when a URI received in a
request is too long.
Note: INDP Notification Recipients ought to be cautious about
depending on URI lengths above 255 bytes, because some older client
or proxy implementations might not properly support these lengths.
INDP URLs MUST be represented in absolute form. Absolute URLs always
begin with a scheme name followed by a colon. For definitive
information on URL syntax and semantics, see "Uniform Resource
Identifiers (URI): Generic Syntax and Semantics" [RFC2396]. This
specification adopts the definitions of "port", "host", "abs_path",
and "query" from [RFC2396], as updated by [RFC2732] and [RFC2373]
(for IPv6 addresses in URLs).
The INDP URL scheme syntax in ABNF is as follows:
indp_URL = "indp:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
If the port is empty or not given, IANA-assigned well-known port
[TBD] is assumed. The semantics are that the identified resource
(see section 5.1.2 of [RFC2616]) is located at the INDP Notification
Recipient listening for HTTP connections on that port of that host,
and the Request-URI for the identified resource is 'abs_path'.
Note: The use of IP addresses in URLs SHOULD be avoided whenever
possible (see [RFC1900]).
If the 'abs_path' is not present in the URL, it MUST be given as "/"
when used as a Request-URI for a resource (see section 5.1.2 of
[RFC2616]). If a proxy receives a host name which is not a fully
qualified domain name, it MAY add its domain to the host name it
received. If a proxy receives a fully qualified domain name, the
proxy MUST NOT change the host name.
12.5.1 INDP URL Examples
The following are examples of valid INDP URLs for Notification
Recipient objects (using DNS host names):
indp://abc.com
indp://abc.com/listener
Note: The use of IP addresses in URLs SHOULD be avoided whenever
possible (see [RFC1900]).
The following literal IPv4 addresses:
192.9.5.5 ; IPv4 address in IPv4 style
186.7.8.9 ; IPv4 address in IPv4 style
are represented in the following example INDP URLs:
indp://192.9.5.5/listener
indp://186.7.8.9/listeners/tom
The following literal IPv6 addresses (conformant to [RFC2373]):
::192.9.5.5 ; IPv4 address in IPv6 style
::FFFF:129.144.52.38 ; IPv4 address in IPv6 style
2010:836B:4179::836B:4179 ; IPv6 address per RFC 2373
are represented in the following example INDP URLs:
indp://[::192.9.5.5]/listener
indp://[::FFFF:129.144.52.38]/listener
indp://[2010:836B:4179::836B:4179]/listeners/tom
12.5.2 INDP URL Comparisons
When comparing two INDP URLs to decide if they match or not, an INDP
Client SHOULD use a case-sensitive octet-by-octet comparison of the
entire URLs, with these exceptions:
. A port that is empty or not given is equivalent to the well-
known port for that INDP URL (port [TBD]);
. Comparisons of host names MUST be case-insensitive;
. Comparisons of scheme names MUST be case-insensitive;
. An empty 'abs_path' is equivalent to an 'abs_path' of "/".
Characters other than those in the "reserved" and "unsafe" sets (see
[RFC2396] and [RFC2732]) are equivalent to their ""%" HEX HEX"
encoding.
For example, the following three URIs are equivalent:
indp://abc.com/~smith/listener
indp://ABC.com/%7Esmith/listener
indp://ABC.com:/%7esmith/listener
13 IANA Considerations
IANA is requested to register the indp URL scheme as defined in
section 12.
IANA is requested to assign a default system port (less than 1024)
for use with the indp URL as defined in section 12.
The rest of this section contains the exact information for IANA to
add to the IPP Registries according to the procedures defined in RFC
2911 [RFC2911] section 6.
Note to RFC Editors: Replace RFC NNNN below with the RFC number
for this document, so that it accurately reflects the content of
the information for the IANA Registry.
13.1 Operation Registrations
The operations defined in this document will be published by IANA
according to the procedures in RFC 2911 [RFC2911] section 6.4 with
the following path:
ftp.isi.edu/iana/assignments/ipp/operations/
The registry entry will contain the following information:
Operations: Ref. Section:
Send-Notifications operation RFC NNNN 8.1
13.2 Additional values of existing attributes
13.2.1 Additional values for the "notify-schemes-supported" Printer
attribute
The "notify-schemes-supported" uriScheme attribute value defined in
this document will be published by IANA according to the procedures
in RFC 2911 [RFC2911] section 6.1 with the following path:
ftp.isi.edu/iana/assignments/ipp/attribute-values/notify-schemes-
supported/
The registry entry will contain the following information:
Ref. Section:
indp RFC NNNN 6.2.1
13.2.2 Additional values for the "operations-supported" Printer
attribute
The "operations-supported" type2 enum attribute value defined in this
document will be published by IANA according to the procedures in RFC
2911 [RFC2911] section 6.1 with the following path:
ftp.isi.edu/iana/assignments/ipp/attribute-values/operations-
supported/
The registry entry will contain the following information:
Value Ref. Section:
Send-Notifications 0x001D RFC NNNN 6.2.1
13.3 Status code Registrations
The status codes defined in this document will be published by IANA
according to the procedures in RFC 2911 [RFC2911] section 6.6 with
the following path:
ftp.isi.edu/iana/assignments/ipp/status-codes/
The registry entry will contain the following information:
Status codes: Ref. Section:
successful-ok-ignored-notifications (0x0004) RFC NNNN 9.1.1
client-error-ignored-all-notifications (0x0416) RFC NNNN 9.1.2
14 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.
15 Security Considerations
The IPP Model and Semantics document [RFC2911] 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 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.
15.1 Security Conformance
Printers (client) MAY support Digest Authentication [RFC2617]. If
Digest Authentication is supported, then MD5 and MD5-sess MUST be Digest Authentication is supported, then MD5 and MD5-sess MUST be
supported, but the Message Integrity feature NEED NOT be supported. supported, but the Message Integrity feature NEED NOT be supported.
Notification Recipient (server) MAY support Digest Authentication Notification Recipient (server) MAY support Digest Authentication
[rfc2617]. If Digest Authentication is supported, then MD5 and MD5-sess [RFC2617]. If Digest Authentication is supported, then MD5 and MD5-
sess MUST be supported, but the Message Integrity feature NEED NOT be
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
MUST be supported, but the Message Integrity feature NEED NOT be
supported. supported.
Notification Recipients MAY support TLS for client authentication, Notification Recipients MAY support TLS for client authentication,
server authentication and operation privacy. If a Notification Recipient server authentication and operation privacy. If a Notification
supports TLS, it MUST support the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA Recipient supports TLS, it MUST support the
cipher suite as mandated by RFC 2246 [rfc2246]. All other cipher suites TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite as mandated by RFC
are OPTIONAL. Notification recipients MAY support Basic Authentication 2246 [RFC2246]. All other cipher suites are OPTIONAL. Notification
(described in HTTP/1.1 [rfc2616]) for client authentication if the recipients MAY support Basic Authentication (described in HTTP/1.1
channel is secure. TLS with the above mandated cipher suite can provide [RFC2616]) for client authentication if the channel is secure. TLS
such a secure channel. with the above mandated cipher suite can provide such a secure
channel.
15 References 16 References
[ipp-iig] [ipp-iig]
Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P., Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P.,
"Internet Printing Protocol/1.1: draft-ietf-ipp-implementers- "Internet Printing Protocol/1.1: draft-ietf-ipp-implementers-
guide-v11-01.txt, work in progress, May 9, 2000 guide-v11-02.txt, work in progress, January 25, 2001
[ipp-mod]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.1: Model and Semantics", <draft-ietf-
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-04.txt>, Notification Specification", <draft-ietf-ipp-not-spec-06.txt>,
August 30, 2000. January 24, 2001.
[ipp-pro] [IANA-MIMEREG]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing IANA MIME Media Types Registry. ftp://ftp.isi.edu/in-
Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
06.txt, May 30, 2000.
[rfc2026] notes/iana/assignments/media-types/
[IANA-PORTREG]
IANA Port Numbers Registry. ftp://ftp.isi.edu/in-
notes/iana/assignments/port-numbers
[RFC1900]
B. Carpenter, Y. Rekhter. Renumbering Needs Work, RFC 1900,
February 1996.
[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.
[rfc2616] [RFC2373]
R. Hinden, S. Deering. IP Version 6 Addressing Architecture, RFC
2373, July 1998.
[RFC2396]
Berners-Lee, T. et al. Uniform Resource Identifiers (URI): Generic
Syntax, RFC 2396, August 1998
[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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol [RFC2617]
August 29, 2000
[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.
16 Author's Addresses [RFC2717]
R. Petke and I. King, "Registration Procedures for URL Scheme
Names", RFC 2717, November 1999.
[RFC2732]
R. Hinden, B. Carpenter, L. Masinter. Format for Literal IPv6
Addresses in URL's, RFC 2732, December 1999.
[RFC2910]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
Protocol/1.1: Encoding and Transport", RFC 2910, September 2001.
[RFC2911]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.1: Model and Semantics", RFC 2911,
September 2001.
17 Author's Addresses
Hugo Parra Hugo Parra
Novell, Inc. Novell, Inc.
1800 South Novell Place 1800 South Novell Place
Provo, UT 84606 Provo, UT 84606
Phone: 801-861-3307 Phone: 801-861-3307
Fax: 801-861-2517 Fax: 801-861-2517
e-mail: hparra@novell.com e-mail: hparra@novell.com
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo, CA 90245 El Segundo, CA 90245
skipping to change at page 27, line 32 skipping to change at page 30, line 39
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo, CA 90245 El Segundo, CA 90245
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
e-mail: hastings@cp10.es.xerox.com e-mail: hastings@cp10.es.xerox.com
17 Full Copyright Statement 18 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
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
assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are included kind, provided that the above copyright notice and this paragraph are
on all such copies and derivative works. However, this document itself included on all such copies and derivative works. However, this
may not be modified in any way, such as by removing the copyright notice document itself may not be modified in any way, such as by removing
or references to the Internet Society or other Internet organizations, the copyright notice or references to the Internet Society or other
except as needed for the purpose of developing Internet standards in Internet organizations, except as needed for the purpose of
which case the procedures for copyrights defined in the Internet developing Internet standards in which case the procedures for
Standards process must be followed, or as required to translate it into copyrights defined in the Internet Standards process must be
languages other than English. followed, or as required to translate it into 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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol This document and the information contained herein is provided on an
August 29, 2000 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK 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.
This document and the information contained herein is provided on an "AS Acknowledgement
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT Funding for the RFC Editor function is currently provided by the
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT Internet Society.
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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