INTERNET-DRAFT
<draft-ietf-ipp-notify-mailto-00.txt>
<draft-ietf-ipp-notify-mailto-01.txt>                     Robert Herriot
                                                             Xerox Corp.
                                                            Henrik Holst
                                                i-data international a/s
                                                            Tom Hastings
                                                             Xerox Corp.
                                                           March 9,
                                                         Carl-Uno Manros
                                                             Xerox Corp.
                                                            July 7, 2000

                   Internet Printing Protocol (IPP):
               The 'mailto:' Notification Delivery Method

    Copyright (C) The Internet Society (2000). All Rights Reserved.

Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of [rfc2026]. [RFC2026].  Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups.  Note that other groups may also distribute working
documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress".

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html.

Abstract

The IPP notification specification [ipp-ntfy] is an OPTIONAL extension document [ipp-ntfy] defines operations that a
client can perform in order to IPP/1.0 create Subscription Objects in a Printer
and IPP/1.1 carry out other operations on them. The Subscription Object
specifies that requires the definition of when one or more
delivery methods for dispatching event notification reports of the specified Events occurs, the Printer
sends an asynchronous Event Notification to the specified Notification Recipients.
Recipient via the specified Delivery Method (i.e., protocol).

The notification extension document [ipp-ntfy] specifies that each
Delivery Method is defined in another document. This document describes the semantics is one
such document, and
syntax of it specifies the 'mailto:' event notification 'mailto' delivery method.

For this
delivery method, Delivery Method, when an Event occurs, the IPP Printer uses the SMTP mail protocol to send
(push) Human Consumable and/or Machine Consumable Notifications to immediately
sends an Event 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 via an email message to perform such notification using
parameters the Notification
Recipient specified in the URL, such as paging. Subscription Object. The Subscriber can specify the
MIME media type message body of both the
email consists of Human Consumable text and Machine Consumable
Notifications.  The Subscriber can also specify a mail address in the
"subscriber-user-data" Subscription attribute is not intended to which the be parsed
by a machine.

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

The Notification Recipient can reply and to which receives the mail system delivers undeliverable
mail messages.  That mail address is usually Event Notification in the Subscribers mail
address, but can be same
way as it receives any mail address. other email message.

INTERNET-DRAFTIPP: The mail messages appear to come from .mailto:. Notification Delivery MethodJuly 7,
2000

The full set of IPP documents includes:

  Design Goals for an Internet Printing Protocol [RFC2567]
  Rationale for the Printer, so that mail agents
can sort Structure and filter on the From: field.  Also the beginning of the

                      Expires: September 9, 2000

Subject line starts with the localized "Printer message: " prefix, so
that mail agents can filter from any Printer.

        There are 7 ISSUES called out in the text.

                      Expires: September 9, 2000

The full set of IPP documents includes:

  Design Goals for an Internet Printing Protocol [RFC2567]
  Rationale for the Structure and Model and Protocol for Model and Protocol for the Internet
     Printing Protocol [RFC2568]
  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: Implementer's Guide [ipp-iig]
  Mapping between LPD and IPP Protocols [RFC2569]
  Internet Printing Protocol (IPP): IPP Event Notification
     Specification [ipp-ntfy]

The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet.  It identifies
requirements for three types of users: end users, operators, and
administrators.  It calls out a subset of end user requirements that are
satisfied in IPP/1.0.  A few OPTIONAL operator operations have been
added to IPP/1.1.

The "Rationale for the Structure and Model and Protocol for the Internet
Printing Protocol" document describes IPP from a high level view,
defines a roadmap for the various documents that form the suite of IPP
specification documents, and gives background and rationale for the IETF
working group's major decisions.

The "Internet Printing Protocol/1.1: Model and Semantics" document
describes a simplified model with abstract objects, their attributes,
and their operations that are independent of encoding and transport.  It
introduces a Printer and a Job object.  The Job object optionally
supports multiple documents per Job.  It also addresses security,
internationalization, and directory issues.

The "Internet Printing Protocol/1.1: Encoding and Transport" document is
a formal mapping of the abstract operations and attributes defined in
the model document onto HTTP/1.1 [RFC2616].  It defines the encoding
rules for a new Internet MIME media type called "application/ipp".  This
document also defines the rules for transporting over HTTP a message
body whose Content-Type is "application/ipp".  This document also
defines a new scheme named 'ipp' for identifying IPP printers and jobs.

The "Internet Printing Protocol/1.1: Implementer's Guide" document gives
insight and advice to implementers of IPP clients and IPP objects.  It
is intended to help them understand IPP/1.1 and some of the
considerations that may assist them in the design of their client and/or
IPP object implementations.  For example, a typical order of processing
requests is given, including error checking.  Motivation for some of the
specification decisions is also included.

The "Mapping between LPD and IPP Protocols" document gives some advice
to implementers of gateways between IPP and LPD (Line Printer Daemon)
implementations.

                      Expires: September 9,

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

The "Event Notification Specification" document extends describes an extension
to the Job Creation
operations IPP/1.0, IPP/1.1, and defines additional operations that allow future versions. This extension allows a
client to subscribe to printing related events.  Subscriptions are modeled as Events. The Subscription objects which can be Per-Job Object
specifies that when one of the specified Event occurs, the Printer sends
an asynchronous Event Notification to the specified Notification
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 Per-Printer Subscriptions.
Additional 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 to query, renew, and cancel for Subscription objects.

                      Expires: September 9, Objects: Get-
Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and
Cancel-Subscription.

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

Table of Contents

1  Introduction......................................................6  Introduction......................................................7

2  Terminology.......................................................6
 2.1Conformance Terminology..........................................6
 2.2Other terminology................................................7  Terminology.......................................................7

3  Model and Operation...............................................7

4  Sending Notifications.............................................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  General Information...............................................8

5  Mail Notification Content........................................11
 5.1Human Consumable Form...........................................13
 5.2Machine Consumable Form.........................................13  Subscription Template Attributes..................................9
 5.1 Additional Subscription Template Attributes.....................9
   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  Event Notification Content.......................................11
 6.1 Headers........................................................11
   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 Description attributes specific 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 the 'mailto:' delivery
method...............................................................13
 6.1"printer-smtp-mail-service-address" (1setOf text(MAX))..........13  French)...............19

7  Conformance Requirements.........................................13 Requirements.........................................20

8  IANA Considerations..............................................14 Considerations..............................................20

9  Internationalization Considerations..............................14 Considerations..............................20

10 Security Considerations..........................................14 Considerations..........................................20

11 References.......................................................15 References.......................................................21

12 Author's Addresses...............................................16 Addresses...............................................22

13 Full Copyright Statement.........................................16 Statement.........................................23

                            Table of Tables

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

Table 1 - SMTP Fields to be filled in................................12

                      Expires: September 9, . 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

An IPP Printer that supports the OPTIONAL IPP

The notification extension document [ipp-ntfy] is called defines operations that a Notification Source which sends event
Notifications
client can perform in order to Notification Recipients.  As such, create Subscription Objects in a Printer either a)
accepts, stores,
and uses notification carry out other operations on them. A Subscription objects to generate
event Notification reports and implement one or more delivery methods
for notifying interested parties, or b) supports Object represents
a subset Subscription abstraction. The Subscription Object specifies that when
one of these tasks
and farms out the remaining tasks specified Events occurs, the Printer sends an asynchronous
Event Notification to a the specified Notification Recipient via the
specified Delivery Method (i.e., protocol).

The notification extension document [ipp-ntfy] specifies that each
Delivery Service. Method is defined in another document. This document describes the semantics is one
such document, and syntax of it specifies the 'mailto:' event
notification 'mailto' delivery method.  Such a Notification Delivery Service then
delivers the event Notification to the Ultimate Notification Recipient.

For this delivery method, Delivery Method, when an Event occurs, the IPP Printer uses the SMTP mail protocol to
send (push) Human Consumable and/or Machine Consumable Notifications to immediately
sends an Event 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 via an email message to perform such notification using
parameters the Notification
Recipient specified in the URL, such as paging. Subscription Object. The Subscriber can specify the
MIME media type message body of both the
email consists of Human Consumable text and Machine Consumable
Notifications. is not intended to be parsed
by a machine. The Subscriber can also specify 'mailto' Delivery Method is a mail address 'push' Delivery Method
as defined in the
"subscriber-user-data" Subscription attribute to which the [ipp-ntfy].

The Notification Recipient can reply and to which receives the mail system delivers undeliverable
mail messages.  That mail address is usually Event Notification in the Subscribers mail
address, but can be same
way as it receives any mail address.

The mail messages appear to come from other email message.

2  Terminology

This section defines the Printer, so following terms that mail agents
can sort and filter on the From: field.  Also the beginning of the
Subject line starts with the localized "Printer message: " prefix, so
that mail agents can filter from any Printer.

2  Terminology

This section defines terminology 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].
  REQUIRED - an adjective used to indicate

For capitalized terms 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 appear in this document

                      Expires: September 9, 2000
     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

  Event Notification (Notification for short) - See [ipp-ntfy]
  Notification Source - See [ipp-ntfy]
  Notification Recipient - See [ipp-ntfy]
  Subscription object - See [ipp-ntfy]
  Ultimate Notification Recipient - See [ipp-ntfy] document, see [ipp-ntfy].

3  Model and Operation

In the IPP Notification Model [ipp-ntfy], a client is able to:

  1. supply one or more Per-Job Subscriptions in the Job Creation
     operation

  2. OPTIONALLY supply Per-Job Subscriptions as subsequent Create-Job-
     Subscription operations

  3. supply one Per-Printer Subscription in the Create-Printer-
     Subscription operation.  The client that creates these Subscription
     objects becomes Creation Operation, when the owner value of the Subscription object.

The client that creates these Subscription objects becomes the owner of "notify-
recipient-uri" attribute contains the Subscription object.

When creating each Subscription object, scheme "mailto", the client supplies the "notify-
recipient" (uri) attribute.  The "notify-recipient" attribute specifies
both a single Notification Recipient that is to receive
requesting that the
Notifications when subsequent events occur and Printer use the method 'mailto' Delivery Method for
Notification delivery that Event
Notifications generated from the IPP Printer is to use. new Subscription Object.

For the 'mailto:'
Notification delivery method defined in this document, Delivery Method, the "notify-
recipient" consists "notify-recipient-uri" attribute value
MUST consist of the 'mailto:' a "mailto" scheme followed by a colon, and then followed
by an SMPT mail address [RFC822].

Notification Sources that implement part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for
the 'mailto:' event notification
delivery method will need to include an SMTP mail agent while
Notification Recipients that implement syntax of the "notify-recipient-uri" attribute value for this delivery method will need to
Delivery Method.

A Printer MUST support an SMTP server.   ISSUE 01:  Is this SMTP terminology correct?

The IPP [RFC821], and it MAY support other email
protocols. A Printer can be the Notification Source or could MAY use some other additional services, such as SMTP delivery
status notification [RFC1891] or S/MIME encryption [RFC2633].

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery Service that actually delivers the mail message.
In this latter case, MethodJuly 7,
2000

If the protocol between client wants the IPP Printer and to send Event Notifications via the
Notification
'mailto' Delivery Service is implementation defined and could be the
INDP protocol (see [indp]).

                      Expires: September 9, 2000

Also the Notification Recipient specified by Method, the "notify-recipient"
Subscription client MUST choose a value for "notify-
recipient-uri" attribute can be either (1) which conforms to the Ultimate Notification
Recipient or can be rules of section 5.2.1.
To avoid denial-of-service attacks, a Notification Delivery Service, such client SHOULD NOT use distribution
lists as a paging
system that accept 'mailto:' parameters to indicate the Ultimate Notification Recipient, such as a phone number or paging subscriber's
id.

4  Sending Notifications

This section defines the processing that Recipient.

When an Event occurs, the IPP Printer MUST perform
when sending an event Notification using the 'mailto:' delivery method.
The usage of each of the immediately:

  1. Find all pertinent Subscription object attributes defined in [ipp-
ntfy] is described here as it applies Objects P according to the 'mailto:' delivery method.
The description rules of each Subscription attribute in this document is not
the complete description, but is just the application
     section 9 of [ipp-ntfy], AND

  2. Find the attribute
to this 'mailto:' delivery method.  See the complete definition subset M of each these Subscription object Objects P whose "notify-
     recipient-uri" attribute in [ipp-ntfy].  ISSUE 02:  Is it has a good
idea to list scheme value of 'mailto', AND

  3. For each Subscription object attribute Object 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 M, the IPP Printer
populates the SMTP fields MUST

     a)generate an email message as specified in section 5.2.2 AND

     b)send the mail message.

4.1 notify-recipient (uri)

This REQUIRED READ-ONLY Subscription object attribute contain email message to the
'mailto:' URI delivery method followed Notification Recipient specified
       by the SMTP mail address [RFC821] part of the Notification Recipient.  As required by the [ipp-ntfy] document, "notify-recipient-uri" attribute
       value (see section 5.2.1).

If the following information is given for this notification delivery
method:

ISSUE 03 - What should we say about any mailto parameters, if any?  For
example, if you want to Printer supports only SMTP, it MUST send over secure mail, etc.

ISSUE 04 - Do we want to define any IPP-specific mailto parameters to
this document?

4.2 notify-events (1setOf type2 keyword)

This REQUIRED READ-ONLY Subscription object attribute identifies the job
and/or printer events that are to be delivered to email message via
SMTP. If the Notification
Recipient as Notifications as defined in [ipp-ntfy] section 7.

Note:  Some rapidly recurring events, such as page events, are not
appropriate to use with this delivery method, especially if Printer supports additional email protocols, it MUST
determine the
recipient mail address is a mailing list.  Implementations MAY choose
either not to support page events with protocol from 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

4.3 notify-format (mimeMediaType)

This REQUIRED READ-ONLY Subscription object part of the "notify-recipient-
uri" attribute indicates value and then send the type
of Human Consumable and/or Machine Consumable format content that email message via the appropriate
email protocol.

When a Subscription Object is listening to
be sent in a frequently occurring Event,
such as 'job-progress', the Printer MUST moderate the sending of Event
Notifications caused by such an Event. It is implementation dependent as
to how a mail message attachment.  For Printer moderates Events and how a human controls 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
moderation.

4  General Information

According to be
represented, e.g., 'audio/32kadpcm'.  The body of the mail message notification extension document [ipp-ntfy], this
document MUST
always be 'text/plain; charset=us-ascii, since that is contain the default following information:

1.The URL scheme name for
'mailto:'.

There the Delivery Method is: 'mailto'

2.Printer support for this delivery method is no "notify-default" Printer attribute to configure.  If the
client did not supply the "notify-format" attribute in the Subscription
Creation operation, the OPTIONAL.

3.For Event Notification content, a Printer MUST populate this attribute with an
implementation-defined default value.  Such a default value support SMTP. It MAY include
multi-part mixed media, so that the
  support other email protocols.

4.Several Event Notifications MUST NOT be combined into a compound
  Event Notification. The Printer can MUST send multi-part mixed
MIME type attachments by default (though there is no way for them as separate email
  messages.

5.The Printer MUST initiate the client
to explicitly request such).  If Delivery Method.

6.The Delivery Method sends Human Consumable Event Notifications.

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
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 out-of-band 'none' value [ipp-col]
was supplied
  information in other encodings.

8.In the Subscription Creation operation, the Event Notification content, a Printer MUST
NOT send any attachment all pieces of
  information specified in section 5.2.2.

9.Frequently occurring Events MUST be moderated to prevent Notification
  Recipients from receiving excessive email.

10.  This Delivery Method has the Notification.

If the MIME media type registration definition permits a charset
parameter, than same latency and reliability as the client MUST use such a specification (instead of
  underlying SMTP (or other) transport.

11.  This Delivery Method has the
"notify-charset" attribute) in order to indicate same security aspects as the charset to be used
  underlying SMTP (or other) transport.

12.  This Delivery Method has no content length restrictions.

13.  There are no additional values that a Printer MUST send in the a
  Notification content.

4.4 subscriber-user-data (octetString(63))

14.  There is one additional Subscription Template attributes. See
  section 5.1.1.

15.  There are no additional Printer Description attributes.

5  Subscription Template Attributes

5.1 Additional Subscription Template Attributes

This REQUIRED READ-ONLY Delivery Method introduces one additional Subscription object attribute holds an SMTP mail
address value that Template
Attribute.

5.1.1 notify-mailto-text-only (boolean)

When the Printer copies to generates an Event Notification from a Subscription
Object, this attribute specifies whether the "From:" inside <> (see RFC
822 [rfc822] section 4.4.1) and Printer generates the "Sender:" SMTP fields (see section
5).  For Event
Notification with only plain text (i.e. 'text/plain') or with Content-
Types that the 'mailto:' notification delivery method, Printer chooses.

The Printer MUST support this attribute if it supports the 'mailto'
Delivery Method.

A client MUST MAY supply the "subscriber-user-data" this attribute. If the a client omits does not supply this
attribute, the Printer MUST either (1) reject the operation with the
'client-error-bad-request' or (2) ignore populate this Subscription, since the
Printer will not have a mail address to put in the "From:" and in attribute with the
"Sender:" SMTP fields, depending value of
'false' on implementation.

When the subscribing user selects the 'mailto:' delivery scheme, the
client SHOULD obtain the user's mail address automatically from the
client system (in an implementation-dependent manner) and supply it as Subscription Object. There is no "notify-mailto-text-
only-default" attribute.

If the value of the "subscriber-user-data" this attribute by default, rather
than require is 'true' in a Subscription Object, the user to explicitly supply it.  Allowing users to supply
message body of each Event Notification that the mail address explicitly would allow Printer generates from
the malicious user to hide
his/her identity when sending notifications by email.

                      Expires: September 9, 2000

4.5 notify-charset (charset)

This OPTIONAL READ-ONLY Subscription object attribute specifies Object MUST contain plain text only (i.e. 'text/plain'
with the charset to be used in the Notification content sent to the Notification
Recipient, whether specified by the notification content is Machine Consumable or
Human Consumable. "notify-charset' Subscription Object
attribute).

INTERNET-DRAFTIPP: The client MUST NOT supply and .mailto:. Notification Delivery MethodJuly 7,
2000

If the Printer MUST NOT
use value of this attribute when the MIME media type registration definition
supplied in the "notify-format" attribute value allows the charset
parameter is 'false' in its MIME media type value, e.g., 'text/plain; charset=utf-
8'.

4.6 notify-natural-language (naturalLanguage)

This OPTIONAL READ-ONLY a Subscription object attribute specifies the
natural language for Object, the IPP object to use in the localized
message body of each Event Notification
content that is sent to the Notification Recipient, whether Printer generates from
the
notification content Subscription Object MAY contain any Content-Type (e.g. 'text/plain',
'text/html', 'multipart/mixed', 'multipart/alternative', 'image/gif',
'audio/basic', etc.).

A Printer MUST support both values ('true' and 'false') of this
attribute. There is Machine Consumable or Human Consumable.

4.7 request-id

This REQUIRED READ-ONLY no "notify-mailto-text-only-supported" attribute.

5.2 Additional Information about Subscription object attribute holds the most
recent request-id sequence number delivered Template Attributes

This section describes additional values for attributes defined in a Notification content to [ipp-
ntfy].

5.2.1 notify-recipient-uri (uri)

This section describes the syntax of the Notification Recipient.  A value of 0 indicates that no
Notifications have been sent for this subscription. attribute for the
'mailto' Delivery Method. The first request-
id sent syntax for a subscription MUST be 1.  Each Notification Recipient has
its own monotonically increasing series values of request-ids, i.e., no gaps, this attribute for
other Delivery Method is defined in other Delivery Method Documents.

In order to be able to detect a missing notification.

4.8 subscription-id (integer (1:MAX))

This REQUIRED READ-ONLY Subscription object attribute uniquely
identifies this Subscription object instance on this support the 'mailto' Delivery Method, the Printer object or
this Job object..

4.9 notify-lease-expiration-time (integer(0:MAX))

This REQUIRED READ-ONLY Subscription object attribute specifies MUST
support the time
in following syntax for the future 'mailto' Delivery Method when the subscription lease will expire, i.e.,
Printer uses SMTP. The line below use RFC 822 syntax rules and terms.

  "mailto:" 1#mailbox

Note: the
"printer-up-time" value at which above syntax allows 1 or more occurrences of  'mailbox'. Each
occurrence of 'mailbox' represents an email address of a Notification
Recipient.

ISSUE: RFC 2368 allows more than one mailbox. Do we want this or just 1?

For SMTP, the lease will expire.

4.10printer-uri (uri)

This REQUIRED READ-ONLY Subscription object attribute identifies phrase 'address part of the
Printer object that created this Subscription object.

                      Expires: September 9, 2000

4.11subscriber-user-name (name(MAX))

This REQUIRED READ-ONLY Subscription object "notify-recipient-uri"
attribute contains value' refers to the name 'mailbox' part of the user that created the Subscription object. value.

The Printer includes MAY support other syntax for the value of this attribute as 'address part' if it
supports other email protocols.

5.2.2 notify-user-data (octetString(63))

This attributes has a special use for the value 'mailto' Delivery Method. It
specifies the email address of the SMTP "FROM" field
outside Subscribing Client. It is primarily
useful when the <> (see RFC 822 [rfc822] section 4.4.1).  For Notification Recipient is some person other than the 'mailto:'
notification delivery method,
Subscribing Client. Then the Notification Recipient has a way to reply
to the Subscribing Client.

If a client MUST supply specifies this Delivery Method in a Subscription Creation
Operation, and the "requesting-
user-name" operation attribute so that specified Notification Recipient is not associated
with the Printer can populate same person as the
"subscriber-user-name" Subscription attribute, in case client, the Printer does
not have a more authenticated printable name (see [ipp-ntfy]). client SHOULD supply its email
address as the value of the "notify-user-data" attribute. If the client omits "requesting-user-name" attribute and the Printer doesn't
have a more authenticated printable name,
does not supply this attribute, the Printer MUST either (1)
reject NOT populate the operation
Subscription Object with the 'client-error-bad-request' or (2) ignore this Subscription, since attribute.

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

6  Event Notification Content

This section describes the Printer will content of an Event Notification sent via the
'mailto' Delivery Method using the SMTP protocol.  This document does
not have describe the content for other email protocols, but an
implementation should use this section as a User Display Name model.

When a Printer sends an email message via SMTP, the content MUST conform
to put in RFC 822. The following sections define the content that a Printer
MUST send. A Printer MAY send additional content as long as the "From:" field outside
resulting content conforms to RFC 822.

Each subsection below specifies the <>, depending on implementation.

ISSUE 05:  Ok syntax that we made "subscriber-user-name" be REQUIRED pertains to the
subsection. The syntax rules and syntactic terms (e.g. 'date-time') in
each subsection come from RFC 822, except for the
Printer to support section on "Content-
Type" which comes from RFC 1521.

The Event Notification content has two parts, the headers and indicate that the client
message body. The headers precede the message body and are separated by
a blank line (see [RFC 822]).

6.1 Headers

When a Printer sends an Event Notification via SMTP, it MUST supply include the
"requester-user-name" operation attribute when
following headers. RFC 822 RECOMMENDS that the delivery method is
'mailto:', headers be in case the Printer does not have a more authenticated
printable name?

4.12notify-printer-up-time (integer(1:MAX)) order
that they appear below.

6.1.1 'Date' header

Syntax:   "Date" ":" date-time

This REQUIRED READ-ONLY Subscription object attribute indicates header contains the
amount of date and time (in seconds) that the Event occurred.

The Printer implementation has been up MUST include a "Date" header if and running.   The only if it supports the
"printer-current-time" Printer includes attribute.

6.1.2 'From' header

Syntax:   "From" ":" mailbox

  where

     mailbox = addr-spec / phrase route-addr

This header causes a typical email reader to show the value of this attribute in both email as coming
from the Human Consumable and Machine Consumable forms.

4.13notify-persistence-granted (boolean)

This REQUIRED Subscription object attribute whether or not Printer that is sending the Per-Job
or Per-Printer Subscription Event Notification.

The Printer MUST include a "From" header whose syntax is persistent, i.e., saved across power
cycles in an implementation-define manner.

5  Mail Notification Content specified
above.

The intent Printer MUST use the second alternative of the mail message syntax for 'mailbox'
defined above (i.e. 'phrase route-addr').   The 'phrase' is that the Notification Recipient is
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
Printer's display 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 it MUST fill in from be the
indicated sources value of the data.

                      Expires: September 9, 2000
                 Table 1 - SMTP Fields to be filled in

SMTP RFC SMTP      Subscription object attribute source for SNMP field
822      Field
section  Name

4.4.1    From: "printer-name"  <"subscriber-user-data">

                   For example, if Bob Jones submits a print job to the
Printer "George Washington" and his attribute. The 'route-addr' MUST contain an email address is
                   jones@acme.com, the From: line will be displayed as:

                   From:  George Washington <jones@acme.com>

                   Mail messages appear to the Notification Recipient
                   to come from the Printer, so that mail agents can
                   sort and filter on the From: field.

                   Note:  The "printer-name" is the Mail Display name.
                   And the "subscriber-user-data" inside <> is assumed
(inside angle brackets) belonging to be either an SMTP mail address so that administrator or the

INTERNET-DRAFTIPP: The .mailto:. Notification
                   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">

                   For example, if Bob Jones submits a print job to the
                   Printer "George Washington" and his Delivery MethodJuly 7,
2000

output-device. This email address is
                   jones@acme.com, the Sender: line will NEED NOT be displayed
                   as:

                   Sender:  Bob Jones <jones@acme.com>

                   Note:  The "subscriber-user-name" is the Mail
                   Display name (Bob Jones).  And the "subscriber-user-
                   data" inside <> capable of receiving mail.
There is assumed no Printer attribute to be an SMTP mail
                   address hold this email address, so that it
cannot be configured using the mail system will send failure to
                   deliver mail messages to the mail address specified
                   by IPP protocol without an implementation-
defined attribute extension.

6.1.3 'Subject' header

Syntax: "Subject"  ":"  *text

This header specifies the "subscriber-user-data", not subject of the Printer.

4.5.1    To:       The rest message and contains a short
summary of the URI following Event Notification.

The Printer MUST include a "Subject" header whose syntax is specified
above.

The Printer MUST localize the 'mailto:' scheme
                   in '*text' using the value values of the "notify-recipient" attribute.

4.7.1    Subject:  Implementation-dependent, but "notify-
charset" and "notify-natural-language" Subscription Object attributes.

For Printer Events, the '*text' SHOULD start with
                   "Printer message: " (localized) the localized word
"printer:", followed by the job
                   or printer event name, job Printer name, etc.  The beginning
                   of and then followed by the Subject line is a standardized prefix, so
                   that mail agents can filter from any Printer.

The Printer MUST repeat any of this information
localized Event name, e.g., in these fields English: "printer: 'tiger' stopped" or in
French: 'imprimeur: 'tigre' arr.t.'.

For Job Events, the
body of '*text' SHOULD start with the message, plus additional information REQUIRED localized phrase
"print job:", followed by the
Notification Specification [ipp-ntfy].

                      Expires: September 9, 2000

5.1 Human Consumable Form

If the format specified Job name, and then followed by the "notify-format" (mimeMediaType)
localized Event name, e.g., in English: "print job: 'financials'
completed".

The wording is a
Human Consumable form, then it implementation dependent.  A Notification Recipient MUST
NOT expect to be sent as 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 MIME according typical email reader to
[rfc1341] 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 [rfc2046] if its value satisfies the MIME type RFC 822 syntax rules for 'mailbox', the
Printer MUST include a "Sender" header whose syntax is anything but 'text/plain'.
Even 'text/plain; charset=utf-8' specified above.
Otherwise, the Printer MUST be represented as NOT include a MIME type in "Sender" header.

For the body of "Sender" header, the message.

ISSUE 06: What if "notify-format" is 'text/plain; charset=utf-8', does
that have to be sent as a mail attachment, since it isn't 'text/plain'
which assumes charset=us-ascii, or can it 'mailbox' MUST be sent as the body value of the
mail message properly identified as 'text/plain; charset=us-ascii'?

5.2 Machine Consumable Form

If "notify-
user-data" Subscription Object attribute. See section 5.2.2 for details
about the format specified by "notify-user-data" attribute.

6.1.5 'Reply-to' header

Syntax:   "Reply-to" ":" mailbox

If the "notify-format" (mimeMediaType) is a
Machine Consumable form, then it MUST be sent as Notification Recipient replies to Event Notification email, this
header causes a MIME attachment
according typical email reader to [rfc1341] and [rfc2046], including the 'application/ipp'.

6  Printer Description attributes specific send email to the 'mailto:' delivery
   method

This section defines Printer Description attributes that person acting
as the Subscribing Client. The rules are REQUIRED
when supporting identical to the 'mailto:' delivery method.

6.1 "printer-smtp-mail-service-address" (1setOf text(MAX))

This REQUIRED Printer Description attribute "Sender"
header.

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

If the Subscription Object contains the DNS or IP
address of "notify-user-data" attribute,
and if its value satisfies the SMTP relaying mail server (see [rfc822]) that 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 use changed to send mail messages when supporting the 'mailto:' delivery
method. 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 System Administrator is expected to configure this
attribute with one or more values. .mailto:. Notification Delivery MethodJuly 7,
2000

  raison: papier coinc.

7  Conformance Requirements

If the IPP Printer supports the 'mailto:' notification delivery scheme, 'mailto' Delivery Method, the Printer MUST meet these conformance requirements:

1.MUST meet MUST:

1.meet the conformance requirements defined in [ipp-ntfy].

2.MUST support at least the 'text/plain' Notification Content format.
  Being able to support any other MIME media types (MUST be sent as
  mail attachments) is OPTIONAL..

3.MUST support

2.support the "notify-mailto-text-only " Subscription Object attribute semantics specified
  defined in section 4 when sending Notifications.

4.MUST fill in 5.1.1.

3.support the SMTP fields in syntax for the mail message as specified "notify-recipient-uri" Subscription Object
  attribute defined in section 5.

                      Expires: September 9, 2000

5.MUST support 5.2.1

4.support the "printer-smtp-mail-service-address" (1setOf
  text(MAX)) Printer Description use for the "notify-user-data" Subscription Object
  attribute defined in section 6. 5.2.2

5.support SMTP for sending Event Notifications.

6.support the 'text/plain' Content-Type for the message body.

7.support sending Event Notification via email with the content
  specified in section 5.2.

8  IANA Considerations

Since

Because the 'mailto:' 'mailto' URL scheme is already defined in a standards track
document [RFC 2368] and registered with IANA, this document does not
require anything further of IANA.

9  Internationalization Considerations

This notification delivery method Delivery Method presents no additional internationalization considerations already
beyond those covered in the [ipp-ntfy]
document.  The IPP Printer MUST localize the Human Consumable format document, and
the 'text' attributes in the Machine Consumable form. sections 6.1.3 and
6.2 of this document.

The Notification Recipient is expected to localize the attributes in present the Machine
Consumable that have email as received
because the 'keyword' attribute syntax according Printer does all necessary localization to the
charset and natural language supplied in the Event
Notification Content which
is derived from the Subscription object as supplied by the Subscriber. contents.

10 Security Considerations

By far the

The biggest security concern is the abuse of notification:
sending unwanted notifications that a Subscribing Client will cause
unsolicited Event Notifications to be sent to third parties parties, potentially
creating denial-of-service problems (i.e., spam).  The problem is made even
worse by notification addresses that may be
redistributed to multiple if the third parties (e.g. mailing lists). are distribution lists.

There exist 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 persons before sending out anything. they can become
Notification Recipients.  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  To

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

minimize the risk, a Printer could disallow third party notifications Notification
Recipients (a traditional facsimile model).

Sometimes the Notification Recipient is not

The Delivery Method recommends that the same person Subscribing Client supply his or
her email address as the
person who created the Subscription.  It is possible for the
Notification Recipient to find out who created the Subscription, since
the subscriber MUST supply value of the "subscriber-user-name" Subscription "notify-user-data" attribute in
the Subscription Creation operation.

The [ipp-ntfy] document discusses general security considerations for
notifications.  Some delivery methods, such as the 'ipp:' delivery
method, avoid the spam problem because the Notification Recipient pulls
the Notifications Operation when desired.  The 'indp:' [indp-method] delivery
method allows the Notification Recipient to return is a special status code
reply to the IPP Printer Send-Notifications operation to cancel
third party. To reduce the
subscription.  The 'mailto:' delivery method does not permit either chance of
these remedies.

ISSUE 07 - Is there any way that a Notification Recipient could reply to spamming or identify the message in such spammer, a way as to cancel
Printer could disallow third party Notification Recipients if the subscription and thereby
solve
Subscribing Client doesn't supply the spam problem?

                      Expires: September 9, 2000 "notify-user-data" attribute with
a valid email address.

Some firewall administrators are preventing prevent mail attachments from being
accepted into their organizations because of the problem of the
attachments containing computer viruses.  The 'mailto:' delivery method 'mailto' Delivery Method
allows the subscriber Subscribing Client to suppress sending any attachments, by specifying
only request that the 'text/plain' MIME media type. Content-Type of a
message body be 'text/plain'.

11 References

[ipp-coll]
     deBry, R., ,

[ipp-iig]
     Hastings, T., Herriot, R., Manros, C., Kugler, K, Holst H., Zehler, P.,
     "Internet Printing
     Protocol/1.0 & 1.1: collection attribute syntax", <draft-ietf-ipp-
     collection-00.doc>, Protocol/1.1:  draft-ietf-ipp-implementers-
     guide-v11-01.txt, work in progress, September May 9, 1999. 2000

[ipp-mod]
     R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
     "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]
     Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,
     Bergman, R., "Internet Printing Protocol/1.1: IPP Event
     Notification Specification", <draft-ietf-ipp-not-spec-01.txt>,
     October 14, 1999. <draft-ietf-ipp-not-spec-03.txt>, May
     10, 2000.

[ipp-pro]
     Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
     Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
     03.txt, June, 1999.

[rfc821]
     05.txt, March 1, 2000.

[RFC821]
     Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821,
     August, 1982.

[rfc822]

[RFC822]
     David H. Crocker, "Standard For The Format Of ARPA Internet Text
     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
     Extensions): Mechanisms for Specifying and Describing the Format of
     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
     2026, October 1996.

[rfc2046]
     Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types.
     N. Freed & N. Borenstein. November 1996. (Obsoletes RFC1521,
     RFC1522, RFC1590),

[RFC2046]
     R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
     Leach, T. Berners-Lee,  "Hypertext Transfer Protocol - HTTP/1.1",
     RFC 2046.

                      Expires: September 9, 2000

[rfc2616] 2616, June 1999.

[RFC2368]
     P. Hoffman, L. Masinter, J. Zawinski, "The mailto URL scheme", RFC
     2616, July 1998.

 [RFC2616]
     R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
     Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
     RFC 2616, June 1999.

 [RFC2633]
     B. Ramsdell, "S/MIME Version 3 Message Specification", RFC 2633,
     June 1999.

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
   i-data international a/s
   Vadstrupvej 35-43
   2880 Bagsvaerd, Denmark

INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000

   Phone: +45 4436-6000
   Fax: +45 4436-6111
   e-mail: hh@i-data.com

   Tom Hastings
   Xerox Corporation
   737 Hawaii St.  ESAE 231
   El Segundo, CA  90245

   Phone: 310-333-6413
   Fax: 310-333-5514
   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

Copyright (C) The Internet Society (2000). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
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
or references to the Internet Society or other Internet organizations,
except as needed for the  purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.

                      Expires: September 9, 2000