draft-ietf-ipp-notify-mailto-00.txt   draft-ietf-ipp-notify-mailto-01.txt 
INTERNET-DRAFT INTERNET-DRAFT
<draft-ietf-ipp-notify-mailto-00.txt> Henrik Holst <draft-ietf-ipp-notify-mailto-01.txt> Robert Herriot
Xerox Corp.
Henrik Holst
i-data international a/s i-data international a/s
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
March 9, 2000 Carl-Uno Manros
Xerox Corp.
July 7, 2000
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'mailto:' Notification Delivery Method The 'mailto:' Notification Delivery Method
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress". or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed as The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
The IPP notification specification [ipp-ntfy] is an OPTIONAL extension The notification extension document [ipp-ntfy] defines operations that a
to IPP/1.0 and IPP/1.1 that requires the definition of one or more client can perform in order to create Subscription Objects in a Printer
delivery methods for dispatching event notification reports to and carry out other operations on them. The Subscription Object
Notification Recipients. This document describes the semantics and specifies that when one of the specified Events occurs, the Printer
syntax of the 'mailto:' event notification delivery method. For this sends an asynchronous Event Notification to the specified Notification
delivery method, the IPP Printer uses the SMTP mail protocol to send Recipient via the specified Delivery Method (i.e., protocol).
(push) Human Consumable and/or Machine Consumable Notifications to
Notification Recipients. The Subscriber specifies the mail address
using the mailto: URL. This mail address can be any user or can be any
of the mail services defined to perform such notification using
parameters in the URL, such as paging. The Subscriber can specify the
MIME media type of both the Human Consumable and Machine Consumable
Notifications. The Subscriber can also specify a mail address in the
"subscriber-user-data" Subscription attribute to which the Notification
Recipient can reply and to which the mail system delivers undeliverable
mail messages. That mail address is usually the Subscribers mail
address, but can be any mail address.
The mail messages appear to come from the Printer, so that mail agents The notification extension document [ipp-ntfy] specifies that each
can sort and filter on the From: field. Also the beginning of the Delivery Method is defined in another document. This document is one
such document, and it specifies the 'mailto' delivery method.
Expires: September 9, 2000 For this Delivery Method, when an Event occurs, the Printer immediately
sends an Event Notification via an email message to the Notification
Recipient specified in the Subscription Object. The message body of the
email consists of Human Consumable text and is not intended to be parsed
by a machine.
Subject line starts with the localized "Printer message: " prefix, so INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
that mail agents can filter from any Printer. 2000
There are 7 ISSUES called out in the text. The Notification Recipient receives the Event Notification in the same
way as it receives any other email message.
Expires: September 9, 2000 INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
The full set of IPP documents includes: The full set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567] Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the Internet Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol [RFC2568] Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [ipp-mod] Internet Printing Protocol/1.1: Model and Semantics [ipp-mod]
Internet Printing Protocol/1.1: Encoding and Transport [ipp-pro] Internet Printing Protocol/1.1: Encoding and Transport [ipp-pro]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
Mapping between LPD and IPP Protocols [RFC2569] Mapping between LPD and IPP Protocols [RFC2569]
Internet Printing Protocol (IPP): Event Notification Specification Internet Printing Protocol (IPP): IPP Event Notification
[ipp-ntfy] Specification [ipp-ntfy]
The "Design Goals for an Internet Printing Protocol" document takes a The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that are administrators. It calls out a subset of end user requirements that are
satisfied in IPP/1.0. A few OPTIONAL operator operations have been satisfied in IPP/1.0. A few OPTIONAL operator operations have been
added to IPP/1.1. added to IPP/1.1.
skipping to change at page 3, line 46 skipping to change at page 3, line 47
and their operations that are independent of encoding and transport. It and their operations that are independent of encoding and transport. It
introduces a Printer and a Job object. The Job object optionally introduces a Printer and a Job object. The Job object optionally
supports multiple documents per Job. It also addresses security, supports multiple documents per Job. It also addresses security,
internationalization, and directory issues. internationalization, and directory issues.
The "Internet Printing Protocol/1.1: Encoding and Transport" document is The "Internet Printing Protocol/1.1: Encoding and Transport" document is
a formal mapping of the abstract operations and attributes defined in a formal mapping of the abstract operations and attributes defined in
the model document onto HTTP/1.1 [RFC2616]. It defines the encoding the model document onto HTTP/1.1 [RFC2616]. It defines the encoding
rules for a new Internet MIME media type called "application/ipp". This rules for a new Internet MIME media type called "application/ipp". This
document also defines the rules for transporting over HTTP a message document also defines the rules for transporting over HTTP a message
body whose Content-Type is "application/ipp". This document defines a body whose Content-Type is "application/ipp". This document also
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.
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: September 9, 2000 INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
The "Event Notification Specification" document extends the Job Creation The "Event Notification Specification" document describes an extension
operations and defines additional operations that allow a client to to the IPP/1.0, IPP/1.1, and future versions. This extension allows a
subscribe to printing related events. Subscriptions are modeled as client to subscribe to printing related Events. The Subscription Object
Subscription objects which can be Per-Job or Per-Printer Subscriptions. specifies that when one of the specified Event occurs, the Printer sends
Additional operations are defined to query, renew, and cancel an asynchronous Event Notification to the specified Notification
Subscription objects. Recipient via the specified Delivery Method (i.e., protocol). A client
associates Subscription Objects with a particular Job by performing the
Create-Job-Subscriptions operation or by submitting a Job with
subscription information. A client associates Subscription Objects with
the Printer by performing a Create-Printer-Subscriptions operation.
Four other operations are defined for Subscription Objects: Get-
Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and
Cancel-Subscription.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
Expires: September 9, 2000
Table of Contents Table of Contents
1 Introduction......................................................6 1 Introduction......................................................7
2 Terminology.......................................................6 2 Terminology.......................................................7
2.1Conformance Terminology..........................................6
2.2Other terminology................................................7
3 Model and Operation...............................................7 3 Model and Operation...............................................7
4 Sending Notifications.............................................8 4 General Information...............................................8
4.1notify-recipient (uri)...........................................8
4.2notify-events (1setOf type2 keyword).............................8
4.3notify-format (mimeMediaType)....................................9
4.4subscriber-user-data (octetString(63))...........................9
4.5notify-charset (charset)........................................10
4.6notify-natural-language (naturalLanguage).......................10
4.7request-id......................................................10
4.8subscription-id (integer (1:MAX))...............................10
4.9notify-lease-expiration-time (integer(0:MAX))...................10
4.10 printer-uri (uri).............................................10
4.11 subscriber-user-name (name(MAX))..............................11
4.12 notify-printer-up-time (integer(1:MAX)).......................11
4.13 notify-persistence-granted (boolean)..........................11
5 Mail Notification Content........................................11 5 Subscription Template Attributes..................................9
5.1Human Consumable Form...........................................13 5.1 Additional Subscription Template Attributes.....................9
5.2Machine Consumable Form.........................................13 5.1.1 notify-mailto-text-only (boolean)9
5.2 Additional Information about Subscription Template Attributes..10
5.2.1 notify-recipient-uri (uri).................................10
5.2.2 notify-user-data (octetString(63)).........................10
6 Printer Description attributes specific to the 'mailto:' delivery 6 Event Notification Content.......................................11
method...............................................................13 6.1 Headers........................................................11
6.1"printer-smtp-mail-service-address" (1setOf text(MAX))..........13 6.1.1 'Date' header..............................................11
6.1.2 'From' header..............................................11
6.1.3 'Subject' header...........................................12
6.1.4 'Sender' header............................................12
6.1.5 'Reply-to' header..........................................12
6.1.6 'To' header................................................13
6.1.7 'Content-type' header......................................13
6.2 Message Body...................................................13
6.2.1 Information in Event Notification Content Common to All Events
.............................................................14
6.2.2 Additional Information in Event Notification Content for Job
Events...........................................................15
6.2.3 Additional Information in Event Notification Content for
Printer Events...................................................16
6.3 Examples.......................................................16
6.3.1 Job Event Example..........................................16
6.3.2 Printer Event Example......................................18
6.3.3 Printer Event Example (localized to French)...............19
7 Conformance Requirements.........................................13 7 Conformance Requirements.........................................20
8 IANA Considerations..............................................14 8 IANA Considerations..............................................20
9 Internationalization Considerations..............................14 9 Internationalization Considerations..............................20
10 Security Considerations..........................................14 10 Security Considerations..........................................20
11 References.......................................................15 11 References.......................................................21
12 Author's Addresses...............................................16 12 Author's Addresses...............................................22
13 Full Copyright Statement.........................................16 13 Full Copyright Statement.........................................23
Table of Tables Table of Tables
Table 1 - SMTP Fields to be filled in................................12 INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
Expires: September 9, 2000 Table 1 . Printer Name in Event Notification Content.................15
Table 2 . Event Name in Event Notification Content 15
Table 4 . Job Name in Event Notification Content for Job Events......15
Table 5 . Job State in Event Notification Content for Job Events.....16
Table 6 . Printer State in Event Notification Content for Printer Events
.................................................................16
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
1 Introduction 1 Introduction
An IPP Printer that supports the OPTIONAL IPP notification extension The notification extension document [ipp-ntfy] defines operations that a
[ipp-ntfy] is called a Notification Source which sends event client can perform in order to create Subscription Objects in a Printer
Notifications to Notification Recipients. As such, a Printer either a) and carry out other operations on them. A Subscription Object represents
accepts, stores, and uses notification Subscription objects to generate a Subscription abstraction. The Subscription Object specifies that when
event Notification reports and implement one or more delivery methods one of the specified Events occurs, the Printer sends an asynchronous
for notifying interested parties, or b) supports a subset of these tasks Event Notification to the specified Notification Recipient via the
and farms out the remaining tasks to a Notification Delivery Service. specified Delivery Method (i.e., protocol).
This document describes the semantics and syntax of the 'mailto:' event
notification delivery method. Such a Notification Delivery Service then
delivers the event Notification to the Ultimate Notification Recipient.
For this delivery method, the IPP Printer uses the SMTP mail protocol to The notification extension document [ipp-ntfy] specifies that each
send (push) Human Consumable and/or Machine Consumable Notifications to Delivery Method is defined in another document. This document is one
Notification Recipients. The Subscriber specifies the mail address such document, and it specifies the 'mailto' delivery method.
using the mailto: URL. This mail address can be any user or can be any
of the mail services defined to perform such notification using
parameters in the URL, such as paging. The Subscriber can specify the
MIME media type of both the Human Consumable and Machine Consumable
Notifications. The Subscriber can also specify a mail address in the
"subscriber-user-data" Subscription attribute to which the Notification
Recipient can reply and to which the mail system delivers undeliverable
mail messages. That mail address is usually the Subscribers mail
address, but can be any mail address.
The mail messages appear to come from the Printer, so that mail agents For this Delivery Method, when an Event occurs, the Printer immediately
can sort and filter on the From: field. Also the beginning of the sends an Event Notification via an email message to the Notification
Subject line starts with the localized "Printer message: " prefix, so Recipient specified in the Subscription Object. The message body of the
that mail agents can filter from any Printer. email consists of Human Consumable text and is not intended to be parsed
by a machine. The 'mailto' Delivery Method is a 'push' Delivery Method
as defined in [ipp-ntfy].
The Notification Recipient receives the Event Notification in the same
way as it receives any other email message.
2 Terminology 2 Terminology
This section defines terminology used throughout this document: This section defines the following terms that are used throughout this
document:
2.1 Conformance Terminology Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT,
MAY, NEED NOT, and OPTIONAL, have special meaning relating to
conformance to this specification. These terms are defined in [ipp-mod
section 13.1 on conformance terminology, most of which is taken from RFC
2119 [RFC2119].
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD For capitalized terms that appear in this document, see [ipp-ntfy].
NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
conformance to this specification. These terms are defined in
[ipp-mod section 13.1 on conformance terminology, most of which is
taken from RFC 2119 [RFC2119].
REQUIRED - an adjective used to indicate that a conforming IPP
Printer implementation MUST support the indicated operation,
object, attribute, attribute value, status code, or out-of-band
value in requests and responses. See [ipp-mod] "Appendix A -
Terminology for a definition of "support". Since support of this
entire notification specification is OPTIONAL for conformance to
IPP/1.0 or IPP/1.1, the use of the term REQUIRED in this document
Expires: September 9, 2000 3 Model and Operation
means "REQUIRED if this OPTIONAL notification specification is
implemented".
OPTIONAL - an adjective used to indicate that a conforming IPP
Printer implementation MAY, but is NOT REQUIRED to, support the
indicated operation, object, attribute, attribute value, status
code, or out-of-band value in requests and responses.
2.2 Other terminology In a Subscription Creation Operation, when the value of the "notify-
recipient-uri" attribute contains the scheme "mailto", the client is
requesting that the Printer use the 'mailto' Delivery Method for Event
Notifications generated from the new Subscription Object.
Event Notification (Notification for short) - See [ipp-ntfy] For this Delivery Method, the "notify-recipient-uri" attribute value
Notification Source - See [ipp-ntfy] MUST consist of a "mailto" scheme followed by a colon, and then followed
Notification Recipient - See [ipp-ntfy] by an address part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for
Subscription object - See [ipp-ntfy] the syntax of the "notify-recipient-uri" attribute value for this
Ultimate Notification Recipient - See [ipp-ntfy] Delivery Method.
3 Model and Operation A Printer MUST support SMTP [RFC821], and it MAY support other email
protocols. A Printer MAY use additional services, such as SMTP delivery
status notification [RFC1891] or S/MIME encryption [RFC2633].
In the IPP Notification Model [ipp-ntfy], a client is able to: INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
1. supply one or more Per-Job Subscriptions in the Job Creation If the client wants the Printer to send Event Notifications via the
operation 'mailto' Delivery Method, the client MUST choose a value for "notify-
recipient-uri" attribute which conforms to the rules of section 5.2.1.
To avoid denial-of-service attacks, a client SHOULD NOT use distribution
lists as the Notification Recipient.
2. OPTIONALLY supply Per-Job Subscriptions as subsequent Create-Job- When an Event occurs, the Printer MUST immediately:
Subscription operations
3. supply one Per-Printer Subscription in the Create-Printer- 1. Find all pertinent Subscription Objects P according to the rules of
Subscription operation. The client that creates these Subscription section 9 of [ipp-ntfy], AND
objects becomes the owner of the Subscription object.
The client that creates these Subscription objects becomes the owner of 2. Find the subset M of these Subscription Objects P whose "notify-
the Subscription object. recipient-uri" attribute has a scheme value of 'mailto', AND
When creating each Subscription object, the client supplies the "notify- 3. For each Subscription Object in M, the Printer MUST
recipient" (uri) attribute. The "notify-recipient" attribute specifies
both a single Notification Recipient that is to receive the
Notifications when subsequent events occur and the method for
Notification delivery that the IPP Printer is to use. For the 'mailto:'
Notification delivery method defined in this document, the "notify-
recipient" consists of the 'mailto:' scheme followed by an SMPT mail
address [RFC822].
Notification Sources that implement the 'mailto:' event notification a)generate an email message as specified in section 5.2.2 AND
delivery method will need to include an SMTP mail agent while
Notification Recipients that implement this delivery method will need to
support an SMTP server. ISSUE 01: Is this SMTP terminology correct?
The IPP Printer can be the Notification Source or could use some other b)send the email message to the Notification Recipient specified
Notification Delivery Service that actually delivers the mail message. by the address part of the "notify-recipient-uri" attribute
In this latter case, the protocol between the IPP Printer and the value (see section 5.2.1).
Notification Delivery Service is implementation defined and could be the
INDP protocol (see [indp]).
Expires: September 9, 2000 If the Printer supports only SMTP, it MUST send the email message via
SMTP. If the Printer supports additional email protocols, it MUST
determine the protocol from the address part of the "notify-recipient-
uri" attribute value and then send the email message via the appropriate
email protocol.
Also the Notification Recipient specified by the "notify-recipient" When a Subscription Object is listening to a frequently occurring Event,
Subscription attribute can be either (1) the Ultimate Notification such as 'job-progress', the Printer MUST moderate the sending of Event
Recipient or can be a Notification Delivery Service, such as a paging Notifications caused by such an Event. It is implementation dependent as
system that accept 'mailto:' parameters to indicate the Ultimate to how a Printer moderates Events and how a human controls the
Notification Recipient, such as a phone number or paging subscriber's moderation.
id.
4 Sending Notifications 4 General Information
This section defines the processing that the IPP Printer MUST perform According to the notification extension document [ipp-ntfy], this
when sending an event Notification using the 'mailto:' delivery method. document MUST contain the following information:
The usage of each of the Subscription object attributes defined in [ipp-
ntfy] is described here as it applies to the 'mailto:' delivery method.
The description of each Subscription attribute in this document is not
the complete description, but is just the application of the attribute
to this 'mailto:' delivery method. See the complete definition of each
Subscription object attribute in [ipp-ntfy]. ISSUE 02: Is it a good
idea to list each Subscription object attribute in this spec with the
applicability to this delivery method? If yes, should all delivery
method specs also do it this way? Section 5 defines how the IPP Printer
populates the SMTP fields in the mail message.
4.1 notify-recipient (uri) 1.The URL scheme name for the Delivery Method is: 'mailto'
This REQUIRED READ-ONLY Subscription object attribute contain the 2.Printer support for this delivery method is OPTIONAL.
'mailto:' URI delivery method followed by the SMTP mail address [RFC821]
of the Notification Recipient. As required by the [ipp-ntfy] document,
the following information is given for this notification delivery
method:
ISSUE 03 - What should we say about any mailto parameters, if any? For 3.For Event Notification content, a Printer MUST support SMTP. It MAY
example, if you want to send over secure mail, etc. support other email protocols.
ISSUE 04 - Do we want to define any IPP-specific mailto parameters to 4.Several Event Notifications MUST NOT be combined into a compound
this document? Event Notification. The Printer MUST send them as separate email
messages.
4.2 notify-events (1setOf type2 keyword) 5.The Printer MUST initiate the Delivery Method.
This REQUIRED READ-ONLY Subscription object attribute identifies the job 6.The Delivery Method sends Human Consumable Event Notifications.
and/or printer events that are to be delivered to the Notification
Recipient as Notifications as defined in [ipp-ntfy] section 7.
Note: Some rapidly recurring events, such as page events, are not INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
appropriate to use with this delivery method, especially if the 2000
recipient mail address is a mailing list. Implementations MAY choose
either not to support page events with the 'mailto:' delivery method
and/or not permit a mailing list to be supplied, if they can detect that
a mail address is a mailing list.
Expires: September 9, 2000 7.The representation and encoding for each piece of information MUST be
plain text (see section 5.2.2). An implementation MAY send the
information in other encodings.
4.3 notify-format (mimeMediaType) 8.In the Event Notification content, a Printer MUST send all pieces of
information specified in section 5.2.2.
This REQUIRED READ-ONLY Subscription object attribute indicates the type 9.Frequently occurring Events MUST be moderated to prevent Notification
of Human Consumable and/or Machine Consumable format content that is to Recipients from receiving excessive email.
be sent in the Notifications as a mail message attachment. For the
'mailto:' delivery method, any registered 'mimeMediaType' value is
allowed, including types that allow pictures to be represented, e.g.,
'application/postscript' or 'image/tiff', and/or sounds to be
represented, e.g., 'audio/32kadpcm'. The body of the mail message MUST
always be 'text/plain; charset=us-ascii, since that is the default for
'mailto:'.
There is no "notify-default" Printer attribute to configure. If the 10. This Delivery Method has the same latency and reliability as the
client did not supply the "notify-format" attribute in the Subscription underlying SMTP (or other) transport.
Creation operation, the Printer MUST populate this attribute with an
implementation-defined default value. Such a default value MAY include
multi-part mixed media, so that the Printer can send multi-part mixed
MIME type attachments by default (though there is no way for the client
to explicitly request such). If the out-of-band 'none' value [ipp-col]
was supplied in the Subscription Creation operation, the Printer MUST
NOT send any attachment in the Notification.
If the MIME media type registration definition permits a charset 11. This Delivery Method has the same security aspects as the
parameter, than the client MUST use such a specification (instead of the underlying SMTP (or other) transport.
"notify-charset" attribute) in order to indicate the charset to be used
in the Notification content.
4.4 subscriber-user-data (octetString(63)) 12. This Delivery Method has no content length restrictions.
This REQUIRED READ-ONLY Subscription object attribute holds an SMTP mail 13. There are no additional values that a Printer MUST send in a
address value that the Printer copies to the "From:" inside <> (see RFC Notification content.
822 [rfc822] section 4.4.1) and the "Sender:" SMTP fields (see section
5). For the 'mailto:' notification delivery method, the client MUST
supply the "subscriber-user-data" attribute. If the client omits this
attribute, the Printer MUST either (1) reject the operation with the
'client-error-bad-request' or (2) ignore this Subscription, since the
Printer will not have a mail address to put in the "From:" and in the
"Sender:" SMTP fields, depending on implementation.
When the subscribing user selects the 'mailto:' delivery scheme, the 14. There is one additional Subscription Template attributes. See
client SHOULD obtain the user's mail address automatically from the section 5.1.1.
client system (in an implementation-dependent manner) and supply it as
the value of the "subscriber-user-data" attribute by default, rather
than require the user to explicitly supply it. Allowing users to supply
the mail address explicitly would allow the malicious user to hide
his/her identity when sending notifications by email.
Expires: September 9, 2000 15. There are no additional Printer Description attributes.
4.5 notify-charset (charset) 5 Subscription Template Attributes
This OPTIONAL READ-ONLY Subscription object attribute specifies the 5.1 Additional Subscription Template Attributes
charset to be used in the Notification content sent to the Notification
Recipient, whether the notification content is Machine Consumable or
Human Consumable. The client MUST NOT supply and the Printer MUST NOT
use this attribute when the MIME media type registration definition
supplied in the "notify-format" attribute value allows the charset
parameter in its MIME media type value, e.g., 'text/plain; charset=utf-
8'.
4.6 notify-natural-language (naturalLanguage) This Delivery Method introduces one additional Subscription Template
Attribute.
This OPTIONAL READ-ONLY Subscription object attribute specifies the 5.1.1 notify-mailto-text-only (boolean)
natural language for the IPP object to use in the localized Notification
content that is sent to the Notification Recipient, whether the
notification content is Machine Consumable or Human Consumable.
4.7 request-id When the Printer generates an Event Notification from a Subscription
Object, this attribute specifies whether the Printer generates the Event
Notification with only plain text (i.e. 'text/plain') or with Content-
Types that the Printer chooses.
This REQUIRED READ-ONLY Subscription object attribute holds the most The Printer MUST support this attribute if it supports the 'mailto'
recent request-id sequence number delivered in a Notification content to Delivery Method.
the Notification Recipient. A value of 0 indicates that no
Notifications have been sent for this subscription. The first request-
id sent for a subscription MUST be 1. Each Notification Recipient has
its own monotonically increasing series of request-ids, i.e., no gaps,
in order to be able to detect a missing notification.
4.8 subscription-id (integer (1:MAX)) A client MAY supply this attribute. If a client does not supply this
attribute, the Printer MUST populate this attribute with the value of
'false' on the Subscription Object. There is no "notify-mailto-text-
only-default" attribute.
This REQUIRED READ-ONLY Subscription object attribute uniquely If the value of this attribute is 'true' in a Subscription Object, the
identifies this Subscription object instance on this Printer object or message body of each Event Notification that the Printer generates from
this Job object.. the Subscription Object MUST contain plain text only (i.e. 'text/plain'
with the charset specified by the "notify-charset' Subscription Object
attribute).
4.9 notify-lease-expiration-time (integer(0:MAX)) INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
This REQUIRED READ-ONLY Subscription object attribute specifies the time If the value of this attribute is 'false' in a Subscription Object, the
in the future when the subscription lease will expire, i.e., the message body of each Event Notification that the Printer generates from
"printer-up-time" value at which the lease will expire. the Subscription Object MAY contain any Content-Type (e.g. 'text/plain',
'text/html', 'multipart/mixed', 'multipart/alternative', 'image/gif',
'audio/basic', etc.).
4.10printer-uri (uri) A Printer MUST support both values ('true' and 'false') of this
attribute. There is no "notify-mailto-text-only-supported" attribute.
This REQUIRED READ-ONLY Subscription object attribute identifies the 5.2 Additional Information about Subscription Template Attributes
Printer object that created this Subscription object.
Expires: September 9, 2000 This section describes additional values for attributes defined in [ipp-
ntfy].
4.11subscriber-user-name (name(MAX)) 5.2.1 notify-recipient-uri (uri)
This REQUIRED READ-ONLY Subscription object attribute contains the name This section describes the syntax of the value of this attribute for the
of the user that created the Subscription object. The Printer includes 'mailto' Delivery Method. The syntax for values of this attribute for
the value of this attribute as the value of the SMTP "FROM" field other Delivery Method is defined in other Delivery Method Documents.
outside the <> (see RFC 822 [rfc822] section 4.4.1). For the 'mailto:'
notification delivery method, the client MUST supply the "requesting-
user-name" operation attribute so that the Printer can populate the
"subscriber-user-name" Subscription attribute, in case the Printer does
not have a more authenticated printable name (see [ipp-ntfy]). If the
client omits "requesting-user-name" attribute and the Printer doesn't
have a more authenticated printable name, the Printer MUST either (1)
reject the operation with the 'client-error-bad-request' or (2) ignore
this Subscription, since the Printer will not have a User Display Name
to put in the "From:" field outside the <>, depending on implementation.
ISSUE 05: Ok that we made "subscriber-user-name" be REQUIRED for the In order to support the 'mailto' Delivery Method, the Printer MUST
Printer to support and indicate that the client MUST supply the support the following syntax for the 'mailto' Delivery Method when the
"requester-user-name" operation attribute when the delivery method is Printer uses SMTP. The line below use RFC 822 syntax rules and terms.
'mailto:', in case the Printer does not have a more authenticated
printable name?
4.12notify-printer-up-time (integer(1:MAX)) "mailto:" 1#mailbox
This REQUIRED READ-ONLY Subscription object attribute indicates the Note: the above syntax allows 1 or more occurrences of 'mailbox'. Each
amount of time (in seconds) that the Printer implementation has been up occurrence of 'mailbox' represents an email address of a Notification
and running. The Printer includes the value of this attribute in both Recipient.
the Human Consumable and Machine Consumable forms.
4.13notify-persistence-granted (boolean) ISSUE: RFC 2368 allows more than one mailbox. Do we want this or just 1?
This REQUIRED Subscription object attribute whether or not the Per-Job For SMTP, the phrase 'address part of the "notify-recipient-uri"
or Per-Printer Subscription is persistent, i.e., saved across power attribute value' refers to the 'mailbox' part of the value.
cycles in an implementation-define manner.
5 Mail Notification Content The Printer MAY support other syntax for the 'address part' if it
supports other email protocols.
The intent of the mail message is that the Notification Recipient is 5.2.2 notify-user-data (octetString(63))
receiving a Human Consumable and/or Machine Consumable mail message from
the Printer with the subject line indicating that it is a printer
notification message and some implementation-defined salient
information, such as the Job name and submitting user name. The body of
the message duplicates this information and includes other information
as REQUIRED by [ipp-ntfy].
Table 1 shows the SMPT fields that the IPP Printer MUST fill in from the This attributes has a special use for the 'mailto' Delivery Method. It
indicated sources of the data. specifies the email address of the Subscribing Client. It is primarily
useful when the Notification Recipient is some person other than the
Subscribing Client. Then the Notification Recipient has a way to reply
to the Subscribing Client.
Expires: September 9, 2000 If a client specifies this Delivery Method in a Subscription Creation
Table 1 - SMTP Fields to be filled in Operation, and the specified Notification Recipient is not associated
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
does not supply this attribute, the Printer MUST NOT populate the
Subscription Object with this attribute.
SMTP RFC SMTP Subscription object attribute source for SNMP field INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
822 Field 2000
section Name
4.4.1 From: "printer-name" <"subscriber-user-data"> 6 Event Notification Content
For example, if Bob Jones submits a print job to the This section describes the content of an Event Notification sent via the
Printer "George Washington" and his email address is 'mailto' Delivery Method using the SMTP protocol. This document does
jones@acme.com, the From: line will be displayed as: not describe the content for other email protocols, but an
implementation should use this section as a model.
From: George Washington <jones@acme.com> When a Printer sends an email message via SMTP, the content MUST conform
to RFC 822. The following sections define the content that a Printer
MUST send. A Printer MAY send additional content as long as the
resulting content conforms to RFC 822.
Mail messages appear to the Notification Recipient Each subsection below specifies the syntax that pertains to the
to come from the Printer, so that mail agents can subsection. The syntax rules and syntactic terms (e.g. 'date-time') in
sort and filter on the From: field. each subsection come from RFC 822, except for the section on "Content-
Type" which comes from RFC 1521.
Note: The "printer-name" is the Mail Display name. The Event Notification content has two parts, the headers and the
And the "subscriber-user-data" inside <> is assumed message body. The headers precede the message body and are separated by
to be an SMTP mail address so that the Notification a blank line (see [RFC 822]).
Recipient can reply to the subscriber. For example,
to say "I picked up your document, thanks."
4.4.2 Sender: "subscriber-user-name" <"subscriber-user-data"> 6.1 Headers
For example, if Bob Jones submits a print job to the When a Printer sends an Event Notification via SMTP, it MUST include the
Printer "George Washington" and his email address is following headers. RFC 822 RECOMMENDS that the headers be in the order
jones@acme.com, the Sender: line will be displayed that they appear below.
as:
Sender: Bob Jones <jones@acme.com> 6.1.1 'Date' header
Note: The "subscriber-user-name" is the Mail Syntax: "Date" ":" date-time
Display name (Bob Jones). And the "subscriber-user-
data" inside <> is assumed to be an SMTP mail
address so that the mail system will send failure to
deliver mail messages to the mail address specified
by the "subscriber-user-data", not the Printer.
4.5.1 To: The rest of the URI following the 'mailto:' scheme This header contains the date and time that the Event occurred.
in the value of the "notify-recipient" attribute.
4.7.1 Subject: Implementation-dependent, but SHOULD start with The Printer MUST include a "Date" header if and only if it supports the
"Printer message: " (localized) followed by the job "printer-current-time" Printer attribute.
or printer event name, job name, etc. The beginning
of the Subject line is a standardized prefix, so
that mail agents can filter from any Printer.
The Printer MUST repeat any of this information in these fields in the 6.1.2 'From' header
body of the message, plus additional information REQUIRED by the
Notification Specification [ipp-ntfy].
Expires: September 9, 2000 Syntax: "From" ":" mailbox
5.1 Human Consumable Form where
If the format specified by the "notify-format" (mimeMediaType) is a mailbox = addr-spec / phrase route-addr
Human Consumable form, then it MUST be sent as a MIME according to
[rfc1341] and [rfc2046] if the MIME type is anything but 'text/plain'.
Even 'text/plain; charset=utf-8' MUST be represented as a MIME type in
the body of the message.
ISSUE 06: What if "notify-format" is 'text/plain; charset=utf-8', does This header causes a typical email reader to show the email as coming
that have to be sent as a mail attachment, since it isn't 'text/plain' from the Printer that is sending the Event Notification.
which assumes charset=us-ascii, or can it be sent as the body of the
mail message properly identified as 'text/plain; charset=us-ascii'?
5.2 Machine Consumable Form The Printer MUST include a "From" header whose syntax is specified
above.
If the format specified by the "notify-format" (mimeMediaType) is a The Printer MUST use the second alternative of the syntax for 'mailbox'
Machine Consumable form, then it MUST be sent as a MIME attachment defined above (i.e. 'phrase route-addr'). The 'phrase' is the
according to [rfc1341] and [rfc2046], including the 'application/ipp'. Printer's display name and it MUST be the value of the "printer-name"
Printer attribute. The 'route-addr' MUST contain an email address
(inside angle brackets) belonging to either an administrator or the
6 Printer Description attributes specific to the 'mailto:' delivery INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
method 2000
This section defines Printer Description attributes that are REQUIRED output-device. This email address NEED NOT be capable of receiving mail.
when supporting the 'mailto:' delivery method. There is no Printer attribute to hold this email address, so that it
cannot be configured using the IPP protocol without an implementation-
defined attribute extension.
6.1 "printer-smtp-mail-service-address" (1setOf text(MAX)) 6.1.3 'Subject' header
This REQUIRED Printer Description attribute contains the DNS or IP Syntax: "Subject" ":" *text
address of the SMTP relaying mail server (see [rfc822]) that the Printer
is to use to send mail messages when supporting the 'mailto:' delivery This header specifies the subject of the message and contains a short
method. The System Administrator is expected to configure this summary of the Event Notification.
attribute with one or more values.
The Printer MUST include a "Subject" header whose syntax is specified
above.
The Printer MUST localize the '*text' using the values of the "notify-
charset" and "notify-natural-language" Subscription Object attributes.
For Printer Events, the '*text' SHOULD start with the localized word
"printer:", followed by the Printer name, and then followed by the
localized Event name, e.g., in English: "printer: 'tiger' stopped" or in
French: 'imprimeur: 'tigre' arr.t.'.
For Job Events, the '*text' SHOULD start with the localized phrase
"print job:", followed by the Job name, and then followed by the
localized Event name, e.g., in English: "print job: 'financials'
completed".
The wording is implementation dependent. A Notification Recipient MUST
NOT expect to be able to parse this text. But an email filter might look
for "printer" or "print job".
6.1.4 'Sender' header
Syntax: "Sender" ":" mailbox
This header causes a typical email reader to show the email as coming on
behalf of the person associated with the Subscribing Client.
If the Subscription Object contains the "notify-user-data" attribute,
and if its value satisfies the RFC 822 syntax rules for 'mailbox', the
Printer MUST include a "Sender" header whose syntax is specified above.
Otherwise, the Printer MUST NOT include a "Sender" header.
For the "Sender" header, the 'mailbox' MUST be the value of the "notify-
user-data" Subscription Object attribute. See section 5.2.2 for details
about the "notify-user-data" attribute.
6.1.5 'Reply-to' header
Syntax: "Reply-to" ":" mailbox
If the Notification Recipient replies to Event Notification email, this
header causes a typical email reader to send email to the person acting
as the Subscribing Client. The rules are identical to the "Sender"
header.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
If the Subscription Object contains the "notify-user-data" attribute,
and if its value satisfies the RFC 822 syntax rules for "mailbox", the
Printer MUST include a "Reply-to" header whose syntax is specified
above. Otherwise, the Printer MUST NOT include a "Reply-to" header.
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
details about the "notify-user-data" attribute.
6.1.6 'To' header
Syntax: "To" ":" 1#mailbox
See [RFC 1521] for the syntax.
This header specifies the Notification Recipient(s).
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
"notify-recipient-uri" Subscription attribute, i.e. the part after the
"mailto:".
6.1.7 'Content-type' header
Syntax: "Content-Type" ":" type "/" subtype *(";"parameter)
See [RFC 1521] for the syntactic terms (e.g. 'type').
This header specifies the format of the message body.
The Printer MUST include the "Content-Type" header.
If the value of the "notify-mailto-text-only" Subscription Object
attribute is 'true', the 'type' MUST be "plain", the 'subtype' MUST be
"text" and the 'parameter' MUST be ' "charset=" XXX' where XXX is the
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 values 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, e.g. html, images, audio,
or multipart.
6.2 Message Body
This document describes a message body that is plain text. The content
of all other Content-Types is implementation dependent. A Printer SHOULD
include a plain text message even when it sends other Content-Types,
i.e. the 'type' of the Content-Type SHOULD be 'multipart'.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
When a Printer sends a plain text message, it MUST localize the text
using the values of the "notify-charset" and "notify-natural-language"
Subscription Object attributes.
Section 9.2 in [ipp-ntfy] specifies the information that a Delivery
Method MUST specify and a Printer SHOULD send. This section contains the
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
body. The specific wording of this information and its layout are
implementation dependent.
a)the Printer name (see Table 1)
b)omitted (see below).
c)for Printer Events only:
i) the Event (see Table 2) and/or Printer state information
(see Table 5)
d)for Job Events only:
i) the job identity (see Table 3)
ii) the Event (see Table 2) and/or Job state information (see
Table 4)
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'
header).
The subsections of this section specify the attributes that a Printer
MUST use to obtain this information.
The Printer MAY send additional information, depending on
implementation.
Notification Recipients MUST NOT expect to be able to parse the message.
The next three sections define the attributes in Event Notification
Contents that are:
a)for all Events
b)for Job Events only
c)for Printer Events only
6.2.1 Information in Event Notification Content Common to All Events
The Printer MUST send the following information.
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
listed in order of preference, with the first one being the preferred
one. An implementation SHOULD use the source value from the earliest row
in each table. The tables in this section and following contain the
following columns for each piece of information:
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
a)Source of Value: the name of the attribute that supplies the
value for the Event Notification
b)Source Object: the object from which the source value comes.
Table 1 lists the source of the information for the Printer Name. The
"printer-name" is more user-friendly unless the Notification Recipient
is in a place where the Printer name is not meaningful.
Table 1 . Printer Name in Event Notification Content
Source Value Source Object
printer-name (name(127)) Printer
notify-printer-uri (uri) Subscription
Table 2 lists the source of the information for the Event name. A
Printer MAY combine this information with state information described
for Jobs in Table 4 or for Printers in Table 5.
Table 2 . Event Name in Event Notification Content
Source Value Source Object
notify-subscribed-event (type2 keyword) Subscription
6.2.2 Additional Information in Event Notification Content for Job
Events
This section lists the source of the additional information that a
Printer MUST send for Job Events.
Table 3 lists the source of the information for the job name. The "job-
name" is likely more meaningful to a user than "job-id".
Table 3 . Job Name in Event Notification Content for Job Events
Source Value Source Object
job-name (name(MAX)) Job
job-id (integer(1:MAX)) Job
Table 4 lists the source of the information for the job-state. If a
Printer supports the "job-state-message" and "job-detailed-state-
message" attributes, it SHOULD use those attributes for the job state
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
information, otherwise, it should fabricate such information from the
"job-state" and "job-state-reasons". For some Events, a Printer MAY
combine this information with Event information.
Table 4 . Job State in Event Notification Content for Job Events
Source Value Source Object
job-state-message (text(MAX)) Job
job-detailed-status-messages (1setOf text(MAX)) Job
job-state (type1 enum) Job
job-state-reasons (1setOf type2 keyword) Job
6.2.3 Additional Information in Event Notification Content for Printer
Events
This section lists the source of the additional information that a
Printer MUST send for Printer Events.
Table 5 lists the source of the information for the printer-state. If a
Printer supports the "printer-state-message", it SHOULD use that
attribute for the job state information, otherwise it SHOULD fabricate
such information from the "printer-state" and "printer-state-reasons".
For some Events, a Printer MAY combine this information with Event
information.
Table 5 . Printer State in Event Notification Content for Printer Events
Source Value Source Object
printer-state-message (text(MAX)) Printer
printer-state (type1 enum) Printer
printer-state-reasons (1setOf type2 keyword) Printer
printer-is-accepting-jobs (boolean) Printer
6.3 Examples
This section contains three examples. One is a Job Event and the other
two are Printer Events, the latter in French.
6.3.1 Job Event Example
This section contains an example of an Event Notification of a Job
Event.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
A Subscribing Client Mike Jones (who works for xyz Corp.) performs a
Subscription Creation Operation as part of the Print-Job operation on
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.
The Subscription Object then has the following attributes:
Attribute Name Attribute Value
notify-recipient-uri mailto:bsmith@abc.com
notify-events job-completed
notify-user-data mjones@xyz.com
notify-mailto-text-only true
notify-charset us-ascii
notify-natural-language en-us
notify-persistence false
notify-subscription-id 35692
notify-sequence-number 0
notify-printer-up-time 34593
notify-printer-uri ipp://tiger@abc.com
notify-job-id 345
notify-subscriber-user- mjones
name
When the Job completes, the Printer generates and sends the following
email message:
Date: 17 Jul 00 1632 PDT
From: tiger <printAdmin@abc.com>
Subject: print job: 'financials' completed
Sender: mjones@xyz.com
Reply-to: mjones@xyz.com
To: bsmith@abc.com
Content-type: text/plain
printer: tiger
job: financials
job-state: completed
The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
6.3.2 Printer Event Example
This section contains an example of an Event Notification of a Printer
Event.
A Subscribing Client Peter Williams, a Printer admin, performs a Create-
Printer-Subscriptions operation on Printer "ipp://tiger@abc.com". The
Subscription Object then has the following attributes:
Attribute Name Attribute Value
notify-recipient-uri mailto:pwilliams@abc.com
notify-events printer-state-changed
notify-mailto-text-only true
notify-charset us-ascii
notify-natural-language en-us
notify-persistence false
notify-subscription-id 4623
notify-sequence-number 0
notify-printer-uptime 23002
notify-printer-uri ipp://tiger@abc.com
notify-lease-expiration- 0
time
notify-subscriber-user- pwilliams
name
When the Printer jams, the Printer generates and sends the following
email message:
Date: 29 Aug 00 0832 PDT
From: tiger <printAdmin@abc.com>
Subject: printer: 'tiger' stopped
To: pwilliams@abc.com
Content-type: text/plain
printer: tiger
state: stopped
reason: jammed paper
The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
6.3.3 Printer Event Example (localized to French)
This section contains an example of an Event Notification of a Printer
Event.
A Subscribing Client Pierre Veyrat, a Printer admin, performs a a
Create-Printer-Subscriptions operation on Printer "ipp://tigre@def.com".
The Subscription Object then has the following attributes:
Attribute Name Attribute Value
notify-recipient-uri mailto:pveyrat@def.com
notify-events printer-state-changed
notify-mailto-text-only true
notify-charset utf-8
notify-natural-language fr
notify-persistence false
notify-subscription-id 50225
notify-sequence-number 0
notify-printer-uptime 53217
notify-printer-uri ipp://tigre@def.com
notify-lease-expiration- 0
time
notify-subscriber-user- pveyrat
name
When the Printer jams, the Printer generates and sends the following
email message:
Note, this example shows the accented characters as an email reader
would show them rather than as they would be encoded in us-ascii.
ISSUE: this needs to changed to real ascii encoding for IETF ascii
document.
Date: 29 Jan 00 0832 CET
From: tigre <admin@def.com>
Subject: imprimeur: 'tigre' arr.t.
To: pveyrat@def.com
Content-type: text/plain;charset=utf-8
imprimeur: tigre@def.com
.tat: arr.t.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
raison: papier coinc.
7 Conformance Requirements 7 Conformance Requirements
If the IPP Printer supports the 'mailto:' notification delivery scheme, If the Printer supports the 'mailto' Delivery Method, the Printer MUST:
the Printer MUST meet these conformance requirements:
1.MUST meet the conformance requirements defined in [ipp-ntfy]. 1.meet the conformance requirements defined in [ipp-ntfy].
2.MUST support at least the 'text/plain' Notification Content format. 2.support the "notify-mailto-text-only " Subscription Object attribute
Being able to support any other MIME media types (MUST be sent as defined in section 5.1.1.
mail attachments) is OPTIONAL..
3.MUST support the Subscription attribute semantics specified in 3.support the syntax for the "notify-recipient-uri" Subscription Object
section 4 when sending Notifications. attribute defined in section 5.2.1
4.MUST fill in the SMTP fields in the mail message as specified in 4.support the use for the "notify-user-data" Subscription Object
section 5. attribute defined in section 5.2.2
Expires: September 9, 2000 5.support SMTP for sending Event Notifications.
5.MUST support the "printer-smtp-mail-service-address" (1setOf 6.support the 'text/plain' Content-Type for the message body.
text(MAX)) Printer Description attribute defined in section 6.
7.support sending Event Notification via email with the content
specified in section 5.2.
8 IANA Considerations 8 IANA Considerations
Since the 'mailto:' URL scheme is already defined in a standards track Because the 'mailto' URL scheme is already defined in a standards track
document and registered with IANA, this document does not require document [RFC 2368] and registered with IANA, this document does not
anything further of IANA. require anything further of IANA.
9 Internationalization Considerations 9 Internationalization Considerations
This notification delivery method presents no additional This Delivery Method presents no internationalization considerations
internationalization considerations already covered in the [ipp-ntfy] beyond those covered in the [ipp-ntfy] document, and sections 6.1.3 and
document. The IPP Printer MUST localize the Human Consumable format and 6.2 of this document.
the 'text' attributes in the Machine Consumable form. The Notification
Recipient is expected to localize the attributes in the Machine The Notification Recipient is expected to present the email as received
Consumable that have the 'keyword' attribute syntax according to the because the Printer does all necessary localization to the Event
charset and natural language supplied in the Notification Content which Notification contents.
is derived from the Subscription object as supplied by the Subscriber.
10 Security Considerations 10 Security Considerations
By far the biggest security concern is the abuse of notification: The biggest security concern is that a Subscribing Client will cause
sending unwanted notifications to third parties (i.e., spam). The unsolicited Event Notifications to be sent to third parties, potentially
problem is made worse by notification addresses that may be creating denial-of-service problems (i.e., spam). The problem is even
redistributed to multiple parties (e.g. mailing lists). There exist worse if the third parties are distribution lists.
scenarios where third party notification is required (see Scenario #2
and #3 in [ipp-not-req]). The fully secure solution would require
active agreement of all recipients before sending out anything.
However, requirement #9 in [ipp-req] ("There is no requirement for IPP
Printer receiving the print request to validate the identity of an event
recipient") argues against this. Certain systems may decide to disallow
third party notifications (a traditional facsimile model).
Sometimes the Notification Recipient is not the same person as the There exist scenarios where third party notification is required (see
person who created the Subscription. It is possible for the Scenario #2 and #3 in [ipp-not-req]). The fully secure solution would
Notification Recipient to find out who created the Subscription, since require active agreement of all persons before they can become
the subscriber MUST supply the "subscriber-user-name" Subscription Notification Recipients. However, requirement #9 in [ipp-req] ("There
attribute in the Subscription Creation operation. is no requirement for IPP Printer receiving the print request to
validate the identity of an event recipient") argues against this. To
The [ipp-ntfy] document discusses general security considerations for INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
notifications. Some delivery methods, such as the 'ipp:' delivery 2000
method, avoid the spam problem because the Notification Recipient pulls
the Notifications when desired. The 'indp:' [indp-method] delivery
method allows the Notification Recipient to return a special status code
reply to the IPP Printer Send-Notifications operation to cancel the
subscription. The 'mailto:' delivery method does not permit either of
these remedies.
ISSUE 07 - Is there any way that a Notification Recipient could reply to minimize the risk, a Printer could disallow third party Notification
the message in such a way as to cancel the subscription and thereby Recipients (a traditional facsimile model).
solve the spam problem?
Expires: September 9, 2000 The Delivery Method recommends that the Subscribing Client supply his or
her email address as the value of the "notify-user-data" attribute in
the Subscription Creation Operation when the Notification Recipient is a
third party. To reduce the chance of spamming or identify the spammer, a
Printer could disallow third party Notification Recipients if the
Subscribing Client doesn't supply the "notify-user-data" attribute with
a valid email address.
Some firewall administrators are preventing mail attachments from being Some firewall administrators prevent mail attachments from being
accepted into their organizations because of the problem of the accepted into their organizations because of the problem of the
attachments containing computer viruses. The 'mailto:' delivery method attachments containing computer viruses. The 'mailto' Delivery Method
allows the subscriber to suppress sending any attachments, by specifying allows the Subscribing Client to request that the Content-Type of a
only the 'text/plain' MIME media type. message body be 'text/plain'.
11 References 11 References
[ipp-coll] [ipp-iig]
deBry, R., , Hastings, T., Herriot, R., "Internet Printing Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P.,
Protocol/1.0 & 1.1: collection attribute syntax", <draft-ietf-ipp- "Internet Printing Protocol/1.1: draft-ietf-ipp-implementers-
collection-00.doc>, work in progress, September 9, 1999. 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.0: Model and Semantics", <draft-ietf-
ipp-model-v11-04.txt>, June, 1999. ipp-model-v11-06.txt>, March 1, 2000.
[ipp-notify-poll]
Manros, C., Hastings, T., Herriot, R., Lewis, H., "Internet
Printing Protocol (IPP): The 'ipp' Notification Delivery Polling
Method", <draft-ietf-ipp-notify-poll-01.txt>, work in progress,
May, 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-01.txt>, Notification Specification", <draft-ietf-ipp-not-spec-03.txt>, May
October 14, 1999. 10, 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-
03.txt, June, 1999. 05.txt, March 1, 2000.
[rfc821] [RFC821]
Jonathan B. Postel, "Simple Mail Transfer Protocol", August, 1982. Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821,
August, 1982.
[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", August 13, 1982. Messages", RFC 822, August 13, 1982.
[rfc1341] INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
[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", June, 1992. Internet Message Bodies", RFC 1341, June, 1992.
[rfc2026] [RFC1521]
N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail
Extensions) Part One: Mechanisms for Specifying and Describing the
Format of Internet Message Bodies", RFC 1521, September 1993.
[RFC1891]
K. Moore, "SMTP Service Extension for Delivery Status
Notifications", RFC 1891, January 1996
[RFC2026]
S. Bradner, "The Internet Standards Process -- Revision 3", RFC S. Bradner, "The Internet Standards Process -- Revision 3", RFC
2026, October 1996. 2026, October 1996.
[rfc2046] [RFC2046]
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
N. Freed & N. Borenstein. November 1996. (Obsoletes RFC1521, Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
RFC1522, RFC1590), RFC 2046. RFC 2616, June 1999.
Expires: September 9, 2000 [RFC2368]
P. Hoffman, L. Masinter, J. Zawinski, "The mailto URL scheme", RFC
2616, July 1998.
[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.
[RFC2633]
B. Ramsdell, "S/MIME Version 3 Message Specification", RFC 2633,
June 1999.
12 Author's Addresses 12 Author's Addresses
Robert Herriot
Xerox Corporation
3400 Hillview Ave., Bldg #1
Palo Alto, CA 94304
Phone: 650-813-7696
Fax: 650-813-6860
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
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
Phone: +45 4436-6000 Phone: +45 4436-6000
Fax: +45 4436-6111 Fax: +45 4436-6111
e-mail: hh@i-data.com e-mail: hh@i-data.com
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo, CA 90245 El Segundo, CA 90245
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
e-mail: hastings@cp10.es.xerox.com e-mail: hastings@cp10.es.xerox.com
Carl-Uno Manros
Xerox Corporation
737 Hawaii St. ESAE 231
El Segundo, CA 90245
Phone: 310-333-8273
Fax: 310-333-5514
e-mail: manros@cp10.es.xerox.com
13 Full Copyright Statement 13 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
skipping to change at line 748 skipping to change at line 1162
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.
Expires: September 9, 2000
 End of changes. 

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