draft-ietf-ipp-notify-mailto-02.txt   draft-ietf-ipp-notify-mailto-03.txt 
INTERNET-DRAFT INTERNET-DRAFT
<draft-ietf-ipp-notify-mailto-02.txt> Robert Herriot <draft-ietf-ipp-notify-mailto-03.txt> Robert Herriot
Xerox Corp. Category: standards track Xerox Corp.
Henrik Holst Henrik Holst
i-data international a/s i-data international a/s
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
Carl-Uno Manros Carl-Uno Manros
Xerox Corp. Xerox Corp.
July 13, 2000 August 30, 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'mailto:' Notification Delivery Method The 'mailto' Delivery Method for Event Notifications
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 2, line 5 skipping to change at page 2, line 5
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. The Subscription Object 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).
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 'mailto' delivery method. such document, and it specifies the 'mailto' delivery method.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
For this Delivery Method, when an Event occurs, the Printer immediately For this Delivery Method, when an Event occurs, the Printer immediately
sends an Event Notification via an email message to the Notification sends an Event Notification via an email message to the Notification
Recipient specified in the Subscription Object. The message body of the Recipient specified in the Subscription Object. The message body of the
email consists of Human Consumable text and is not intended to be parsed email consists of Human Consumable text that is not intended to be
by a machine. parsed by a machine.
The Notification Recipient receives the Event Notification in the same The Notification Recipient receives the Event Notification in the same
way as it receives any other email message. way as it receives any other email message.
The full set of IPP documents includes: PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
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 4, line 5 skipping to change at page 4, line 5
defines a new scheme named 'ipp' for identifying IPP printers and jobs. defines a new scheme named 'ipp' for identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document gives The "Internet Printing Protocol/1.1: Implementer's Guide" document gives
insight and advice to implementers of IPP clients and IPP objects. It insight and advice to implementers of IPP clients and IPP objects. It
is intended to help them understand IPP/1.1 and some of the is intended to help them understand IPP/1.1 and some of the
considerations that may assist them in the design of their client and/or considerations that may assist them in the design of their client and/or
IPP object implementations. For example, a typical order of processing IPP object implementations. For example, a typical order of processing
requests is given, including error checking. Motivation for some of the requests is given, including error checking. Motivation for some of the
specification decisions is also included. specification decisions is also included.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
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.
The "Event Notification Specification" document describes an extension The "Event Notification Specification" document describes an extension
to the IPP/1.0, IPP/1.1, and future versions. This extension allows a to the IPP/1.0, IPP/1.1, and future versions. This extension allows a
client to subscribe to printing related Events. The Subscription Object client to subscribe to printing related Events. The Subscription Object
specifies that when one of the specified Event occurs, the Printer sends specifies that when one of the specified Event occurs, the Printer sends
an asynchronous Event Notification to the specified Notification an asynchronous Event Notification to the specified Notification
Recipient via the specified Delivery Method (i.e., protocol). A client Recipient via the specified Delivery Method (i.e., protocol). A client
associates Subscription Objects with a particular Job by performing the associates Subscription Objects with a particular Job by performing the
Create-Job-Subscriptions operation or by submitting a Job with Create-Job-Subscriptions operation or by submitting a Job with
subscription information. A client associates Subscription Objects with subscription information. A client associates Subscription Objects with
the Printer by performing a Create-Printer-Subscriptions operation. the Printer by performing a Create-Printer-Subscriptions operation.
Four other operations are defined for Subscription Objects: Get- Four other operations are defined for Subscription Objects: Get-
Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and
Cancel-Subscription. Cancel-Subscription.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Table of Contents Table of Contents
1 Introduction ......................................................7 1 Introduction ......................................................7
2 Terminology .......................................................7 2 Terminology .......................................................7
3 Model and Operation ...............................................7 3 Model and Operation ...............................................7
4 General Information ...............................................9 4 General Information ...............................................9
5 Subscription Template Attributes .................................11 5 Subscription Template Attributes .................................11
5.1 Additional Subscription Template Attributes ...................11 5.1 Additional Subscription Template Attributes ...................11
5.1.1 notify-mailto-text-only (boolean)..........................11 5.1.1 notify-mailto-text-only (boolean)..........................11
5.2 Additional Information about Subscription Template Attributes .12 5.2 Additional Information about Subscription Template Attributes .12
5.2.1 notify-recipient-uri (uri).................................12 5.2.1 notify-recipient-uri (uri).................................12
5.2.2 notify-user-data (octetString(63)).........................12 5.2.2 notify-user-data (octetString(63)).........................12
6 Event Notification Content .......................................13 6 Event Notification Content .......................................13
6.1 Headers .......................................................13 6.1 Headers .......................................................13
6.1.1 'Date' header..............................................13 6.1.1 'Date' header..............................................13
6.1.2 'From' header..............................................13 6.1.2 'From' header..............................................14
6.1.3 'Subject' header...........................................14 6.1.3 'Subject' header...........................................14
6.1.4 'Sender' header............................................14 6.1.4 'Sender' header............................................15
6.1.5 'Reply-to' header..........................................15 6.1.5 'Reply-to' header..........................................15
6.1.6 'To' header................................................15 6.1.6 'To' header................................................15
6.1.7 'Content-type' header......................................16 6.1.7 'Content-type' header......................................16
6.2 Message Body ..................................................16 6.2 Message Body ..................................................16
6.2.1 Event Notification Content Common to All Events............17 6.3 Plain Text Content ............................................17
6.2.2 Additional Event Notification Content for Job Events.......19 6.3.1 Event Notification Content Common to All Events............18
6.2.3 Additional Event Notification Content for Printer Events...20 6.3.2 Additional Event Notification Content for Job Events.......20
6.3 Examples ......................................................21 6.3.3 Additional Event Notification Content for Printer Events...21
6.3.1 Job Event Example..........................................21 6.4 Examples ......................................................21
6.3.2 Printer Event Example......................................23 6.4.1 Job Event Example..........................................22
6.3.3 Printer Event Example (localized to Danish)...............24 6.4.2 Printer Event Example......................................23
6.4.3 Printer Event Example (localized to Danish)...............24
7 Conformance Requirements .........................................25 7 Conformance Requirements .........................................25
8 IANA Considerations ..............................................25 8 IANA Considerations ..............................................26
9 Internationalization Considerations ..............................26 9 Internationalization Considerations ..............................26
10 Security Considerations ..........................................26 10 Security Considerations ..........................................26
11 References .......................................................27 11 References .......................................................27
12 Author's Addresses ...............................................28 12 Author's Addresses ...............................................28
13 Full Copyright Statement .........................................29 13 Full Copyright Statement .........................................29
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Table of Tables Table of Tables
Table 1 - Information about the Delivery Method.......................9 Table 1 - Information about the Delivery Method.......................9
Table 2 - Printer Name in Event Notification Content.................18 Table 2 - Additional Subscription Template Attributes................11
Table 3 - Event Name in Event Notification Content...................19 Table 3 - Printer Name in Event Notification Content.................19
Table 4 - Job Name in Event Notification Content.....................19 Table 4 - Event Name in Event Notification Content...................19
Table 5 - Job State in Event Notification Content....................20 Table 5 - Job Name in Event Notification Content.....................20
Table 6 - Printer State in Event Notification Content................21 Table 6 - Job State in Event Notification Content....................20
Table 7 - Printer State in Event Notification Content................21
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 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).
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 'mailto' delivery method. such document, and it specifies the 'mailto' delivery method.
For this Delivery Method, when an Event occurs, the Printer immediately For this Delivery Method, when an Event occurs, the Printer immediately
sends an Event Notification via an email message to the Notification sends an Event Notification via an email message to the Notification
Recipient specified in the Subscription Object. The message body of the Recipient specified in the Subscription Object. The message body of the
email consists of Human Consumable text and is not intended to be parsed email consists of Human Consumable text that is not intended to be
by a machine. The 'mailto' Delivery Method is a 'push' Delivery Method parsed by a machine. The 'mailto' Delivery Method is a 'push' Delivery
as defined in [ipp-ntfy]. Method as defined in [ipp-ntfy].
The Notification Recipient receives the Event Notification in the same The Notification Recipient receives the Event Notification in the same
way as it receives any other email message. way as it receives any other email message.
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 this
document: document:
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT,
skipping to change at page 8, line 5 skipping to change at page 8, line 5
For capitalized terms that appear in this document, see [ipp-ntfy]. For capitalized terms that appear in this document, see [ipp-ntfy].
3 Model and Operation 3 Model and Operation
In a Subscription Creation Operation, when the value of the "notify- In a Subscription Creation Operation, when the value of the "notify-
recipient-uri" attribute contains the scheme "mailto", the client is recipient-uri" attribute contains the scheme "mailto", the client is
requesting that the Printer use the 'mailto' Delivery Method for Event requesting that the Printer use the 'mailto' Delivery Method for Event
Notifications generated from the new Subscription Object. Notifications generated from the new Subscription Object.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
For this Delivery Method, the "notify-recipient-uri" attribute value For this Delivery Method, the "notify-recipient-uri" attribute value
MUST consist of a "mailto" scheme followed by a colon, and then followed MUST consist of a "mailto" scheme followed by a colon, and then followed
by an address part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for by an address part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for
the syntax of the "notify-recipient-uri" attribute value for this the syntax of the "notify-recipient-uri" attribute value for this
Delivery Method. Delivery Method.
A Printer MUST support SMTP [RFC821], and it MAY support other email A Printer MUST support SMTP [RFC821], and it MAY support other email
protocols. A Printer MAY use additional services, such as SMTP delivery protocols. A Printer MAY use additional services, such as SMTP delivery
status notification [RFC1891] or S/MIME encryption [RFC2633]. status notification [RFC1891] or S/MIME encryption [RFC2633].
skipping to change at page 8, line 43 skipping to change at page 8, line 45
b)send the email message to the Notification Recipient specified b)send the email message to the Notification Recipient specified
by the address part of the "notify-recipient-uri" attribute by the address part of the "notify-recipient-uri" attribute
value (see section 5.2.1). value (see section 5.2.1).
If the Printer supports only SMTP, it MUST send the email message via If the Printer supports only SMTP, it MUST send the email message via
SMTP. If the Printer supports additional email protocols, it MUST SMTP. If the Printer supports additional email protocols, it MUST
determine the protocol from the address part of the "notify-recipient- determine the protocol from the address part of the "notify-recipient-
uri" attribute value and then send the email message via the appropriate uri" attribute value and then send the email message via the appropriate
email protocol. email protocol.
When a Subscription Object is listening to a frequently occurring Event, When a Subscribing Client is subscribing to the 'job-progress' event
such as 'job-progress', the Printer MUST moderate the sending of Event (which is a frequently occurring event), it SHOULD supply the "notify-
Notifications caused by such an Event. It is implementation dependent as PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
to how a Printer moderates Events and how a human controls the
moderation. time-interval" attribute (see [ipp-ntfy]) in the Subscription Creation
request with a suitable value to limit the time between 'job-progress'
Event Notifications sent by the Printer.
4 General Information 4 General Information
If a Printer supports this Delivery Method, the following are its If a Printer supports this Delivery Method, the following are its
characteristics. characteristics.
Table 1 - Information about the Delivery Method Table 1 - Information about the Delivery Method
Document Method Conformance Delivery Method Realization Document Method Conformance Delivery Method Realization
Requirement Requirement
1. What is the URL scheme name mailto 1. What is the URL scheme name mailto
for the Delivery Method? for the Delivery Method?
2. Is the Delivery Method RECOMMENDED 2.Is the Delivery Method
REQUIRED, RECOMMEND, or REQUIRED, RECOMMENDED, or
OPTIONAL for an IPP Printer OPTIONAL for an IPP Printer to RECOMMENDED
to support? support?
3. What transport and delivery 3.What transport and delivery A Printer MUST support SMTP. It MAY
protocols does the Printer use support other email protocols. protocols does the Printer use support other email protocols.
to deliver the Event to deliver the Event
Notification Content, i.e., Notification Content, i.e.,
what is the entire network A Printer MUST support SMTP. It MAY 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 Notifications be combined into combine several Event Notifications
a Compound Event Notification? into a single email message. a Compound Event Notification? into a single email message.
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 Human Consumable 6. Is the Event Notification Human Consumable
content Machine Consumable or content Machine Consumable or
Human Consumable? Human Consumable?
7. What section in this document Section 6 7. What section in this document Section 6
answers the following answers the following
question? For a Machine question? For a Machine
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
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 thereof? For a Human
Consumable Event Notification, Consumable Event Notification,
what is the representation and what is the representation and
encoding of pieces of encoding of pieces of
information defined in section information defined in section
9.2 of [ipp-ntfy] and the 9.2 of [ipp-ntfy] and the
conformance requirements conformance requirements
thereof? thereof?
8. What are the latency and 8.What are the latency and Same as the underlying SMTP (or
reliability of the transport Same as the underlaying SMTP (or other reliability of the transport other optional) email transport
and delivery protocol? optional email transport) and delivery protocol?
9. What are the security aspects 9.What are the security aspects Same as the underlying SMTP (or
of the transport and delivery Same as the underlying SMTP (or other of the transport and delivery other optional) email transport
protocol, e.g., how it is optional email transport) protocol, e.g., how it is
handled in firewalls? handled in firewalls?
10. What are the content length None 10. What are the content length None
restrictions? restrictions?
11. What are the additional None 11. What are the additional None
values or pieces of values or pieces of
information that a Printer information that a Printer
sends in an Event Notification sends in an Event Notification
content and the conformance content and the conformance
skipping to change at page 11, line 5 skipping to change at page 11, line 5
Subscription Template and/or mailto-text-only" Subscription Template and/or mailto-text-only"
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 None
Printer Description attributes Printer Description attributes
and the conformance and the conformance
requirements thereof? requirements thereof?
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
5 Subscription Template Attributes 5 Subscription Template Attributes
5.1 Additional Subscription Template Attributes 5.1 Additional Subscription Template Attributes
This Delivery Method introduces one additional Subscription Template This Delivery Method introduces one additional Subscription Template
Attribute. Attribute (See Table 2).
Table 2 - Additional Subscription Template Attributes
Attribute in Subscription Default and Supported Printer
Object Attributes
notify-mailto-text-only N/A
(boolean)
5.1.1 notify-mailto-text-only (boolean) 5.1.1 notify-mailto-text-only (boolean)
When the Printer generates an Event Notification from a Subscription When the Printer generates an Event Notification from a Subscription
Object, this attribute specifies whether the Printer generates the Event Object, this attribute specifies whether the Printer generates the Event
Notification with only plain text (i.e. 'text/plain') or with Content- Notification with only plain text (i.e. 'text/plain') or with Content-
Types that the Printer chooses. Types that the Printer chooses.
The Printer MUST support this attribute if it supports the 'mailto' The Printer MUST support this attribute if it supports the 'mailto'
Delivery Method. Delivery Method.
skipping to change at page 11, line 34 skipping to change at page 11, line 44
'false' on the Subscription Object. There is no "notify-mailto-text- 'false' on the Subscription Object. There is no "notify-mailto-text-
only-default" attribute. only-default" attribute.
If the value of this attribute is 'true' in a Subscription Object, the If the value of this attribute is 'true' in a Subscription Object, the
message body of each Event Notification that the Printer generates from message body of each Event Notification that the Printer generates from
the Subscription Object MUST contain plain text only (i.e. 'text/plain' the Subscription Object MUST contain plain text only (i.e. 'text/plain'
with the charset specified by the "notify-charset' Subscription Object with the charset specified by the "notify-charset' Subscription Object
attribute). attribute).
If the value of this attribute is 'false' in a Subscription Object, the If the value of this attribute is 'false' in a Subscription Object, the
message body of each Event Notification that the Printer generates from Content-Type of the message body of each Event Notification that the
the Subscription Object MUST contain a 'multipart/alternative'. One Printer generates from the Subscription Object MUST be either
message body of the 'multipart/alternative' MUST be the same as the
'text/plain' message body when this attribute has the value of 'true'. PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Each of the other message bodies of the 'multipart/alternative' MAY be
any Content-Type (e.g. 'text/html', 'image/gif', 'audio/basic', etc.). 'text/plain' or 'multipart', depending on implementation. If the
Content-Type is 'multipart', one message body of the 'multipart' MUST be
the same as the 'text/plain' message body when this attribute has the
value of 'true'. Each of the other message bodies of the 'multipart' MAY
be any Content-Type (e.g. 'text/html', 'image/gif', 'audio/basic',
etc.).
A Printer MUST support both values ('true' and 'false') of this A Printer MUST support both values ('true' and 'false') of this
attribute. There is no "notify-mailto-text-only-supported" attribute. attribute. There is no "notify-mailto-text-only-supported" attribute.
5.2 Additional Information about Subscription Template Attributes 5.2 Additional Information about Subscription Template Attributes
This section describes additional values for attributes defined in [ipp- This section describes additional values for attributes defined in [ipp-
ntfy]. ntfy].
5.2.1 notify-recipient-uri (uri) 5.2.1 notify-recipient-uri (uri)
skipping to change at page 12, line 24 skipping to change at page 12, line 36
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 'mailto' Delivery Method, the Printer MUST In order to support the 'mailto' Delivery Method, the Printer MUST
support the following syntax for the 'mailto' Delivery Method when the support the following syntax for the 'mailto' Delivery Method when the
Printer uses SMTP. The line below use RFC 822 syntax rules and terms. Printer uses SMTP. The line below use RFC 822 syntax rules and terms.
"mailto:" mailbox "mailto:" mailbox
Note: the above syntax allows 1 occurrence of 'mailbox'. The occurrence Note: the above syntax allows 1 occurrence of 'mailbox'. The occurrence
of 'mailbox' represents an email address of a Notification Recipient. of 'mailbox' represents an email address of a Notification Recipient.
This syntax
For SMTP, the phrase 'address part' of the "notify-recipient-uri" For SMTP, the phrase 'address part' of the "notify-recipient-uri"
attribute value refers to the 'mailbox' part of the value. attribute value refers to the 'mailbox' part of the value.
The Printer MAY support other syntax for the 'address part' if it The Printer MAY support other syntax for the 'address part' if it
supports email protocols in addition to SMTP. supports email protocols in addition to SMTP.
5.2.2 notify-user-data (octetString(63)) 5.2.2 notify-user-data (octetString(63))
This attributes has a special use for the 'mailto' Delivery Method. It This attributes has a special use for the 'mailto' Delivery Method. It
specifies the email address of the Subscribing Client. It is primarily specifies the email address of the Subscribing Client. It is primarily
useful when the Notification Recipient is some person other than the useful when the Notification Recipient is some person other than the
Subscribing Client. Then the Notification Recipient has a way to reply Subscribing Client. Then the Notification Recipient has a way to reply
to the Subscribing Client. to the Subscribing Client.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
If a client specifies this Delivery Method in a Subscription Creation If a client specifies this Delivery Method in a Subscription Creation
Operation, and the specified Notification Recipient is not associated Operation, and the specified Notification Recipient is not associated
with the same person as the client, the client SHOULD supply its email with the same person as the client, the client SHOULD supply its email
address as the value of the "notify-user-data" attribute. If the client address as the value of the "notify-user-data" attribute. If the client
does not supply this attribute, the Printer MUST NOT populate the does not supply this attribute, the Printer MUST NOT populate the
Subscription Object with this attribute. Subscription Object with this attribute.
6 Event Notification Content 6 Event Notification Content
This section describes the content of an Event Notification sent via the This section describes the content of an Event Notification sent via the
skipping to change at page 13, line 41 skipping to change at page 14, line 5
6.1.1 'Date' header 6.1.1 'Date' header
Syntax: "Date" ":" date-time Syntax: "Date" ":" date-time
This header contains the date and time that the Event occurred. This header contains the date and time that the Event occurred.
The Printer MUST include a "Date" header if and only if it supports the The Printer MUST include a "Date" header if and only if it supports the
"printer-current-time" Printer attribute. "printer-current-time" Printer attribute.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
6.1.2 'From' header 6.1.2 'From' header
Syntax: "From" ":" mailbox Syntax: "From" ":" mailbox
where where
mailbox = addr-spec / phrase route-addr mailbox = addr-spec / phrase route-addr
This header causes a typical email reader to show the email as coming This header causes a typical email reader to show the email as coming
from the Printer that is sending the Event Notification. from the Printer that is sending the Event Notification.
skipping to change at page 14, line 44 skipping to change at page 15, line 5
For Printer Events, the '*text' SHOULD start with the localized word For Printer Events, the '*text' SHOULD start with the localized word
"printer:", followed by the Printer name, and then followed by the "printer:", followed by the Printer name, and then followed by the
localized Event name, e.g., in English: "printer: 'tiger' stopped" or in localized Event name, e.g., in English: "printer: 'tiger' stopped" or in
Danish: 'Printeren 'tiger' er standset'. Danish: 'Printeren 'tiger' er standset'.
For Job Events, the '*text' SHOULD start with the localized phrase For Job Events, the '*text' SHOULD start with the localized phrase
"print job:", followed by the Job name, and then followed by the "print job:", followed by the Job name, and then followed by the
localized Event name, e.g., in English: "print job: 'financials' localized Event name, e.g., in English: "print job: 'financials'
completed". completed".
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
The wording is implementation dependent. A Notification Recipient MUST The wording is implementation dependent. A Notification Recipient MUST
NOT expect to be able to parse this text. But an email filter might look NOT expect to be able to parse this text. But an email filter might look
for "printer" or "print job". for "printer" or "print job".
6.1.4 'Sender' header 6.1.4 'Sender' header
Syntax: "Sender" ":" mailbox Syntax: "Sender" ":" mailbox
This header causes a typical email reader to show the email as coming on This header causes a typical email reader to show the email as coming on
behalf of the person associated with the Subscribing Client. behalf of the person associated with the Subscribing Client.
skipping to change at page 15, line 41 skipping to change at page 16, line 5
For the "Reply-to" header, the "mailbox" MUST be the value of the For the "Reply-to" header, the "mailbox" MUST be the value of the
"notify-user-data" Subscription Object attribute. See section 5.2.2 for "notify-user-data" Subscription Object attribute. See section 5.2.2 for
details about the "notify-user-data" attribute. details about the "notify-user-data" attribute.
6.1.6 'To' header 6.1.6 'To' header
Syntax: "To" ":" 1#mailbox Syntax: "To" ":" 1#mailbox
See [RFC 1521] for the syntax. See [RFC 1521] for the syntax.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
This header specifies the Notification Recipient(s). This header specifies the Notification Recipient(s).
The Printer MUST include a "To" header whose syntax is specified above. The Printer MUST include a "To" header whose syntax is specified above.
The '1#mailbox' MUST be the '1#mailbox' part of the value of the The '1#mailbox' MUST be the '1#mailbox' part of the value of the
"notify-recipient-uri" Subscription attribute, i.e. the part after the "notify-recipient-uri" Subscription attribute, i.e. the part after the
"mailto:". "mailto:".
6.1.7 'Content-type' header 6.1.7 'Content-type' header
Syntax: "Content-Type" ":" type "/" subtype *(";"parameter) Syntax: "Content-Type" ":" type "/" subtype *(";"parameter)
See [RFC 1521] for the syntactic terms (e.g. 'type'). See [RFC 1521] for the syntactic terms (e.g. 'type').
This header specifies the format of the message body. This header specifies the format of the message body.
The Printer MUST include the "Content-Type" header. The Printer MUST include the "Content-Type" header.
If the value of the "notify-mailto-text-only" Subscription Object The "notify-mailto-text-only" attribute determines the 'type' and
attribute is 'true', the 'type' MUST be "plain", the 'subtype' MUST be 'subtype' values. The possible values are "text/plain" and "multipart"
"text" and the 'parameter' MUST be ' "charset=" XXX' where XXX is the values.
value of the "notify-charset" Subscription Object attribute, e.g.
'text/plain;charset=UTF-8'.
If the value of the "notify-mailto-text-only" Subscription Object
attribute is 'false', the 'type' MUST be "multipart", the 'subtype' MUST
be "alternative" and the 'parameter' MUST include the boundary string.
Each header of a body part of a multipart entity also has a Content-Type
and its value of 'type', 'subtype' and 'parameter' MUST be values
allowed by RFC 1521 or some registered MIME type. That is, a Printer MAY
send any format it wishes in each body part of a multipart entity, e.g.
'text/html', 'image/gif', or 'audio/basic'.
6.2 Message Body 6.2 Message Body
This document describes a message body that is plain text. The content The message body MUST contain Human Consumable content as plain text. It
of all other Content-Types is implementation dependent. A Printer MUST MAY also contain other types of implementation dependent content.
include a plain text message even when it sends other Content-Types in a
'multipart/alternative'. For plain text, the Content-Type of Human Consumable content MUST be
'text/plain'. For implementation dependent content, the Content-Type of
Human Consumable content MUST be 'multipart'. The Content-Type of one
body part MUST be 'text/plain' and the Content-Types of the other body
parts are implementation dependent. See section 6.3 for a description of
plain text content.
The following table shows the Content-Type of the message body for the
"notify-mailto-text-only" attribute:
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
"notify- Content-Type Message Body
mailto-text- of Message
only" Body
attribute
false 'text/plain' Human Consumable
true 'text/plain' Human Consumable plain
or* text
'multipart' Human Consumable where
one body part is plain
text
* The Content-Type depends on the implementation. A Printer MAY send
'text/plain' only or it MAY send several body parts of various
Content-Types within a message body whose Content-Type is
'multipart'.
6.3 Plain Text Content
When a Printer sends a plain text message, it MUST localize the text When a Printer sends a plain text message, it MUST localize the text
using the values of the "notify-charset" and "notify-natural-language" using the values of the "notify-charset" and "notify-natural-language"
Subscription Object attributes. Subscription Object attributes.
Section 9.2 in [ipp-ntfy] specifies the information that a Delivery Section 9.2 in [ipp-ntfy] specifies the information that a Delivery
Method MUST specify and a Printer SHOULD send. This section contains the Method MUST specify and a Printer SHOULD send.
information from section 9.2 in [ipp-ntfy] and changes "Printer SHOULD
send" to "Printer MUST send".
A Printer MUST send the following localized information in the message A Printer SHOULD send the following localized information in the message
body. The specific wording of this information and its layout are body. The specific wording of this information and its layout are
implementation dependent. implementation dependent.
a)the Printer name (see Table 2) a)the Printer name (see Table 3)
b)omitted (see below). b)omitted (see below).
c)for Printer Events only: c)for Printer Events only:
i) the Event (see Table 3) and/or Printer state information i) the Event (see Table 4) and/or Printer state information
(see Table 6) (see Table 7)
d)for Job Events only: d)for Job Events only:
i) the job identity (see Table 4) i) the job identity (see Table 5)
ii) the Event (see Table 3) and/or Job state information (see ii) the Event (see Table 4) and/or Job state information (see
Table 5) Table 6)
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Item b) in the above list is omitted because the Printer sends the time Item b) in the above list is omitted because the Printer sends the time
of the Event as an email header (see section 6.1.1 on the 'Date' of the Event as an email header (see section 6.1.1 on the 'Date'
header). header).
The subsections of this section specify the attributes that a Printer The subsections of this section specify the attributes that a Printer
MUST use to obtain this information. MUST use to obtain this information.
The Printer MAY send additional information, depending on The Printer MAY send additional information, depending on
implementation. implementation.
skipping to change at page 17, line 36 skipping to change at page 18, line 28
The next three sections define the attributes in Event Notification The next three sections define the attributes in Event Notification
Contents that are: Contents that are:
a) for all Events a) for all Events
b) for Job Events only b) for Job Events only
c) for Printer Events only c) for Printer Events only
6.2.1 Event Notification Content Common to All Events 6.3.1Event Notification Content Common to All Events
The Printer MUST send the following information. The Printer MUST send the following information.
There is a separate table for each piece of information. Each row in the There is a separate table for each piece of information. Each row in the
table represents a source value for the information and the values are table represents a source value for the information and the values are
listed in order of preference, with the first one being the preferred listed in order of preference, with the first one being the preferred
one. An implementation SHOULD use the source value from the earliest row one. An implementation SHOULD use the source value from the earliest row
in each table. It MAY use the source value from another row instead, or in each table. It MAY use the source value from another row instead, or
it MAY combine the source values from several rows. An implementation is it MAY combine the source values from several rows. An implementation is
free to determine the best way to present this information. free to determine the best way to present this information.
The tables in this section and following contain the following columns The tables in this section and following sections contain the following
for each piece of information: columns for each piece of information:
a) Source of Value: the name of the attribute that supplies the a) Source of Value: the name of the attribute that supplies the
value for the Event Notification value for the Event Notification
b) Sends: if the Printer supports the value (column 1) on the PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Source Object (column 3) the Delivery Method MUST specify
MUST: that the Printer MUST send the value.
SHOULD: either that the Printer MUST send the value or that b)Sends:
the value is incompatible with the Delivery Method.
MAY: that the Printer MUST, SHOULD, MAY, MUST NOT, SHOULD NOT, MAY: this is the only value used in the tables. It means that
or NEED NOT send the value. The Delivery Method specifies the the Printer OPTIONALLY sends this value. However, the Printer
level of conformance for the Printer. SHOULD use at least one value from each table.
c) Source Object: the object from which the source value comes. c) Source Object: the object from which the source value comes.
In all tables of this section, all rows contain a "MAY" in order to Table 3 lists the source of the information for the Printer Name. The
state that the Delivery Method specifies the conformance.
Table 2 lists the source of the information for the Printer Name. The
"printer-name" is more user-friendly unless the Notification Recipient "printer-name" is more user-friendly unless the Notification Recipient
is in a place where the Printer name is not meaningful. For example, an is in a place where the Printer name is not meaningful. For example, an
implementation could have the intelligence to send the value of the implementation could have the intelligence to send the value of the
"printer-name" attribute to a Notification Recipient that can access the "printer-name" attribute to a Notification Recipient that can access the
Printer via value of the "printer-name" attribute and otherwise send the Printer via value of the "printer-name" attribute and otherwise send the
value of the "notify-printer-uri" attribute. value of the "notify-printer-uri" attribute.
Table 2 - Printer Name in Event Notification Content Table 3 - Printer Name in Event Notification Content
Source Value Sends Source Object Source Value Sends Source Object
printer-name (name(127)) MAY Printer printer-name (name(127)) MAY Printer
Source Value Sends Source Object
notify-printer-uri (uri) MAY Subscription notify-printer-uri (uri) MAY Subscription
Table 3 lists the source of the information for the Event name. A Table 4 lists the source of the information for the Event name. A
Printer MAY combine this information with state information described Printer MAY combine this information with state information described
for Jobs in Table 5 or for Printers in Table 6. for Jobs in Table 6 or for Printers in Table 7.
Table 3 - Event Name in Event Notification Content Table 4 - Event Name in Event Notification Content
Source Value Sends Source Object Source Value Sends Source Object
notify-subscribed-event (type2 keyword) MAY Subscription notify-subscribed-event (type2 keyword) MAY Subscription
6.2.2 Additional Event Notification Content for Job Events PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
6.3.2Additional Event Notification Content for Job Events
This section lists the source of the additional information that a This section lists the source of the additional information that a
Printer MUST send for Job Events. Printer MUST send for Job Events.
Table 4 lists the source of the information for the job name. The "job- Table 5 lists the source of the information for the job name. The "job-
name" is likely more meaningful to a user than "job-id". name" is likely more meaningful to a user than "job-id".
Table 4 - Job Name in Event Notification Content Table 5 - Job Name in Event Notification Content
Source Value Sends Source Object Source Value Sends Source Object
job-name (name(MAX)) MAY Job job-name (name(MAX)) MAY Job
Source Value Sends Source Object
job-id (integer(1:MAX)) MAY Job job-id (integer(1:MAX)) MAY Job
Table 5 lists the source of the information for the job-state. If a Table 6 lists the source of the information for the job-state. If a
Printer supports the "job-state-message" and "job-detailed-state- Printer supports the "job-state-message" and "job-detailed-state-
message" attributes, it SHOULD use those attributes for the job state message" attributes, it SHOULD use those attributes for the job state
information, otherwise, it should fabricate such information from the information, otherwise, it should fabricate such information from the
"job-state" and "job-state-reasons". For some Events, a Printer MAY "job-state" and "job-state-reasons". For some Events, a Printer MAY
combine this information with Event information. combine this information with Event information.
Table 5 - Job State in Event Notification Content Table 6 - Job State in Event Notification Content
Source Value Sends Source Source Value Sends Source
Object Object
job-state-message (text(MAX)) MAY Job job-state-message (text(MAX)) MAY Job
job-detailed-status-messages (1setOf MAY Job job-detailed-status-messages (1setOf MAY Job
text(MAX)) text(MAX))
job-state (type1 enum) MAY Job job-state (type1 enum) MAY Job
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Source Value Sends Source
Object
job-state-reasons (1setOf type2 keyword) MAY Job job-state-reasons (1setOf type2 keyword) MAY Job
6.2.3 Additional Event Notification Content for Printer Events 6.3.3Additional Event Notification Content for Printer Events
This section lists the source of the additional information that a This section lists the source of the additional information that a
Printer MUST send for Printer Events. Printer MUST send for Printer Events.
Table 6 lists the source of the information for the printer-state. If a Table 7 lists the source of the information for the printer-state. If a
Printer supports the "printer-state-message", it SHOULD use that Printer supports the "printer-state-message", it SHOULD use that
attribute for the job state information, otherwise it SHOULD fabricate attribute for the job state information, otherwise it SHOULD fabricate
such information from the "printer-state" and "printer-state-reasons". such information from the "printer-state" and "printer-state-reasons".
For some Events, a Printer MAY combine this information with Event For some Events, a Printer MAY combine this information with Event
information. information.
Table 6 - Printer State in Event Notification Content Table 7 - Printer State in Event Notification Content
Source Value Sends Source Object Source Value Sends Source Object
printer-state-message (text(MAX)) MAY Printer printer-state-message (text(MAX)) MAY Printer
printer-state (type1 enum) MAY Printer printer-state (type1 enum) MAY Printer
printer-state-reasons (1setOf type2 MAY Printer printer-state-reasons (1setOf type2 MAY Printer
keyword) keyword)
printer-is-accepting-jobs (boolean) MAY Printer printer-is-accepting-jobs (boolean) MAY Printer
6.3 Examples 6.4 Examples
This section contains three examples. One is a Job Event and the other This section contains three examples. One is a Job Event and the other
two are Printer Events, the latter in Danish. two are Printer Events, the latter in Danish.
A Printer implementation NEED NOT generate Event Notification content A Printer implementation NEED NOT generate Event Notification content
that is identical or even similar to these examples. In fact it would be that is identical or even similar to these examples. In fact it would be
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
unfortunate if every implementation copied these example as is. These unfortunate if every implementation copied these example as is. These
examples merely show some possibilities and are not necessarily the best examples merely show some possibilities and are not necessarily the best
way to convey information about an Event. way to convey information about an Event.
6.3.1 Job Event Example 6.4.1Job Event Example
This section contains an example of an Event Notification of a Job This section contains an example of an Event Notification of a Job
Event. Event.
A Subscribing Client Mike Jones (who works for xyz Corp.) performs a A Subscribing Client Mike Jones (who works for xyz Corp.) performs a
Subscription Creation Operation as part of the Print-Job operation on Subscription Creation Operation as part of the Print-Job operation on
Printer "ipp://tiger@abc.com". Mike Jones specifies that the "job-name" Printer "ipp://tiger@abc.com". Mike Jones specifies that the "job-name"
is "financials". Mike is printing the Job for Bill Smith at abc Corp. is "financials". Mike is printing the Job for Bill Smith at abc Corp.
The Subscription Object then has the following attributes: The Subscription Object then has the following attributes:
skipping to change at page 22, line 32 skipping to change at page 23, line 5
notify-printer-up-time 34593 notify-printer-up-time 34593
notify-printer-uri ipp://tiger@abc.com notify-printer-uri ipp://tiger@abc.com
notify-job-id 345 notify-job-id 345
notify-subscriber-user- mjones notify-subscriber-user- mjones
name name
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
When the Job completes, the Printer generates and sends the following When the Job completes, the Printer generates and sends the following
email message: email message:
Date: 17 Jul 00 1632 PDT Date: 17 Jul 00 1632 PDT
From: tiger <printAdmin@abc.com> From: tiger <printAdmin@abc.com>
Subject: print job: 'financials' completed Subject: print job: 'financials' completed
Sender: mjones@xyz.com Sender: mjones@xyz.com
Reply-to: mjones@xyz.com Reply-to: mjones@xyz.com
To: bsmith@abc.com To: bsmith@abc.com
Content-type: text/plain Content-type: text/plain
printer: tiger printer: tiger
job: financials job: financials
job-state: completed job-state: completed
The reader should note that the phrases are not identical to IPP The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English. keywords. They have been localized to English.
6.3.2 Printer Event Example 6.4.2Printer Event Example
This section contains an example of an Event Notification of a Printer This section contains an example of an Event Notification of a Printer
Event. Event.
A Subscribing Client Peter Williams, a Printer admin, performs a Create- A Subscribing Client Peter Williams, a Printer admin, performs a Create-
Printer-Subscriptions operation on Printer "ipp://tiger@abc.com". The Printer-Subscriptions operation on Printer "ipp://tiger@abc.com". The
Subscription Object then has the following attributes: Subscription Object then has the following attributes:
Attribute Name Attribute Value Attribute Name Attribute Value
skipping to change at page 23, line 30 skipping to change at page 24, line 5
notify-mailto-text-only true notify-mailto-text-only true
notify-charset us-ascii notify-charset us-ascii
notify-natural-language en-us notify-natural-language en-us
notify-subscription-id 4623 notify-subscription-id 4623
notify-sequence-number 0 notify-sequence-number 0
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Attribute Name Attribute Value
notify-printer-uptime 23002 notify-printer-uptime 23002
notify-printer-uri ipp://tiger@abc.com notify-printer-uri ipp://tiger@abc.com
notify-lease-expiration- 0 notify-lease-expiration- 0
time time
notify-subscriber-user- pwilliams notify-subscriber-user- pwilliams
name name
skipping to change at page 24, line 4 skipping to change at page 24, line 27
name name
When the Printer jams, the Printer generates and sends the following When the Printer jams, the Printer generates and sends the following
email message: email message:
Date: 29 Aug 00 0832 PDT Date: 29 Aug 00 0832 PDT
From: tiger <printAdmin@abc.com> From: tiger <printAdmin@abc.com>
Subject: printer: 'tiger' has stopped Subject: printer: 'tiger' has stopped
To: pwilliams@abc.com To: pwilliams@abc.com
Content-type: text/plain Content-type: text/plain
Printer tiger has stopped with a paper jam. Printer tiger has stopped with a paper jam.
The reader should note that the phrases are not identical to IPP The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English. keywords. They have been localized to English.
6.3.3 Printer Event Example (localized to Danish) 6.4.3Printer Event Example (localized to Danish)
This section contains an example of an Event Notification of a Printer This section contains an example of an Event Notification of a Printer
Event localized to Danish. Event localized to Danish.
A Subscribing Client Per Jensen, a Printer admin, performs a a Create- A Subscribing Client Per Jensen, a Printer admin, performs a a Create-
Printer-Subscriptions operation on Printer "ipp://tiger@def.dk". The Printer-Subscriptions operation on Printer "ipp://tiger@def.dk". The
Subscription Object then has the following attributes: Subscription Object then has the following attributes:
Attribute Name Attribute Value Attribute Name Attribute Value
notify-recipient-uri mailto:pjensen@def.dk notify-recipient-uri mailto:pjensen@def.dk
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Attribute Name Attribute Value
notify-events printer-state-changed notify-events printer-state-changed
notify-mailto-text-only true notify-mailto-text-only true
notify-charset utf-8 notify-charset utf-8
notify-natural-language da notify-natural-language da
notify-subscription-id 50225 notify-subscription-id 50225
skipping to change at page 25, line 18 skipping to change at page 25, line 47
To: pjensen@def.dk To: pjensen@def.dk
Content-type: text/plain;charset=utf-8 Content-type: text/plain;charset=utf-8
Printerens navn er 'tiger'. Printerens navn er 'tiger'.
Printeren er standset. Printeren er standset.
Aarsagen er papir stop. Aarsagen er papir stop.
7 Conformance Requirements 7 Conformance Requirements
The 'mailto' Delivery Method is RECOMMENDED for a Printer to support. The 'mailto' Delivery Method is RECOMMENDED for a Printer to support.
If the Printer supports the 'mailto' Delivery Method, the Printer MUST: If the Printer supports the 'mailto' Delivery Method, the Printer MUST:
1. meet the conformance requirements defined in [ipp-ntfy]. 1. meet the conformance requirements defined in [ipp-ntfy].
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
2. support the "notify-mailto-text-only " Subscription Object attribute 2. support the "notify-mailto-text-only " Subscription Object attribute
defined in section 5.1.1. defined in section 5.1.1.
3. support the syntax for the "notify-recipient-uri" Subscription Object 3. support the syntax for the "notify-recipient-uri" Subscription Object
attribute defined in section 5.2.1 attribute defined in section 5.2.1
4. support the use for the "notify-user-data" Subscription Object 4. support the use for the "notify-user-data" Subscription Object
attribute defined in section 5.2.2 attribute defined in section 5.2.2
5. support SMTP for sending Event Notifications. 5. support SMTP for sending Event Notifications.
skipping to change at page 26, line 22 skipping to change at page 27, line 5
because the Printer does all necessary localization to the Event because the Printer does all necessary localization to the Event
Notification contents. Notification contents.
10 Security Considerations 10 Security Considerations
The biggest security concern is that a Subscribing Client will cause The biggest security concern is that a Subscribing Client will cause
unsolicited Event Notifications to be sent to third parties, potentially unsolicited Event Notifications to be sent to third parties, potentially
creating denial-of-service problems (i.e., spam). The problem is even creating denial-of-service problems (i.e., spam). The problem is even
worse if the third parties are distribution lists. worse if the third parties are distribution lists.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
There exist scenarios where third party notification is required (see There exist scenarios where third party notification is required (see
Scenario #2 and #3 in [ipp-not-req]). The fully secure solution would Scenario #2 and #3 in [ipp-not-req]). The fully secure solution would
require active agreement of all persons before they can become require active agreement of all persons before they can become
Notification Recipients. However, requirement #9 in [ipp-req] ("There Notification Recipients. However, requirement #9 in [ipp-req] ("There
is no requirement for IPP Printer receiving the print request to is no requirement for IPP Printer receiving the print request to
validate the identity of an event recipient") argues against this. To validate the identity of an event recipient") argues against this. To
minimize the risk, a Printer could disallow third party Notification minimize the risk, a Printer could disallow third party Notification
Recipients (a traditional facsimile model). Recipients (a traditional facsimile model).
The Delivery Method recommends that the Subscribing Client supply his or The Delivery Method recommends that the Subscribing Client supply his or
skipping to change at page 27, line 12 skipping to change at page 27, line 37
allows the Subscribing Client to request that the Content-Type of a allows the Subscribing Client to request that the Content-Type of a
message body be 'text/plain'. message body be 'text/plain'.
11 References 11 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-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
"Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf- Printing Protocol/1.0: Model and Semantics", <draft-ietf-ipp-model-v11-
ipp-model-v11-06.txt>, March 1, 2000. 07.txt>, May 22, 2000.[ipp-ntfy]
Herriot, R., Hastings, T., Isaacson, S., Martin, J., deBry, R.,
[ipp-ntfy] Shepherd, M., Bergman, R., "Internet Printing Protocol/1.1: IPP
Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M., Event Notification Specification", <draft-ietf-ipp-not-spec-
Bergman, R., "Internet Printing Protocol/1.1: IPP Event 04.txt>, August 30, 2000.
Notification Specification", <draft-ietf-ipp-not-spec-04.txt>, July
13, 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-
05.txt, March 1, 2000. 06.txt, May 20, 2000.
[RFC821] [RFC821]
Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821, Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821,
August, 1982. August, 1982.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
[RFC822] [RFC822]
David H. Crocker, "Standard For The Format Of ARPA Internet Text David H. Crocker, "Standard For The Format Of ARPA Internet Text
Messages", RFC 822, August 13, 1982. Messages", RFC 822, August 13, 1982.
[RFC1341] [RFC1341]
N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail
Extensions): Mechanisms for Specifying and Describing the Format of Extensions): Mechanisms for Specifying and Describing the Format of
Internet Message Bodies", RFC 1341, June, 1992. Internet Message Bodies", RFC 1341, June, 1992.
[RFC1521] [RFC1521]
skipping to change at page 28, line 38 skipping to change at page 29, line 5
B. Ramsdell, "S/MIME Version 3 Message Specification", RFC 2633, B. Ramsdell, "S/MIME Version 3 Message Specification", RFC 2633,
June 1999. June 1999.
12 Author's Addresses 12 Author's Addresses
Robert Herriot Robert Herriot
Xerox Corporation Xerox Corporation
3400 Hillview Ave., Bldg #1 3400 Hillview Ave., Bldg #1
Palo Alto, CA 94304 Palo Alto, CA 94304
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
Phone: 650-813-7696 Phone: 650-813-7696
Fax: 650-813-6860 Fax: 650-813-6860
Email: robert.herriot@pahv.xerox.com Email: robert.herriot@pahv.xerox.com
Henrik Holst Henrik Holst
i-data international a/s i-data international a/s
Vadstrupvej 35-43 Vadstrupvej 35-43
2880 Bagsvaerd, Denmark 2880 Bagsvaerd, Denmark
Phone: +45 4436-6000 Phone: +45 4436-6000
skipping to change at page 29, line 35 skipping to change at page 30, line 5
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
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.
PWG-DRAFT IPP: The 'mailto:' Delivery Method August 30, 2000
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
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.
 End of changes. 

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