draft-ietf-ipp-indp-method-02.txt   draft-ietf-ipp-indp-method-03.txt 
INTERNET-DRAFT INTERNET-DRAFT
<draft-ietf-ipp-indp-method-02.txt> <draft-ietf-ipp-indp-method-03.txt>
Hugo Parra Category: standards track Hugo Parra
Novell, Inc. Novell, Inc.
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
July 14, 2000 August 29, 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'indp' Delivery Method for Event Notifications and Protocol/1.0
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 45 skipping to change at page 2, line 5
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 a
Printer and carry out other operations on them. The Subscription Object Printer and carry out other operations on them. The Subscription Object
specifies that when one of the specified Events occurs, the Printer specifies that when one of the specified Events occurs, the Printer
sends an asynchronous Event Notification to the specified Notification sends an asynchronous Event Notification to the specified Notification
Recipient via the specified Delivery Method (i.e., protocol). 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 Protocol.
This Delivery Method is a simple protocol consisting of a single This Delivery Method is a simple protocol consisting of a single
operation: the Send-Notifications operation which uses the same encoding operation: the Send-Notifications operation which uses the same encoding
and transport as IPP. This document defines version '1.0' of the and transport as IPP. This document defines version '1.0' of the
protocol. protocol.
For this Delivery Method, when an Event occurs, the Printer immediately For this Delivery Method, when an Event occurs, the Printer immediately
sends (pushes) an Event Notification via the Send-Notifications sends (pushes) an Event Notification via the Send-Notifications
operation to the Notification Recipient specified in the Subscription operation to the Notification Recipient specified in the Subscription
Expires: January 14, 2001
Object. The Event Notification content consists of Machine Consumable Object. The Event Notification content consists of Machine Consumable
attributes and a Human Consumable "notify-text" attribute. The attributes and a Human Consumable "notify-text" attribute. The
Notification Recipient returns a response to the Printer. Notification Recipient returns a response to the Printer.
Expires: January 14, 2001 INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
The full set of IPP documents includes: The basic 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]
Internet Printing Protocol (IPP): IPP Event Notification Internet Printing Protocol (IPP): IPP Event Notification
Specification [ipp-ntfy] Specification [ipp-ntfy]
skipping to change at page 3, line 52 skipping to change at page 4, line 4
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
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 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 14, 2001 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 2 Terminology.......................................................7
3 Model and Operation...............................................8 3 Model and Operation...............................................8
4 General Information...............................................8 4 General Information ...............................................9
5 Subscription object attributes...................................10 5 Subscription object attributes ...................................12
5.1Subscription Template Attribute Conformance.....................10 5.1 SUBSCRIPTION TEMPLATE ATTRIBUTE CONFORMANCE.....................12
5.2Additional Information about Subscription Template Attributes...10 5.2 ADDITIONAL INFORMATION ABOUT SUBSCRIPTION TEMPLATE ATTRIBUTES...13
5.2.1 notify-recipient-uri (uri)................................10 5.2.1 ....................................notify-recipient-uri (uri)
5.3Subscription Description Attribute Conformance..................11 13
5.3 SUBSCRIPTION DESCRIPTION ATTRIBUTE CONFORMANCE..................13
6 Printer Description Attributes...................................11 6 Printer Description Attributes ...................................13
6.1Printer Description Attribute Conformance.......................11 6.1 PRINTER DESCRIPTION ATTRIBUTE CONFORMANCE.......................13
6.2New Values for Existing Printer Description Attributes..........11 6.2 NEW VALUES FOR EXISTING PRINTER DESCRIPTION ATTRIBUTES..........14
6.2.1 notify-schemes-supported (1setOf uriScheme)...............11 6.2.1 ...................notify-schemes-supported (1setOf uriScheme)
6.2.2 operations-supported (1setOf type2 enum)..................11 14
6.2.2 ......................operations-supported (1setOf type2 enum)
14
7 Attributes Only in Event Notifications...........................12 7 Attributes Only in Event Notifications ...........................14
8 Operations for Notification......................................12 8 Operations for Notification ......................................15
8.1Send-Notifications operation....................................12 8.1 SEND-NOTIFICATIONS OPERATION....................................15
8.1.1 Send-Notifications Request................................13 8.1.1 ....................................Send-Notifications Request
8.1.2 Send-Notifications Response...............................15 16
8.1.2 ...................................Send-Notifications Response
20
9 Status Codes.....................................................17 9 Status Codes .....................................................22
9.1Additional Status Codes.........................................17 9.1 ADDITIONAL STATUS CODES.........................................22
9.1.1 successful-ok-ignored-notifications (0x0004)..............17 9.1.1 ..................successful-ok-ignored-notifications (0x0004)
9.2Status Codes returned in Event Notification Attributes Groups...17 22
9.2.1 client-error-not-found (0x0406)...........................18 9.2 STATUS CODES RETURNED IN EVENT NOTIFICATION ATTRIBUTES GROUPS...22
9.2.2 successful-ok-but-cancel-subscription (0x0006)............18 9.2.1 ...............................client-error-not-found (0x0406)
23
9.2.2 ................successful-ok-but-cancel-subscription (0x0006)
23
10 Encoding and Transport...........................................18 10 Encoding and Transport ...........................................23
10.1 Encoding of the Operation Layer...............................18
10.2 Encoding of Transport Layer...................................18
11 Conformance Requirements.........................................18 INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
11.1 Printer Conformance Requirements..............................19 August 29, 2000
11.2 Notification Recipient Requirements...........................19
12 IANA Considerations..............................................19 10.1 ENCODING OF THE OPERATION LAYER ...............................23
10.2 ENCODING OF TRANSPORT LAYER ...................................24
13 Internationalization Considerations..............................19 11 Conformance Requirements .........................................24
11.1 PRINTER CONFORMANCE REQUIREMENTS ..............................24
11.2 NOTIFICATION RECIPIENT REQUIREMENTS ...........................25
14 Security Considerations..........................................19 12 IANA Considerations ..............................................25
Expires: January 14, 2001 13 Internationalization Considerations ..............................25
14.1 Security Conformance..........................................20
15 References.......................................................20 14 Security Considerations ..........................................25
14.1 SECURITY CONFORMANCE ..........................................25
16 Author's Addresses...............................................21 15 References .......................................................26
17 Full Copyright Statement.........................................21 16 Author's Addresses ...............................................27
17 Full Copyright Statement .........................................27
Tables Tables
Table 1 - Information about the Delivery Method.......................8 Table 1 - Information about the Delivery Method.......................9
Table 2 . Operation-id assignments...................................12 Table 2 - Operation-id assignments...................................14
Table 3 . Attributes in Event Notification Content...................13 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...........................................................14 Events ...........................................................19
Table 5 . Combinations of Events and Subscribed Events for "job- Table 5 - Combinations of Events and Subscribed Events for "job-
impressions-completed"...........................................15 impressions-completed" ...........................................19
Table 6 . Additional Attributes in Event Notification Content for Table 6 - Additional Attributes in Event Notification Content for
Printer Events...................................................15 Printer Events ...................................................20
Expires: January 14, 2001 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 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).
skipping to change at page 7, line 47 skipping to change at page 8, line 4
This section defines the following terms that are used throughout this This section defines the following terms that are used throughout this
document: 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 [ipp-mod]
section 12.2. section 12.2.
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
conformance as specified in RFC 2119 [RFC2119] and [ipp-mod] 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, section 12.1. These terms refer to conformance to this document,
if this document is implemented. 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] with
the same meanings and are not reproduced here. 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.
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-
skipping to change at page 8, line 39 skipping to change at page 9, line 5
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 10.2 for more details. 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
'indp' Delivery Method, the client MUST choose a value for "notify-
recipient-uri" attribute which conforms to the rules of section 5.2.1.
When an Event occurs, the Printer MUST immediately:
1. Find all pertinent Subscription Objects P according to the rules of
section 9 of [ipp-ntfy], AND
2. Find the subset M of these Subscription Objects P whose "notify-
recipient-uri" attribute has a scheme value of 'indp', AND
3. For each Subscription Object in M, the Printer MUST
a)generate a Send-Notifications request as specified in section
8.1.1 AND
b)send the Send-Notifications request to the Notification
Recipient specified by the address part of the "notify-
recipient-uri" attribute value (see section 5.2.1).
If several events occur sufficiently close to one another for the same
or different Subscription objects, but with the same Notification
Recipient, the Printer MAY combine them into a single Send-Notifications
request using a separate Event Notification 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 RECOMMENDED 2.Is the Delivery Method is
REQUIRED, RECOMMENDED, or REQUIRED, RECOMMENDED, or
OPTIONAL for an IPP Printer to OPTIONAL for an IPP Printer to RECOMMENDED
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 to deliver the Event [rfc2616]
Notification content, i.e.,
Expires: January 14, 2001
Document Method conformance 'indp' realization
requirement
Notification content, i.e., [rfc2616]
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
8.1.1 8.1.1
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
August 29, 2000
Document Method conformance 'indp' realization
requirement
7.What section in this The representation and encoding 7.What section in this The representation and encoding
document answers the following is the same as IPP. See 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 Consumable
Event Notification, what is the Event Notification, what is the
skipping to change at page 10, line 5 skipping to change at page 11, line 40
9.What are 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 delivery protocol, e.g., how it
is handled in firewalls? is handled in firewalls?
10. What are the content They are the same as for 10. What are the content They are the same as for
length restrictions? IPP/1.0 and IPP/1.1 itself (see length restrictions? IPP/1.0 and IPP/1.1 itself (see
[ipp-mod]). [ipp-mod]).
Expires: January 14, 2001
Document Method conformance 'indp' realization
requirement
11. What are the additional A new Event Notifications 11. What are the 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 sends in an 10.1) and additional status that a Printer sends in an 10.1) and additional status
Event Notification and the codes for use in the response Event Notification and the codes for use in the response
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
Document Method conformance 'indp' realization
requirement
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 None 13. What are the additional
Printer Description attributes Printer Description attributes
and the conformance and the conformance None
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.
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 Template
attributes defined in [ipp-ntfy]. attributes defined in [ipp-ntfy].
5.2.1 notify-recipient-uri (uri) 5.2.1 notify-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 the
'indp' Delivery Method. The syntax for values of this attribute for 'indp' Delivery Method. The syntax for values of this attribute for
other Delivery Method is defined in other Delivery Method Documents. 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 Printer
MUST support the following syntax: MUST support the following syntax:
Expires: January 14, 2001
The 'indp://' URI scheme. The remainder of the URI indicates the The 'indp://' URI scheme. The remainder of the URI indicates the
host and address of the Notification Recipient that is to receive host and address of the Notification Recipient that is to receive
the Send-Notification operation. 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.
skipping to change at page 11, line 29 skipping to change at page 14, line 5
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 Description
attributes. attributes.
6.2.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:
skipping to change at page 12, line 5 skipping to change at page 14, line 29
document. document.
6.2.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
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 Notifications
besides those defined in [ipp-ntfy]. 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 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.
8.1 Send-Notifications operation 8.1 Send-Notifications operation
skipping to change at page 13, line 5 skipping to change at page 16, line 5
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: 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-error-
forbidden', 'client-error-not-authenticated', or 'client-error-not- forbidden', 'client-error-not-authenticated', or 'client-error-not-
authorized' status code , the Printer SHOULD cancel the subscription. authorized' status code , the Printer SHOULD cancel the subscription.
Expires: January 14, 2001 INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
8.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" '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 contents of the Subscription object's - a "request-id" - the request id (see [ipp-mod] section 3.1.2).
"notify-sequence-number" after incrementing for the first try
(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:
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.
The Printer MUST use the values of "notify-charset" and "notify-
natural-language", respectively, from one Subscription Object
associated with the Event Notifications in this request.
Normally, there is only one matched Subscription Object, or the
value of the "notify-charset" and "notify-natural-language"
attributes is the same in all Subscription Objects. If not, the
Printer MUST pick one Subscription Object from which to obtain the
value of these attributes. The algorithm for picking the
Subscription Object is implementation dependent. The choice of
natural language is not critical because 'text' and 'name' values
can override the "attributes-natural-language" Operation attribute.
The Printer's choice of charset is critical because a bad choice
may leave it unable to send some 'text' and 'name' values
accurately.
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 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 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.
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 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
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 *** attribute, if any ***
attributes from the "notify-attributes" MUST Job attributes from the "notify-attributes" MUST *** Job
attribute *** attribute, if any ***
attributes from the "notify-attributes" MUST Subscription attributes from the "notify-attributes" MUST *** Subscription
attribute *** 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 it
supports the "printer-current-time" attribute on the Printer 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 and the 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
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)) *
* 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'
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 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
8.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 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 [ipp-mod].
The Notification Recipient can return any status codes defined in The Notification Recipient can return any status codes defined in
skipping to change at page 17, line 5 skipping to change at page 21, line 50
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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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 Status Codes 9 Status Codes
skipping to change at page 17, line 47 skipping to change at page 22, line 45
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 8.1.2 for further details. Notifications request. See section 8.1.2 for further details.
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 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 4. was not consumed OR
2. was consumed, but the Notification Recipient wants to cancel the 5. 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
August 29, 2000
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.
Expires: January 14, 2001
9.2.1 client-error-not-found (0x0406) 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 8.1.2 for Attributes Group because it was not expected. See section 8.1.2 for
further details. further details.
skipping to change at page 18, line 39 skipping to change at page 24, line 5
10.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"
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
10.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 11 Conformance Requirements
This section defines conformance requirements for Printers and This section defines conformance requirements for Printers and
Notification Recipients. Notification Recipients.
Expires: January 14, 2001
11.1 Printer Conformance Requirements 11.1 Printer Conformance Requirements
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: If the Printer supports the 'indp' Delivery Method, the Printer MUST:
1.meet the conformance requirements defined in [ipp-ntfy]. 1.meet the conformance requirements defined in [ipp-ntfy].
2.support the conformance requirements for Subscription object 2.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
skipping to change at page 19, line 29 skipping to change at page 25, line 5
3.support the conformance requirements for Printer Description object 3.support the conformance requirements for Printer Description object
attributes defined in section 6. attributes defined in section 6.
4.support the 'indp' protocol by sending Event Notifications using the 4.support the 'indp' protocol by sending Event Notifications using the
Send-Notifications operation defined in section 8.1. Send-Notifications operation defined in section 8.1.
5.support sending Event Notification via email with the content 5.support sending Event Notification via email with the content
specified in section 8.1.1. specified in section 8.1.1.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
11.2 Notification Recipient Requirements 11.2 Notification Recipient Requirements
A Notification Recipient MUST accept Send-Notifications requests and A Notification Recipient MUST accept Send-Notifications requests and
return Send-Notifications responses as defined in sections 8 and 9. 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 and Protocol will The 'indp' URL scheme for the 'indp' Delivery Method and Protocol will
be registered with IANA. IANA will assign a default port to use with be registered with IANA. IANA will assign a default port to use with
the 'indp' Delivery Method and Protocol. the 'indp' Delivery Method and Protocol.
skipping to change at page 20, line 4 skipping to change at page 25, line 35
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.
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
Printers (client) MAY support Digest Authentication [rfc2617]. If 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
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
MUST be supported, but the Message Integrity feature NEED NOT be 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 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
[ipp-iig]
Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P.,
"Internet Printing Protocol/1.1: draft-ietf-ipp-implementers-
guide-v11-01.txt, work in progress, May 9, 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.1: 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-04.txt>, July Notification Specification", <draft-ietf-ipp-not-spec-04.txt>,
13, 2000. August 30, 2000.
[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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
[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.
16 Author's Addresses 16 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
skipping to change at page 21, line 57 skipping to change at page 28, line 5
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
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.
INTERNET-DRAFTIPP: The 'indp' Notification Delivery Method and Protocol
August 29, 2000
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 14, 2001
 End of changes. 

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