draft-ietf-ipp-notify-mailto-01.txt   draft-ietf-ipp-notify-mailto-02.txt 
INTERNET-DRAFT INTERNET-DRAFT
<draft-ietf-ipp-notify-mailto-01.txt> Robert Herriot <draft-ietf-ipp-notify-mailto-02.txt> Robert Herriot
Xerox Corp. Xerox Corp.
Henrik Holst Henrik Holst
i-data international a/s i-data international a/s
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
Carl-Uno Manros Carl-Uno Manros
Xerox Corp. Xerox Corp.
July 7, 2000 July 13, 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
skipping to change at page 2, line 5 skipping to change at page 2, line 11
The notification extension document [ipp-ntfy] specifies that each The notification extension document [ipp-ntfy] specifies that each
Delivery Method is defined in another document. This document is one Delivery Method is defined in another document. This document is one
such document, and it specifies the 'mailto' delivery method. such document, and it specifies the 'mailto' delivery method.
For this Delivery Method, when an Event occurs, the Printer immediately For this Delivery Method, when an Event occurs, the Printer immediately
sends an Event Notification via an email message to the Notification sends an Event Notification via an email message to the Notification
Recipient specified in the Subscription Object. The message body of the Recipient specified in the Subscription Object. The message body of the
email consists of Human Consumable text and is not intended to be parsed email consists of Human Consumable text and is not intended to be parsed
by a machine. by a machine.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
The Notification Recipient receives the Event Notification in the same The Notification Recipient receives the Event Notification in the same
way as it receives any other email message. way as it receives any other email message.
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): IPP Event Notification Internet Printing Protocol (IPP): IPP Event Notification
skipping to change at page 4, line 5 skipping to change at page 4, line 9
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.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
The "Event Notification Specification" document describes an extension The "Event Notification Specification" document describes an extension
to the IPP/1.0, IPP/1.1, and future versions. This extension allows a to the IPP/1.0, IPP/1.1, and future versions. This extension allows a
client to subscribe to printing related Events. The Subscription Object client to subscribe to printing related Events. The Subscription Object
specifies that when one of the specified Event occurs, the Printer sends specifies that when one of the specified Event occurs, the Printer sends
an asynchronous Event Notification to the specified Notification an asynchronous Event Notification to the specified Notification
Recipient via the specified Delivery Method (i.e., protocol). A client Recipient via the specified Delivery Method (i.e., protocol). A client
associates Subscription Objects with a particular Job by performing the associates Subscription Objects with a particular Job by performing the
Create-Job-Subscriptions operation or by submitting a Job with Create-Job-Subscriptions operation or by submitting a Job with
subscription information. A client associates Subscription Objects with subscription information. A client associates Subscription Objects with
the Printer by performing a Create-Printer-Subscriptions operation. the Printer by performing a Create-Printer-Subscriptions operation.
Four other operations are defined for Subscription Objects: Get- Four other operations are defined for Subscription Objects: Get-
Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and
Cancel-Subscription. Cancel-Subscription.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
Table of Contents Table of Contents
1 Introduction......................................................7 1 Introduction......................................................7
2 Terminology.......................................................7 2 Terminology.......................................................7
3 Model and Operation...............................................7 3 Model and Operation...............................................7
4 General Information...............................................8 4 General Information ...............................................9
5 Subscription Template Attributes..................................9 5 Subscription Template Attributes .................................11
5.1 Additional Subscription Template Attributes.....................9 5.1 Additional Subscription Template Attributes ...................11
5.1.1 notify-mailto-text-only (boolean)9 5.1.1 notify-mailto-text-only (boolean)..........................11
5.2 Additional Information about Subscription Template Attributes..10 5.2 Additional Information about Subscription Template Attributes .12
5.2.1 notify-recipient-uri (uri).................................10 5.2.1 notify-recipient-uri (uri).................................12
5.2.2 notify-user-data (octetString(63)).........................10 5.2.2 notify-user-data (octetString(63)).........................12
6 Event Notification Content.......................................11 6 Event Notification Content .......................................13
6.1 Headers........................................................11 6.1 Headers .......................................................13
6.1.1 'Date' header..............................................11 6.1.1 'Date' header..............................................13
6.1.2 'From' header..............................................11 6.1.2 'From' header..............................................13
6.1.3 'Subject' header...........................................12 6.1.3 'Subject' header...........................................14
6.1.4 'Sender' header............................................12 6.1.4 'Sender' header............................................14
6.1.5 'Reply-to' header..........................................12 6.1.5 'Reply-to' header..........................................15
6.1.6 'To' header................................................13 6.1.6 'To' header................................................15
6.1.7 'Content-type' header......................................13 6.1.7 'Content-type' header......................................16
6.2 Message Body...................................................13 6.2 Message Body ..................................................16
6.2.1 Information in Event Notification Content Common to All Events 6.2.1 Event Notification Content Common to All Events............17
.............................................................14 6.2.2 Additional Event Notification Content for Job Events.......19
6.2.2 Additional Information in Event Notification Content for Job 6.2.3 Additional Event Notification Content for Printer Events...20
Events...........................................................15 6.3 Examples ......................................................21
6.2.3 Additional Information in Event Notification Content for 6.3.1 Job Event Example..........................................21
Printer Events...................................................16 6.3.2 Printer Event Example......................................23
6.3 Examples.......................................................16 6.3.3 Printer Event Example (localized to Danish)...............24
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.........................................20 7 Conformance Requirements .........................................25
8 IANA Considerations..............................................20 8 IANA Considerations ..............................................25
9 Internationalization Considerations..............................20 9 Internationalization Considerations ..............................26
10 Security Considerations..........................................20 10 Security Considerations ..........................................26
11 References.......................................................21 11 References .......................................................27
12 Author's Addresses...............................................22 12 Author's Addresses ...............................................28
13 Full Copyright Statement.........................................23 13 Full Copyright Statement .........................................29
Table of Tables Table of Tables
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7, Table 1 - Information about the Delivery Method.......................9
2000
Table 1 . Printer Name in Event Notification Content.................15
Table 2 . Event Name in Event Notification Content 15 Table 2 - Printer Name in Event Notification Content.................18
Table 4 . Job Name in Event Notification Content for Job Events......15 Table 3 - Event Name in Event Notification Content...................19
Table 5 . Job State in Event Notification Content for Job Events.....16 Table 4 - Job Name in Event Notification Content.....................19
Table 6 . Printer State in Event Notification Content for Printer Events Table 5 - Job State in Event Notification Content....................20
.................................................................16
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7, Table 6 - Printer State in Event Notification Content................21
2000
1 Introduction 1 Introduction
The notification extension document [ipp-ntfy] defines operations that a The notification extension document [ipp-ntfy] defines operations that a
client can perform in order to create Subscription Objects in a Printer client can perform in order to create Subscription Objects in a Printer
and carry out other operations on them. A Subscription Object represents and carry out other operations on them. A Subscription Object represents
a Subscription abstraction. The Subscription Object specifies that when a Subscription abstraction. The Subscription Object specifies that when
one of the specified Events occurs, the Printer sends an asynchronous one of the specified Events occurs, the Printer sends an asynchronous
Event Notification to the specified Notification Recipient via the Event Notification to the specified Notification Recipient via the
specified Delivery Method (i.e., protocol). specified Delivery Method (i.e., protocol).
skipping to change at page 8, line 5 skipping to change at page 8, line 15
For this Delivery Method, the "notify-recipient-uri" attribute value For this Delivery Method, the "notify-recipient-uri" attribute value
MUST consist of a "mailto" scheme followed by a colon, and then followed MUST consist of a "mailto" scheme followed by a colon, and then followed
by an address part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for by an address part (e.g. 'mailto:smith@abc.com'). See section 5.2.1 for
the syntax of the "notify-recipient-uri" attribute value for this the syntax of the "notify-recipient-uri" attribute value for this
Delivery Method. Delivery Method.
A Printer MUST support SMTP [RFC821], and it MAY support other email A Printer MUST support SMTP [RFC821], and it MAY support other email
protocols. A Printer MAY use additional services, such as SMTP delivery protocols. A Printer MAY use additional services, such as SMTP delivery
status notification [RFC1891] or S/MIME encryption [RFC2633]. status notification [RFC1891] or S/MIME encryption [RFC2633].
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
If the client wants the Printer to send Event Notifications via the If the client wants the Printer to send Event Notifications via the
'mailto' Delivery Method, the client MUST choose a value for "notify- 'mailto' Delivery Method, the client MUST choose a value for "notify-
recipient-uri" attribute which conforms to the rules of section 5.2.1. recipient-uri" attribute which conforms to the rules of section 5.2.1.
To avoid denial-of-service attacks, a client SHOULD NOT use distribution To avoid denial-of-service attacks, a client SHOULD NOT use distribution
lists as the Notification Recipient. lists as the Notification Recipient.
When an Event occurs, the Printer MUST immediately: When an Event occurs, the Printer MUST immediately:
1. Find all pertinent Subscription Objects P according to the rules of 1. Find all pertinent Subscription Objects P according to the rules of
section 9 of [ipp-ntfy], AND section 9 of [ipp-ntfy], AND
skipping to change at page 8, line 38 skipping to change at page 9, line 4
value (see section 5.2.1). value (see section 5.2.1).
If the Printer supports only SMTP, it MUST send the email message via If the Printer supports only SMTP, it MUST send the email message via
SMTP. If the Printer supports additional email protocols, it MUST SMTP. If the Printer supports additional email protocols, it MUST
determine the protocol from the address part of the "notify-recipient- determine the protocol from the address part of the "notify-recipient-
uri" attribute value and then send the email message via the appropriate uri" attribute value and then send the email message via the appropriate
email protocol. email protocol.
When a Subscription Object is listening to a frequently occurring Event, When a Subscription Object is listening to a frequently occurring Event,
such as 'job-progress', the Printer MUST moderate the sending of Event such as 'job-progress', the Printer MUST moderate the sending of Event
Notifications caused by such an Event. It is implementation dependent as Notifications caused by such an Event. It is implementation dependent as
to how a Printer moderates Events and how a human controls the to how a Printer moderates Events and how a human controls the
moderation. moderation.
4 General Information 4 General Information
If a Printer supports this Delivery Method, the following are its
characteristics.
According to the notification extension document [ipp-ntfy], this Table 1 - Information about the Delivery Method
document MUST contain the following information:
1.The URL scheme name for the Delivery Method is: 'mailto'
2.Printer support for this delivery method is OPTIONAL.
3.For Event Notification content, a Printer MUST support SMTP. It MAY Document Method Conformance Delivery Method Realization
support other email protocols. Requirement
4.Several Event Notifications MUST NOT be combined into a compound 1. What is the URL scheme name mailto
Event Notification. The Printer MUST send them as separate email for the Delivery Method?
messages.
5.The Printer MUST initiate the Delivery Method. 2. Is the Delivery Method RECOMMENDED
REQUIRED, RECOMMEND, or
OPTIONAL for an IPP Printer
to support?
6.The Delivery Method sends Human Consumable Event Notifications. 3. What transport and delivery
protocols does the Printer use support other email protocols.
to deliver the Event
Notification Content, i.e.,
what is the entire network A Printer MUST support SMTP. It MAY
stack?
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7, 4. Can several Event A Printer implementation MAY
2000 Notifications be combined into combine several Event Notifications
a Compound Event Notification? into a single email message.
7.The representation and encoding for each piece of information MUST be 5. Is the Delivery Method This Delivery Method is a push.
plain text (see section 5.2.2). An implementation MAY send the initiated by the Notification
information in other encodings. Recipient (pull), or by the
Printer (push)?
8.In the Event Notification content, a Printer MUST send all pieces of 6. Is the Event Notification Human Consumable
information specified in section 5.2.2. content Machine Consumable or
Human Consumable?
9.Frequently occurring Events MUST be moderated to prevent Notification 7. What section in this document Section 6
Recipients from receiving excessive email. answers the following
question? For a Machine
Consumable Event Notification,
what is the representation and
encoding of values defined in
section 9.1 of [ipp-ntfy] and
the conformance requirements
thereof? For a Human
Consumable Event Notification,
what is the representation and
encoding of pieces of
information defined in section
9.2 of [ipp-ntfy] and the
conformance requirements
thereof?
10. This Delivery Method has the same latency and reliability as the 8. What are the latency and
underlying SMTP (or other) transport. reliability of the transport Same as the underlaying SMTP (or other
and delivery protocol? optional email transport)
11. This Delivery Method has the same security aspects as the 9. What are the security aspects
underlying SMTP (or other) transport. of the transport and delivery Same as the underlying SMTP (or other
protocol, e.g., how it is optional email transport)
handled in firewalls?
12. This Delivery Method has no content length restrictions. 10. What are the content length None
restrictions?
13. There are no additional values that a Printer MUST send in a 11. What are the additional None
Notification content. values or pieces of
information that a Printer
sends in an Event Notification
content and the conformance
requirements thereof?
14. There is one additional Subscription Template attributes. See 12. What are the additional See section 5.1.1 on "notify-
section 5.1.1. Subscription Template and/or mailto-text-only"
Subscription Description
attributes and the conformance
requirements thereof?
15. There are no additional Printer Description attributes. 13. What are the additional None
Printer Description attributes
and the conformance
requirements thereof?
5 Subscription Template Attributes 5 Subscription Template Attributes
5.1 Additional Subscription Template Attributes 5.1 Additional Subscription Template Attributes
This Delivery Method introduces one additional Subscription Template This Delivery Method introduces one additional Subscription Template
Attribute. Attribute.
5.1.1 notify-mailto-text-only (boolean) 5.1.1 notify-mailto-text-only (boolean)
skipping to change at page 10, line 5 skipping to change at page 11, line 33
attribute, the Printer MUST populate this attribute with the value of attribute, the Printer MUST populate this attribute with the value of
'false' on the Subscription Object. There is no "notify-mailto-text- 'false' on the Subscription Object. There is no "notify-mailto-text-
only-default" attribute. only-default" attribute.
If the value of this attribute is 'true' in a Subscription Object, the If the value of this attribute is 'true' in a Subscription Object, the
message body of each Event Notification that the Printer generates from message body of each Event Notification that the Printer generates from
the Subscription Object MUST contain plain text only (i.e. 'text/plain' the Subscription Object MUST contain plain text only (i.e. 'text/plain'
with the charset specified by the "notify-charset' Subscription Object with the charset specified by the "notify-charset' Subscription Object
attribute). attribute).
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
If the value of this attribute is 'false' in a Subscription Object, the If the value of this attribute is 'false' in a Subscription Object, the
message body of each Event Notification that the Printer generates from message body of each Event Notification that the Printer generates from
the Subscription Object MAY contain any Content-Type (e.g. 'text/plain', the Subscription Object MUST contain a 'multipart/alternative'. One
'text/html', 'multipart/mixed', 'multipart/alternative', 'image/gif', message body of the 'multipart/alternative' MUST be the same as the
'audio/basic', etc.). 'text/plain' message body when this attribute has the value of 'true'.
Each of the other message bodies of the 'multipart/alternative' MAY be
any Content-Type (e.g. 'text/html', 'image/gif', 'audio/basic', etc.).
A Printer MUST support both values ('true' and 'false') of this A Printer MUST support both values ('true' and 'false') of this
attribute. There is no "notify-mailto-text-only-supported" attribute. attribute. There is no "notify-mailto-text-only-supported" attribute.
5.2 Additional Information about Subscription Template Attributes 5.2 Additional Information about Subscription Template Attributes
This section describes additional values for attributes defined in [ipp- This section describes additional values for attributes defined in [ipp-
ntfy]. ntfy].
5.2.1 notify-recipient-uri (uri) 5.2.1 notify-recipient-uri (uri)
This section describes the syntax of the value of this attribute for the This section describes the syntax of the value of this attribute for the
'mailto' Delivery Method. The syntax for values of this attribute for 'mailto' Delivery Method. The syntax for values of this attribute for
other Delivery Method is defined in other Delivery Method Documents. other Delivery Method is defined in other Delivery Method Documents.
In order to support the 'mailto' Delivery Method, the Printer MUST In order to support the 'mailto' Delivery Method, the Printer MUST
support the following syntax for the 'mailto' Delivery Method when the support the following syntax for the 'mailto' Delivery Method when the
Printer uses SMTP. The line below use RFC 822 syntax rules and terms. Printer uses SMTP. The line below use RFC 822 syntax rules and terms.
"mailto:" 1#mailbox "mailto:" mailbox
Note: the 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? Note: the above syntax allows 1 occurrence of 'mailbox'. The occurrence
of 'mailbox' represents an email address of a Notification Recipient.
This syntax
For SMTP, the phrase 'address part of the "notify-recipient-uri" For SMTP, the phrase 'address part' of the "notify-recipient-uri"
attribute value' refers to the 'mailbox' part of the value. attribute value refers to the 'mailbox' part of the value.
The Printer MAY support other syntax for the 'address part' if it The Printer MAY support other syntax for the 'address part' if it
supports other email protocols. supports email protocols in addition to SMTP.
5.2.2 notify-user-data (octetString(63)) 5.2.2 notify-user-data (octetString(63))
This attributes has a special use for the 'mailto' Delivery Method. It This attributes has a special use for the 'mailto' Delivery Method. It
specifies the email address of the Subscribing Client. It is primarily specifies the email address of the Subscribing Client. It is primarily
useful when the Notification Recipient is some person other than the useful when the Notification Recipient is some person other than the
Subscribing Client. Then the Notification Recipient has a way to reply Subscribing Client. Then the Notification Recipient has a way to reply
to the Subscribing Client. to the Subscribing Client.
If a client specifies this Delivery Method in a Subscription Creation If a client specifies this Delivery Method in a Subscription Creation
Operation, and the specified Notification Recipient is not associated Operation, and the specified Notification Recipient is not associated
with the same person as the client, the client SHOULD supply its email with the same person as the client, the client SHOULD supply its email
address as the value of the "notify-user-data" attribute. If the client address as the value of the "notify-user-data" attribute. If the client
does not supply this attribute, the Printer MUST NOT populate the does not supply this attribute, the Printer MUST NOT populate the
Subscription Object with this attribute. Subscription Object with this attribute.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
6 Event Notification Content 6 Event Notification Content
This section describes the content of an Event Notification sent via the This section describes the content of an Event Notification sent via the
'mailto' Delivery Method using the SMTP protocol. This document does 'mailto' Delivery Method using the SMTP protocol. This document does
not describe the content for other email protocols, but an not describe the content for other email protocols, but an
implementation should use this section as a model. implementation should use this section as a model.
When a Printer sends an email message via SMTP, the content MUST conform 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 to RFC 822. The following sections define the content that a Printer
MUST send. A Printer MAY send additional content as long as the MUST send. A Printer MAY send additional content as long as the
skipping to change at page 12, line 4 skipping to change at page 14, line 16
from the Printer that is sending the Event Notification. from the Printer that is sending the Event Notification.
The Printer MUST include a "From" header whose syntax is specified The Printer MUST include a "From" header whose syntax is specified
above. above.
The Printer MUST use the second alternative of the syntax for 'mailbox' The Printer MUST use the second alternative of the syntax for 'mailbox'
defined above (i.e. 'phrase route-addr'). The 'phrase' is the defined above (i.e. 'phrase route-addr'). The 'phrase' is the
Printer's display name and it MUST be the value of the "printer-name" Printer's display name and it MUST be the value of the "printer-name"
Printer attribute. The 'route-addr' MUST contain an email address Printer attribute. The 'route-addr' MUST contain an email address
(inside angle brackets) belonging to either an administrator or the (inside angle brackets) belonging to either an administrator or the
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
output-device. This email address NEED NOT be capable of receiving mail. output-device. This email address NEED NOT be capable of receiving mail.
There is no Printer attribute to hold this email address, so that it There is no Printer attribute to hold this email address, so that it
cannot be configured using the IPP protocol without an implementation- cannot be configured using the IPP protocol without an implementation-
defined attribute extension. defined attribute extension.
6.1.3 'Subject' header 6.1.3 'Subject' header
Syntax: "Subject" ":" *text Syntax: "Subject" ":" *text
This header specifies the subject of the message and contains a short This header specifies the subject of the message and contains a short
skipping to change at page 12, line 29 skipping to change at page 14, line 37
The Printer MUST include a "Subject" header whose syntax is specified The Printer MUST include a "Subject" header whose syntax is specified
above. above.
The Printer MUST localize the '*text' using the values of the "notify- The Printer MUST localize the '*text' using the values of the "notify-
charset" and "notify-natural-language" Subscription Object attributes. charset" and "notify-natural-language" Subscription Object attributes.
For Printer Events, the '*text' SHOULD start with the localized word For Printer Events, the '*text' SHOULD start with the localized word
"printer:", followed by the Printer name, and then followed by the "printer:", followed by the Printer name, and then followed by the
localized Event name, e.g., in English: "printer: 'tiger' stopped" or in localized Event name, e.g., in English: "printer: 'tiger' stopped" or in
French: 'imprimeur: 'tigre' arr.t.'. Danish: 'Printeren 'tiger' er standset'.
For Job Events, the '*text' SHOULD start with the localized phrase For Job Events, the '*text' SHOULD start with the localized phrase
"print job:", followed by the Job name, and then followed by the "print job:", followed by the Job name, and then followed by the
localized Event name, e.g., in English: "print job: 'financials' localized Event name, e.g., in English: "print job: 'financials'
completed". completed".
The wording is implementation dependent. A Notification Recipient MUST The wording is implementation dependent. A Notification Recipient MUST
NOT expect to be able to parse this text. But an email filter might look NOT expect to be able to parse this text. But an email filter might look
for "printer" or "print job". for "printer" or "print job".
skipping to change at page 13, line 5 skipping to change at page 15, line 26
6.1.5 'Reply-to' header 6.1.5 'Reply-to' header
Syntax: "Reply-to" ":" mailbox Syntax: "Reply-to" ":" mailbox
If the Notification Recipient replies to Event Notification email, this If the Notification Recipient replies to Event Notification email, this
header causes a typical email reader to send email to the person acting header causes a typical email reader to send email to the person acting
as the Subscribing Client. The rules are identical to the "Sender" as the Subscribing Client. The rules are identical to the "Sender"
header. header.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
If the Subscription Object contains the "notify-user-data" attribute, If the Subscription Object contains the "notify-user-data" attribute,
and if its value satisfies the RFC 822 syntax rules for "mailbox", the and if its value satisfies the RFC 822 syntax rules for "mailbox", the
Printer MUST include a "Reply-to" header whose syntax is specified Printer MUST include a "Reply-to" header whose syntax is specified
above. Otherwise, the Printer MUST NOT include a "Reply-to" header. above. Otherwise, the Printer MUST NOT include a "Reply-to" header.
For the "Reply-to" header, the "mailbox" MUST be the value of the For the "Reply-to" header, the "mailbox" MUST be the value of the
"notify-user-data" Subscription Object attribute. See section 5.2.2 for "notify-user-data" Subscription Object attribute. See section 5.2.2 for
details about the "notify-user-data" attribute. details about the "notify-user-data" attribute.
6.1.6 'To' header 6.1.6 'To' header
skipping to change at page 13, line 48 skipping to change at page 16, line 22
The Printer MUST include the "Content-Type" header. The Printer MUST include the "Content-Type" header.
If the value of the "notify-mailto-text-only" Subscription Object If the value of the "notify-mailto-text-only" Subscription Object
attribute is 'true', the 'type' MUST be "plain", the 'subtype' MUST be attribute is 'true', the 'type' MUST be "plain", the 'subtype' MUST be
"text" and the 'parameter' MUST be ' "charset=" XXX' where XXX is the "text" and the 'parameter' MUST be ' "charset=" XXX' where XXX is the
value of the "notify-charset" Subscription Object attribute, e.g. value of the "notify-charset" Subscription Object attribute, e.g.
'text/plain;charset=UTF-8'. 'text/plain;charset=UTF-8'.
If the value of the "notify-mailto-text-only" Subscription Object If the value of the "notify-mailto-text-only" Subscription Object
attribute is 'false, the values of 'type', 'subtype' and 'parameter' attribute is 'false', the 'type' MUST be "multipart", the 'subtype' MUST
MUST be values allowed by RFC 1521 or some registered MIME type. That be "alternative" and the 'parameter' MUST include the boundary string.
is, a Printer MAY send any format it wishes, e.g. html, images, audio, Each header of a body part of a multipart entity also has a Content-Type
or multipart. and its value of 'type', 'subtype' and 'parameter' MUST be values
allowed by RFC 1521 or some registered MIME type. That is, a Printer MAY
send any format it wishes in each body part of a multipart entity, e.g.
'text/html', 'image/gif', or 'audio/basic'.
6.2 Message Body 6.2 Message Body
This document describes a message body that is plain text. The content This document describes a message body that is plain text. The content
of all other Content-Types is implementation dependent. A Printer SHOULD of all other Content-Types is implementation dependent. A Printer MUST
include a plain text message even when it sends other Content-Types, include a plain text message even when it sends other Content-Types in a
i.e. the 'type' of the Content-Type SHOULD be 'multipart'. 'multipart/alternative'.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
When a Printer sends a plain text message, it MUST localize the text When a Printer sends a plain text message, it MUST localize the text
using the values of the "notify-charset" and "notify-natural-language" using the values of the "notify-charset" and "notify-natural-language"
Subscription Object attributes. Subscription Object attributes.
Section 9.2 in [ipp-ntfy] specifies the information that a Delivery Section 9.2 in [ipp-ntfy] specifies the information that a Delivery
Method MUST specify and a Printer SHOULD send. This section contains the Method MUST specify and a Printer SHOULD send. This section contains the
information from section 9.2 in [ipp-ntfy] and changes "Printer SHOULD information from section 9.2 in [ipp-ntfy] and changes "Printer SHOULD
send" to "Printer MUST send". send" to "Printer MUST send".
A Printer MUST send the following localized information in the message A Printer MUST send the following localized information in the message
body. The specific wording of this information and its layout are body. The specific wording of this information and its layout are
implementation dependent. implementation dependent.
a)the Printer name (see Table 1) a)the Printer name (see Table 2)
b)omitted (see below). b)omitted (see below).
c)for Printer Events only: c)for Printer Events only:
i) the Event (see Table 2) and/or Printer state information i) the Event (see Table 3) and/or Printer state information
(see Table 5) (see Table 6)
d)for Job Events only: d)for Job Events only:
i) the job identity (see Table 3) i) the job identity (see Table 4)
ii) the Event (see Table 2) and/or Job state information (see ii) the Event (see Table 3) and/or Job state information (see
Table 4) Table 5)
Item b) in the above list is omitted because the Printer sends the time Item b) in the above list is omitted because the Printer sends the time
of the Event as an email header (see section 6.1.1 on the 'Date' of the Event as an email header (see section 6.1.1 on the 'Date'
header). header).
The subsections of this section specify the attributes that a Printer The subsections of this section specify the attributes that a Printer
MUST use to obtain this information. MUST use to obtain this information.
The Printer MAY send additional information, depending on The Printer MAY send additional information, depending on
implementation. implementation.
skipping to change at page 14, line 52 skipping to change at page 17, line 36
The next three sections define the attributes in Event Notification The next three sections define the attributes in Event Notification
Contents that are: Contents that are:
a)for all Events a)for all Events
b)for Job Events only b)for Job Events only
c)for Printer Events only c)for Printer Events only
6.2.1 Information in Event Notification Content Common to All Events 6.2.1 Event Notification Content Common to All Events
The Printer MUST send the following information. The Printer MUST send the following information.
There is a separate table for each piece of information. Each row in the There is a separate table for each piece of information. Each row in the
table represents a source value for the information and the values are table represents a source value for the information and the values are
listed in order of preference, with the first one being the preferred listed in order of preference, with the first one being the preferred
one. An implementation SHOULD use the source value from the earliest row one. An implementation SHOULD use the source value from the earliest row
in each table. The tables in this section and following contain the in each table. It MAY use the source value from another row instead, or
following columns for each piece of information:
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7, it MAY combine the source values from several rows. An implementation is
2000 free to determine the best way to present this information.
The tables in this section and following contain the following columns
for each piece of information:
a)Source of Value: the name of the attribute that supplies the a)Source of Value: the name of the attribute that supplies the
value for the Event Notification value for the Event Notification
b)Source Object: the object from which the source value comes. b) Sends: if the Printer supports the value (column 1) on the
Source Object (column 3) the Delivery Method MUST specify
Table 1 lists the source of the information for the Printer Name. The MUST: that the Printer MUST send the value.
SHOULD: either that the Printer MUST send the value or that
the value is incompatible with the Delivery Method.
MAY: that the Printer MUST, SHOULD, MAY, MUST NOT, SHOULD NOT,
or NEED NOT send the value. The Delivery Method specifies the
level of conformance for the Printer.
c) Source Object: the object from which the source value comes.
In all tables of this section, all rows contain a "MAY" in order to
state that the Delivery Method specifies the conformance.
Table 2 lists the source of the information for the Printer Name. The
"printer-name" is more user-friendly unless the Notification Recipient "printer-name" is more user-friendly unless the Notification Recipient
is in a place where the Printer name is not meaningful. is in a place where the Printer name is not meaningful. For example, an
implementation could have the intelligence to send the value of the
"printer-name" attribute to a Notification Recipient that can access the
Printer via value of the "printer-name" attribute and otherwise send the
value of the "notify-printer-uri" attribute.
Table 1 . Printer Name in Event Notification Content Table 2 - Printer Name in Event Notification Content
Source Value Source Object Source Value Sends Source Object
printer-name (name(127)) Printer printer-name (name(127)) MAY Printer
notify-printer-uri (uri) Subscription Source Value Sends Source Object
Table 2 lists the source of the information for the Event name. A notify-printer-uri (uri) MAY Subscription
Table 3 lists the source of the information for the Event name. A
Printer MAY combine this information with state information described Printer MAY combine this information with state information described
for Jobs in Table 4 or for Printers in Table 5. for Jobs in Table 5 or for Printers in Table 6.
Table 2 . Event Name in Event Notification Content Table 3 - Event Name in Event Notification Content
Source Value Source Object Source Value Sends Source Object
notify-subscribed-event (type2 keyword) Subscription notify-subscribed-event (type2 keyword) MAY Subscription
6.2.2 Additional Information in Event Notification Content for Job 6.2.2 Additional Event Notification Content for Job Events
Events
This section lists the source of the additional information that a This section lists the source of the additional information that a
Printer MUST send for Job Events. Printer MUST send for Job Events.
Table 3 lists the source of the information for the job name. The "job- Table 4 lists the source of the information for the job name. The "job-
name" is likely more meaningful to a user than "job-id". name" is likely more meaningful to a user than "job-id".
Table 3 . Job Name in Event Notification Content for Job Events Table 4 - Job Name in Event Notification Content
Source Value Source Object Source Value Sends Source Object
job-name (name(MAX)) Job job-name (name(MAX)) MAY Job
job-id (integer(1:MAX)) Job Source Value Sends Source Object
Table 4 lists the source of the information for the job-state. If a job-id (integer(1:MAX)) MAY Job
Table 5 lists the source of the information for the job-state. If a
Printer supports the "job-state-message" and "job-detailed-state- Printer supports the "job-state-message" and "job-detailed-state-
message" attributes, it SHOULD use those attributes for the job state message" attributes, it SHOULD use those attributes for the job state
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
information, otherwise, it should fabricate such information from the information, otherwise, it should fabricate such information from the
"job-state" and "job-state-reasons". For some Events, a Printer MAY "job-state" and "job-state-reasons". For some Events, a Printer MAY
combine this information with Event information. combine this information with Event information.
Table 4 . Job State in Event Notification Content for Job Events Table 5 - Job State in Event Notification Content
Source Value Source Object Source Value Sends Source
Object
job-state-message (text(MAX)) Job job-state-message (text(MAX)) MAY Job
job-detailed-status-messages (1setOf text(MAX)) Job job-detailed-status-messages (1setOf MAY Job
text(MAX))
job-state (type1 enum) Job job-state (type1 enum) MAY Job
job-state-reasons (1setOf type2 keyword) Job job-state-reasons (1setOf type2 keyword) MAY Job
6.2.3 Additional Information in Event Notification Content for Printer 6.2.3 Additional Event Notification Content for Printer Events
Events
This section lists the source of the additional information that a This section lists the source of the additional information that a
Printer MUST send for Printer Events. Printer MUST send for Printer Events.
Table 5 lists the source of the information for the printer-state. If a Table 6 lists the source of the information for the printer-state. If a
Printer supports the "printer-state-message", it SHOULD use that Printer supports the "printer-state-message", it SHOULD use that
attribute for the job state information, otherwise it SHOULD fabricate attribute for the job state information, otherwise it SHOULD fabricate
such information from the "printer-state" and "printer-state-reasons". such information from the "printer-state" and "printer-state-reasons".
For some Events, a Printer MAY combine this information with Event For some Events, a Printer MAY combine this information with Event
information. information.
Table 5 . Printer State in Event Notification Content for Printer Events Table 6 - Printer State in Event Notification Content
Source Value Source Object Source Value Sends Source Object
printer-state-message (text(MAX)) Printer printer-state-message (text(MAX)) MAY Printer
printer-state (type1 enum) Printer printer-state (type1 enum) MAY Printer
printer-state-reasons (1setOf type2 keyword) Printer printer-state-reasons (1setOf type2 MAY Printer
keyword)
printer-is-accepting-jobs (boolean) Printer printer-is-accepting-jobs (boolean) MAY Printer
6.3 Examples 6.3 Examples
This section contains three examples. One is a Job Event and the other This section contains three examples. One is a Job Event and the other
two are Printer Events, the latter in French. two are Printer Events, the latter in Danish.
A Printer implementation NEED NOT generate Event Notification content
that is identical or even similar to these examples. In fact it would be
unfortunate if every implementation copied these example as is. These
examples merely show some possibilities and are not necessarily the best
way to convey information about an Event.
6.3.1 Job Event Example 6.3.1 Job Event Example
This section contains an example of an Event Notification of a Job This section contains an example of an Event Notification of a Job
Event. Event.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
A Subscribing Client Mike Jones (who works for xyz Corp.) performs a A Subscribing Client Mike Jones (who works for xyz Corp.) performs a
Subscription Creation Operation as part of the Print-Job operation on Subscription Creation Operation as part of the Print-Job operation on
Printer "ipp://tiger@abc.com". Mike Jones specifies that the "job-name" Printer "ipp://tiger@abc.com". Mike Jones specifies that the "job-name"
is "financials". Mike is printing the Job for Bill Smith at abc Corp. is "financials". Mike is printing the Job for Bill Smith at abc Corp.
The Subscription Object then has the following attributes: The Subscription Object then has the following attributes:
Attribute Name Attribute Value Attribute Name Attribute Value
notify-recipient-uri mailto:bsmith@abc.com notify-recipient-uri mailto:bsmith@abc.com
notify-events job-completed notify-events job-completed
notify-user-data mjones@xyz.com notify-user-data mjones@xyz.com
notify-mailto-text-only true notify-mailto-text-only true
notify-charset us-ascii notify-charset us-ascii
notify-natural-language en-us notify-natural-language en-us
notify-persistence false
notify-subscription-id 35692 notify-subscription-id 35692
notify-sequence-number 0 notify-sequence-number 0
notify-printer-up-time 34593 notify-printer-up-time 34593
notify-printer-uri ipp://tiger@abc.com notify-printer-uri ipp://tiger@abc.com
notify-job-id 345 notify-job-id 345
skipping to change at page 18, line 5 skipping to change at page 23, line 5
To: bsmith@abc.com To: bsmith@abc.com
Content-type: text/plain Content-type: text/plain
printer: tiger printer: tiger
job: financials job: financials
job-state: completed job-state: completed
The reader should note that the phrases are not identical to IPP The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English. keywords. They have been localized to English.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
6.3.2 Printer Event Example 6.3.2 Printer Event Example
This section contains an example of an Event Notification of a Printer This section contains an example of an Event Notification of a Printer
Event. Event.
A Subscribing Client Peter Williams, a Printer admin, performs a Create- A Subscribing Client Peter Williams, a Printer admin, performs a Create-
Printer-Subscriptions operation on Printer "ipp://tiger@abc.com". The Printer-Subscriptions operation on Printer "ipp://tiger@abc.com". The
Subscription Object then has the following attributes: Subscription Object then has the following attributes:
Attribute Name Attribute Value Attribute Name Attribute Value
skipping to change at page 18, line 29 skipping to change at page 23, line 26
notify-recipient-uri mailto:pwilliams@abc.com notify-recipient-uri mailto:pwilliams@abc.com
notify-events printer-state-changed notify-events printer-state-changed
notify-mailto-text-only true notify-mailto-text-only true
notify-charset us-ascii notify-charset us-ascii
notify-natural-language en-us notify-natural-language en-us
notify-persistence false
notify-subscription-id 4623 notify-subscription-id 4623
notify-sequence-number 0 notify-sequence-number 0
notify-printer-uptime 23002 notify-printer-uptime 23002
notify-printer-uri ipp://tiger@abc.com notify-printer-uri ipp://tiger@abc.com
notify-lease-expiration- 0 notify-lease-expiration- 0
time time
notify-subscriber-user- pwilliams notify-subscriber-user- pwilliams
name name
When the Printer jams, the Printer generates and sends the following When the Printer jams, the Printer generates and sends the following
email message: email message:
Date: 29 Aug 00 0832 PDT Date: 29 Aug 00 0832 PDT
From: tiger <printAdmin@abc.com> From: tiger <printAdmin@abc.com>
Subject: printer: 'tiger' stopped Subject: printer: 'tiger' has stopped
To: pwilliams@abc.com To: pwilliams@abc.com
Content-type: text/plain Content-type: text/plain
Printer tiger has stopped with a paper jam.
printer: tiger
state: stopped
reason: jammed paper
The reader should note that the phrases are not identical to IPP The reader should note that the phrases are not identical to IPP
keywords. They have been localized to English. keywords. They have been localized to English.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7, 6.3.3 Printer Event Example (localized to Danish)
2000
6.3.3 Printer Event Example (localized to French)
This section contains an example of an Event Notification of a Printer This section contains an example of an Event Notification of a Printer
Event. Event localized to Danish.
A Subscribing Client Pierre Veyrat, a Printer admin, performs a a A Subscribing Client Per Jensen, a Printer admin, performs a a Create-
Create-Printer-Subscriptions operation on Printer "ipp://tigre@def.com". Printer-Subscriptions operation on Printer "ipp://tiger@def.dk". The
The Subscription Object then has the following attributes: Subscription Object then has the following attributes:
Attribute Name Attribute Value Attribute Name Attribute Value
notify-recipient-uri mailto:pveyrat@def.com notify-recipient-uri mailto:pjensen@def.dk
notify-events printer-state-changed notify-events printer-state-changed
notify-mailto-text-only true notify-mailto-text-only true
notify-charset utf-8 notify-charset utf-8
notify-natural-language fr notify-natural-language da
notify-persistence false
notify-subscription-id 50225 notify-subscription-id 50225
notify-sequence-number 0 notify-sequence-number 0
notify-printer-uptime 53217 notify-printer-uptime 53217
notify-printer-uri ipp://tigre@def.com notify-printer-uri ipp://tiger@def.dk
notify-lease-expiration- 0 notify-lease-expiration- 0
time time
notify-subscriber-user- pveyrat notify-subscriber-user- pjensen
name name
When the Printer jams, the Printer generates and sends the following When the Printer jams, the Printer generates and sends the following
email message: email message:
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 Date: 29 Jan 00 0832 CET
From: tigre <admin@def.com> From: tiger <admin@def.dk>
Subject: imprimeur: 'tigre' arr.t. Subject: Printeren 'tiger' er standset
To: pveyrat@def.com To: pjensen@def.dk
Content-type: text/plain;charset=utf-8 Content-type: text/plain;charset=utf-8
imprimeur: tigre@def.com Printerens navn er 'tiger'.
.tat: arr.t. Printeren er standset.
Aarsagen er papir stop.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
raison: papier coinc.
7 Conformance Requirements 7 Conformance Requirements
The 'mailto' Delivery Method is RECOMMENDED for a Printer to support.
If the Printer supports the 'mailto' Delivery Method, the Printer MUST: If the Printer supports the 'mailto' Delivery Method, the Printer MUST:
1.meet the conformance requirements defined in [ipp-ntfy]. 1.meet the conformance requirements defined in [ipp-ntfy].
2.support the "notify-mailto-text-only " Subscription Object attribute 2.support the "notify-mailto-text-only " Subscription Object attribute
defined in section 5.1.1. defined in section 5.1.1.
3.support the syntax for the "notify-recipient-uri" Subscription Object 3.support the syntax for the "notify-recipient-uri" Subscription Object
attribute defined in section 5.2.1 attribute defined in section 5.2.1
skipping to change at page 21, line 4 skipping to change at page 26, line 28
unsolicited Event Notifications to be sent to third parties, potentially unsolicited Event Notifications to be sent to third parties, potentially
creating denial-of-service problems (i.e., spam). The problem is even creating denial-of-service problems (i.e., spam). The problem is even
worse if the third parties are distribution lists. worse if the third parties are distribution lists.
There exist scenarios where third party notification is required (see There exist scenarios where third party notification is required (see
Scenario #2 and #3 in [ipp-not-req]). The fully secure solution would Scenario #2 and #3 in [ipp-not-req]). The fully secure solution would
require active agreement of all persons before they can become require active agreement of all persons before they can become
Notification Recipients. However, requirement #9 in [ipp-req] ("There Notification Recipients. However, requirement #9 in [ipp-req] ("There
is no requirement for IPP Printer receiving the print request to is no requirement for IPP Printer receiving the print request to
validate the identity of an event recipient") argues against this. To validate the identity of an event recipient") argues against this. To
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
minimize the risk, a Printer could disallow third party Notification minimize the risk, a Printer could disallow third party Notification
Recipients (a traditional facsimile model). Recipients (a traditional facsimile model).
The Delivery Method recommends that the Subscribing Client supply his or The Delivery Method recommends that the Subscribing Client supply his or
her email address as the value of the "notify-user-data" attribute in her email address as the value of the "notify-user-data" attribute in
the Subscription Creation Operation when the Notification Recipient is a the Subscription Creation Operation when the Notification Recipient is a
third party. To reduce the chance of spamming or identify the spammer, a third party. To reduce the chance of spamming or identify the spammer, a
Printer could disallow third party Notification Recipients if the Printer could disallow third party Notification Recipients if the
Subscribing Client doesn't supply the "notify-user-data" attribute with Subscribing Client doesn't supply the "notify-user-data" attribute with
a valid email address. a valid email address.
skipping to change at page 21, line 37 skipping to change at page 27, line 16
[ipp-iig] [ipp-iig]
Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P., Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P.,
"Internet Printing Protocol/1.1: draft-ietf-ipp-implementers- "Internet Printing Protocol/1.1: draft-ietf-ipp-implementers-
guide-v11-01.txt, work in progress, May 9, 2000 guide-v11-01.txt, work in progress, May 9, 2000
[ipp-mod] [ipp-mod]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf- "Internet Printing Protocol/1.0: Model and Semantics", <draft-ietf-
ipp-model-v11-06.txt>, March 1, 2000. 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-03.txt>, May Notification Specification", <draft-ietf-ipp-not-spec-04.txt>, July
10, 2000. 13, 2000.
[ipp-pro] [ipp-pro]
Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11- Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11-
05.txt, March 1, 2000. 05.txt, March 1, 2000.
[RFC821] [RFC821]
Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821, Jonathan B. Postel, "Simple Mail Transfer Protocol", RFC 821,
August, 1982. August, 1982.
[RFC822] [RFC822]
David H. Crocker, "Standard For The Format Of ARPA Internet Text David H. Crocker, "Standard For The Format Of ARPA Internet Text
Messages", RFC 822, August 13, 1982. Messages", RFC 822, August 13, 1982.
INTERNET-DRAFTIPP: The .mailto:. Notification Delivery MethodJuly 7,
2000
[RFC1341] [RFC1341]
N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail
Extensions): Mechanisms for Specifying and Describing the Format of Extensions): Mechanisms for Specifying and Describing the Format of
Internet Message Bodies", RFC 1341, June, 1992. Internet Message Bodies", RFC 1341, June, 1992.
[RFC1521] [RFC1521]
N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail N. Borenstein, N. Freed, "MIME (Multipurpose Internet Mail
Extensions) Part One: Mechanisms for Specifying and Describing the Extensions) Part One: Mechanisms for Specifying and Describing the
Format of Internet Message Bodies", RFC 1521, September 1993. Format of Internet Message Bodies", RFC 1521, September 1993.
skipping to change at page 23, line 5 skipping to change at page 28, line 47
Phone: 650-813-7696 Phone: 650-813-7696
Fax: 650-813-6860 Fax: 650-813-6860
Email: robert.herriot@pahv.xerox.com Email: robert.herriot@pahv.xerox.com
Henrik Holst Henrik Holst
i-data international a/s i-data international a/s
Vadstrupvej 35-43 Vadstrupvej 35-43
2880 Bagsvaerd, Denmark 2880 Bagsvaerd, Denmark
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
 End of changes. 

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