7 Network Working Group T. Hastings
8 Request for Comments: 3381 Xerox Corporation
10 Category: Standards Track IBM Printing Company
12 Hitachi Koki Imaging Solutions
16 Internet Printing Protocol (IPP):
17 Job Progress Attributes
21 This document specifies an Internet standards track protocol for the
22 Internet community, and requests discussion and suggestions for
23 improvements. Please refer to the current edition of the "Internet
24 Official Protocol Standards" (STD 1) for the standardization state
25 and status of this protocol. Distribution of this memo is unlimited.
29 Copyright (C) The Internet Society (2002). All Rights Reserved.
33 This document defines four new Job Description attributes for
34 monitoring job progress to be registered as OPTIONAL extensions to
35 the Internet Printing Protocol (IPP/1.0 and IPP/1.1). These
36 attributes are drawn from the PWG Job Monitoring MIB. This document
37 also defines a new "sheet-collate" Job Template attribute to control
38 sheet collation and to help with the interpretation of the job
58 Hastings, et. al. Standards Track [Page 1]
60 RFC 3381 IPP: Job Progress Attributes September 2002
65 1 Introduction.....................................................2
66 2 Terminology......................................................2
67 2.1 Conformance Terminology........................................4
68 2.2 Other terminology..............................................4
69 3 Job Template attributes..........................................4
70 3.1 sheet-collate (type2 keyword)..................................4
71 4 IPP Job Description attributes for monitoring Job Progress.......6
72 4.1 job-collation-type (type2 enum)................................9
73 4.2 sheet-completed-copy-number (integer(0:MAX))..................11
74 4.3 sheet-completed-document-number (integer(0:MAX))..............11
75 4.4 impressions-completed-current-copy (integer(0:MAX))...........11
76 5 Conformance Requirements........................................11
77 6 IANA Considerations.............................................12
78 6.1 Attributes....................................................
79 6.2 Keyword Attribute Values......................................
80 6.3 Enum Attribute Values.........................................
81 7 Internationalization Considerations.............................12
82 8 Security Considerations.........................................12
83 9 References......................................................12
84 10 Description of the Base IPP Documents..........................13
85 11 Authors' Addresses.............................................15
86 12 Full Copyright Statement.......................................16
90 This document defines four new Job Description attributes for
91 monitoring job progress to be registered as OPTIONAL extensions to
92 IPP/1.0 [RFC2566] and IPP/1.1 [RFC2911]. These attributes are drawn
93 from the PWG Job Monitoring MIB [RFC2707]. See section 10 for a
94 description of the base IPP documents. The new Job Description
97 "job-collation-type" (type2 enum)
98 "sheet-completed-copy-number" (integer(0:MAX))
99 "sheet-completed-document-number" (integer(0:MAX))
100 "impressions-completed-current-copy" (integer(0:MAX))
102 This document also defines a new "sheet-collate" Job Template
103 attribute to control sheet collation and to help with the
104 interpretation of the job progress attributes. These new attributes
105 may also be used by themselves in combination with the IPP/1.1 "job-
106 impressions-completed" attribute, as useful job progress monitoring
107 attributes and/or may be passed in an IPP Notification (see [ipp-
114 Hastings, et. al. Standards Track [Page 2]
116 RFC 3381 IPP: Job Progress Attributes September 2002
121 This section defines terminology used throughout this document.
123 2.1 Conformance Terminology
125 Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD
126 NOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating to
127 conformance, as defined in RFC 2119 [RFC2119] and [RFC2911] section
128 12.1. If an implementation supports the extension defined in this
129 document, then these terms apply; otherwise, they do not. These
130 terms define conformance to this document only; they do not affect
131 conformance to other documents, unless explicitly stated otherwise.
133 2.2 Other terminology
135 This document uses terms such as Job object (or Job), IPP Printer
136 object (or Printer), "operation", "attribute", "keyword", "support",
137 and "impression". These terms have special meaning and are defined
138 in the model terminology [RFC2911], section 12.2.
140 3 Job Template attributes
142 3.1 sheet-collate (type2 keyword)
144 +===================+======================+=====================+
145 | Job Attribute |Printer: Default Value| Printer: Supported |
146 | | Attribute | Values Attribute |
147 +===================+======================+=====================+
148 | sheet-collate | sheet-collate-default| sheet-collate- |
149 | (type2 keyword) | (type2 keyword) | supported (1setOf |
150 | | | type2 keyword) |
151 +-------------------+----------------------+---------------------+
153 This attribute specifies whether or not the media sheets of each copy
154 of each printed document in a job are to be in sequence, when
155 multiple copies of the document are specified by the 'copies'
158 Standard keyword values are:
160 'uncollated': each print-stream sheet is printed a number of
161 times in succession equal to the value of the 'copies'
162 attribute, followed by the next print-stream sheet.
164 'collated': each copy of each document is printed with the
165 print-stream sheets in sequence, followed by the next document
170 Hastings, et. al. Standards Track [Page 3]
172 RFC 3381 IPP: Job Progress Attributes September 2002
175 For example, suppose a document produces two media sheets as output,
176 and "copies" is equal to '6'. For the 'uncollated' case, six copies
177 of the first media sheet are printed, followed by six copies of the
178 second media sheet. For the 'collated' case, one copy of each of the
179 six sheets is printed, followed by another copy of each of the six
182 Whether the effect of sheet collation is achieved by placing copies
183 of a document in multiple output bins, or in the same output bin with
184 implementation defined document separation, is implementation
185 dependent. Also whether it is achieved by making multiple passes
186 over the job or by using an output sorter, is implementation
189 Note: IPP/1.0 [RFC2566] and IPP/1.1 [RFC2911] are silent on whether
190 or not sheets within documents are collated. The "sheet-collate-
191 supported" Printer attribute permits a Printer object to indicate
192 whether or not it collates sheets with each document and whether it
193 allows the client to control sheet collation. An implementation is
194 able to indicate that it supports uncollated sheets, collated sheets,
195 or both, using the 'uncollated', 'collated', or both 'uncollated' and
196 'collated' values, respectively.
198 This attribute is affected by "multiple-document-handling". The
199 "multiple-document-handling" attribute describes the collation of
200 documents, and the "sheet-collate" attribute describes the semantics
201 of collating individual pages within a document. To better explain
202 the interaction between these two attributes, the term "set" is
203 introduced. A "set" is a logical boundary between the delivered
204 media sheets of a printed job. For example, in the case of a ten
205 page single document with collated pages and a request for 50 copies,
206 each of the 50 printed copies of the document constitutes a "set".
207 In the above example if the pages were uncollated, then 50 copies of
208 each of the individual pages within the document would represent each
226 Hastings, et. al. Standards Track [Page 4]
228 RFC 3381 IPP: Job Progress Attributes September 2002
231 The following table describes the interaction of "sheet-collate" with
232 multiple document handling.
234 "sheet- "multiple- Semantics
238 'collated' 'single- Each copy of the concatenated
239 document' documents, with their pages in
240 sequence, represents a "set".
242 'collated' 'single- Each copy of the concatenated
243 document-new- documents, with their pages in
244 sheet' sequence, represents a "set".
246 'collated' 'separate- Each copy of each separate
247 documents- document, with its pages in
248 collated- sequence, represents a "set".
251 'collated' 'separate- Each copy of each separate
252 documents- document, with its pages in
253 uncollated- sequence, represents a "set".
256 'uncollated' 'single- Each media sheet of the document
257 document' is printed a number of times equal
258 to the "copies" attribute; which
261 'uncollated' 'single- Each media sheet of the
262 document-new- concatenated documents is printed
263 sheet' a number of times equal to the
264 "copies" attribute; which
267 'uncollated' 'separate- This is a degenerate case, and the
268 documents- printer object MUST reject the job
269 collated- and return the status, "client-
270 copies' error-conflicting-attributes".
272 'uncollated' 'separate- This is a degenerate case, and the
273 documents- printer object MUST reject the job
274 uncollated- and return the status "client-
275 copies error-conflicting-attributes".
282 Hastings, et. al. Standards Track [Page 5]
284 RFC 3381 IPP: Job Progress Attributes September 2002
287 From the above table it is obvious that the implicit value of the
288 "sheet-collate" attribute in a printer that does not support the
289 "sheet-collate" attribute, is 'collated.' The semantics of
290 "multiple-document-handling" are otherwise nonsensical in the case
291 of separate documents.
293 4 IPP Job Description attributes for monitoring Job Progress
295 The following IPP Job Description attributes are proposed to be added
296 to IPP through the type2 registration procedures. They are useful
297 for monitoring the progress of a job. They are also used as
298 attributes in the notification content in a notification report
301 There are a number of Job Description attributes for monitoring the
302 progress of a job. These objects and attributes count the number of
303 K octets, impressions, sheets, and pages requested or completed. For
304 impressions and sheets, "completed" means stacked, unless the
305 implementation is unable to detect when each sheet is stacked, in
306 which case, stacked is approximated when the processing of each sheet
307 is completed. There are objects and attributes for the overall job
308 and for the current copy of the document currently being stacked.
309 For the latter, the rate at which the various objects and attributes
310 count, depends on the sheet and document collation of the job.
312 Consider the following four Job Description attributes that are used
313 to monitor the progress of a job's impressions:
315 1. "job-impressions-completed" - counts the total number of
316 impressions stacked for the job (see [RFC2911] section
319 2. "impressions-completed-current-copy" - counts the number of
320 impressions stacked for the current document copy.
322 3. "sheet-completed-copy-number" - identifies the number of the
323 copy for the current document being stacked, where the first
326 4. "sheet-completed-document-number" - identifies the current
327 document within the job that is being stacked, where the first
328 document in a job is 1. NOTE: this attribute SHOULD NOT be
329 implemented for implementations that only support one document
338 Hastings, et. al. Standards Track [Page 6]
340 RFC 3381 IPP: Job Progress Attributes September 2002
343 For each of the three types of job collation, a job with three copies
344 of two documents (1, 2), where each document consists of 3
345 impressions, the four variables have the following values, as each
346 sheet is stacked for one-sided printing:
348 "job-collation-type" = 'uncollated-sheets(3)'
350 "job- "impressions- "sheet- "sheet-
351 impressions- completed- completed- completed-
352 completed" current-copy" copy-number" document-
394 Hastings, et. al. Standards Track [Page 7]
396 RFC 3381 IPP: Job Progress Attributes September 2002
399 "job-collation-type" = 'collated-documents(4)'
401 "job- "impressions- "sheet- "sheet-
402 impressions- completed- completed- completed-
403 completed" current-copy" copy- document-
450 Hastings, et. al. Standards Track [Page 8]
452 RFC 3381 IPP: Job Progress Attributes September 2002
455 "job-collation-type" = 'uncollated-documents(5)'
457 "job- "impressions- "sheet- "sheet-
458 impressions- completed- completed- completed-
459 completed" current-copy" copy-t document-
482 4.1 job-collation-type (type2 enum)
484 Job Collation includes sheet collation and document collation. Sheet
485 collation is defined to be the ordering of sheets within a document
486 copy. Document collation is defined to be the ordering of document
487 copies within a multi-document job. The value of the "job-
488 collation-type" is affected by the value of the "sheet-collate" Job
489 Template attribute (see section 3.1), if supplied and supported.
491 The Standard enum values are:
493 '1' 'other': not one of the defined values
495 '2' 'unknown': the collation type is unknown
497 '3' 'uncollated-sheets': No collation of the sheets within each
498 document copy, i.e., each sheet of a document that
499 is to produce multiple copies, is replicated before
500 the next sheet in the document is processed and
501 stacked. If the device has an output bin collator,
502 the 'uncollated-sheets(3)' value may actually
506 Hastings, et. al. Standards Track [Page 9]
508 RFC 3381 IPP: Job Progress Attributes September 2002
511 produce collated sheets as far as the user is
512 concerned (in the output bins). However, when the
513 job collation is the 'uncollated-sheets(3)' value,
514 job progress is indistinguishable from a monitoring
515 application between a device that has an output bin
516 collator and one that does not.
518 '4' 'collated-documents': Collation of the sheets within each
519 document copy is performed within the printing
520 device by making multiple passes over, either the
521 source or an intermediate representation of the
522 document. In addition, when there are multiple
523 documents per job, the i'th copy of each document is
524 stacked before the j'th copy of each document, i.e.,
525 the documents are collated within each job copy.
526 For example, if a job is submitted with documents, A
527 and B, the job is made available to the end user as:
528 A, B, A, B, .... The 'collated-documents(4)' value
529 corresponds to the IPP [RFC2911] 'separate-
530 documents-collated-copies' keyword value of the
531 "multiple-document-handling" attribute.
533 If the job's "copies" attribute is '1' (or not
534 supplied), then the "job-collation-type" attribute
535 is defined to be '4'.
537 '5' 'uncollated-documents': Collation of the sheets within each
538 document copy is performed within the printing
539 device by making multiple passes over either the
540 source or an intermediate representation of the
541 document. In addition, when there are multiple
542 documents per job, all copies of the first document
543 in the job are stacked before any copied of the next
544 document in the job, i.e., the documents are
545 uncollated within the job. For example, if a job is
546 submitted with documents, A and B, the job is made
547 available to the end user as: A, A, ..., B, B, ....
548 The 'uncollated-documents(5)' value corresponds to
549 the IPP [RFC2911] 'separate-documents-uncollated-
550 copies' keyword value of the "multiple-document-
562 Hastings, et. al. Standards Track [Page 10]
564 RFC 3381 IPP: Job Progress Attributes September 2002
567 4.2 sheet-completed-copy-number (integer(0:MAX))
569 The number of the copy being stacked for the current document. This
570 number starts at 0, is set to 1 when the first sheet of the first
571 copy for each document is being stacked and is equal to n where n is
572 the nth sheet stacked in the current document copy. If the value is
573 unknown, the Printer MUST return the 'unknown' out-of-band value (see
574 [RFC2911] section 4.1), rather than the -2 value used in some MIBs
577 4.3 sheet-completed-document-number (integer(0:MAX))
579 The ordinal number of the document in the job that is currently being
580 stacked. This number starts at 0, increments to 1 when the first
581 sheet of the first document in the job is being stacked, and is equal
582 to n where n is the nth document in the job, starting with 1. If the
583 value is unknown, the Printer MUST return the 'unknown' out-of-band
584 value (see [RFC2911] section 4.1), rather than the -2 value used in
587 Implementations that only support one document job SHOULD NOT
588 implement this attribute.
590 4.4 impressions-completed-current-copy (integer(0:MAX))
592 The number of impressions completed by the device for the current
593 copy of the current document so far. For printing, the impressions
594 completed includes interpreting, marking, and stacking the output.
595 For other types of job services, the number of impressions completed
596 includes the number of impressions processed. If the value is
597 unknown, the Printer MUST return the 'unknown' out-of-band value (see
598 [RFC2911] section 4.1), rather than the -2 value used in some MIBs
601 This value MUST be reset to 0 for each document in the job and for
604 5 Conformance Requirements
606 This section summarizes the Conformance Requirements detailed in the
607 definitions in this document. In general each of the attributes
608 defined in this document are OPTIONAL for a client and/or a Printer
609 to support, so that client and Printer implementers MAY implement any
610 combination of these attributes.
618 Hastings, et. al. Standards Track [Page 11]
620 RFC 3381 IPP: Job Progress Attributes September 2002
623 6 IANA Considerations
625 This section contains registration information for IANA to add to the
626 IPP Registry according to the procedures defined in RFC 2911
627 [RFC2911], section 6. The resulting registrations will be published
628 in the http://www.iana.org/assignments/ipp-registrations registry.
632 Job Template attributes: Ref. Section:
633 sheet-collate (type2 keyword) RFC 3381 3.1
634 sheet-default (type2 keyword) RFC 3381 3.1
635 sheet-supported (1setOf type2 keyword) RFC 3381 3.1
637 Job Description attributes: Ref. Section:
638 job-collation-type (type2 enum) RFC 3381 4.1
639 sheet-completed-copy-number (integer(0:MAX)) RFC 3381 4.2
640 sheet-completed-document-number (integer(0:MAX))RFC 3381 4.3
641 impressions-completed-current-copy (integer(0:MAX))
643 6.2 Keyword Attribute Values
645 The following table provides registration information for all of the
646 attributes defined in this document that have keyword values. These
647 keywords are to be registered according to the procedures defined in
648 RFC 2911 [RFC2911] section 6.1.
650 sheet-collate (type2 keyword) RFC 3381 3.1
651 'uncollated' RFC 3381 3.1
652 'collated' RFC 3381 3.1
653 sheet-collate-default (type2 keyword) RFC 3381 3.1
654 See "sheet-collate" attribute
655 sheet-collate-supported (1setOf type2 keyword) RFC 3381 3.1
656 See "sheet-collate" attribute
658 6.3 Enum Attribute Values
660 The following table provides registration information for all of the
661 attributes defined in this document that have enum values. These
662 enums are to be registered according to the procedures defined in RFC
663 2911 [RFC2911] section 6.1.
665 job-collation-type (type2 enum) RFC 3381 4.1
666 '1' 'other' RFC 3381 4.1
667 '2' 'unknown' RFC 3381 4.1
668 '3' 'uncollated-sheets' RFC 3381 4.1
669 '4' 'collated-documents' RFC 3381 4.1
670 '5' 'uncollated-documents' RFC 3381 4.1
674 Hastings, et. al. Standards Track [Page 12]
676 RFC 3381 IPP: Job Progress Attributes September 2002
679 7 Internationalization Considerations
681 The IPP extensions defined in this document require the same
682 internationalization considerations as any of the Job Template and
683 Job Description attributes defined in IPP/1.1 [RFC2911].
685 8 Security Considerations
687 The IPP extensions defined in this document require the same security
688 considerations as any of the Job Template attributes and Job
689 Description attributes defined in IPP/1.1 [RFC2911].
693 9.1 Normative References
695 [RFC2910] Herriot, R., Butler, S., Moore, P. and R. Turner,
696 "Internet Printing Protocol/1.1: Encoding and Transport",
697 RFC 2910, September 2000.
699 [RFC2911] Hastings, T., Herriot, R., deBry, R., Isaacson, S. and P.
700 Powell, "Internet Printing Protocol/1.1: Model and
701 Semantics", RFC 2911, September 2000.
703 9.2 Informative References
705 [RFC2565] Herriot, R., Butler, S., Moore, P. and R. Turner,
706 "Internet Printing Protocol/1.0: Encoding and Transport",
707 RFC 2565, April 1999.
709 [RFC2566] deBry, R., Hastings, T., Herriot, R., Isaacson, S. and P.
710 Powell, "Internet Printing Protocol/1.0: Model and
711 Semantics", RFC 2566, April 1999.
713 [RFC2567] Wright, F.D., "Design Goals for an Internet Printing
714 Protocol", RFC 2567, April 1999.
716 [RFC2568] Zilles, S., "Rationale for the Structure and Model and
717 Protocol for the Internet Printing Protocol", RFC 2568,
720 [RFC2569] Herriot, R., Hastings, T., Jacobs, N. and J. Martin,
721 "Mapping between LPD and IPP Protocols", RFC 2569, April
724 [RFC2707] Bergman, R., Hastings, T., Isaacson, S. and H. Lewis, "PWG
725 Job Monitoring MIB - V1", RFC 2707, November 1999.
730 Hastings, et. al. Standards Track [Page 13]
732 RFC 3381 IPP: Job Progress Attributes September 2002
735 [RFC3196] Hastings, T., Manros, C., Zehler, P., Kugler, C. and H.
736 Holst, "Internet Printing Protocol/1.1: Implementor's
737 Guide", RFC 3196, November 2001.
739 [ipp-ntfy] Herriot, R., Hastings, T., et. al., "Internet Printing
740 Protocol (IPP): Event Notification and Subscriptions",
743 10 Description of the Base IPP Documents
745 The base set of IPP documents includes:
747 Design Goals for an Internet Printing Protocol [RFC2567]
748 Rationale for the Structure and Model and Protocol for the
749 Internet Printing Protocol [RFC2568]
750 Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
751 Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
752 Internet Printing Protocol/1.1: Implementer's Guide [RFC3196]
753 Mapping between LPD and IPP Protocols [RFC2569]
755 The "Design Goals for an Internet Printing Protocol" document takes a
756 broad look at distributed printing functionality, and enumerates
757 real-life scenarios that help to clarify the features that need to be
758 included in a printing protocol for the Internet. It identifies
759 requirements for three types of users: end users, operators, and
760 administrators. It calls out a subset of end user requirements that
761 are satisfied in IPP/1.0 [RFC2566, RFC2565]. A few OPTIONAL operator
762 operations have been added to IPP/1.1 [RFC2911, RFC2910].
764 The "Rationale for the Structure and Model and Protocol for the
765 Internet Printing Protocol" document describes IPP from a high level
766 view, defines a roadmap for the various documents that form the suite
767 of IPP specification documents, and gives background and rationale
768 for the IETF IPP working group's major decisions.
770 The "Internet Printing Protocol/1.1: Model and Semantics" document
771 describes a simplified model with abstract objects, their attributes,
772 and their operations. The model introduces a Printer and a Job. The
773 Job supports multiple documents per Job. The model document also
774 addresses how security, internationalization, and directory issues
777 The "Internet Printing Protocol/1.1: Encoding and Transport" document
778 is a formal mapping of the abstract operations and attributes defined
779 in the model document onto HTTP/1.1 [RFC2616]. It also defines the
780 encoding rules for a new Internet MIME media type called
781 "application/ipp". This document also defines the rules for
782 transporting over HTTP a message body whose Content-Type is
786 Hastings, et. al. Standards Track [Page 14]
788 RFC 3381 IPP: Job Progress Attributes September 2002
791 "application/ipp". This document defines the 'ipp' scheme for
792 identifying IPP printers and jobs.
794 The "Internet Printing Protocol/1.1: Implementer's Guide" document
795 gives insight and advice to implementers of IPP clients and IPP
796 objects. It is intended to help them understand IPP/1.1 and some of
797 the considerations that may assist them in the design of their client
798 and/or IPP object implementations. For example, a typical order of
799 processing requests is given, including error checking. Motivation
800 for some of the specification decisions is also included.
802 The "Mapping between LPD and IPP Protocols" document gives some
803 advice to implementers of gateways between IPP and LPD (Line Printer
804 Daemon) implementations.
806 In addition to the base IPP documents, the "Event Notification
807 Specification" document [ipp-ntfy] defines OPTIONAL operations that
808 allow a client to subscribe to printing related events.
809 Subscriptions include "Per-Job subscriptions" and "Per-Printer
810 subscriptions". Subscriptions are modeled as Subscription objects.
811 Four other operations are defined for subscription objects: get
812 attributes, get subscriptions, renew a subscription, and cancel a
842 Hastings, et. al. Standards Track [Page 15]
844 RFC 3381 IPP: Job Progress Attributes September 2002
847 11 Authors' Addresses
851 737 Hawaii St. ESAE 231
856 EMail: hastings@cp10.es.xerox.com
861 Boulder, CO 80301-9191
863 Phone: (303) 924-5337
864 EMail: harryl@us.ibm.com
867 Hitachi Koki Imaging Solutions
868 1757 Tapo Canyon Road
869 Simi Valley, CA 93063-3394
873 EMail: rbergma@hitachi-hkis.com
875 IPP Web Page: http://www.pwg.org/ipp/
876 IPP Mailing List: ipp@pwg.org
878 To subscribe to the ipp mailing list, send the following email:
880 1) send it to majordomo@pwg.org
881 2) leave the subject line blank
882 3) put the following two lines in the message body:
886 Implementers of this specification document are encouraged to join
887 the IPP Mailing List in order to participate in any discussions of
888 clarification issues and review of registration proposals for
889 additional attributes and values. In order to reduce spam, the
890 mailing list rejects mail from non-subscribers, so you must subscribe
891 to the mailing list in order to send a question or comment to the
898 Hastings, et. al. Standards Track [Page 16]
900 RFC 3381 IPP: Job Progress Attributes September 2002
903 12 Full Copyright Statement
905 Copyright (C) The Internet Society (2002). All Rights Reserved.
907 This document and translations of it may be copied and furnished to
908 others, and derivative works that comment on or otherwise explain it
909 or assist in its implementation may be prepared, copied, published
910 and distributed, in whole or in part, without restriction of any
911 kind, provided that the above copyright notice and this paragraph are
912 included on all such copies and derivative works. However, this
913 document itself may not be modified in any way, such as by removing
914 the copyright notice or references to the Internet Society or other
915 Internet organizations, except as needed for the purpose of
916 developing Internet standards in which case the procedures for
917 copyrights defined in the Internet Standards process must be
918 followed, or as required to translate it into languages other than
921 The limited permissions granted above are perpetual and will not be
922 revoked by the Internet Society or its successors or assigns.
924 This document and the information contained herein is provided on an
925 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
926 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
927 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
928 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
929 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
933 Funding for the RFC Editor function is currently provided by the
954 Hastings, et. al. Standards Track [Page 17]