idnits 2.17.1 draft-ietf-ipp-url-scheme-03.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: ---------------------------------------------------------------------------- ** 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 current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. 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. ** The abstract seems to contain references ([RFC-2732], [RFC-2616], [RFC-2910], [RFC-2911], [RFC-2717], [RFC-2373], [RFC-2396]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. ** 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 176: '...citly specify a port MUST be used over...' RFC 2119 keyword, line 185: '...quests and responses) MUST be conveyed...' RFC 2119 keyword, line 187: '... [IANA-MIMEREG]. IPP URLs MUST refer to IPP Printers which support...' RFC 2119 keyword, line 200: '... Codepoints outside [US-ASCII] MUST be hex escaped by the mechanism...' RFC 2119 keyword, line 220: '... Printer MUST return 'client-error-r...' (20 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in '[Target Category: Standards Track]', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 (2 April 2001) is 8425 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: 'RFC-2119' is mentioned on line 123, but not defined == Missing Reference: 'RFC-1900' is mentioned on line 510, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-MIMEREG' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-PORTREG' ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2373 (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 2717 (Obsoleted by RFC 4395) ** Obsolete normative reference: RFC 2732 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2910 (Obsoleted by RFC 8010) ** Obsolete normative reference: RFC 2911 (Obsoleted by RFC 8011) -- Possible downref: Non-RFC (?) normative reference: ref. 'US-ASCII' Summary: 15 errors (**), 0 flaws (~~), 6 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Printing Protocol Working Group Bob Herriot 3 INTERNET DRAFT Xerox Corporation 4 Expires 2 October 2001 Ira McDonald 5 High North Inc 6 [Target Category: Standards Track] 2 April 2001 8 Internet Printing Protocol (IPP): 9 IPP URL Scheme 10 12 Copyright (C) The Internet Society (2001). All Rights Reserved. 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 To view the list of Internet-Draft Shadow Directories, see 28 http://www.ietf.org/shadow.html. 30 Abstract 32 This document is intended for use in registering the "ipp" URL scheme 33 with IANA and fully conforms to the requirements in [RFC-2717]. This 34 document defines the "ipp" URL (Uniform Resource Locator) scheme for 35 specifying the location of an IPP Printer, IPP Job, or other IPP 36 object (defined in some future version of IPP) which implements the 37 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 38 [RFC-2910] or any later version of IPP. The intended usage of the 39 "ipp" URL scheme is COMMON. The IPP URL scheme defined in this 40 document is based on the ABNF for the HTTP URL scheme defined in 41 HTTP/1.1 [RFC-2616], which is derived from the URI Generic Syntax 42 [RFC-2396] and further updated by [RFC-2732] and [RFC-2373] (for IPv6 43 addresses in URLs). An IPP URL is transformed into an HTTP URL 44 according to the rules specified in section 5 of the IPP/1.1 Protocol 45 [RFC-2910]. 47 Table of Contents 49 1. Introduction ............................................... 3 50 2. Terminology ................................................ 4 51 2.1. Conformance Terminology ................................ 4 52 2.2. Model Terminology ...................................... 4 53 3. IPP Model for Printers and Jobs ............................ 5 54 4. IPP URL Scheme ............................................. 6 55 4.1. IPP URL Scheme Applicability and Intended Usage ........ 6 56 4.2. IPP URL Scheme Associated IPP Port ..................... 6 57 4.3. IPP URL Scheme Associated MIME Type .................... 6 58 4.4. IPP URL Scheme Character Encoding ...................... 6 59 4.5. IPP URL Scheme Syntax in ABNF .......................... 7 60 4.5.1. IPP URL Examples ................................... 8 61 4.5.2. IPP URL Comparisons ................................ 9 62 5. Conformance Requirements ................................... 10 63 5.1. Conformance Requirements for IPP Clients ............... 10 64 5.2. Conformance Requirements for IPP Printers .............. 10 65 6. IANA Considerations ........................................ 11 66 7. Internationalization Considerations ........................ 11 67 8. Security Considerations .................................... 11 68 9. References ................................................. 12 69 10. Acknowledgments ........................................... 12 70 11. Authors' Addresses ........................................ 13 71 12. Appendix X - Change History ............................... 13 72 13. Full Copyright Statement .................................. 15 73 1. Introduction 75 See section 1 'Introduction' in [RFC-2911] for a full description of 76 the IPP document set and overview information about IPP. 78 This document is intended for use in registering the "ipp" URL scheme 79 with IANA and fully conforms to the requirements in [RFC-2717]. This 80 document defines the "ipp" URL (Uniform Resource Locator) scheme for 81 specifying the location of an IPP Printer, IPP Job, or other IPP 82 object (defined in some future version of IPP) which implements the 83 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 84 [RFC-2910] or any later version of IPP. The intended usage of the 85 "ipp" URL scheme is COMMON. 87 This document defines: 88 - IPP URL scheme applicability and intended usage; 89 - IPP URL scheme associated port (i.e., well-known port 631); 90 - IPP URL scheme associated MIME type (i.e., "application/ipp"); 91 - IPP URL scheme syntax in ABNF [RFC-2234]; 92 - IPP URL scheme character encoding; 93 - IPP URL scheme IANA, internationalization, and security 94 considerations. 96 This document is laid out as follows: 97 - Section 2 is the terminology used throughout the document. 99 - Section 3 provides references to the IPP Printer and IPP Job object 100 model. 102 - Section 4 specifies IPP URL scheme. 104 - Section 5 specifies the conformance requirements for IPP Clients 105 and IPP Printers that claim conformance to this document. 107 - Section 6, 7, and 8 specify IANA, internationalization, and 108 security considerations. 110 - Sections 9, 10, 11, 12, and 13 list references, acknowledgements, 111 authors' addresses, change history, and full IETF copyright 112 statement. 114 2. Terminology 116 This specification document uses the terminology defined in this 117 section. 119 2.1. Conformance Terminology 121 The uppercase terms "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 122 NOT" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 123 this document are to be interpreted as described in [RFC-2119]. 124 These terms are used to specify conformance requirements for all 125 implementations of this specification. 127 2.2. Model Terminology 129 See section 12.2 'Model Terminology' in [RFC-2911]. 131 3. IPP Model for Printers and Jobs 133 See section 2 'IPP Objects', section 2.1 'Printer Object', and 134 section 2.2 'Job Object' in [RFC-2911] for a full description of the 135 IPP object model and terminology. 137 In this document, "IPP Client" means the software (on some hardware 138 platform) that submits, monitors, and/or manages print jobs via 139 IPP/1.1 [RFC-2910] [RFC-2911], or any later version of IPP to a 140 spooler, gateway, or actual printing device. 142 In this document, "IPP Printer object" means the software (on some 143 hardware platform) that receives print jobs and/or printer/job 144 operations via IPP/1.1 [RFC-2910] [RFC-2911], or any later version of 145 IPP from an "IPP Client". 147 In this document, "IPP Printer" is a synonym for "IPP Printer 148 object". 150 In this document, "IPP Job object" means the set of attributes and 151 documents for one print job on an "IPP Printer". 153 In this document, "IPP Job" is a synonym for "IPP Job object". 155 In this document, "IPP URL" means a URL with the "ipp" scheme. 157 Note: In this document, "IPP URL" is a synonym for "ipp_URL" (in 158 section 4 'IPP URL Scheme' of this document) and "ipp-URL" (in 159 section 5 'IPP URL Scheme' of [RFC-2910]). 161 4. IPP URL Scheme 163 4.1. IPP URL Scheme Applicability and Intended Usage 165 This document is intended for use in registering the "ipp" URL scheme 166 with IANA and fully conforms to the requirements in [RFC-2717]. This 167 document defines the "ipp" URL (Uniform Resource Locator) scheme for 168 specifying the location of an IPP Printer, IPP Job, or other IPP 169 object (defined in some future version of IPP) which implements the 170 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 171 [RFC-2910] or any later version of IPP. The intended usage of the 172 "ipp" URL scheme is COMMON. 174 4.2. IPP URL Scheme Associated IPP Port 176 All IPP URLs which do NOT explicitly specify a port MUST be used over 177 IANA-assigned well-known port 631 for the IPP protocol described in 178 [RFC-2910]. 180 See: IANA Port Numbers Registry [IANA-PORTREG]. registration with 181 IANA. 183 4.3. IPP URL Scheme Associated MIME Type 185 All IPP protocol operations (requests and responses) MUST be conveyed 186 in an "application/ipp" MIME media type as registered in 187 [IANA-MIMEREG]. IPP URLs MUST refer to IPP Printers which support 188 this "application/ipp" MIME media type. 190 See: IANA MIME Media Types Registry [IANA-MIMEREG]. 192 4.4. IPP URL Scheme Character Encoding 194 The IPP URL scheme defined in this document is based on the ABNF for 195 the HTTP URL scheme defined in HTTP/1.1 [RFC-2616], which is derived 196 from the URI Generic Syntax [RFC-2396] and further updated by 197 [RFC-2732] and [RFC-2373] (for IPv6 addresses in URLs). The IPP URL 198 scheme is case-insensitive in the host name or host address part; 199 however the path part is case-sensitive, as in [RFC-2396]. 200 Codepoints outside [US-ASCII] MUST be hex escaped by the mechanism 201 specified in [RFC-2396]. 203 4.5. IPP URL Scheme Syntax in ABNF 205 Note: In this document, "IPP URL" is a synonym for "ipp_URL" (in 206 section 4 'IPP URL Scheme' of this document) and "ipp-URL" (in 207 section 5 'IPP URL Scheme' of [RFC-2910]). 209 This document is intended for use in registering the "ipp" URL scheme 210 with IANA and fully conforms to the requirements in [RFC-2717]. This 211 document defines the "ipp" URL (Uniform Resource Locator) scheme for 212 specifying the location of an IPP Printer, IPP Job, or other IPP 213 object (defined in some future version of IPP) which implements the 214 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 215 [RFC-2910] or any later version of IPP. The intended usage of the 216 "ipp" URL scheme is COMMON. 218 The IPP protocol places a limit of 1023 octets (NOT characters) on 219 the length of a URI (see section 4.1.5 'uri' in [RFC-2911]). An IPP 220 Printer MUST return 'client-error-request-value-too-long' (see 221 section 13.1.4.10 in [RFC-2911]) when a URI received in a request 222 (e.g., in the "printer-uri" attribute) is too long. 224 Note: IPP Printers ought to be cautious about depending on URI 225 lengths above 255 bytes, because some older client implementations 226 might not properly support these lengths. 228 IPP URLs MUST be represented in absolute form. Absolute URLs always 229 begin with a scheme name followed by a colon. For definitive 230 information on URL syntax and semantics, see "Uniform Resource 231 Identifiers (URI): Generic Syntax and Semantics" [RFC-2396]. This 232 specification adopts the definitions of "URI-reference", 233 "absoluteURI", "relativeURI", "port", "host","abs_path", "rel_path", 234 and "authority" from [RFC-2396], as updated by [RFC-2732] and 235 [RFC-2373] (for IPv6 addresses in URLs). 237 The IPP URL scheme syntax in ABNF is as follows: 239 ipp_URL = "ipp:" "//" host [ ":" port ] [ abs_path [ "?" query ]] 241 If the port is empty or not given, port 631 is assumed. The 242 semantics are that the identified resource (see section 5.1.2 of 243 [RFC-2616]) is located at the IPP Printer or IPP Job listening for 244 HTTP connections on that port of that host, and the Request-URI for 245 the identified resource is 'abs_path'. 247 If the 'abs_path' is not present in the URL, it MUST be given as "/" 248 when used as a Request-URI for a resource (see section 5.1.2 of 249 [RFC-2616]). 251 4.5.1. IPP URL Examples 253 The following are examples of valid IPP URLs for IPP Printers: 255 ipp://abc.com 256 ipp://abc.com/printer 257 ipp://abc.com/tiger 258 ipp://abc.com/printers/tiger 259 ipp://abc.com/printers/fox 260 ipp://abc.com/printers/tiger/bob 261 ipp://abc.com/printers/tiger/ira 262 ipp://printer.abc.com 263 ipp://printers.abc.com/tiger 264 ipp://printers.abc.com/tiger/bob 265 ipp://printers.abc.com/tiger/ira 267 Each of the above URLs are legitimate URLs for IPP Printers and each 268 references a logically different IPP Printer, even though some of the 269 IPP Printers may share the same hardware. The last part of the path 270 'bob' or 'ira' may represent two different hardware devices where 271 'tiger' represents some grouping of IPP Printers (e.g., a 272 load-balancing spooler) or the two names may represent separate human 273 recipients ('bob' and 'ira') on the same hardware device (e.g., a 274 printer supporting two job queues). In either case both 'bob' and 275 'ira' behave as different IPP Printers. 277 The following are examples of IPP URLs with (optional) ports and 278 paths: 280 ipp://abc.com 281 ipp://abc.com/~smith/printer 282 ipp://abc.com:631/~smith/printer 284 The first and second IPP URLs above MUST be resolved to port 631 285 (IANA assigned well-known port for IPP). The second and third IPP 286 URLs above are equivalent (see section 4.5.2 below). 288 The following literal IPv4 addresses: 290 192.9.5.5 ; IPv4 address in IPv4 style 291 186.7.8.9 ; IPv4 address in IPv4 style 293 are represented in the following example IPP URLs: 295 ipp://192.9.5.5/prt1 296 ipp://186.7.8.9/printers/tiger/bob 298 The following literal IPv6 addresses (conformant to [RFC-2373]): 300 ::192.9.5.5 ; IPv4 address in IPv6 style 301 ::FFFF:129.144.52.38 ; IPv4 address in IPv6 style 302 2010:836B:4179::836B:4179 ; IPv6 address per RFC 2373 304 are represented in the following example IPP URLs: 306 ipp://[::192.9.5.5]/prt1 307 ipp://[::FFFF:129.144.52.38]:631/printers/tiger 308 ipp://[2010:836B:4179::836B:4179]/printers/tiger/bob 310 4.5.2. IPP URL Comparisons 312 When comparing two IPP URLs to decide if they match or not, an IPP 313 Client MUST use the same rules as those defined for HTTP URI 314 comparisons in [RFC-2616], with the sole following exception: 316 - A port that is empty or not given MUST be treated as equivalent to 317 the well-known port for that IPP URL (port 631); 319 See: Section 3.2.3 'URI Comparison' in [RFC-2616]. 321 5. Conformance Requirements 323 5.1. Conformance Requirements for IPP Clients 325 IPP Clients that conform to this specification: 327 a) MUST send IPP URLs (e.g., in the "printer-uri" operation attribute 328 in 'Print-Job') that conform to the ABNF specified in section 4.5 329 of this document; 331 b) MUST send IPP operations via the port specified in the IPP URL (if 332 present) or otherwise via IANA assigned well-known port 631; 334 c) MUST convert IPP URLs to their corresponding HTTP URL forms 335 according to the rules in section 5 'IPP URL Scheme' in 336 [RFC-2910]; 338 d) SHOULD interoperate with IPP/1.0 Printers according to the rules 339 in section 9 'Interoperability with IPP/1.0 Implementations' and 340 section 9.2 'Security and URL Schemes' in [RFC-2910]. 342 5.2. Conformance Requirements for IPP Printers 344 IPP Printers that conform to this specification: 346 a) SHOULD reject received IPP URLs in "application/ipp" request 347 bodies (e.g., in the "printer-uri" attribute in a 'Print-Job' 348 request) that do not conform to the ABNF for IPP URLs specified in 349 section 4.5 of this document; 351 b) SHOULD return IPP URLs in "application/ipp" response bodies (e.g., 352 in the "job-uri" attribute in a 'Print-Job' response) that do 353 conform to the ABNF for IPP URLs specified in section 4.5 of this 354 document; 356 c) MUST listen for IPP operations on IANA-assigned well-known port 357 631, unless explicitly configured by system administrators or site 358 policies; 360 d) SHOULD NOT listen for IPP operations on any other port, unless 361 explicitly configured by system administrators or site policies; 363 e) SHOULD interoperate with IPP/1.0 Clients according to the rules in 364 section 9 'Interoperability with IPP/1.0 Implementations' and 365 section 9.2 'Security and URL Schemes' in [RFC-2910]. 367 6. IANA Considerations 369 This document is intended for use in registering the "ipp" URL scheme 370 with IANA and fully conforms to the requirements in [RFC-2717]. This 371 document defines the "ipp" URL (Uniform Resource Locator) scheme for 372 specifying the location of an IPP Printer, IPP Job, or other IPP 373 object (defined in some future version of IPP) which implements the 374 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 375 [RFC-2910] or any later version of IPP. The intended usage of the 376 "ipp" URL scheme is COMMON. 378 This IPP URL Scheme specification does not introduce any additional 379 IANA considerations, beyond those described in [RFC-2910] and 380 [RFC-2911]. 382 See: Section 6 'IANA Considerations' in [RFC-2910] 383 See: Section 6 'IANA Considerations' in [RFC-2911]. 385 7. Internationalization Considerations 387 This IPP URL Scheme specification does not introduce any additional 388 internationalization considerations, beyond those described in 389 [RFC-2910] and [RFC-2911]. 391 See: Section 7 'Internationalization Considerations' in [RFC-2910]. 392 See: Section 7 'Internationalization Considerations' in [RFC-2911]. 394 8. Security Considerations 396 This IPP URL Scheme specification does not introduce any additional 397 security considerations, beyond those described in [RFC-2910] and 398 [RFC-2911]. 400 See: Section 8 'Security Considerations' in [RFC-2910]. 401 See: Section 8 'Security Considerations' in [RFC-2911]. 403 9. References 405 See: Section 10 'References' in [RFC-2910]. 407 [IANA-MIMEREG] IANA MIME Media Types Registry. 408 ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/... 410 [IANA-PORTREG] IANA Port Numbers Registry. 411 ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers 413 [RFC-2234] D. Crocker, P. Overell. Augmented BNF for Syntax 414 Specifications: ABNF, RFC 2234, November 1997. 416 [RFC-2373] R. Hinden, S. Deering. IP Version 6 Addressing 417 Architecture, RFC 2373, July 1998. 419 [RFC-2396] T. Berners-Lee, R. Fielding, L. Masinter. Uniform 420 Resource Identifiers (URI): Generic Syntax, RFC 2396, August 1998. 422 [RFC-2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, 423 P. Leach, T. Berners-Lee. Hypertext Transfer Protocol -- HTTP/1.1, 424 RFC 2616, June 1999. 426 [RFC-2717] R. Petke, I. King. Registration Procedures for URL Scheme 427 Names, RFC 2717, November 1999. 429 [RFC-2732] R. Hinden,B. Carpenter, L. Masinter. Format for Literal 430 IPv6 Addresses in URL's, RFC 2732, December 1999. 432 [RFC-2910] R. Herriot, S. Butler, P. Moore, R. Turner, J. Wenn. 433 IPP/1.1 Encoding and Transport, RFC 2910, September 2000. 435 [RFC-2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell. 436 IPP/1.1 Model and Semantics, RFC 2911, September 2000. 438 [US-ASCII] Coded Character Set -- 7-bit American Standard Code for 439 Information Interchange, ANSI X3.4-1986. 441 10. Acknowledgments 443 This document is a product of the Internet Printing Protocol Working 444 Group of the Internet Engineering Task Force (IETF). 446 Thanks to Pat Fleming (IBM), Tom Hastings (Xerox), Harry Lewis (IBM), 447 Hugo Parra (Novell), Don Wright (Lexmark), and all the members of the 448 IETF IPP WG. 450 Section 5 'IPP URL Scheme' in IPP/1.1 Encoding and Transport 451 [RFC-2910] was the primary input to this IPP URL Scheme 452 specification. 454 11. Authors' Addresses 456 Robert Herriot 457 Xerox Corporation 458 3400 Hill View Ave, Building 1 459 Palo Alto, CA 94304 461 Phone: +1 650-813-7696 462 Fax: +1 650-813-6860 463 Email: robert.herriot@pahv.xerox.com 465 Ira McDonald 466 High North Inc 467 221 Ridge Ave 468 Grand Marais, MI 49839 470 Phone: +1 906-494-2434 471 Email: imcdonald@crt.xerox.com 472 Email: imcdonald@sharplabs.com 474 Usage questions and comments on this IPP URL Scheme should be sent to 475 the IETF IPP WG mailing list at 'ipp@pwg.org'. 477 12. Appendix X - Change History 479 [To be deleted before RFC publication] 481 2 April 2001 - draft-ietf-ipp-url-scheme-03.txt 482 - final edits after IETF IPP WG 'last call' comments; 483 - revised 'Abstract' and section 1 'Introduction' to remove 484 references to ISSUE's and request for comments to the 'ipp@pwg.org' 485 mailing list, in preparation for publication as an RFC; 486 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to delete all 487 references to HTTP proxy behavior (which IPP does NOT specify), per 488 request of Don Wright; 489 - revised section 4.5.1 'IPP URL Examples' to remove note 490 discouraging the use of literal IP addresses in URLs, to remove 491 dependency on Informational [RFC-1900]; 492 - revised section 4.5.2 'IPP URL Comparisons' to specify the use of 493 rules defined in section 3.2.3 'URI Comparison' in [RFC-2616], with 494 the sole exception that an empty port MUST be treated as equivalent 495 to the IPP well-known port 631, per request of Don Wright; 496 - revised section 9 'References' to delete all unused references; 497 - revised section 11 'Authors' Addresses' to add the address of the 498 IPP WG mailing list for usage questions and comments; 500 13 February 2001 - draft-ietf-ipp-url-scheme-02.txt 501 - revised section 3 'IPP Model for Printers and Jobs' and section 4.5 502 'IPP URL Scheme Syntax in ABNF' to add notes stating that "IPP URL" 503 (in this document) is a synonym for "ipp-URL" in [RFC-2910], per 504 request of Bob Herriot; 505 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to correct typo 506 that showed "http:" rather than "ipp:" in the one-line ABNF, per 507 request of Tom Hastings; 508 - revised section 4.5.1 'IPP URL Examples' to add a note discouraging 509 the use of literal IP addresses in URLs, per [RFC-2616] and 510 [RFC-1900]; 512 5 February 2001 - draft-ietf-ipp-url-scheme-01.txt 513 - revised section 4.1 'IPP URL Applicability and Intended Usage' to 514 clarify that a given IPP URL MAY identify an IPP Printer object or 515 an IPP Job object, per request of Tom Hastings; 516 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to define IPP 517 URLs consistently with section 3.2.2 'http URL' of HTTP/1.1 518 [RFC-2616], per request of Tom Hastings; 519 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to clarify that 520 IPP URLs may reference IPP Printer objects, IPP Job objects, or 521 (possibly other future) IPP objects, per request of Bob Herriot; 522 - added section 4.5.1 'IPP URL Examples' to supply meaningful 523 examples of IPP URLs with host names, IPv4 addresses, and IPv6 524 addresses, per request of Tom Hastings; 525 - added section 4.5.2 'IPP URL Comparisons' to define IPP URL 526 comparisons consistently with section 3.3 'URI Comparison' of 527 HTTP/1.1 [RFC-2616], per request of Tom Hastings; 528 - revised section 5.1 'Conformance Requirements for IPP Clients' to 529 clarify that an IPP Client MUST convert IPP URLs to their 530 corresponding HTTP URL forms according to section 5 'IPP URL 531 Scheme' in [RFC-2910], per request of Tom Hastings and Bob Herriot; 532 - revised section 5.1 'Conformance Requirements for IPP Clients' and 533 section 5.2 'Conformance Requirements for IPP Printers' to clarify 534 that IPP Clients and IPP Printers SHOULD interoperate with IPP/1.0 535 systems according to section 9 'Interoperability with IPP/1.0 536 Implementations' in [RFC-2910], per request of Carl Kugler; 537 - revised section 5.2 'Conformance Requirements for IPP Printers' to 538 clarify that an IPP Printer MUST listen on (IANA assigned 539 well-known) port 631, unless explicitly configured, per request of 540 Michael Sweet; 541 - revised section 5.2 'Conformance Requirements for IPP Printers' to 542 clarify that an IPP Printer SHOULD NOT listen on ports other than 543 (IANA assigned well-known) port 631, unless explicitly configured, 544 per request of Don Wright; 546 - revised section 6 'IANA Considerations' to clarify that the sole 547 purpose of the entire document is IANA registration of the "ipp" 548 URL scheme; 549 - deleted Appendix A 'Registration of IPP Port' as unnecessary (port 550 is already registered); 551 - deleted Appendix B 'Registration of MIME "application/ipp" as 552 unnecessary (MIME registry has recently caught up to RFC 2910); 554 11 January 2001 - draft-ietf-ipp-url-scheme-00.txt 555 - initial version - simple "ipp" URL scheme without parameters or 556 query part (consistent with existing and IPP/1.1 implementations); 557 - added Appendix A 'Registration of IPP Port' (placeholder) for 558 updated IANA registration of port 631 with references to IPP/1.1; 559 - added Appendix B 'Registration of MIME "application/ipp"' with 560 updated IANA registration for IPP MIME type with references to both 561 IPP/1.0 and IPP/1.1; 563 13. Full Copyright Statement 565 Copyright (C) The Internet Society (2001). All Rights Reserved. 567 This document and translations of it may be copied and furnished to 568 others, and derivative works that comment on or otherwise explain it 569 or assist in its implementation may be prepared, copied, published 570 and distributed, in whole or in part, without restriction of any 571 kind, provided that the above copyright notice and this paragraph are 572 included on all such copies and derivative works. However, this 573 document itself may not be modified in any way, such as by removing 574 the copyright notice or references to the Internet Society or other 575 Internet organizations, except as needed for the purpose of 576 developing Internet standards in which case the procedures for 577 copyrights defined in the Internet Standards process must be 578 followed, or as required to translate it into languages other than 579 English. 581 The limited permissions granted above are perpetual and will not be 582 revoked by the Internet Society or its successors or assigns. 584 This document and the information contained herein is provided on an 585 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 586 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 587 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 588 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 589 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.