< draft-sweet-rfc2911bis-10.txt   draft-sweet-rfc2911bis-11.txt >
IPP WG M. Sweet IPP WG M. Sweet
Internet-Draft Apple Inc. Internet-Draft Apple Inc.
Obsoletes: 2911,3381,3382 (if approved) I. McDonald Obsoletes: 2911,3381,3382 (if approved) I. McDonald
Intended status: Standards Track High North, Inc. Intended status: Standards Track High North, Inc.
Expires: February 6, 2017 August 5, 2016 Expires: February 26, 2017 August 25, 2016
Internet Printing Protocol/1.1: Model and Semantics Internet Printing Protocol/1.1: Model and Semantics
draft-sweet-rfc2911bis-10 draft-sweet-rfc2911bis-11
Abstract Abstract
The Internet Printing Protocol (IPP) is an application level protocol The Internet Printing Protocol (IPP) is an application level protocol
for distributed printing using Internet tools and technologies. This for distributed printing using Internet tools and technologies. This
document describes a simplified model consisting of abstract objects, document describes a simplified model consisting of abstract objects,
attributes, and operations that is independent of encoding and attributes, and operations that is independent of encoding and
transport. The model consists of several objects including Printers transport. The model consists of several objects including Printers
and Jobs. Jobs optionally support multiple Documents. and Jobs. Jobs optionally support multiple Documents.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 6, 2017. This Internet-Draft will expire on February 26, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1. Simplified Printing Model . . . . . . . . . . . . . . . . . 11 1.1. Simplified Printing Model . . . . . . . . . . . . . . . . . 11
2. Conventions Used in This Document . . . . . . . . . . . . . . 13 2. Conventions Used in This Document . . . . . . . . . . . . . . 14
2.1. Requirements Language . . . . . . . . . . . . . . . . . . . 13 2.1. Requirements Language . . . . . . . . . . . . . . . . . . . 14
2.2. Printing Terminology . . . . . . . . . . . . . . . . . . . 14 2.2. Printing Terminology . . . . . . . . . . . . . . . . . . . 14
2.3. Model Terminology . . . . . . . . . . . . . . . . . . . . . 14 2.3. Model Terminology . . . . . . . . . . . . . . . . . . . . . 15
2.3.1. Administrator . . . . . . . . . . . . . . . . . . . . . . 14 2.3.1. Administrator . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2. Attributes . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.2. Attributes . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2.1. Attribute Group Name . . . . . . . . . . . . . . . . . 15 2.3.2.1. Attribute Group Name . . . . . . . . . . . . . . . . . 15
2.3.2.2. Attribute Name . . . . . . . . . . . . . . . . . . . . 15 2.3.2.2. Attribute Name . . . . . . . . . . . . . . . . . . . . 15
2.3.2.3. Attribute Syntax . . . . . . . . . . . . . . . . . . . 15 2.3.2.3. Attribute Syntax . . . . . . . . . . . . . . . . . . . 15
2.3.2.4. Attribute Value . . . . . . . . . . . . . . . . . . . . 15 2.3.2.4. Attribute Value . . . . . . . . . . . . . . . . . . . . 16
2.3.3. End User . . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.3. End User . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.4. Impression . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.4. Impression . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.5. Input Page . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.5. Input Page . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.6. Job Creation Operation . . . . . . . . . . . . . . . . . 16 2.3.6. Job Creation Operation . . . . . . . . . . . . . . . . . 16
2.3.7. Keyword . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.7. Keyword . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.8. Media Sheet . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.8. Media Sheet . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.9. Operator . . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.9. Operator . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.10. Set . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.3.10. Set . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.11. Supports . . . . . . . . . . . . . . . . . . . . . . . . 17 2.3.11. Supports . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.12. Terminating State . . . . . . . . . . . . . . . . . . . . 19 2.3.12. Terminating State . . . . . . . . . . . . . . . . . . . . 19
2.4. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . 19 2.4. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . 19
3. IPP Objects . . . . . . . . . . . . . . . . . . . . . . . . . 20 3. IPP Objects . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1. Printer Object . . . . . . . . . . . . . . . . . . . . . . 21 3.1. Printer Object . . . . . . . . . . . . . . . . . . . . . . 21
3.2. Job Object . . . . . . . . . . . . . . . . . . . . . . . . 23 3.2. Job Object . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3. Object Relationships . . . . . . . . . . . . . . . . . . . 24 3.3. Object Relationships . . . . . . . . . . . . . . . . . . . 24
3.4. Object Identity . . . . . . . . . . . . . . . . . . . . . . 25 3.4. Object Identity . . . . . . . . . . . . . . . . . . . . . . 25
4. IPP Operations . . . . . . . . . . . . . . . . . . . . . . . 27 4. IPP Operations . . . . . . . . . . . . . . . . . . . . . . . 27
skipping to change at page 6, line 51 skipping to change at page 6, line 51
6.2.5. Extensions . . . . . . . . . . . . . . . . . . . . . . . 162 6.2.5. Extensions . . . . . . . . . . . . . . . . . . . . . . . 162
6.2.6. Attribute Syntaxes . . . . . . . . . . . . . . . . . . . 162 6.2.6. Attribute Syntaxes . . . . . . . . . . . . . . . . . . . 162
6.2.7. Security . . . . . . . . . . . . . . . . . . . . . . . . 162 6.2.7. Security . . . . . . . . . . . . . . . . . . . . . . . . 162
6.3. Charset and Natural Language Requirements . . . . . . . . . 163 6.3. Charset and Natural Language Requirements . . . . . . . . . 163
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 163 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 163
7.1. Object Extensions . . . . . . . . . . . . . . . . . . . . . 164 7.1. Object Extensions . . . . . . . . . . . . . . . . . . . . . 164
7.2. Attribute Extensibility . . . . . . . . . . . . . . . . . . 164 7.2. Attribute Extensibility . . . . . . . . . . . . . . . . . . 164
7.3. Keyword Extensibility . . . . . . . . . . . . . . . . . . . 165 7.3. Keyword Extensibility . . . . . . . . . . . . . . . . . . . 165
7.4. Enum Extensibility . . . . . . . . . . . . . . . . . . . . 166 7.4. Enum Extensibility . . . . . . . . . . . . . . . . . . . . 166
7.5. Attribute Group Extensibility . . . . . . . . . . . . . . . 166 7.5. Attribute Group Extensibility . . . . . . . . . . . . . . . 166
7.6. Out-of-band Attribute Value Extensibility . . . . . . . . . 166 7.6. Out-of-band Attribute Value Extensibility . . . . . . . . . 167
7.7. Attribute Syntax Extensibility . . . . . . . . . . . . . . 167 7.7. Attribute Syntax Extensibility . . . . . . . . . . . . . . 167
7.8. Operation Extensibility . . . . . . . . . . . . . . . . . . 167 7.8. Operation Extensibility . . . . . . . . . . . . . . . . . . 167
7.9. Status Code Extensibility . . . . . . . . . . . . . . . . . 167 7.9. Status Code Extensibility . . . . . . . . . . . . . . . . . 168
8. Internationalization Considerations . . . . . . . . . . . . . 168 8. Internationalization Considerations . . . . . . . . . . . . . 168
9. Security Considerations . . . . . . . . . . . . . . . . . . . 172 9. Security Considerations . . . . . . . . . . . . . . . . . . . 172
9.1. Security Scenarios . . . . . . . . . . . . . . . . . . . . 173 9.1. Security Scenarios . . . . . . . . . . . . . . . . . . . . 173
9.1.1. Client and Server in the Same Security Domain . . . . . . 173 9.1.1. Client and Server in the Same Security Domain . . . . . . 173
9.1.2. Client and Server in Different Security Domains . . . . . 173 9.1.2. Client and Server in Different Security Domains . . . . . 173
9.1.3. Print by Reference . . . . . . . . . . . . . . . . . . . 174 9.1.3. Print by Reference . . . . . . . . . . . . . . . . . . . 174
9.2. URIs in Operation, Job, and Printer attributes . . . . . . 174 9.2. URIs in Operation, Job, and Printer attributes . . . . . . 174
9.3. URIs for each authentication mechanisms . . . . . . . . . . 174 9.3. URIs for each authentication mechanisms . . . . . . . . . . 174
9.4. Restricted Queries . . . . . . . . . . . . . . . . . . . . 175 9.4. Restricted Queries . . . . . . . . . . . . . . . . . . . . 175
9.5. Operations performed by Operators and Administrators . . . 175 9.5. Operations performed by Operators and Administrators . . . 176
9.6. Queries on Jobs submitted using non-IPP protocols . . . . . 176 9.6. Queries on Jobs submitted using non-IPP protocols . . . . . 176
10. Changes Since RFC 2911 . . . . . . . . . . . . . . . . . . . 176 10. Changes Since RFC 2911 . . . . . . . . . . . . . . . . . . . 176
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 177 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.1. Normative References . . . . . . . . . . . . . . . . . . . 177 11.1. Normative References . . . . . . . . . . . . . . . . . . . 178
11.2. Informative References . . . . . . . . . . . . . . . . . . 182 11.2. Informative References . . . . . . . . . . . . . . . . . . 183
Appendix A. Formats for IPP Registration Proposals . . . . . . . 184 Appendix A. Formats for IPP Registration Proposals . . . . . . . 185
A.1. Attribute Registration . . . . . . . . . . . . . . . . . . 185 A.1. Attribute Registration . . . . . . . . . . . . . . . . . . 185
A.2. Type2 Keyword Attribute Value Registration . . . . . . . . 186 A.2. Type2 Keyword Attribute Value Registration . . . . . . . . 186
A.3. Type2 Enum Attribute Value Registration . . . . . . . . . . 186 A.3. Type2 Enum Attribute Value Registration . . . . . . . . . . 187
A.4. Operation Registration . . . . . . . . . . . . . . . . . . 186 A.4. Operation Registration . . . . . . . . . . . . . . . . . . 187
A.5. Status code registration . . . . . . . . . . . . . . . . . 187 A.5. Status code registration . . . . . . . . . . . . . . . . . 188
Appendix B. Status Codes and Suggested Status Code Messages . . 187 Appendix B. Status Codes and Suggested Status Code Messages . . 188
B.1. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 189 B.1. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 189
B.1.1. Informational . . . . . . . . . . . . . . . . . . . . . . 189 B.1.1. Informational . . . . . . . . . . . . . . . . . . . . . . 189
B.1.2. Successful Status Codes . . . . . . . . . . . . . . . . . 189 B.1.2. Successful Status Codes . . . . . . . . . . . . . . . . . 190
B.1.2.1. successful-ok (0x0000) . . . . . . . . . . . . . . . . 189 B.1.2.1. successful-ok (0x0000) . . . . . . . . . . . . . . . . 190
B.1.2.2. successful-ok-ignored-or-substituted-attributes B.1.2.2. successful-ok-ignored-or-substituted-attributes
(0x0001) . . . . . . . . . . . . . . . . . . . . . . . 189 (0x0001) . . . . . . . . . . . . . . . . . . . . . . . 190
B.1.2.3. successful-ok-conflicting-attributes (0x0002) . . . . . 190 B.1.2.3. successful-ok-conflicting-attributes (0x0002) . . . . . 190
B.1.3. Redirection Status Codes . . . . . . . . . . . . . . . . 190 B.1.3. Redirection Status Codes . . . . . . . . . . . . . . . . 190
B.1.4. Client Error Status Codes . . . . . . . . . . . . . . . . 190 B.1.4. Client Error Status Codes . . . . . . . . . . . . . . . . 191
B.1.4.1. client-error-bad-request (0x0400) . . . . . . . . . . . 190 B.1.4.1. client-error-bad-request (0x0400) . . . . . . . . . . . 191
B.1.4.2. client-error-forbidden (0x0401) . . . . . . . . . . . . 190 B.1.4.2. client-error-forbidden (0x0401) . . . . . . . . . . . . 191
B.1.4.3. client-error-not-authenticated (0x0402) . . . . . . . . 191 B.1.4.3. client-error-not-authenticated (0x0402) . . . . . . . . 191
B.1.4.4. client-error-not-authorized (0x0403) . . . . . . . . . 191 B.1.4.4. client-error-not-authorized (0x0403) . . . . . . . . . 191
B.1.4.5. client-error-not-possible (0x0404) . . . . . . . . . . 191 B.1.4.5. client-error-not-possible (0x0404) . . . . . . . . . . 192
B.1.4.6. client-error-timeout (0x0405) . . . . . . . . . . . . . 191 B.1.4.6. client-error-timeout (0x0405) . . . . . . . . . . . . . 192
B.1.4.7. client-error-not-found (0x0406) . . . . . . . . . . . . 191 B.1.4.7. client-error-not-found (0x0406) . . . . . . . . . . . . 192
B.1.4.8. client-error-gone (0x0407) . . . . . . . . . . . . . . 192 B.1.4.8. client-error-gone (0x0407) . . . . . . . . . . . . . . 192
B.1.4.9. client-error-request-entity-too-large (0x0408) . . . . 192 B.1.4.9. client-error-request-entity-too-large (0x0408) . . . . 193
B.1.4.10. client-error-request-value-too-long (0x0409) . . . . . 192 B.1.4.10. client-error-request-value-too-long (0x0409) . . . . . 193
B.1.4.11. client-error-document-format-not-supported (0x040A) . . 193 B.1.4.11. client-error-document-format-not-supported (0x040A) . . 193
B.1.4.12. client-error-attributes-or-values-not-supported B.1.4.12. client-error-attributes-or-values-not-supported
(0x040B) . . . . . . . . . . . . . . . . . . . . . . . 193 (0x040B) . . . . . . . . . . . . . . . . . . . . . . . 194
B.1.4.13. client-error-uri-scheme-not-supported (0x040C) . . . . 194 B.1.4.13. client-error-uri-scheme-not-supported (0x040C) . . . . 194
B.1.4.14. client-error-charset-not-supported (0x040D) . . . . . . 194 B.1.4.14. client-error-charset-not-supported (0x040D) . . . . . . 194
B.1.4.15. client-error-conflicting-attributes (0x040E) . . . . . 194 B.1.4.15. client-error-conflicting-attributes (0x040E) . . . . . 195
B.1.4.16. client-error-compression-not-supported (0x040F) . . . . 194 B.1.4.16. client-error-compression-not-supported (0x040F) . . . . 195
B.1.4.17. client-error-compression-error (0x0410) . . . . . . . . 194 B.1.4.17. client-error-compression-error (0x0410) . . . . . . . . 195
B.1.4.18. client-error-document-format-error (0x0411) . . . . . . 195 B.1.4.18. client-error-document-format-error (0x0411) . . . . . . 195
B.1.4.19. client-error-document-access-error (0x0412) . . . . . . 195 B.1.4.19. client-error-document-access-error (0x0412) . . . . . . 195
B.1.5. Server Error Status Codes . . . . . . . . . . . . . . . . 195 B.1.5. Server Error Status Codes . . . . . . . . . . . . . . . . 196
B.1.5.1. server-error-internal-error (0x0500) . . . . . . . . . 195 B.1.5.1. server-error-internal-error (0x0500) . . . . . . . . . 196
B.1.5.2. server-error-operation-not-supported (0x0501) . . . . . 195 B.1.5.2. server-error-operation-not-supported (0x0501) . . . . . 196
B.1.5.3. server-error-service-unavailable (0x0502) . . . . . . . 196 B.1.5.3. server-error-service-unavailable (0x0502) . . . . . . . 196
B.1.5.4. server-error-version-not-supported (0x0503) . . . . . . 196 B.1.5.4. server-error-version-not-supported (0x0503) . . . . . . 197
B.1.5.5. server-error-device-error (0x0504) . . . . . . . . . . 196 B.1.5.5. server-error-device-error (0x0504) . . . . . . . . . . 197
B.1.5.6. server-error-temporary-error (0x0505) . . . . . . . . . 197 B.1.5.6. server-error-temporary-error (0x0505) . . . . . . . . . 197
B.1.5.7. server-error-not-accepting-Jobs (0x0506) . . . . . . . 197 B.1.5.7. server-error-not-accepting-Jobs (0x0506) . . . . . . . 198
B.1.5.8. server-error-busy (0x0507) . . . . . . . . . . . . . . 197 B.1.5.8. server-error-busy (0x0507) . . . . . . . . . . . . . . 198
B.1.5.9. server-error-job-canceled (0x0508) . . . . . . . . . . 197 B.1.5.9. server-error-job-canceled (0x0508) . . . . . . . . . . 198
B.1.5.10. server-error-multiple-document-jobs-not-supported B.1.5.10. server-error-multiple-document-jobs-not-supported
(0x0509) . . . . . . . . . . . . . . . . . . . . . . . 197 (0x0509) . . . . . . . . . . . . . . . . . . . . . . . 198
B.2. Status Codes for IPP Operations . . . . . . . . . . . . . . 198 B.2. Status Codes for IPP Operations . . . . . . . . . . . . . . 198
Appendix C. Processing IPP Attributes . . . . . . . . . . . . . 199 Appendix C. Processing IPP Attributes . . . . . . . . . . . . . 200
C.1. Fidelity . . . . . . . . . . . . . . . . . . . . . . . . . 200 C.1. Fidelity . . . . . . . . . . . . . . . . . . . . . . . . . 201
C.2. Page Description Language (PDL) Override . . . . . . . . . 201 C.2. Page Description Language (PDL) Override . . . . . . . . . 202
C.3. Using Job Template Attributes During Document Processing. . 203 C.3. Using Job Template Attributes During Document Processing. . 204
Appendix D. Generic Directory Schema . . . . . . . . . . . . . . 205 Appendix D. Generic Directory Schema . . . . . . . . . . . . . . 205
Appendix E. Change History . . . . . . . . . . . . . . . . . . . 207 Appendix E. Acknowledgements . . . . . . . . . . . . . . . . . . 208
E.1. Changes In -10 . . . . . . . . . . . . . . . . . . . . . . 207 Appendix F. Change History . . . . . . . . . . . . . . . . . . . 208
E.2. Changes In -09 . . . . . . . . . . . . . . . . . . . . . . 209 F.1. Changes In -11 . . . . . . . . . . . . . . . . . . . . . . 208
E.3. Changes In -08 . . . . . . . . . . . . . . . . . . . . . . 210 F.2. Changes In -10 . . . . . . . . . . . . . . . . . . . . . . 208
E.4. Changes In -07 . . . . . . . . . . . . . . . . . . . . . . 210 F.3. Changes In -09 . . . . . . . . . . . . . . . . . . . . . . 210
E.5. Changes In -06 . . . . . . . . . . . . . . . . . . . . . . 211 F.4. Changes In -08 . . . . . . . . . . . . . . . . . . . . . . 211
E.6. Changes In -05 . . . . . . . . . . . . . . . . . . . . . . 214 F.5. Changes In -07 . . . . . . . . . . . . . . . . . . . . . . 212
E.7. Changes In -04 . . . . . . . . . . . . . . . . . . . . . . 216 F.6. Changes In -06 . . . . . . . . . . . . . . . . . . . . . . 212
E.8. Changes In -03 . . . . . . . . . . . . . . . . . . . . . . 216 F.7. Changes In -05 . . . . . . . . . . . . . . . . . . . . . . 215
E.9. Changes In -02 . . . . . . . . . . . . . . . . . . . . . . 217 F.8. Changes In -04 . . . . . . . . . . . . . . . . . . . . . . 217
E.10. Changes In -01 . . . . . . . . . . . . . . . . . . . . . . 217 F.9. Changes In -03 . . . . . . . . . . . . . . . . . . . . . . 218
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 218 F.10. Changes In -02 . . . . . . . . . . . . . . . . . . . . . . 218
F.11. Changes In -01 . . . . . . . . . . . . . . . . . . . . . . 219
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 219
1. Introduction 1. Introduction
The Internet Printing Protocol (IPP) is an application level protocol The Internet Printing Protocol (IPP) is an application level protocol
for distributed printing using Internet tools and technologies. IPP for distributed printing using Internet tools and technologies. IPP
version 1.1 (IPP/1.1) focuses primarily on End User functionality version 1.1 (IPP/1.1) focuses primarily on End User functionality
with a few administrative operations included. IPP versions 2.0, with a few administrative operations included. IPP versions 2.0,
2.1, and 2.2 provide many new operations and are defined separately. 2.1, and 2.2 provide many new operations and are defined separately.
This document is just one of a suite of documents that fully define This document is just one of a suite of documents that fully define
skipping to change at page 164, line 40 skipping to change at page 164, line 40
extensions was formerly Expert Review; this document changes the extensions was formerly Expert Review; this document changes the
policy to Specification Required. policy to Specification Required.
7.2. Attribute Extensibility 7.2. Attribute Extensibility
Since attribute names are type2 keywords (see Section 5.1.4), the Since attribute names are type2 keywords (see Section 5.1.4), the
IANA policy (using terms defined in [RFC5226]) for attribute IANA policy (using terms defined in [RFC5226]) for attribute
extensions is Expert Review. extensions is Expert Review.
For vendor attribute extensions, implementers SHOULD use keywords For vendor attribute extensions, implementers SHOULD use keywords
with a suitable distinguishing prefix such as "xxx-" where xxx with a suitable distinguishing prefix such as 'smiNNN-' where NNN is
follows the syntax rules for keywords (see Section 5.1.4) and is the a SMI Private Enterprise Number (PEN) [IANA-PEN]. For example, if
reversed (lowercase) fully qualified domain name [RFC1035]. For the company Example Corp. had obtained the SMI PEN 32473, then a
example, if the company Example Corp. had obtained the domain name vendor attribute 'foo' would be: 'smi32473-foo'.
"example.com", then a vendor attribute 'foo' would be: 'com.example-
foo'. Note: Prior versions of this document recommended using a fully
qualified domain name [RFC1035] as the prefix ('example.com-foo')
and many IPP implementations have also used reversed domain names
('com.example-foo'). Domain names have proven problematic due to
the length of some domain names, parallel use of country-specific
domain names ('example.co.jp-foo'), and changes in ownership of
domain names.
If a new Printer attribute is defined and its values can be affected If a new Printer attribute is defined and its values can be affected
by a specific Document format, its specification needs to contain the by a specific Document format, its specification needs to contain the
following sentence: following sentence:
"The value of this attribute returned in a Get-Printer-Attributes "The value of this attribute returned in a Get-Printer-Attributes
response MAY depend on the "document-format" attribute supplied response MAY depend on the "document-format" attribute supplied
(see Section 4.2.5.1) of the IPP/1.1 Model and Semantics." (see Section 4.2.5.1) of the IPP/1.1 Model and Semantics."
If the specification does not, then its value in the Get-Printer- If the specification does not, then its value in the Get-Printer-
skipping to change at page 165, line 42 skipping to change at page 165, line 46
For type1 and type2 keywords, the proposer includes the name of the For type1 and type2 keywords, the proposer includes the name of the
keyword in the registration proposal and the name is part of the keyword in the registration proposal and the name is part of the
technical review. technical review.
For vendor keyword extensions, implementers SHOULD either: For vendor keyword extensions, implementers SHOULD either:
a. follow attribute-specific guidance such as defined in a. follow attribute-specific guidance such as defined in
[PWG5101.1]; or [PWG5101.1]; or
b. use keywords with a suitable distinguishing prefix, such as b. use keywords with a suitable distinguishing prefix, such as
"xxx-" where xxx follows the syntax rules for keywords (see 'smiNNN-' where NNN is a SMI Private Enterprise Number (PEN)
Section 5.1.4) and is the reversed (lowercase) fully qualified [IANA-PEN].
domain name [RFC1035].
For example, if the company Example Corp. had obtained the domain For example, if the company Example Corp. had obtained the SMI PEN
name "example.com", then a vendor keyword 'abc' would be: 32473, then a vendor keyword 'foo' would be: 'smi32473-foo'.
'com.example-abc'.
Note: Prior versions of this document recommended using a fully
qualified domain name [RFC1035] as the prefix ('example.com-foo')
and many IPP implementations have also used reversed domain names
('com.example-foo'). Domain names have proven problematic due to
the length of some domain names, parallel use of country-specific
domain names ('example.co.jp-foo'), and changes in ownership of
domain names.
When a type2 keyword extension is approved, the IPP Designated When a type2 keyword extension is approved, the IPP Designated
Expert(s) become the points of contact for any future maintenance Expert(s) become the points of contact for any future maintenance
that might be required for that registration. that might be required for that registration.
7.4. Enum Extensibility 7.4. Enum Extensibility
The IANA policy (using terms defined in [RFC5226]) for type1 enum The IANA policy (using terms defined in [RFC5226]) for type1 enum
extensions is Specification Required. The IANA policy for type2 enum extensions is Specification Required. The IANA policy for type2 enum
extensions is Expert Review. The IANA policy for vendor enum extensions is Expert Review. The IANA policy for vendor enum
skipping to change at page 177, line 22 skipping to change at page 177, line 32
o Obsoleted all attributes and values defined in RFC 3381, as they o Obsoleted all attributes and values defined in RFC 3381, as they
do not interact well with the "finishings" attribute and have do not interact well with the "finishings" attribute and have
never been widely implemented. never been widely implemented.
o Deprecated the Purge-Jobs and Restart-Job operations which destroy o Deprecated the Purge-Jobs and Restart-Job operations which destroy
accounting information. accounting information.
o Dropped type3 registration procedures. o Dropped type3 registration procedures.
o Changed the vendor attribute and keyword naming recommendations to
use SMI Private Enterprise Numbers ("smiNNN-foo") instead of
domain names.
o Split READ-ONLY Job Description and Printer Description attributes o Split READ-ONLY Job Description and Printer Description attributes
into Job Status and Printer Status attributes to match the current into Job Status and Printer Status attributes to match the current
IANA IPP registry organization. IANA IPP registry organization.
o Referenced all IETF and PWG IPP standards. o Referenced all IETF and PWG IPP standards.
o Updated OPTIONAL operations, attributes, and values to RECOMMENDED o Updated OPTIONAL operations, attributes, and values to RECOMMENDED
for consistency with IPP 2.0, IPP Everywhere, and the IPP for consistency with IPP 2.0, IPP Everywhere, and the IPP
Implementor's Guide v2.0 (IG). Implementor's Guide v2.0 (IG).
skipping to change at page 181, line 23 skipping to change at page 181, line 45
[RFC3510] Herriot, R. and I. McDonald, "Internet Printing [RFC3510] Herriot, R. and I. McDonald, "Internet Printing
Protocol/1.1: IPP URL Scheme", RFC 3510, April 2003. Protocol/1.1: IPP URL Scheme", RFC 3510, April 2003.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[RFC3805] Bergman, R., Lewis, H., and I. McDonald, "Printer MIB v2", [RFC3805] Bergman, R., Lewis, H., and I. McDonald, "Printer MIB v2",
RFC 3805, June 2004. RFC 3805, June 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005.
[RFC3995] Herriot, R. and T. Hastings, "Internet Printing Protocol [RFC3995] Herriot, R. and T. Hastings, "Internet Printing Protocol
(IPP): Event Notifications and Subscriptions", RFC 3995, (IPP): Event Notifications and Subscriptions", RFC 3995,
March 2005. March 2005.
[RFC3996] Herriot, R., Hastings, T., and H. Lewis, "Internet [RFC3996] Herriot, R., Hastings, T., and H. Lewis, "Internet
Printing Protocol (IPP): The 'ippget' Delivery Method for Printing Protocol (IPP): The 'ippget' Delivery Method for
Event Notifications", RFC 3996, March 2005. Event Notifications", RFC 3996, March 2005.
[RFC3998] Kugler, C., Lewis, H., and T. Hastings, "Internet Printing [RFC3998] Kugler, C., Lewis, H., and T. Hastings, "Internet Printing
skipping to change at page 182, line 6 skipping to change at page 182, line 27
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13, RFC
RFC 6838, January 2013. 6838, January 2013.
[RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol [RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
(HTTP/1.1): Message Syntax and Routing", RFC 7230, June (HTTP/1.1): Message Syntax and Routing", RFC 7230, June
2014. 2014.
[RFC7472] McDonald, I. and M. Sweet, "Internet Printing Protocol [RFC7472] McDonald, I. and M. Sweet, "Internet Printing Protocol
(IPP) over HTTPS Transport Binding and the 'ipps' URI (IPP) over HTTPS Transport Binding and the 'ipps' URI
Scheme", RFC 7472, March 2015. Scheme", RFC 7472, March 2015.
[RFC7612] Flemming, P. and I. McDonald, "Lightweight Directory [RFC7612] Flemming, P. and I. McDonald, "Lightweight Directory
Access Protocol (LDAP): Schema for Printer Services", Access Protocol (LDAP): Schema for Printer Services", RFC
RFC 7612, June 2015. 7612, June 2015.
[RFC7616] Shekh-Yusef, R., Ahrens, D., and S. Bremer, "HTTP Digest [RFC7616] Shekh-Yusef, R., Ahrens, D., and S. Bremer, "HTTP Digest
Access Authentication", September 2015, Access Authentication", September 2015,
<http://tools.ietf.org/html/rfc7616>. <http://tools.ietf.org/html/rfc7616>.
[RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme", [RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme",
September 2015, <http://tools.ietf.org/html/rfc7617>. September 2015, <http://tools.ietf.org/html/rfc7617>.
[RFC793] Postel, J., "Transmission Control Protocol", STD 7, [RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC
RFC 793, September 1981. 793, September 1981.
11.2. Informative References 11.2. Informative References
[HTPP] Barnett, J., Carter, K., and R. DeBry, "Initial Draft - [HTPP] Barnett, J., Carter, K., and R. DeBry, "Initial Draft -
Hypertext Printing Protocol - HTPP/1.0", 10 1996, Hypertext Printing Protocol - HTPP/1.0", 10 1996,
<ftp://ftp.pwg.org/pub/pwg/ipp/historic/htpp/ <ftp://ftp.pwg.org/pub/pwg/ipp/historic/htpp/
overview.ps.gz>. overview.ps.gz>.
[IANA-CS] "IANA Registry of Coded Character Sets", [IANA-CS] "IANA Registry of Coded Character Sets",
<http://www.iana.org/assignments/character-sets/ <http://www.iana.org/assignments/character-sets/
character-sets.xhtml>. character-sets.xhtml>.
[IANA-MT] "IANA Registry of Media Types", [IANA-MT] "IANA Registry of Media Types",
<http://www.iana.org/assignments/media-types/ <http://www.iana.org/assignments/media-types/
media-types.xhtml>. media-types.xhtml>.
[IANA-PEN]
"IANA Registry of Private Enterprise Numbers",
<http://www.iana.org/assignments/enterprise-numbers/
enterprise-numbers>.
[ISO32000] [ISO32000]
"Document management -- Portable document format -- Part "Document management -- Portable document format -- Part
1: PDF 1.7", 7 2008, 1: PDF 1.7", 7 2008,
<http://www.adobe.com/devnet/acrobat/pdfs/ <http://www.adobe.com/devnet/acrobat/pdfs/
PDF32000_2008.pdf>. PDF32000_2008.pdf>.
[LDPA] Hastings, T., Isaacson, S., MacKay, M., Manros, C., [LDPA] Hastings, T., Isaacson, S., MacKay, M., Manros, C.,
Taylor, D., and P. Zehler, "LDPA - Lightweight Document Taylor, D., and P. Zehler, "LDPA - Lightweight Document
Printing Application", October 1996, Printing Application", October 1996,
<ftp://ftp.pwg.org/pub/pwg/ipp/historic/ldpa/ <ftp://ftp.pwg.org/pub/pwg/ipp/historic/ldpa/
skipping to change at page 184, line 6 skipping to change at page 184, line 31
[RFC2568] Zilles, S., "Rationale for the Structure of the Model and [RFC2568] Zilles, S., "Rationale for the Structure of the Model and
Protocol for the Internet Printing Protocol", RFC 2568, Protocol for the Internet Printing Protocol", RFC 2568,
April 1999. April 1999.
[RFC2569] Herriot, R., Jacobs, N., Hastings, T., and J. Martin, [RFC2569] Herriot, R., Jacobs, N., Hastings, T., and J. Martin,
"Mapping between LPD and IPP Protocols", RFC 2569, April "Mapping between LPD and IPP Protocols", RFC 2569, April
1999. 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
STD 58, RFC 2579, April 1999. 58, RFC 2579, April 1999.
[RFC2978] Freed, N. and J. Postel, "IANA Charset Registration [RFC2978] Freed, N. and J. Postel, "IANA Charset Registration
Procedures", BCP 19, RFC 2978, October 2000. Procedures", BCP 19, RFC 2978, October 2000.
[RFC3239] Kugler, C., Lewis, H., and T. Hastings, "Internet Printing [RFC3239] Kugler, C., Lewis, H., and T. Hastings, "Internet Printing
Protocol (IPP): Requirements for Job, Printer, and Device Protocol (IPP): Requirements for Job, Printer, and Device
Administrative Operations", RFC 3239, February 2002. Administrative Operations", RFC 3239, February 2002.
[RFC3997] Hastings, T., deBry, R., and H. Lewis, "Internet Printing [RFC3997] Hastings, T., deBry, R., and H. Lewis, "Internet Printing
Protocol (IPP): Requirements for IPP Notifications", Protocol (IPP): Requirements for IPP Notifications", RFC
RFC 3997, March 2005. 3997, March 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122, DOI
DOI 10.17487/RFC4122, July 2005, 10.17487/RFC4122, July 2005,
<http://www.rfc-editor.org/info/rfc4122>. <http://www.rfc-editor.org/info/rfc4122>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' [RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010, URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010,
<http://www.rfc-editor.org/info/rfc6068>. <http://www.rfc-editor.org/info/rfc6068>.
skipping to change at page 207, line 26 skipping to change at page 208, line 11
+------------------------------------+-------------+----------------+ +------------------------------------+-------------+----------------+
| supported | OPTIONAL | Section 5.4.20 | | supported | OPTIONAL | Section 5.4.20 |
+------------------------------------+-------------+----------------+ +------------------------------------+-------------+----------------+
| uri-authentication-supported | RECOMMENDED | Section 5.4.2 | | uri-authentication-supported | RECOMMENDED | Section 5.4.2 |
+------------------------------------+-------------+----------------+ +------------------------------------+-------------+----------------+
| uri-security-supported | RECOMMENDED | Section 5.4.3 | | uri-security-supported | RECOMMENDED | Section 5.4.3 |
+------------------------------------+-------------+----------------+ +------------------------------------+-------------+----------------+
Table 23: Attributes in Directory Entries Table 23: Attributes in Directory Entries
Appendix E. Change History Appendix E. Acknowledgements
E.1. Changes In -10 The authors would like to acknowledge the following individuals for
their contributions to the original IPP/1.1 specifications:
Roger deDry, Tom Hastings (original RFC 2911 editor), Robert Herriot,
Scott A. Isaacson, Kirk Ocke, Patrick Powell, and Peter Zehler
Appendix F. Change History
F.1. Changes In -11
The following changes are in draft-sweet-rfc2911bis-11:
o Restored the acknowledgements section to include authors from the
original RFC 2911 and 3382.
o Updated the vendor extension recommendations for keywords and
attributes to use SMI Enterprise Number prefixes, per ISTO-PWG IPP
workgroup decision on August 23, 2016.
F.2. Changes In -10
The following changes are in draft-sweet-rfc2910bis-10: The following changes are in draft-sweet-rfc2910bis-10:
o Abstract: Mention that this document obsoletes RFC 2910 and 3382, o Abstract: Mention that this document obsoletes RFC 2910 and 3382,
and reword for clarity. and reword for clarity.
o Editor's Note: Add parenthetical note to RFC editor to remove o Editor's Note: Add parenthetical note to RFC editor to remove
before publication. before publication.
o Acronyms: Drop external reference to PWG web site. o Acronyms: Drop external reference to PWG web site.
skipping to change at page 209, line 38 skipping to change at page 210, line 46
of-band attribute values which now require a specification. of-band attribute values which now require a specification.
Updated templates to reflect current requirements. IPP Designated Updated templates to reflect current requirements. IPP Designated
Expert(s) are the change controllers. Expert(s) are the change controllers.
o Appendix C.1: Reword section on substituting unsupported values to o Appendix C.1: Reword section on substituting unsupported values to
avoid confusion. avoid confusion.
o Moved RFC 3239 and 3997 references to the Informative References o Moved RFC 3239 and 3997 references to the Informative References
section. section.
E.2. Changes In -09 F.3. Changes In -09
The following changes are in draft-sweet-rfc2911bis-09: The following changes are in draft-sweet-rfc2911bis-09:
o Section 2.3.4: Mention imposition of input pages on impressions o Section 2.3.4: Mention imposition of input pages on impressions
during processing. during processing.
o Section 2.3.8: Mention roll media. o Section 2.3.8: Mention roll media.
o Section 4.1.4: Reworded for clarity. o Section 4.1.4: Reworded for clarity.
skipping to change at page 210, line 27 skipping to change at page 211, line 34
o Section 4.3.3.2: Moved Status Message after Natural Language and o Section 4.3.3.2: Moved Status Message after Natural Language and
Character Set. Character Set.
o Section 4.3.4.2: Moved Status Message after Natural Language and o Section 4.3.4.2: Moved Status Message after Natural Language and
Character Set. Character Set.
o Section 5.1: Moved out-of-band syntaxes to their own sub-section. o Section 5.1: Moved out-of-band syntaxes to their own sub-section.
o Section 5.2.6: Origin of media sheet is the top left corner. o Section 5.2.6: Origin of media sheet is the top left corner.
E.3. Changes In -08 F.4. Changes In -08
The following changes are in draft-sweet-rfc2911bis-08: The following changes are in draft-sweet-rfc2911bis-08:
o Section 2.3.3 (End User): Capitalize defined terms. o Section 2.3.3 (End User): Capitalize defined terms.
o Section 2.3.11 (Supports): Add a final paragraph on naming o Section 2.3.11 (Supports): Add a final paragraph on naming
conventions for xxx-supported, xxx-default, and xxx-configured. conventions for xxx-supported, xxx-default, and xxx-configured.
o Section 4.1.3 (Attributes): Updated last paragraph to use o Section 4.1.3 (Attributes): Updated last paragraph to use
normative language (IPP object MUST return an error) normative language (IPP object MUST return an error)
o Section 4.2.1.2: (Print-Job Response): Reword reference to job- o Section 4.2.1.2: (Print-Job Response): Reword reference to job-
state-reasons attribute. state-reasons attribute.
o Section 5.4.12 (printer-state-reasons): Added RFC 3805 property o Section 5.4.12 (printer-state-reasons): Added RFC 3805 property
values that correspond to each reason, sorted list. values that correspond to each reason, sorted list.
o Section 11.1 (Normative References): Fixed title of RFC 7612 o Section 11.1 (Normative References): Fixed title of RFC 7612
reference. reference.
E.4. Changes In -07 F.5. Changes In -07
The following changes are in draft-sweet-rfc2911bis-07: The following changes are in draft-sweet-rfc2911bis-07:
o Global: Normalize "end-user" as "End User" (defined term). o Global: Normalize "end-user" as "End User" (defined term).
o Global: Fix capitalization of "xxx-from-operator" and "xxx-by- o Global: Fix capitalization of "xxx-from-operator" and "xxx-by-
operator". operator".
o Global: Drop "system" in front of "Administrator". o Global: Drop "system" in front of "Administrator".
skipping to change at page 211, line 33 skipping to change at page 212, line 42
o Section 9.1: Drop "considered" from "are considered illustrative" o Section 9.1: Drop "considered" from "are considered illustrative"
(they are). (they are).
o Appendix B: Point to IIG 2.0 for how to display status messages. o Appendix B: Point to IIG 2.0 for how to display status messages.
o Appendix D: Add references to LDAP schema and IPP Everywhere. o Appendix D: Add references to LDAP schema and IPP Everywhere.
o o
E.5. Changes In -06 F.6. Changes In -06
The following changes are in draft-sweet-rfc2911bis-06: The following changes are in draft-sweet-rfc2911bis-06:
o Global: Changed "malformed" to "malformed". o Global: Changed "malformed" to "malformed".
o Global: Make sure all operations are marked OPTIONAL, RECOMMENDED, o Global: Make sure all operations are marked OPTIONAL, RECOMMENDED,
or REQUIRED. or REQUIRED.
o Global: Fix spelling: "attribure" to "attribute". o Global: Fix spelling: "attribure" to "attribute".
skipping to change at page 214, line 31 skipping to change at page 215, line 41
o Appendix B.1.3: "in this document" (not in IPP/1.1). o Appendix B.1.3: "in this document" (not in IPP/1.1).
o Appendix C: Deleted this appendix in its entirety since PWG 5101.1 o Appendix C: Deleted this appendix in its entirety since PWG 5101.1
supersedes it and is already referenced. supersedes it and is already referenced.
o Appendix D.3: Rewording, fix typos. o Appendix D.3: Rewording, fix typos.
o Table 22: Fix (missing cells) o Table 22: Fix (missing cells)
E.6. Changes In -05 F.7. Changes In -05
The following changes are in draft-sweet-rfc2911bis-05: The following changes are in draft-sweet-rfc2911bis-05:
o Global: Drop use of "OPTIONALLY", use MAY instead. o Global: Drop use of "OPTIONALLY", use MAY instead.
o Global: Printers SHOULD return unsupported attributes. o Global: Printers SHOULD return unsupported attributes.
o Global: Update use of "need only" to less awkward wording. o Global: Update use of "need only" to less awkward wording.
o Global: Reword all usage of "NOT REQUIRED". o Global: Reword all usage of "NOT REQUIRED".
skipping to change at page 216, line 29 skipping to change at page 217, line 39
o Section B.*: Drop conformance, move the rest to the beginning. o Section B.*: Drop conformance, move the rest to the beginning.
o Added references to the IPP Implementor's Guide 2.0, PWG 5101.1 o Added references to the IPP Implementor's Guide 2.0, PWG 5101.1
(MSN2), IPP 2.0, and IPP Everywhere. (MSN2), IPP 2.0, and IPP Everywhere.
o Updated PWG 5100.12 reference to current stable draft in formal o Updated PWG 5100.12 reference to current stable draft in formal
vote (for full IEEE standard). vote (for full IEEE standard).
o Various editorial corrections. o Various editorial corrections.
E.7. Changes In -04 F.8. Changes In -04
The following changes are in draft-sweet-rfc2911bis-04: The following changes are in draft-sweet-rfc2911bis-04:
o Removed restart and purge from the abstract. o Removed restart and purge from the abstract.
o Eliminated use of confusing ISO "NEED NOT" conformance o Eliminated use of confusing ISO "NEED NOT" conformance
terminology. terminology.
o Added DEPRECATED terminology. o Added DEPRECATED terminology.
o Marked Purge-Jobs and Restart-Job as DEPRECATED. o Marked Purge-Jobs and Restart-Job as DEPRECATED.
o Added reference to PWG 5100.11 (JPS2) for the Resubmit-Job o Added reference to PWG 5100.11 (JPS2) for the Resubmit-Job
operation (safe replacement for Restart-Job) operation (safe replacement for Restart-Job)
E.8. Changes In -03 F.9. Changes In -03
The following changes are in draft-sweet-rfc2911bis-03: The following changes are in draft-sweet-rfc2911bis-03:
o Submission type is now IETF (AD-sponsored), clarify goals. o Submission type is now IETF (AD-sponsored), clarify goals.
o Also obsolete RFC 3381 per PWG IPP WG o Also obsolete RFC 3381 per PWG IPP WG
o References to RFC 2617 are updated to the updated drafts in the o References to RFC 2617 are updated to the updated drafts in the
RFC editor's queue RFC editor's queue
o Section 4.1.5: Clarify note at end of section. o Section 4.1.5: Clarify note at end of section.
o Section 4.1.8: Clarify conformance requirements are for IPP/1.1 o Section 4.1.8: Clarify conformance requirements are for IPP/1.1
implementations. implementations.
o Section 5.4.3: Drop 'ssl3' value, fix examples. o Section 5.4.3: Drop 'ssl3' value, fix examples.
o Section 6.2.4: Reword "understand" -> "decode and process" o Section 6.2.4: Reword "understand" -> "decode and process"
o References: Drop SSL reference. o References: Drop SSL reference.
o Global: Don't use SSL3 in examples, use TLS o Global: Don't use SSL3 in examples, use TLS
o Global: Client, Printer, and Job are defined terms, capitalize o Global: Client, Printer, and Job are defined terms, capitalize
o Global: Fix lots of uses of "may" (conformance term) o Global: Fix lots of uses of "may" (conformance term)
E.9. Changes In -02 F.10. Changes In -02
The following changes are in draft-sweet-rfc2911bis-02: The following changes are in draft-sweet-rfc2911bis-02:
o Section 1: Dropped RFC 3381 reference since we are obsoleting it. o Section 1: Dropped RFC 3381 reference since we are obsoleting it.
o Section 4.1.5: Added reference to IPP and IPPS URI scheme RFCs. o Section 4.1.5: Added reference to IPP and IPPS URI scheme RFCs.
o Section 4.1.8: Added references to RFC 3510 and 7472 which define o Section 4.1.8: Added references to RFC 3510 and 7472 which define
the IPP and IPPS URI schemes and port number. the IPP and IPPS URI schemes and port number.
o Added section listing major changes since RFC 2911. o Added section listing major changes since RFC 2911.
o Fix all "it is recommended" passive voice conformance o Fix all "it is recommended" passive voice conformance
requirements. requirements.
E.10. Changes In -01 F.11. Changes In -01
The following changes are in draft-sweet-rfc2911bis-01: The following changes are in draft-sweet-rfc2911bis-01:
o Errata ID 364: Fix range of "redirection" status codes (to 0x03xx) o Errata ID 364: Fix range of "redirection" status codes (to 0x03xx)
o Errata ID 694: Fix range of vendor status codes (0x0n80 to 0x0nff) o Errata ID 694: Fix range of vendor status codes (0x0n80 to 0x0nff)
o Errata ID 3072: Reword multiple-document-handling definition since o Errata ID 3072: Reword multiple-document-handling definition since
it also applies to single document Jobs and is the only it also applies to single document Jobs and is the only
interoperable way to request uncollated copies. interoperable way to request uncollated copies.
 End of changes. 49 change blocks. 
97 lines changed or deleted 140 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/