idnits 2.17.1 draft-ietf-ipp-job-prog-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 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 14 longer pages, the longest (page 13) being 72 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 13 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([RFC2568], [RFC2616], [RFC2569], [RFC2566], [RFC2567]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** 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 73: '... IPP/1.0. A few OPTIONAL operator ope...' RFC 2119 keyword, line 112: '...ecification" document defines OPTIONAL...' RFC 2119 keyword, line 255: '...ents- object MUST reject the job a...' RFC 2119 keyword, line 260: '...ents- object MUST reject the job a...' RFC 2119 keyword, line 306: '...1. NOTE: this attribute SHOULD NOT be...' (6 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 635 has weird spacing: '...for the purpo...' -- 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 (July 6, 2000) is 8666 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2026' is mentioned on line 23, but not defined == Missing Reference: 'RFC2616' is mentioned on line 91, but not defined ** Obsolete undefined reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) == Unused Reference: 'RFC2565' is defined on line 560, but no explicit reference was found in the text == Unused Reference: 'RFC2707' is defined on line 586, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2565 (Obsoleted by RFC 2910) ** Obsolete normative reference: RFC 2566 (Obsoleted by RFC 2911) ** Downref: Normative reference to an Experimental RFC: RFC 2567 ** Downref: Normative reference to an Experimental RFC: RFC 2568 ** Downref: Normative reference to an Experimental RFC: RFC 2569 ** Downref: Normative reference to an Informational RFC: RFC 2707 Summary: 15 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT 3 4 T. Hastings 5 Xerox Corporation 6 H. Lewis 7 IBM Printing Company 8 R. Bergman 9 Hitachi Koki Imaging Solutions 10 July 6, 2000 12 IPP: Job Progress Attributes 14 Copyright (C) The Internet Society (2000). All Rights Reserved. 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with all 19 provisions of Section 10 of [RFC2026]. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, and 21 its working groups. Note that other groups may also distribute working 22 documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference material 27 or to cite them other than as "work in progress". 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed as 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This document defines four new Job Description attributes for monitoring 38 job progress to be registered as extensions to IPP/1.0 [RFC2566] and 39 IPP/1.1 [ipp-mod]. These attributes are drawn from the PWG Job 40 Monitoring MIB [rfc2707]. The new Job Description attributes are: 42 "job-collation-type" (type2 enum) 43 "sheet-completed-copy-number" (integer(0:MAX)) 44 "sheet-completed-document-number" (integer(0:MAX)) 45 "impressions-completed-current-copy" (integer(0:MAX)) 47 This document also defines a new "sheet-collate" Job Template attribute 48 to control sheet collation and to help with the interpretation of the 49 job progress attributes. These new attributes may also be used by 50 themselves in combination with the IPP/1.1 "job-impressions-completed" 51 attribute as useful job progress monitoring attributes and/or may be 52 passed in an IPP Notification (see [ipp-ntfy]). 54 Expires January 6, 2001 55 The full set of IPP documents includes: 57 Design Goals for an Internet Printing Protocol [RFC2567] 58 Rationale for the Structure and Model and Protocol for the Internet 59 Printing Protocol [RFC2568] 60 Internet Printing Protocol/1.1: Model and Semantics [ipp-mod] 61 Internet Printing Protocol/1.1: Encoding and Transport [ipp-pro] 62 Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] 63 Mapping between LPD and IPP Protocols [RFC2569] 64 Internet Printing Protocol/1.0 & 1.1: Event Notification 65 Specification [ipp-ntfy] 67 The "Design Goals for an Internet Printing Protocol" document takes a 68 broad look at distributed printing functionality, and it enumerates 69 real-life scenarios that help to clarify the features that need to be 70 included in a printing protocol for the Internet. It identifies 71 requirements for three types of users: end users, operators, and 72 administrators. It calls out a subset of end user requirements that are 73 satisfied in IPP/1.0. A few OPTIONAL operator operations have been 74 added to IPP/1.1. 76 The "Rationale for the Structure and Model and Protocol for the Internet 77 Printing Protocol" document describes IPP from a high level view, 78 defines a roadmap for the various documents that form the suite of IPP 79 specification documents, and gives background and rationale for the IETF 80 working group's major decisions. 82 The "Internet Printing Protocol/1.1: Model and Semantics" document 83 describes a simplified model with abstract objects, their attributes, 84 and their operations that are independent of encoding and transport. It 85 introduces a Printer and a Job object. The Job object optionally 86 supports multiple documents per Job. It also addresses security, 87 internationalization, and directory issues. 89 The "Internet Printing Protocol/1.1: Encoding and Transport" document is 90 a formal mapping of the abstract operations and attributes defined in 91 the model document onto HTTP/1.1 [RFC2616]. It defines the encoding 92 rules for a new Internet MIME media type called "application/ipp". This 93 document also defines the rules for transporting over HTTP a message 94 body whose Content-Type is "application/ipp". This document defines a 95 new scheme named 'ipp' for identifying IPP printers and jobs. 97 The "Internet Printing Protocol/1.1: Implementer's Guide" document gives 98 insight and advice to implementers of IPP clients and IPP objects. It 99 is intended to help them understand IPP/1.1 and some of the 100 considerations that may assist them in the design of their client and/or 101 IPP object implementations. For example, a typical order of processing 102 requests is given, including error checking. Motivation for some of the 103 specification decisions is also included. 105 The "Mapping between LPD and IPP Protocols" document gives some advice 106 to implementers of gateways between IPP and LPD (Line Printer Daemon) 107 implementations. 109 Hastings, Lewis, Bergman 111 Expires January 6, 2001 112 The "Event Notification Specification" document defines OPTIONAL 113 operations that allow a client to subscribe to printing related events. 114 Subscriptions include "Per-Job subscriptions" and "Per-Printer 115 subscriptions". Subscriptions are modeled as Subscription objects. 116 Four other operations are defined for subscription objects: get 117 attributes, get subscriptions, renew a subscription, and cancel a 118 subscription. 120 Hastings, Lewis, Bergman 122 Expires January 6, 2001 123 TABLE OF CONTENTS 125 1 New Job Template attribute.......................................5 127 1.1 "sheet-collate" (boolean)...................................5 129 2 IPP Job Description attributes for monitoring Job Progress.......7 131 2.1 "job-collation-type" (type2 enum)..........................10 133 2.2 "sheet-completed-copy-number" (integer(0:MAX)).............11 135 2.3 "sheet-completed-document-number" (integer(0:MAX)).........11 137 2.4 "impressions-completed-current-copy" (integer(0:MAX))......12 139 3 Conformance Requirements........................................12 141 4 IANA Considerations.............................................12 143 5 Internationalization Considerations.............................12 145 6 Security Considerations.........................................12 147 7 References......................................................12 149 8 Author's Addresses..............................................13 151 9 Full Copyright Statement........................................14 153 Hastings, Lewis, Bergman 155 Expires January 6, 2001 156 1 New Job Template attribute 158 1.1 "sheet-collate" (boolean) 160 +===================+======================+======================+ 161 | Job Attribute |Printer: Default Value| Printer: Supported | 162 | | Attribute | Values Attribute | 163 +===================+======================+======================+ 164 | sheet-collate | sheet-collate-default| sheet-collate- | 165 | (type2 keyword) | (type2 keyword) | supported (1setOf | 166 | | | type2 keyword) | 167 +-------------------+----------------------+----------------------+ 169 This attribute specifies whether or not the media sheets of each copy of 170 each printed document in a job are to be in sequence, when multiple 171 copies of the document are specified by the 'copies' attribute. 173 Standard keyword values are: 175 'uncollated': each print-stream sheet is printed a number of times 176 in succession equal to the value of the 'copies' attribute, 177 followed by the next print-stream sheet. 179 'collated': each copy of each document is printed with the print- 180 stream sheets in sequence, followed by the next document copy. 182 For example, suppose a document produces two media sheets as output, and 183 "copies" is equal to '6', For the 'uncollated' case, six copies of the 184 first media sheet are printed followed by six copies of the second media 185 sheet. For the 'collated' case, one copy of each of the six sheets are 186 printed followed by another copy of each of the six media sheets. 188 Whether the effect of sheet collation is achieved by placing copies of a 189 document in multiple output bins or in the same output bin with 190 implementation defined document separation is implementation dependent. 191 Also whether it is achieved by making multiple passes over the job or by 192 using an output sorter is implementation dependent. 194 Note: IPP/1.0 [RFC2566] and IPP/1.1 [ipp-mod] is silent on whether or 195 not sheets within documents are collated. The "sheet-collate-supported" 196 Printer attribute permits a Printer object to indicate whether or not it 197 collates sheets with each document and whether it allows the client to 198 control sheet collation. An implementation is able to indicate that it 199 supports uncollated sheets, collated sheets, or both, using the 200 'uncollated', 'collated', or both 'uncollated' and 'collated' values, 201 respectively. 203 This attribute is affected by "multiple-document-handling." The 204 "multiple-document-handling" attribute describes the collation of 205 documents, and the "sheet-collate" attribute describes the semantics of 206 collating individual pages within a document. To better explain the 207 interaction between these two attributes the term "set" is introduced. 208 A "set" is a logical boundary between the delivered media sheets of a 209 printed job. For-example, in the case of a ten page single document 210 with collated pages and a request for 50 copies, each of the 50 printed 212 Hastings, Lewis, Bergman 214 Expires January 6, 2001 215 copies of the document constitutes a "set." In the above example if the 216 pages were uncollated, then 50 copies of each of the individual pages 217 within the document would represent each "set". 219 The following table describes the interaction of "sheet-collate" with 220 multiple document handling. 222 "sheet- "multiple- Semantics 223 collate" document- 224 handling" 226 'collated' 'single- Each copy of the concatenated documents, 227 document' with their pages in sequence, represents a 228 "set." 230 'collated' 'single- Each copy of the concatenated documents, 231 document-new- with their pages in sequence, represents a 232 sheet' "set." 234 'collated' 'separate- Each copy of each separate document, with 235 documents- its pages in sequence, represents a "set." 236 collated- 237 copies' 239 'collated' 'separate- Each copy of each separate document, with 240 documents- its pages in sequence, represents a "set." 241 uncollated- 242 copies 244 'uncollated' 'single- Each media sheet of the document is 245 document' printed a number of times equal to the 246 "copies" attribute; which constitutes a 247 "set." 249 'uncollated' 'single- Each media sheet of the concatenated 250 document-new- documents is printed a number of times 251 sheet' equal to the "copies" attribute; which 252 constitutes a "set." 254 'uncollated' 'separate- This is a degenerate case, and the printer 255 documents- object MUST reject the job and return the 256 collated- status, "client-error-conflicting- 257 copies' attributes." 259 'uncollated' 'separate- This is a degenerate case, and the printer 260 documents- object MUST reject the job and return the 261 uncollated- status "client-error-conflicting- 262 copies attributes." 264 From the above table it is obvious that the implicit value of the 265 "sheet-collate" attribute in a printer that does not support the 266 "sheet-collate" attribute, is 'collated.' The semantics of 267 "multiple-document-handling" are otherwise nonsensical in the case 268 of separate documents. 270 Hastings, Lewis, Bergman 272 Expires January 6, 2001 273 2 IPP Job Description attributes for monitoring Job Progress 275 The following IPP Job Description attributes are proposed to be added to 276 IPP through the type2 registration procedures. They are useful for 277 monitoring the progress of a job. They are also used at attributes in 278 the notification content in a notification report [ipp-ntfy]. 280 There are a number of Job Description attributes for monitoring the 281 progress of a job. These objects and attributes count the number of K 282 octets, impressions, sheets, and pages requested or completed. For 283 impressions and sheets, "completed" means stacked, unless the 284 implementation is unable to detect when each sheet is stacked, in which 285 case stacked is approximated when processing of each sheet completes. 286 There are objects and attributes for the overall job and for the current 287 copy of the document currently being stacked. For the latter, the rate 288 at which the various objects and attributes count depends on the sheet 289 and document collation of the job. 291 Consider the following four Job Description attributes that are used to 292 monitor the progress of a job's impressions: 294 1."job-impressions-completed" - counts the total number of 295 impressions stacked for the job (see [ipp-mod] section 4.3.18.2) 297 2."impressions-completed-current-copy" - counts the number of 298 impressions stacked for the current document copy 300 3."sheet-completed-copy-number" - identifies the number of the 301 copy for the current document being stacked where the first copy 302 is 1. 304 4."sheet-completed-document-number" - identifies the current 305 document within the job that is being stacked where the first 306 document in a job is 1. NOTE: this attribute SHOULD NOT be 307 implemented for implementations that only support one document 308 per job. 310 For each of the three types of job collation, a job with three copies of 311 two documents (1, 2), where each document consists of 3 impressions, the 312 four variables have the following values as each sheet is stacked for 313 one-sided printing: 315 Hastings, Lewis, Bergman 317 Expires January 6, 2001 318 "job-collation-type" = 'uncollated-sheets(3)' 320 "job- "impressions- "sheet- "sheet- 321 impressions- completed- completed- completed- 322 completed" current-copy" copy-number" document- 323 number" 325 0 0 0 0 326 1 1 1 1 327 2 1 2 1 328 3 1 3 1 329 4 2 1 1 330 5 2 2 1 331 6 2 3 1 332 7 3 1 1 333 8 3 2 1 334 9 3 3 1 335 10 1 1 2 336 11 1 2 2 337 12 1 3 2 338 13 2 1 2 339 14 2 2 2 340 15 2 3 2 341 16 3 1 2 342 17 3 2 2 343 18 3 3 2 345 Hastings, Lewis, Bergman 347 Expires January 6, 2001 348 "job-collation-type" = 'collated-documents(4)' 350 "job- "impressions- "sheet- "sheet- 351 impressions- completed- completed- completed- 352 completed" current-copy" copy-number" document- 353 number" 355 0 0 0 0 356 1 1 1 1 357 2 2 1 1 358 3 3 1 1 359 4 1 1 2 360 5 2 1 2 361 6 3 1 2 362 7 1 2 1 363 8 2 2 1 364 9 3 2 1 365 10 1 2 2 366 11 2 2 2 367 12 3 2 2 368 13 1 3 1 369 14 2 3 1 370 15 3 3 1 371 16 1 3 2 372 17 2 3 2 373 18 3 3 2 375 Hastings, Lewis, Bergman 377 Expires January 6, 2001 378 "job-collation-type" = 'uncollated-documents(5)' 380 "job- "impressions- "sheet- "sheet- 381 impressions- completed- completed- completed- 382 completed" current-copy" copy-number" document- 383 number" 385 0 0 0 0 386 1 1 1 1 387 2 2 1 1 388 3 3 1 1 389 4 1 2 1 390 5 2 2 1 391 6 3 2 1 392 7 1 3 1 393 8 2 3 1 394 9 3 3 1 395 10 1 1 2 396 11 2 1 2 397 12 3 1 2 398 13 1 2 2 399 14 2 2 2 400 15 3 2 2 401 16 1 3 2 402 17 2 3 2 403 18 3 3 2 405 2.1 "job-collation-type" (type2 enum) 407 Job Collation includes sheet collation and document collation. Sheet 408 collation is defined to be the ordering of sheets within a document 409 copy. Document collation is defined to be ordering of document copies 410 within a multi-document job. The value of the "job-collation-type" is 411 affected by the value of the "sheet-collate" Job Template attribute (see 412 section 1.1), if supplied and supported. 414 The Standard enum values are: 416 '1' 'other': not one of the defined values 418 '2' 'unknown': the collation type is unknown 420 '3' 'uncollated-sheets': No collation of the sheets within each 421 document copy, i.e., each sheet of a document that is to 422 produce multiple copies is replicated before the next 423 sheet in the document is processed and stacked. If the 424 device has an output bin collator, the 'uncollated- 425 sheets(3)' value may actually produce collated sheets as 426 far as the user is concerned (in the output bins). 427 However, when the job collation is the 'uncollated- 428 sheets(3)' value, job progress is indistinguishable to a 430 Hastings, Lewis, Bergman 432 Expires January 6, 2001 433 monitoring application between a device that has an 434 output bin collator and one that does not. 436 '4' 'collated-documents': Collation of the sheets within each 437 document copy is performed within the printing device by 438 making multiple passes over either the source or an 439 intermediate representation of the document. In 440 addition, when there are multiple documents per job, the 441 i'th copy of each document is stacked before the j'th 442 copy of each document, i.e., the documents are collated 443 within each job copy. For example, if a job is submitted 444 with documents, A and B, the job is made available to the 445 end user as: A, B, A, B, .. The 'collated-documents(4)' 446 value corresponds to the IPP [ipp-mod] 'separate- 447 documents-collated-copies' keyword value of the 448 "multiple-document-handling" attribute. 450 If the job's "copies" attribute is '1' (or not 451 supplied), then the "job-collation-type" attribute is 452 defined to be '4'. 454 '5' 'uncollated-documents': Collation of the sheets within each 455 document copy is performed within the printing device by 456 making multiple passes over either the source or an 457 intermediate representation of the document. In 458 addition, when there are multiple documents per job, all 459 copies of the first document in the job are stacked 460 before the any copied of the next document in the job, 461 i.e., the documents are uncollated within the job. For 462 example, if a job is submitted with documents, A and B, 463 the job is mad available to the end user as: A, A, ., B, 464 B, .. The 'uncollated-documents(5)' value corresponds to 465 the IPP [ipp-mod] 'separate-documents-uncollated-copies' 466 keyword value of the "multiple-document-handling" 467 attribute. 469 2.2 "sheet-completed-copy-number" (integer(0:MAX)) 471 The number of the copy being stacked for the current document. This 472 number starts at 0, is set to 1 when the first sheet of the first copy 473 for each document is being stacked and is equal to n where n is the nth 474 sheet stacked in the current document copy. If the value is unknown, 475 the Printer MUST return the 'unknown' out-of-band value (see [ipp-mod] 476 section 4.1), rather than the -2 value used in some MIBs [rfc2707]. 478 2.3 "sheet-completed-document-number" (integer(0:MAX)) 480 The ordinal number of the document in the job that is currently being 481 stacked. This number starts at 0, increments to 1 when the first sheet 482 of the first document in the job is being stacked, and is equal to n 483 where n is the nth document in the job, starting with 1. If the value is 484 unknown, the Printer MUST return the 'unknown' out-of-band value (see 486 Hastings, Lewis, Bergman 488 Expires January 6, 2001 489 [ipp-mod] section 4.1), rather than the -2 value used in some MIBs 490 [rfc2707]. 492 Implementations that only support one document jobs SHOULD NOT implement 493 this attribute. 495 2.4 "impressions-completed-current-copy" (integer(0:MAX)) 497 The number of impressions completed by the device for the current copy 498 of the current document so far. For printing, the impressions completed 499 includes interpreting, marking, and stacking the output. For other 500 types of job services, the number of impressions completed includes the 501 number of impressions processed. If the value is unknown, the Printer 502 MUST return the 'unknown' out-of-band value (see [ipp-mod] section 4.1), 503 rather than the -2 value used in some MIBs [rfc2707]. 505 This value SHALL be reset to 0 for each document in the job and for each 506 document copy. 508 3 Conformance Requirements 510 This section summarizes the Conformance Requirements detailed in the 511 definitions in this document. In general each of the attributes defined 512 in this document are OPTIONAL for a Printer to support, so that Printer 513 implementers MAY implement any combination of attributes. 515 4 IANA Considerations 517 IANA will be called on to register the attributes defined in this 518 document, using the procedures outlined in [ipp-mod]. 520 5 Internationalization Considerations 522 The IPP extensions defined in this document require the same 523 internationalization considerations as any of the Job Template and Job 524 Descriptions attributes defined in IPP/1.1 [ipp-mod]. 526 6 Security Considerations 528 The IPP extensions defined in this document require the same security 529 considerations as any of the Job Template attributes and Job 530 Descriptions attributes defined in IPP/1.1 [ipp-mod]. 532 7 References 534 [ipp-iig] 536 Hastings, T., Manros, C., "Internet Printing Protocol/1.1: draft- 537 ietf-ipp-implementers-guide-v11-01.txt, work in progress, May 2000. 539 [ipp-mod] 541 deBry, R., , Hastings, T., Herriot, R., Isaacson, S., Powell, P., 542 "Internet Printing Protocol/1.1: Model and Semantics", , work in progress, May, 2000. 545 Hastings, Lewis, Bergman 547 Expires January 6, 2001 548 [ipp-ntfy] 550 Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M., 551 Bergman, R., " IPP Event Notification Specification", , work in progress, June, 2000. 554 [ipp-pro] 556 Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing 557 Protocol/1.1: Encoding and Transport", draft-ietf-ipp-protocol-v11- 558 06.txt, May, 2000. 560 [RFC2565] 562 Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing 563 Protocol/1.0: Encoding and Transport", RFC 2565, April 1999. 565 [RFC2566] 567 deBry, R., , Hastings, T., Herriot, R., Isaacson, S., Powell, P., 568 "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, 569 April 1999. 571 [RFC2567] 573 Wright, D., "Design Goals for an Internet Printing Protocol", RFC 574 2567, April 1999. 576 [RFC2568] 578 Zilles, S., "Rationale for the Structure and Model and Protocol for 579 the Internet Printing Protocol", RFC 2568, April 1999. 581 [RFC2569] 583 Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between 584 LPD and IPP Protocols", RFC 2569, April 1999. 586 [RFC2707] 588 Bergman, R., Hastings, T., Isaacson, S., Lewis, H. "PWG Job 589 Monitoring MIB - V1", RFC 2707, November, 1999. 591 8 Author's Addresses 593 Tom Hastings 594 Xerox Corporation 595 737 Hawaii St. ESAE 231 596 El Segundo, CA 90245 597 Phone: 310-333-6413 598 Fax: 310-333-5514 599 e-mail: hastings@cp10.es.xerox.com 601 Harry Lewis 603 Hastings, Lewis, Bergman 605 Expires January 6, 2001 606 IBM 607 P.O. Box 1900 608 Boulder, CO 80301-9191 610 Phone: (303) 924-5337 611 FAX: 612 e-mail: harryl@us.ibm.com 614 Ron Bergman (Editor) 615 Hitachi Koki Imaging Solutions 616 1757 Tapo Canyon Road 617 Simi Valley, CA 93063-3394 619 Phone: 805-578-4421 620 Fax: 805-578-4001 621 Email: rbergma@hitachi-hkis.com 623 9 Full Copyright Statement 625 Copyright (C) The Internet Society (2000). All Rights Reserved. 627 This document and translations of it may be copied and furnished to 628 others, and derivative works that comment on or otherwise explain it or 629 assist in its implementation may be prepared, copied, published and 630 distributed, in whole or in part, without restriction of any kind, 631 provided that the above copyright notice and this paragraph are included 632 on all such copies and derivative works. However, this document itself 633 may not be modified in any way, such as by removing the copyright notice 634 or references to the Internet Society or other Internet organizations, 635 except as needed for the purpose of developing Internet standards in 636 which case the procedures for copyrights defined in the Internet 637 Standards process must be followed, or as required to translate it into 638 languages other than English. 640 The limited permissions granted above are perpetual and will not be 641 revoked by the Internet Society or its successors or assigns. 643 This document and the information contained herein is provided on an "AS 644 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 645 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 646 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 647 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 648 FITNESS FOR A PARTICULAR PURPOSE. 650 Hastings, Lewis, Bergman 652 Expires January 6, 2001