draft-ietf-ipp-notify-get-08.txt   draft-ietf-ipp-notify-get-09.txt 
Internet Printing Protocol WG R. Herriot Internet Printing Protocol WG R. Herriot
INTERNET-DRAFT consultant INTERNET-DRAFT consultant
<draft-ietf-ipp-notify-get-08.txt> T. Hastings <draft-ietf-ipp-notify-get-09.txt> T. Hastings
Updates: RFC 2911 and [ipp-ntfy] Xerox Corp. Updates: RFC 2911 and [ipp-ntfy] Xerox Corp.
[Target category: standards track] H. Lewis [Target category: standards track] H. Lewis
Expires: April 10, 2003 IBM Corp. Expires: August 21, 2003 IBM Corp.
October 10, 2002 February 21, 2003
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
The 'ippget' Delivery Method for Event Notifications The 'ippget' Delivery Method for Event Notifications
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Status of this Memo: Status of this Memo:
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 3, line 5 skipping to change at page 3, line 5
12 Conformance Requirements.......................................25 12 Conformance Requirements.......................................25
12.1 Conformance for IPP Printers.................................26 12.1 Conformance for IPP Printers.................................26
12.2 Conformance for IPP Clients..................................26 12.2 Conformance for IPP Clients..................................26
13 Normative References...........................................27 13 Normative References...........................................27
14 Informative References.........................................27 14 Informative References.........................................27
15 IANA Considerations............................................28 15 IANA Considerations............................................28
15.1 Attribute Registrations......................................29 15.1 Attribute Registrations......................................29
15.2 Additional keyword attribute value registrations for existing 15.2 Delivery Method and Additional keyword attribute value
attributes........................................................29 registrations for existing attributes.............................29
15.3 Additional enum attribute values.............................29 15.3 Additional enum attribute values.............................29
15.4 Operation Registrations......................................29 15.4 Operation Registrations......................................30
15.5 Status code Registrations....................................30 15.5 Status code Registrations....................................30
16 Internationalization Considerations............................30 16 Intellectual Property..........................................30
17 Security Considerations........................................30 17 Internationalization Considerations............................30
17.1 Notification Recipient client access rights..................31
17.2 Printer security threats.....................................31
17.3 Notification Recipient security threats......................31
17.4 Security requirements for Printers...........................32
17.5 Security requirements for clients............................32
18 Contributors...................................................32 18 Security Considerations........................................31
18.1 Notification Recipient client access rights..................31
18.2 Printer security threats.....................................32
18.3 Notification Recipient security threats......................32
18.4 Security requirements for Printers...........................32
18.5 Security requirements for clients............................33
19 Authors' Addresses.............................................32 19 Contributors...................................................33
20 Description of Base IPP documents (Informative)................33 20 Authors' Addresses.............................................33
21 Full Copyright Statement.......................................35 21 Description of Base IPP documents (Informative)................34
22 Full Copyright Statement.......................................35
Table of Tables Table of Tables
Table 1 - Information about the Delivery Method....................7 Table 1 - Information about the Delivery Method....................7
Table 2 - Combinations of "notify-wait", "status-code", and "notify- Table 2 - Combinations of "notify-wait", "status-code", and "notify-
get-interval" .................................................16 get-interval" .................................................16
Table 3 - Attributes in Event Notification Content................19 Table 3 - Attributes in Event Notification Content................19
Table 4 - Additional Attributes in Event Notification Content for Job Table 4 - Additional Attributes in Event Notification Content for Job
Events ........................................................20 Events ........................................................20
Table 5 - Combinations of Events and Subscribed Events for "job- Table 5 - Combinations of Events and Subscribed Events for "job-
skipping to change at page 4, line 16 skipping to change at page 4, line 16
This document describes an extension to the Internet Printing This document describes an extension to the Internet Printing
Protocol/1.1: Model and Semantics [RFC 2911], [RFC 2910]. This Protocol/1.1: Model and Semantics [RFC 2911], [RFC 2910]. This
document specifies the 'ippget' Pull Delivery Method for use with the document specifies the 'ippget' Pull Delivery Method for use with the
"Internet Printing Protocol (IPP): Event Notifications and "Internet Printing Protocol (IPP): Event Notifications and
Subscriptions" specification [ipp-ntfy]. This IPPGET Delivery Method Subscriptions" specification [ipp-ntfy]. This IPPGET Delivery Method
is REQUIRED for all clients and Printers that support [ipp-ntfy]. is REQUIRED for all clients and Printers that support [ipp-ntfy].
The Notification Recipient, acting as a client, fetches (pulls) Event The Notification Recipient, acting as a client, fetches (pulls) Event
Notifications using the Get-Notifications operation defined in this Notifications using the Get-Notifications operation defined in this
document. For a description of the base IPP documents, see section document. For a description of the base IPP documents, see section
20 of this document. For a description of the IPP Event Notification 21 of this document. For a description of the IPP Event Notification
Model, see [ipp-ntfy]. Model, see [ipp-ntfy].
With this Pull Delivery Method, when an Event occurs, the Printer With this Pull Delivery Method, when an Event occurs, the Printer
saves the Event Notification for a period of time called the Event saves the Event Notification for a period of time called the Event
Life. The Notification Recipient fetches (pulls) the Event Life. The Notification Recipient fetches (pulls) the Event
Notifications using the Get-Notifications operation. This operation Notifications using the Get-Notifications operation. This operation
causes the Printer to return all Event Notifications held for the causes the Printer to return all Event Notifications held for the
specified Subscription object(s). If the Notification Recipient has specified Subscription object(s). If the Notification Recipient has
selected the Event Wait Mode option to wait for additional Event selected the Event Wait Mode option to wait for additional Event
Notifications, the Printer MAY continue to return Event Notifications Notifications, the Printer MAY continue to return Event Notifications
skipping to change at page 8, line 15 skipping to change at page 8, line 15
Notification, what is the Notification, what is the
representation and encoding of pieces representation and encoding of pieces
of information defined in section 9.2 of information defined in section 9.2
of [ipp-ntfy] and the conformance of [ipp-ntfy] and the conformance
requirements thereof? requirements thereof?
8. What are the latency and reliability Same as IPP and the 8. What are the latency and reliability Same as IPP and the
of the transport and delivery underlying HTTP of the transport and delivery underlying HTTP
protocol? transport protocol? transport
9. What are the security aspects of the Same as IPP and the 9. What are the security aspects of the
transport and delivery protocol, e.g., underlying HTTP transport and delivery protocol, e.g., underlying HTTP
how it is handled in firewalls? transport and in the how it is handled in firewalls? transportPandnintthe
same direction, so no same direction, so no
new firewall new firewall
considerations. considerations.
10.What are the content length None 10.What are the content length
restrictions? restrictions? None
11.What are the additional values or 11.What are the additional values or None
pieces of information that a Printer pieces of information that a Printer
sends in an Event Notification content sends in an Event Notification content
and the conformance requirements and the conformance requirements
thereof? None thereof?
12.What are the additional Subscription None 12.What are the additional Subscription None
Template and/or Subscription Template and/or Subscription
Description attributes and the Description attributes and the
conformance requirements thereof? conformance requirements thereof?
13.What are the additional Printer "ipp-event-life" 13.What are the additional Printer "ipp-event-life"
Description attributes and the (integer (15: MAX)) Description attributes and the (integer (15: MAX))
conformance requirements thereof? conformance requirements thereof?
skipping to change at page 16, line 19 skipping to change at page 16, line 19
returns: Notification returns: Notification
"notify-wait" "status-code" "notify-get- Attribute "notify-wait" "status-code" "notify-get- Attribute
interval" Groups interval" Groups
1. 'false'* 'successful-ok' MUST return N maybe 1. 'false'* 'successful-ok' MUST return N maybe
2. 'false'* 'not-found' MUST NOT MUST NOT 2. 'false'* 'not-found' MUST NOT MUST NOT
3. 'false'* 'busy' MUST return N MUST NOT 3. 'false'* 'busy' MUST return N MUST NOT
4. 'false'* 'events- MUST NOT 'job- 4. 'false'* 'events- 'job-
complete' completed' complete' MUST NOT completed'
5. 'true' 'successful-ok' MUST NOT MUST 5. 'true' 'successful-ok' MUST NOT MUST
6. 'true' 'successful-ok' MUST return N maybe 6. 'true' 'successful-ok' MUST return N maybe
7. 'true' 'not-found' MUST NOT MUST NOT 7. 'true' 'not-found' MUST NOT MUST NOT
8. 'true' 'busy' MUST return N MUST NOT 8. 'true' 'busy' MUST return N MUST NOT
9. 'true' 'events- MUST NOT 'job- 9. 'true' 'events- MUST NOT 'job-
skipping to change at page 26, line 45 skipping to change at page 26, line 45
8. MUST listen for the IPP Get-Notifications operation requests on 8. MUST listen for the IPP Get-Notifications operation requests on
IANA-assigned well-known port 631, unless explicitly configured IANA-assigned well-known port 631, unless explicitly configured
by system administrators or site policies; by system administrators or site policies;
9. SHOULD NOT listen for IPP Get-Notifications operation requests 9. SHOULD NOT listen for IPP Get-Notifications operation requests
on any other port, unless explicitly configured by system on any other port, unless explicitly configured by system
administrators or site policies. administrators or site policies.
10. MUST meet the security conformance requirements as stated in 10. MUST meet the security conformance requirements as stated in
section 17.4. section 18.4.
12.2 Conformance for IPP Clients 12.2 Conformance for IPP Clients
It is OPTIONAL for an IPP Client to support IPP Notifications as It is OPTIONAL for an IPP Client to support IPP Notifications as
defined in [ipp-ntfy]. However, if a client supports IPP defined in [ipp-ntfy]. However, if a client supports IPP
Notifications, the client MUST support the 'ippget' Delivery Method Notifications, the client MUST support the 'ippget' Delivery Method
as defined in this document as one of its Delivery Methods. IPP as defined in this document as one of its Delivery Methods. IPP
Clients that conform to this specification: Clients that conform to this specification:
1.MUST create Subscription Objects by sending Subscription 1.MUST create Subscription Objects by sending Subscription
skipping to change at page 27, line 22 skipping to change at page 27, line 22
2.MUST send IPP Get-Notifications operation requests (see section 2.MUST send IPP Get-Notifications operation requests (see section
5.1) via the port specified in the associated 'ipp' URL (if 5.1) via the port specified in the associated 'ipp' URL (if
present) or otherwise via IANA assigned well-known port 631; present) or otherwise via IANA assigned well-known port 631;
3.MUST convert the associated 'ipp' URLs for use in IPP Get- 3.MUST convert the associated 'ipp' URLs for use in IPP Get-
Notifications operation to their corresponding 'http' URL forms Notifications operation to their corresponding 'http' URL forms
for use in the HTTP layer according to the rules in section 5 for use in the HTTP layer according to the rules in section 5
"IPP URL Scheme" in [RFC2910]. "IPP URL Scheme" in [RFC2910].
4.MUST meet the security conformance requirements as stated in 4.MUST meet the security conformance requirements as stated in
section 17.5. section 18.5.
13 Normative References 13 Normative References
[ipp-ntfy] [ipp-ntfy]
Herriot, R., and T. Hastings, "Internet Printing Protocol/1.1: IPP Herriot, R., and T. Hastings, "Internet Printing Protocol/1.1: IPP
Event Notifications and Subscriptions", <draft-ietf-ipp-not-spec- Event Notifications and Subscriptions", <draft-ietf-ipp-not-spec-
10.txt>, September 10, 2002. 11.txt>, February 21, 2003.
[RFC2119] [RFC2119]
S. Bradner, "Key words for use in RFCs to Indicate Requirement S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119 , March 1997 Levels", RFC 2119 , March 1997
[RFC2910] [RFC2910]
Herriot, R., Butler, S., Moore, P., and R. Tuner, "Internet Herriot, R., Butler, S., Moore, P., and R. Tuner, "Internet
Printing Protocol/1.1: Encoding and Transport", RFC 2910, September Printing Protocol/1.1: Encoding and Transport", RFC 2910, September
2000. 2000.
skipping to change at page 29, line 11 skipping to change at page 29, line 11
Note to RFC Editors: Replace RFC NNNN below with the RFC number Note to RFC Editors: Replace RFC NNNN below with the RFC number
for this document, so that it accurately reflects the content of for this document, so that it accurately reflects the content of
the information for the IANA Registry. the information for the IANA Registry.
15.1 Attribute Registrations 15.1 Attribute Registrations
The following table lists the attributes defined in this document. The following table lists the attributes defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.2. [RFC2911] section 6.2.
Printer Description attributes: Ref. Section: Printer Description attributes: Reference Section
ippget-event-life (integer(15:MAX)) RFC NNNN 8.1 ------------------------------- --------- -------
ippget-event-life (integer(15:MAX)) [RFCNNNN] 8.1
15.2 Additional keyword attribute value registrations for existing 15.2 Delivery Method and Additional keyword attribute value
attributes registrations for existing attributes
This section lists additional keyword attribute value registrations This section lists additional keyword attribute value registrations
for use with existing attributes defined in other documents. These for use with existing attributes defined in other documents. These
are to be registered according to the procedures in RFC 2911 are to be registered according to the procedures in RFC 2911
[RFC2911] section 6.1. [RFC2911] section 6.1. According to [ipp-ntfy] section 24.7.3, Pull
Delivery Method registrations are the keyword attribute value
registrations for the "notify-pull-method" and "notify-pull-method-
supported" attributes.
keyword Attribute Values: Ref. Section: Attribute (attribute syntax)
Values Reference Section
----------------------- --------- -------
notify-pull-method (type2 keyword) [ipp-ntfy] 5.3.2 notify-pull-method (type2 keyword) [ipp-ntfy] 5.3.2
notify-pull-method-supported (1setOf type2 keyword) notify-pull-method-supported (1setOf type2 keyword)
[ipp-ntfy] 5.3.2.1 [ipp-ntfy] 5.3.2.1
ippget RFC NNNN 9.1 ippget [RFCNNNN] 9.1
15.3 Additional enum attribute values 15.3 Additional enum attribute values
The following table lists the enum attribute values defined in this The following table lists the enum attribute values defined in this
document. These are to be registered according to the procedures in document. These are to be registered according to the procedures in
RFC 2911 [RFC2911] section 6.1. RFC 2911 [RFC2911] section 6.1.
Attribute Attribute (attribute syntax)
Value Name Reference Section Value Name Reference Section
------ ----------------------------- --------- ------- ------ ----------------------------- --------- -------
operations-supported (type2 enum) RFC2911 4.4.15 operations-supported (type2 enum) [RFC2911] 4.4.15
0x001C Get-Notifications RFC NNNN 9.2 0x001C Get-Notifications [RFCNNNN] 9.2
15.4 Operation Registrations 15.4 Operation Registrations
The following table lists the operations defined in this document. The following table lists the operations defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.4. [RFC2911] section 6.4.
Operations: Ref. Section: Operations: Reference Section
Get-Notifications operation RFC NNNN 5 ----------- --------- -------
Get-Notifications [RFCNNNN] 5
15.5 Status code Registrations 15.5 Status code Registrations
The following table lists the status codes defined in this document. The following table lists the status codes defined in this document.
This is to be registered according to the procedures in RFC 2911 This is to be registered according to the procedures in RFC 2911
[RFC2911] section 6.6. [RFC2911] section 6.6.
Status codes: Ref. Section: Status codes: Reference Section
successful-ok-events-complete (0x0007) RFC NNNN 10.1 ------------- --------- -------
successful-ok-events-complete (0x0007) [RFCNNNN] 10.1
16 Internationalization Considerations 16 Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in RFC 2028. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
17 Internationalization Considerations
The IPP Printer MUST localize the "notify-text" attribute as The IPP Printer MUST localize the "notify-text" attribute as
specified in section 14 of [ipp-ntfy]. specified in section 14 of [ipp-ntfy].
In addition, when the client receives the Get-Notifications response, In addition, when the client receives the Get-Notifications response,
it is expected to localize the attributes that have the 'keyword' it is expected to localize the attributes that have the 'keyword'
attribute syntax according to the charset and natural language attribute syntax according to the charset and natural language
requested in the Get-Notifications request. requested in the Get-Notifications request.
17 Security Considerations 18 Security Considerations
The IPP Model and Semantics document [RFC2911 section 8] discusses The IPP Model and Semantics document [RFC2911 section 8] discusses
high-level security requirements (Client Authentication, Server high-level security requirements (Client Authentication, Server
Authentication and Operation Privacy). The IPP Transport and Authentication and Operation Privacy). The IPP Transport and
Encoding document [RFC2910 section 8] discusses the security Encoding document [RFC2910 section 8] discusses the security
requirements for the IPP protocol. Client Authentication is the requirements for the IPP protocol. Client Authentication is the
mechanism by which the client proves its identity to the server in a mechanism by which the client proves its identity to the server in a
secure manner. Server Authentication is the mechanism by which the secure manner. Server Authentication is the mechanism by which the
server proves its identity to the client in a secure manner. server proves its identity to the client in a secure manner.
Operation Privacy is defined as a mechanism for protecting operations Operation Privacy is defined as a mechanism for protecting operations
skipping to change at page 31, line 5 skipping to change at page 31, line 36
order to maintain the same security support as IPP/1.1. order to maintain the same security support as IPP/1.1.
The access control model for the Get-Notifications operation defined The access control model for the Get-Notifications operation defined
in this document is the same as the access control model for the Get- in this document is the same as the access control model for the Get-
Job-Attributes operation (see [RFC2911] section 3.2.6). The primary Job-Attributes operation (see [RFC2911] section 3.2.6). The primary
difference is that a Get-Notifications operation is directed at difference is that a Get-Notifications operation is directed at
Subscription Objects rather than at Job objects, and a returned Subscription Objects rather than at Job objects, and a returned
attribute group contains Event Notification attributes rather than attribute group contains Event Notification attributes rather than
Job object attributes. Job object attributes.
17.1 Notification Recipient client access rights 18.1 Notification Recipient client access rights
The Notification Recipient client MUST have the following access The Notification Recipient client MUST have the following access
rights to the Subscription object(s) targeted by the Get- rights to the Subscription object(s) targeted by the Get-
Notifications operation request: Notifications operation request:
The authenticated user (see [RFC2911] section 8.3) performing this The authenticated user (see [RFC2911] section 8.3) performing this
operation MUST be (1) the owner of each Subscription Object operation MUST be (1) the owner of each Subscription Object
identified by the "notify-subscription-ids" operation attribute identified by the "notify-subscription-ids" operation attribute
(see section 5.1.1), (2) an operator or administrator of the (see section 5.1.1), (2) an operator or administrator of the
Printer (see [RFC2911] Sections 1 and 8.5), or (3) be otherwise Printer (see [RFC2911] Sections 1 and 8.5), or (3) be otherwise
authorized by the Printer's administrator-configured security authorized by the Printer's administrator-configured security
policy to request Event Notifications from the target Subscription policy to request Event Notifications from the target Subscription
Object(s). Furthermore, the Printer's security policy MAY limit Object(s). Furthermore, the Printer's security policy MAY limit
the attributes returned by the Get-Notifications operation, in a the attributes returned by the Get-Notifications operation, in a
manner similar to the Get-Job-Attributes operation (see [RFC2911] manner similar to the Get-Job-Attributes operation (see [RFC2911]
end of section 3.3.4.2). end of section 3.3.4.2).
17.2 Printer security threats 18.2 Printer security threats
Because the Get-Notifications operation is sent in the same direction Because the Get-Notifications operation is sent in the same direction
as Job Creation operations, usually by the same client, this Event as Job Creation operations, usually by the same client, this Event
Notification Delivery Method poses no additional authentication, Notification Delivery Method poses no additional authentication,
authorization, privacy, firewall, or port assignment issues above authorization, privacy, firewall, or port assignment issues above
those for the IPP Get-Job-Attributes and Get-Printer-Attributes those for the IPP Get-Job-Attributes and Get-Printer-Attributes
operations (see [RFC2911] sections 3.2.6 and 3.2.5). operations (see [RFC2911] sections 3.2.6 and 3.2.5).
17.3 Notification Recipient security threats 18.3 Notification Recipient security threats
Unwanted Events Notifications (spam): Unlike Push Event Notification Unwanted Events Notifications (spam): Unlike Push Event Notification
Delivery Methods in which the IPP Printer initiates the Event Delivery Methods in which the IPP Printer initiates the Event
Notification, with the Pull Delivery Method defined in this document, Notification, with the Pull Delivery Method defined in this document,
the Notification Recipient is the client who initiates the Get- the Notification Recipient is the client who initiates the Get-
Notifications operation (see section 5). Therefore, there is no Notifications operation (see section 5). Therefore, there is no
chance of "spam" notifications with this method. chance of "spam" notifications with this method.
Note: when a client stays connected to a Printer using the Event Note: when a client stays connected to a Printer using the Event
Wait Mode (see section 5.1.3) in order to receive Event Notifications Wait Mode (see section 5.1.3) in order to receive Event Notifications
skipping to change at page 32, line 11 skipping to change at page 32, line 43
does a Get-Notifications request, the client gets all events for the does a Get-Notifications request, the client gets all events for the
Subscription Object in the sequence number range (see section 5.1.2), Subscription Object in the sequence number range (see section 5.1.2),
not just the ones the client wants. If a client subscribes to a Per- not just the ones the client wants. If a client subscribes to a Per-
Printer Subscription job event, such as 'job-completed', and someone Printer Subscription job event, such as 'job-completed', and someone
then starts and cancels thousands of jobs, the client would have to then starts and cancels thousands of jobs, the client would have to
receive these events in addition to the ones the client is interested receive these events in addition to the ones the client is interested
in. A client can protect itself better by subscribing to his own in. A client can protect itself better by subscribing to his own
jobs using a Per-Job Subscription, rather than creating a Per-Printer jobs using a Per-Job Subscription, rather than creating a Per-Printer
subscription whose Job events apply to all jobs. subscription whose Job events apply to all jobs.
17.4 Security requirements for Printers 18.4 Security requirements for Printers
For the Get-Notifications operation defined in this document, the For the Get-Notifications operation defined in this document, the
same Printer conformance requirements apply for supporting and using same Printer conformance requirements apply for supporting and using
Client Authentication, Server Authentication and Operation Privacy as Client Authentication, Server Authentication and Operation Privacy as
stated in [RFC2910] section 8 for all IPP operations. stated in [RFC2910] section 8 for all IPP operations.
17.5 Security requirements for clients 18.5 Security requirements for clients
For the Get-Notifications operation defined in this document, the For the Get-Notifications operation defined in this document, the
same client conformance requirements apply for supporting and using same client conformance requirements apply for supporting and using
Client Authentication, Server Authentication and Operation Privacy as Client Authentication, Server Authentication and Operation Privacy as
stated in [RFC2910] section 8 for all IPP operations. stated in [RFC2910] section 8 for all IPP operations.
18 Contributors 19 Contributors
Carl Kugler and Harry Lewis contributed the basic idea of in-band Carl Kugler and Harry Lewis contributed the basic idea of in-band
"smart polling" coupled with multiple responses for a single "smart polling" coupled with multiple responses for a single
operation on the same connection, one response for each event as it operation on the same connection, one response for each event as it
occurs. Without their continual persuasion, we would not have occurs. Without their continual persuasion, we would not have
arrived at this Delivery Method specification and would not have been arrived at this Delivery Method specification and would not have been
able to agree on a single REQUIRED Delivery Method for IPP. able to agree on a single REQUIRED Delivery Method for IPP.
Carl Kugler Carl Kugler
IBM IBM
P.O. Box 1900 P.O. Box 1900
Boulder, CO 80301-9191 Boulder, CO 80301-9191
Phone: Phone:
Fax: Fax:
e-mail: kugler@us.ibm.com e-mail: kugler@us.ibm.com
19 Authors' Addresses 20 Authors' Addresses
Robert Herriot Robert Herriot
706 Colorado Ave. 706 Colorado Ave.
Palo Alto, CA 94303 Palo Alto, CA 94303
Phone: 650-327-4466 Phone: 650-327-4466
Fax: 650-327-4466 Fax: 650-327-4466
email: bob@herriot.com email: bob@herriot.com
Thomas N. Hastings Thomas N. Hastings
Xerox Corporation Xerox Corporation
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo CA 90245 El Segundo CA 90245
skipping to change at page 33, line 47 skipping to change at page 34, line 31
end end
Implementers of this specification document are encouraged to join Implementers of this specification document are encouraged to join
the IPP Mailing List in order to participate in any discussions of the IPP Mailing List in order to participate in any discussions of
clarification issues and review of registration proposals for clarification issues and review of registration proposals for
additional attributes and values. In order to reduce spam the additional attributes and values. In order to reduce spam the
mailing list rejects mail from non-subscribers, so you must subscribe mailing list rejects mail from non-subscribers, so you must subscribe
to the mailing list in order to send a question or comment to the to the mailing list in order to send a question or comment to the
mailing list. mailing list.
20 Description of Base IPP documents (Informative) 21 Description of Base IPP documents (Informative)
The base set of IPP documents includes: The base 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 [RFC2911] Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910] Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [RFC3196] Internet Printing Protocol/1.1: Implementer's Guide [RFC3196]
Mapping between LPD and IPP Protocols [RFC2569] Mapping between LPD and IPP Protocols [RFC2569]
skipping to change at page 35, line 5 skipping to change at page 35, line 39
objects. It is intended to help them understand IPP/1.1 and some of 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 the considerations that may assist them in the design of their client
and/or IPP object implementations. For example, a typical order of and/or IPP object implementations. For example, a typical order of
processing requests is given, including error checking. Motivation processing requests is given, including error checking. Motivation
for some of the specification decisions is also included. for some of the specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some The "Mapping between LPD and IPP Protocols" document gives some
advice to implementers of gateways between IPP and LPD (Line Printer advice to implementers of gateways between IPP and LPD (Line Printer
Daemon) implementations. Daemon) implementations.
21 Full Copyright Statement 22 Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

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