idnits 2.17.1 draft-ietf-ipp-ops-admin-req-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 12 longer pages, the longest (page 9) being 77 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 6 Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 4 IANA Considerations' ) ** The document seems to lack an Authors' Addresses Section. ** There are 232 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([RFC2568], [RFC2616], [RFC2569], [IPP-PRO], [IPP-IIG], [IPP-MOD], [RFC2565,RFC2566], [RFC2566], [RFC2567]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 39: '...ements and use cases for some OPTIONAL...' RFC 2119 keyword, line 70: '... IPP/1.0. A few OPTIONAL operator ope...' RFC 2119 keyword, line 140: '... and use cases for additional OPTIONAL...' RFC 2119 keyword, line 145: '...rstands jobs and MAY represent one or ...' RFC 2119 keyword, line 183: '.... Such a Subordinate Printer MAY have...' (2 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 15, 2000) is 8649 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? 'RFC2565' on line 41 looks like a reference -- Missing reference section? 'RFC2566' on line 538 looks like a reference -- Missing reference section? 'RFC2567' on line 56 looks like a reference -- Missing reference section? 'RFC2568' on line 58 looks like a reference -- Missing reference section? 'IPP-MOD' on line 59 looks like a reference -- Missing reference section? 'IPP-PRO' on line 60 looks like a reference -- Missing reference section? 'IPP-IIG' on line 61 looks like a reference -- Missing reference section? 'RFC2569' on line 62 looks like a reference -- Missing reference section? 'RFC2616' on line 88 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 3 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Printing Protocol WG Carl Kugler 3 INTERNET-DRAFT H. Lewis 4 IBM Corporation 5 Category: Informational T. Hastings (editor) 6 Xerox Corporation 7 August 15, 2000 9 Internet Printing Protocol (IPP): 10 Requirements for Job, Printer, and Device Administrative Operations 12 Copyright (C) The Internet Society (2000). All Rights Reserved. 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with all 17 provisions of Section 10 of [rfc2026]. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, and 19 its working groups. Note that other groups may also distribute working 20 documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference material 25 or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed as 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This document is a submission to the Internet Printing Protocol Working 35 Group of the Internet Engineering Task Force (IETF). After approval, it 36 is intended to be an Informational RFC. Comments should be submitted to 37 the ipp@pwg.org mailing list. 39 This document specifies the requirements and use cases for some OPTIONAL 40 administrative operations for use with the Internet Printing 41 Protocol/1.0 (IPP) [RFC2565, RFC2566] and IPP/1.1 [ipp-mod, ipp-pro]. 42 Some of these administrative operations operate on the IPP Job and 43 Printer objects. The remaining operations operate on a new Device 44 object that more closely models a single output device (see [ipp-mod]). 46 Expires: January 17, 2001 47 The scope of IPP, is characterized in RFC2526 "Design Goals for an 48 Internet Printing Protocol". It is not the intent of this document to 49 revise or clarify this scope or conjecture as to the degree of industry 50 adoption or trends related to IPP within printing systems. It is the 51 intent of this document to extend the original set of operations - in a 52 similar fashion to the Set1 extensions which referred to IPP/1.0 and 53 were later incorporated into IPP/1.1. 55 The full set of IPP documents includes: 56 Design Goals for an Internet Printing Protocol [RFC2567] 57 Rationale for the Structure and Model and Protocol for the Internet 58 Printing Protocol [RFC2568] 59 Internet Printing Protocol/1.1: Model and Semantics [IPP-MOD] 60 Internet Printing Protocol/1.1: Encoding and Transport [IPP-PRO] 61 Internet Printing Protocol/1.1: Implementer's Guide [IPP-IIG] 62 Mapping between LPD and IPP Protocols [RFC2569] 64 The "Design Goals for an Internet Printing Protocol" document takes a 65 broad look at distributed printing functionality, and it enumerates 66 real-life scenarios that help to clarify the features that need to be 67 included in a printing protocol for the Internet. It identifies 68 requirements for three types of users: end users, operators, and 69 administrators. It calls out a subset of end user requirements that are 70 satisfied in IPP/1.0. A few OPTIONAL operator operations have been 71 added to IPP/1.1. 73 The "Rationale for the Structure and Model and Protocol for the Internet 74 Printing Protocol" document describes IPP from a high level view, 75 defines a roadmap for the various documents that form the suite of IPP 76 specification documents, and gives background and rationale for the IETF 77 working group's major decisions. 79 The "Internet Printing Protocol/1.1: Model and Semantics", describes a 80 simplified model with abstract objects, their attributes, and their 81 operations that are independent of encoding and transport. It introduces 82 a Printer object and a Job object. The Job object optionally supports 83 multiple documents per Job. It also addresses security, 84 internationalization, and directory issues. 86 The "Internet Printing Protocol/1.1: Encoding and Transport" document is 87 a formal mapping of the abstract operations and attributes defined in 88 the model document onto HTTP/1.1 [RFC2616]. It defines the encoding 89 rules for a new Internet MIME media type called "application/ipp". This 90 document also defines the rules for transporting over HTTP a message 91 body whose Content-Type is "application/ipp". This document defines a 92 new scheme named 'ipp' for identifying IPP printers and jobs. 94 The "Internet Printing Protocol/1.1: Implementer's Guide" document gives 95 insight and advice to implementers of IPP clients and IPP objects. It 96 is intended to help them understand IPP/1.1 and some of the 97 considerations that may assist them in the design of their client and/or 98 IPP object implementations. For example, a typical order of processing 99 requests is given, including error checking. Motivation for some of the 100 specification decisions is also included. 102 Expires: January 17, 2001 103 The "Mapping between LPD and IPP Protocols" document gives some advice 104 to implementers of gateways between IPP and LPD (Line Printer Daemon) 105 implementations. 107 Expires: January 17, 2001 108 Table of Contents 110 1 Introduction........................................................5 112 2 Terminology.........................................................5 114 3 Requirements and Use Cases..........................................6 116 4 IANA Considerations................................................10 118 5 Internationalization Considerations................................10 120 6 Security Considerations............................................10 122 7 Author's Addresses.................................................10 124 8 References.........................................................11 126 9 Appendix A: Full Copyright Statement...............................11 128 List of Tables 129 Table 1 - List of Printer Operations and corresponding Device Operations 130 ..................................................................9 132 Expires: January 17, 2001 134 1 Introduction 136 The Internet Printing Protocol (IPP) is an application level protocol 137 that can be used for distributed printing using Internet tools and 138 technologies. IPP version 1.1 ([ipp-mod, ipp-pro]) focuses on end user 139 functionality with a few administrative operations included. This 140 document defines the requirements and use cases for additional OPTIONAL 141 end user, operator, and administrator operations used to control Job 142 objects, Printer objects (see [ipp-mod]) and a new Device object. The 143 new Device object more closely models a single output device and has no 144 notion of a job, while the Printer object models a print service which 145 understands jobs and MAY represent one or more output devices. 147 2 Terminology 149 This section defines terminology used throughout this document and the 150 corresponding documents that define the Administrative operations on 151 Job, Printer, and Device objects. 153 This document uses terms such as "attributes", "keywords", and 154 "support". These terms have special meaning and are defined in the 155 model terminology [ipp-mod] section 12.2. 157 In addition, the following capitalized terms are defined: 159 IPP Printer object (or Printer for short) - a software abstraction 160 defined by [ipp-mod]. 162 Printer Operation - an operation whose target is an IPP Printer 163 object and whose effect is on the Printer object. 165 Output Device - the physical imaging mechanism that an IPP Printer 166 controls. Note: while this term is capitalized in this 167 specification (but not in [ipp-mod]), there is no formal object 168 called an Output Device. 170 Device Operation - an operation whose target is an IPP Printer object 171 and whose defined effect is on an Output Device. 173 Output Device Fan-Out - a configuration in which an IPP Printer 174 controls more that one output-device. 176 Printer fan-out - a configuration in which an IPP Printer object 177 controls more than one Subordinate IPP Printer object. 179 Printer fan-in - a configuration in which an IPP Printer object is 180 controlled by more than one IPP Printer object. 182 Subordinate Printer - an IPP Printer object that is controlled by 183 another IPP Printer object. Such a Subordinate Printer MAY have 184 one or more Subordinate Printers. 186 Leaf Printer - a Subordinate Printer that has no Subordinate 187 Printers. 189 Non-Leaf Printer - an IPP Printer object that has one or more 190 Subordinate Printers. 192 Chained Printer - a Non-Leaf Printer that has exactly one Subordinate 193 Printer. 195 Job Creation operations - IPP operations that create a Job object: 196 Print-Job, Print-URI, and Create-Job. 198 Expires: January 17, 2001 200 3 Requirements and Use Cases 202 The Administrative operations for Job and Printer objects will be 203 defined in one document [ipp-admin-ops]. The Administrative operations 204 for Device objects will be defined in a separate document (see [ipp- 205 device-ops]). The requirements are presented here together to show the 206 parallelism. 208 1.Have separate operations for affecting the IPP Printer versus 209 affecting the Output Device, so its clear what the intent of each is 210 and implementers can implement one or the other or both. 212 2.Support fan-out of Printer objects. 214 3.Support fan-out of Output Devices. 216 4.Support fan-in of Printer objects, as long as it doesn't make the 217 semantics more complicated when not supporting fan-in. 219 5.Support fan-in of output objects, as long as it doesn't make the 220 semantics more complicated when not supporting fan-in. 222 6.Instead of having operation attributes that alter the behavior of the 223 operation significantly, have separate operations, so that it is 224 simple and clear to a client which semantics the Printer is 225 supporting (by querying the "operations-supported" attribute) and it 226 is simple to describe the capabilities of a Printer implementation in 227 written documentation (just list the OPTIONAL operations supported). 229 7.Need a Printer Operation to prevent a Printer object from accepting 230 new IPP jobs, but currently accepted jobs continue unaffected to be 231 scheduled and processed. Need a companion one to restore the Printer 232 object to accept new IPP jobs. 234 Usage: Operator is preparing to take the IPP Printer out of service 235 or to change the configuration of the IPP Printer. 237 Suggested name and operations: Disable-Printer and Enable-Printer 239 8.Need a Device Operation to prevent an Output Device from accepting 240 any new jobs from any job submission protocol and a companion one to 241 restore the Output Device to accepting any jobs. 243 Usage: Operator is preparing to take the Output Device out of 244 service. 246 Suggested name and operations: Disable-Device and Enable Device 248 9.Need a Printer Operation to stop the processing after the current IPP 249 job completes and not start processing any additional IPP jobs 250 (either by scheduling the jobs or sending them to the Output Device), 251 but continue to accept new IPP jobs. Need a companion operation to 252 start processing/sending IPP jobs again. 254 Usage: Operator wants to gracefully stop the IPP Printer at the next 255 job boundary. The Pause-Printer-After-Current-Job operation is also 256 invoked implicitly by the Deactivate-Printer and the Shutdown-Printer 257 Operations. 259 Suggested name and operations: Pause-Printer-After-Current-Job, 260 (IPP/1.1) Resume-Printer 262 Expires: January 17, 2001 264 10. Need a Device Operation to stop the processing the current job 265 "immediately", no matter what protocol. Its like the Pause button on 266 the Output Device. This operation is for emergencies. The stop 267 point depends on implementation, but can be mid page, end of page, 268 end of sheet, or after a few sheets for Output Devices that can't 269 stop that quickly. The paper path isn't run out. Need a companion 270 operation to start processing the current any-protocol job without 271 losing any thing. 273 Usage: Operator sees something bad about to happen, such as the 274 paper is about to jam, or the toner is running out, or the device is 275 overheating or wants to add more paper. 277 Suggested name and operations: Pause-Device-Now, Resume-Device 279 11. Need a Printer Operation to stop the processing of IPP jobs after 280 all of the currently accepted jobs have been processed, but any newly 281 accepted jobs go into the 'processing-held' state. 283 Usage: This allows an operator to reconfigure the Output Device in 284 order to let jobs that are held waiting for resources, such as 285 special media, to get a chance. Then the operator uses another 286 operation after reconfiguring. He repeats the two operations to 287 restore the Output Device to its normal media. 289 Suggested name and operations: Hold-New-Jobs, Release-Held-New-Jobs 291 12. Need a Device Operation to stop the processing the current any- 292 protocol job at a convenient point, such as after the current copy 293 (or end of job if last or only copy). Need a companion operation to 294 start processing the current any-protocol job or next job without 295 losing any thing. 297 Usage: The operator wants to empty the output bin that is near full. 298 The paper path is run out. 300 Suggested name and operations: Pause-Device-After-Current-Copy, 301 Resume-Device 303 13. Need a Device Operation that always pauses on a device-defined 304 boundary, no matter how many copies, in order to not break up a job. 305 Need a companion operation to start processing the current any- 306 protocol job or next job without losing any thing. 308 Usage: The operator wants to empty the output bin that is near full, 309 but he doesn't want to break up a job in case it has multiple copies. 310 The paper path is run out. 312 Suggested name and operations: Pause-Device-After-Current-Job, 313 Resume-Device 315 14. Need a Printer Operation that combines Disable-Printer, Pause- 316 Printer-After-Current-Job, and rejects all other Job, Printer, and 317 Device Operations, except Job and Printer queries, System 318 Administrator Set-Printer-Attributes, and the companion operation to 319 resume activity. In other words, this operation makes the Printer a 320 read-only object in a graceful manner for end-users and the operator. 322 Usage: The administrator wants to reconfigure the Printer object 323 using the Set-Printer-Attributes operation without disturbing the 325 Expires: January 17, 2001 326 current in process work, but wants to make sure that the operator 327 isn't also trying to change the Printer object as part of running the 328 Printer. 330 Suggested name and operation: Deactivate-Printer, Activate-Printer 332 15. Need a Device Operation that combines Disable-Device, Pause-Device- 333 After-Current-Job, and rejects all other Device Operations, except 334 Job and Printer queries and the companion operation to resume 335 activity. In other words, this operation makes the Output Device a 336 read-only object in a graceful manner. 338 Usage: The field service person wants to open up the device without 339 disturbing the current in process work, perhaps to replace staples, 340 or replace the toner cartridge. 342 Suggested name and operation: Deactivate-Device, Activate-Device 344 16. Need a Printer Operation to recover from the IPP Printer software 345 that has gotten confused (run out of heap memory or gotten into a 346 state that it doesn't seem to be able to get out of). This is a 347 condition that shouldn't happen, but does in real life. Any volatile 348 information is saved if possible before the software is re- 349 initialized. No companion operation is needed to undo this. We 350 don't want to go back to the "confused" state :-). 352 Usage: The IPP Printer software has gotten confused or isn't 353 responding properly. 355 Suggested name and operation: Restart-Printer 357 17. Need a Device Operation to recover from the Output Device hardware 358 and software that has gotten confused (gotten into a state that it 359 doesn't seem to be able to get out of, run out of heap memory, etc.). 360 This is a condition that shouldn't happen, but does in real life. 361 This is the same and has the same options as the Printer MIB reset. 362 No companion operation is needed to undo this. We don't want to go 363 back to the "confused" state :-). 365 Usage: The Output Device has gotten confused or need resetting to 366 some initial conditions. 368 Suggested name and operation: Reset-Device 370 18. Need a Printer Operation to put the IPP Printer object out of 371 business with no way in the protocol to bring that instantiation back 372 to life (but see Startup-Printer which brings up exactly one new 373 instantiation to life with the same URL). Any volatile information 374 is saved if possible. 376 Usage: The Printer is being moved or the building's power is being 377 shut off. 379 Suggested name and operation: Shutdown-Printer 381 19. Need a Printer Operation to bring an IPP Printer to life when there 382 is an already running host. 384 Usage: After the host is started (by means outside the IPP 385 protocol), the operator is able to ask the host to bring up any 387 Expires: January 17, 2001 388 number of Printer objects (that the host has been configured in some 389 way) each with distinct URLs. 391 Suggested name and operation: Startup-Printer 393 20. Need a Device Operation to power off the Output Device after 394 writing out any software state. It is assumed that other operations 395 have more gracefully prepared the Output Device for this drastic and 396 immediate. There is no companion Device Operation to bring the power 397 back on. 399 Usage: The Output Device is going to be moved, the power in the 400 building is going to be shutoff, the repair man has arrived and needs 401 to take the Output Device apart. 403 Suggested name and operation: Power-Off-Device 405 21. Need a Device Operation to startup a powered-off device. 407 Usage: After a Power-Off-Device, if the device can be powered back 408 up (possibly by an intervening host that supports the Device 409 Operation). 411 Suggest name and operation: Power-On-Device 413 The tentative list of Printer and the corresponding Device Operations is 414 shown in Table 1: 416 Table 1 - List of Printer Operations and corresponding Device Operations 418 Printer Operation Corresponding Device Operation 419 equivalent 420 (see [ipp-device-ops]) 422 Disable-Printer Disable-Device 424 Enable-Printer Enable-Device 426 Pause-Printer (IPP/1.1 - Pause-Device-Now 427 [ipp-mod] - one 428 interpretation) 430 no Pause-Device-After-Current-Copy 432 Pause-Printer-After-Current- Pause-Device-After-Current-Job 433 Job 435 Resume-Printer (IPP/1.1 - Resume-Device 436 [ipp-mod]) 438 Hold-New-Jobs no 440 Release-Held-New-Jobs no 442 Deactivate-Printer Deactivate-Device 444 Activate-Printer Activate-Device 446 Purge-Jobs (IPP/1.1 - [ipp- Purge-Device 447 mod]) 449 Restart-Printer Reset-Device 451 Shutdown-Printer Power-Off-Device 453 Startup-Printer Power-On-Device 455 There are no conformance dependencies between Printer Operations and 456 Device Operations. Either MAY be supported without supporting the 457 corresponding operations. 459 Expires: January 17, 2001 460 4 IANA Considerations 462 The operations and attributes in this registration proposal will be 463 published by IANA according to the procedures in RFC 2566 [rfc2566] 464 section 6.4 for operations with the following URL: 466 ftp.isi.edu/iana/assignments/ipp/operations/ipp-admin-ops.txt 468 5 Internationalization Considerations 470 This document has the same localization considerations as the [ipp-mod]. 472 6 Security Considerations 474 The IPP Model and Semantics document [ipp-mod] discusses high level 475 security requirements (Client Authentication, Server Authentication and 476 Operation Privacy). Client Authentication is the mechanism by which the 477 client proves its identity to the server in a secure manner. Server 478 Authentication is the mechanism by which the server proves its identity 479 to the client in a secure manner. Operation Privacy is defined as a 480 mechanism for protecting operations from eavesdropping. 482 7 Author's Addresses 484 Carl Kugler 485 IBM 486 Boulder CO 488 Phone: (303) 924-5060 489 FAX: 490 e-mail: kugler@us.ibm.com 492 Tom Hastings 493 Xerox Corporation 494 737 Hawaii St. ESAE 231 495 El Segundo, CA 90245 497 Phone: 310-333-6413 498 Fax: 310-333-5514 499 e-mail: hastings@cp10.es.xerox.com 501 Harry Lewis 502 IBM 503 Boulder CO 505 Phone: (303) 924-5337 506 FAX: 507 e-mail: harryl@us.ibm.com 509 Expires: January 17, 2001 511 8 References 513 [ipp-device-ops] 514 Kugler, C., Hastings, T., Lewis, H., "Internet Printing Protocol 515 (IPP): Device Administrative Operations", , work in progress, TBD. 518 [ipp-iig] 519 Hastings, T., Manros, C., "Internet Printing Protocol/1.1: draft- 520 ietf-ipp-implementers-guide-v11-01.txt, work in progress, May 9, 521 2000. 523 [ipp-mod] 524 R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, 525 "Internet Printing Protocol/1.0: Model and Semantics", , May 22, 2000. 528 [ipp-ops-set2] 529 Kugler, C., , Hastings, T., Lewis, H, "Internet Printing Protocol 530 (IPP): Job and Printer Administrative Operations", , work in progress, July 19, 2000. 533 [ipp-pro] 534 Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing 535 Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11- 536 06.txt, May 30, 2000. 538 [RFC2566] 539 R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, 540 "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, 541 April 1999. 543 9 Appendix A: Full Copyright Statement 545 Copyright (C) The Internet Society (1998,1999). All Rights Reserved 547 This document and translations of it may be copied and furnished to 548 others, and derivative works that comment on or otherwise explain it or 549 assist in its implementation may be prepared, copied, published and 550 distributed, in whole or in part, without restriction of any kind, 551 provided that the above copyright notice and this paragraph are included 552 on all such copies and derivative works. However, this document itself 553 may not be modified in any way, such as by removing the copyright notice 554 or references to the Internet Society or other Internet organizations, 555 except as needed for the purpose of developing Internet standards in 556 which case the procedures for copyrights defined in the Internet 557 Standards process must be followed, or as required to translate it into 558 languages other than English. 560 The limited permissions granted above are perpetual and will not be 561 revoked by the Internet Society or its successors or assigns. 563 This document and the information contained herein is provided on an "AS 564 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 566 Expires: January 17, 2001 567 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 568 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 569 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 570 FITNESS FOR A PARTICULAR PURPOSE. 572 Expires: January 17, 2001