idnits 2.17.1 draft-ietf-ipp-url-scheme-01.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-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 181: '...citly specify a port MUST be used over...' RFC 2119 keyword, line 190: '...quests and responses) MUST be conveyed...' RFC 2119 keyword, line 192: '... [IANA-MIMEREG]. IPP URLs MUST refer to IPP Printers which support...' RFC 2119 keyword, line 205: '... Codepoints outside [US-ASCII] MUST be hex escaped by the mechanism...' RFC 2119 keyword, line 221: '... implementation MUST be able to handl...' (24 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 (5 February 2001) is 8475 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 134, but not defined == Unused Reference: 'IANA-CHARREG' is defined on line 419, but no explicit reference was found in the text == Unused Reference: 'NET-SSL3' is defined on line 428, but no explicit reference was found in the text == Unused Reference: 'RFC-1759' is defined on line 431, but no explicit reference was found in the text == Unused Reference: 'RFC-2046' is defined on line 437, but no explicit reference was found in the text == Unused Reference: 'RFC-2048' is defined on line 440, but no explicit reference was found in the text == Unused Reference: 'RFC-2246' is defined on line 452, but no explicit reference was found in the text == Unused Reference: 'RFC-2277' is defined on line 455, but no explicit reference was found in the text == Unused Reference: 'RFC-2279' is defined on line 458, but no explicit reference was found in the text == Unused Reference: 'RFC-2565' is defined on line 461, but no explicit reference was found in the text == Unused Reference: 'RFC-2566' is defined on line 464, but no explicit reference was found in the text == Unused Reference: 'RFC-2579' is defined on line 467, but no explicit reference was found in the text == Unused Reference: 'RFC-2617' is defined on line 474, but no explicit reference was found in the text == Unused Reference: 'RFC-2718' is defined on line 481, but no explicit reference was found in the text == Unused Reference: 'RFC-2978' is defined on line 493, but no explicit reference was found in the text == Unused Reference: 'RFC-3066' is defined on line 496, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-CHARREG' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-MIMEREG' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-PORTREG' -- Possible downref: Non-RFC (?) normative reference: ref. 'NET-SSL3' ** Obsolete normative reference: RFC 1759 (Obsoleted by RFC 3805) ** Downref: Normative reference to an Informational RFC: RFC 1900 ** Obsolete normative reference: RFC 2048 (Obsoleted by RFC 4288, RFC 4289) ** 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 2246 (Obsoleted by RFC 4346) ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 2565 (Obsoleted by RFC 2910) ** Obsolete normative reference: RFC 2566 (Obsoleted by RFC 2911) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) ** Obsolete normative reference: RFC 2717 (Obsoleted by RFC 4395) ** Obsolete normative reference: RFC 2718 (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) ** Obsolete normative reference: RFC 3066 (Obsoleted by RFC 4646, RFC 4647) -- Possible downref: Non-RFC (?) normative reference: ref. 'US-ASCII' Summary: 25 errors (**), 0 flaws (~~), 19 warnings (==), 7 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 5 August 2001 Ira McDonald 5 High North Inc 6 [Target Category: Standards Track] 5 February 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 a product of the Internet Printing Protocol Working 33 Group of the Internet Engineering Task Force (IETF). Comments should 34 be submitted to the ipp@pwg.org mailing list. 36 This document is intended for use in registering the "ipp" URL scheme 37 with IANA and fully conforms to the requirements in [RFC-2717]. This 38 document defines the "ipp" URL (Uniform Resource Locator) scheme for 39 specifying the location of an IPP Printer, IPP Job, or other IPP 40 object (defined in some future version of IPP) which implements the 41 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 42 [RFC-2910] or any later version of IPP. The intended usage of the 43 "ipp" URL scheme is COMMON. 45 The IPP URL scheme defined in this document is based on the ABNF for 46 the HTTP URL scheme defined in HTTP/1.1 [RFC-2616], which is derived 47 from the URI Generic Syntax [RFC-2396] and further updated by 48 [RFC-2732] and [RFC-2373] (for IPv6 addresses in URLs). An IPP URL 49 is transformed into an HTTP URL according to the rules specified in 50 section 5 of the IPP/1.1 Protocol [RFC-2910]. 52 Table of Contents 54 1. Introduction ............................................... 3 55 2. Terminology ................................................ 4 56 2.1. Conformance Terminology ................................ 4 57 2.2. Model Terminology ...................................... 4 58 3. IPP Model for Printers and Jobs ............................ 4 59 4. IPP URL Scheme ............................................. 5 60 4.1. IPP URL Scheme Applicability and Intended Usage ........ 5 61 4.2. IPP URL Scheme Associated IPP Port ..................... 5 62 4.3. IPP URL Scheme Associated MIME Type .................... 5 63 4.4. IPP URL Scheme Character Encoding ...................... 5 64 4.5. IPP URL Scheme Syntax in ABNF .......................... 6 65 4.5.1. IPP URL Examples ................................... 7 66 4.5.2. IPP URL Comparisons ................................ 8 67 5. Conformance Requirements ................................... 9 68 5.1. Conformance Requirements for IPP Clients ............... 9 69 5.2. Conformance Requirements for IPP Printers .............. 9 70 6. IANA Considerations ........................................ 10 71 7. Internationalization Considerations ........................ 10 72 8. Security Considerations .................................... 10 73 9. References ................................................. 11 74 10. Acknowledgments ........................................... 12 75 11. Authors' Addresses ........................................ 13 76 12. Appendix X - Change History ............................... 13 77 13. Full Copyright Statement .................................. 14 78 1. Introduction 80 See section 1 'Introduction' in [RFC-2911] for a full description of 81 the IPP document set and overview information about IPP. 83 The open issues in this document each begin 'ISSUE_n:'. 85 This document is a product of the Internet Printing Protocol Working 86 Group of the Internet Engineering Task Force (IETF). Comments should 87 be submitted to the ipp@pwg.org mailing list. 89 This document is intended for use in registering the "ipp" URL scheme 90 with IANA and fully conforms to the requirements in [RFC-2717]. This 91 document defines the "ipp" URL (Uniform Resource Locator) scheme for 92 specifying the location of an IPP Printer, IPP Job, or other IPP 93 object (defined in some future version of IPP) which implements the 94 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 95 [RFC-2910] or any later version of IPP. The intended usage of the 96 "ipp" URL scheme is COMMON. 98 This document defines: 99 - IPP URL scheme applicability and intended usage; 100 - IPP URL scheme associated port (i.e., well-known port 631); 101 - IPP URL scheme associated MIME type (i.e., "application/ipp"); 102 - IPP URL scheme syntax in ABNF [RFC-2234]; 103 - IPP URL scheme character encoding; 104 - IPP URL scheme IANA, internationalization, and security 105 considerations. 107 This document is laid out as follows: 108 - Section 2 is the terminology used throughout the document. 110 - Section 3 provides references to the IPP Printer and IPP Job object 111 model. 113 - Section 4 specifies IPP URL scheme. 115 - Section 5 specifies the conformance requirements for IPP Clients 116 and IPP Printers that claim conformance to this document. 118 - Section 6, 7, and 8 specify IANA, internationalization, and 119 security considerations. 121 - Sections 9, 10, 11, 12, and 13 list references, acknowledgements, 122 authors' addresses, change history, and full IETF copyright 123 statement. 125 2. Terminology 127 This specification document uses the terminology defined in this 128 section. 130 2.1. Conformance Terminology 132 The uppercase terms "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 133 NOT" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 134 this document are to be interpreted as described in [RFC-2119]. 135 These terms are used to specify conformance requirements for all 136 implementations of this specification. 138 2.2. Model Terminology 140 See section 12.2 'Model Terminology' in [RFC-2911]. 142 3. IPP Model for Printers and Jobs 144 See section 2 'IPP Objects', section 2.1 'Printer Object', and 145 section 2.2 'Job Object' in [RFC-2911] for a full description of the 146 IPP object model and terminology. 148 In this document, "IPP Client" means the software (on some hardware 149 platform) that submits, monitors, and/or manages print jobs via 150 IPP/1.1 [RFC-2910] [RFC-2911], or any later version of IPP to a 151 spooler, gateway, or actual printing device. 153 In this document, "IPP Printer object" means the software (on some 154 hardware platform) that receives print jobs and/or printer/job 155 operations via IPP/1.1 [RFC-2910] [RFC-2911], or any later version of 156 IPP from an "IPP Client". 158 In this document, "IPP Printer" is a synonym for "IPP Printer 159 object". 161 In this document, "IPP Job object" means the set of attributes and 162 documents for one print job on an "IPP Printer". 164 In this document, "IPP Job" is a synonym for "IPP Job object". 166 4. IPP URL Scheme 168 4.1. IPP URL Scheme Applicability and Intended Usage 170 This document is intended for use in registering the "ipp" URL scheme 171 with IANA and fully conforms to the requirements in [RFC-2717]. This 172 document defines the "ipp" URL (Uniform Resource Locator) scheme for 173 specifying the location of an IPP Printer, IPP Job, or other IPP 174 object (defined in some future version of IPP) which implements the 175 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 176 [RFC-2910] or any later version of IPP. The intended usage of the 177 "ipp" URL scheme is COMMON. 179 4.2. IPP URL Scheme Associated IPP Port 181 All IPP URLs which do NOT explicitly specify a port MUST be used over 182 IANA-assigned well-known port 631 for the IPP protocol described in 183 [RFC-2910]. 185 See: IANA Port Numbers Registry [IANA-PORTREG]. registration with 186 IANA. 188 4.3. IPP URL Scheme Associated MIME Type 190 All IPP protocol operations (requests and responses) MUST be conveyed 191 in an "application/ipp" MIME media type as registered in 192 [IANA-MIMEREG]. IPP URLs MUST refer to IPP Printers which support 193 this "application/ipp" MIME media type. 195 See: IANA MIME Media Types Registry [IANA-MIMEREG]. 197 4.4. IPP URL Scheme Character Encoding 199 The IPP URL scheme defined in this document is based on the ABNF for 200 the HTTP URL scheme defined in HTTP/1.1 [RFC-2616], which is derived 201 from the URI Generic Syntax [RFC-2396] and further updated by 202 [RFC-2732] and [RFC-2373] (for IPv6 addresses in URLs). The IPP URL 203 scheme is case-insensitive in the host name or host address part; 204 however the path part is case-sensitive, as in [RFC-2396]. 205 Codepoints outside [US-ASCII] MUST be hex escaped by the mechanism 206 specified in [RFC-2396]. 208 4.5. IPP URL Scheme Syntax in ABNF 210 This document is intended for use in registering the "ipp" URL scheme 211 with IANA and fully conforms to the requirements in [RFC-2717]. This 212 document defines the "ipp" URL (Uniform Resource Locator) scheme for 213 specifying the location of an IPP Printer, IPP Job, or other IPP 214 object (defined in some future version of IPP) which implements the 215 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 216 [RFC-2910] or any later version of IPP. The intended usage of the 217 "ipp" URL scheme is COMMON. 219 The IPP protocol places a limit 1023 octets (NOT characters) on the 220 length of a URI in section 4.1.5 'uri' in [RFC-2911]. An IPP Printer 221 implementation MUST be able to handle the URI of any resource that it 222 supports. An IPP Printer MUST return 223 'client-error-request-value-too-long' (see section 13.1.4.10 in 224 [RFC-2911]) when a URI received in a request (e.g., in the 225 "printer-uri" attribute) is too long. 227 Note: IPP Printers ought to be cautious about depending on URI 228 lengths above 255 bytes, because some older client or proxy 229 implementations might not properly support these lengths. 231 IPP URLs MUST be represented in absolute form. Absolute URLs always 232 begin with a scheme name followed by a colon. For definitive 233 information on URL syntax and semantics, see "Uniform Resource 234 Identifiers (URI): Generic Syntax and Semantics" [RFC-2396]. This 235 specification adopts the definitions of "URI-reference", 236 "absoluteURI", "relativeURI", "port", "host","abs_path", "rel_path", 237 and "authority" from [RFC-2396], as updated by [RFC-2732] and 238 [RFC-2373] (for IPv6 addresses in URLs). 240 The IPP URL scheme syntax in ABNF is as follows: 242 ipp_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]] 244 If the port is empty or not given, port 631 is assumed. The 245 semantics are that the identified resource (see section 5.1.2 of 246 [RFC-2616]) is located at the IPP Printer or IPP Job listening for 247 HTTP connections on that port of that host, and the Request-URI for 248 the identified resource is 'abs_path'. The use of IP addresses in 249 URLs SHOULD be avoided whenever possible (see [RFC-1900]). 251 If the 'abs_path' is not present in the URL, it MUST be given as "/" 252 when used as a Request-URI for a resource (see section 5.1.2 of 253 [RFC-2616]). If a proxy receives a host name which is not a fully 254 qualified domain name, it MAY add its domain to the host name it 255 received. If a proxy receives a fully qualified domain name, the 256 proxy MUST NOT change the host name. 258 4.5.1. IPP URL Examples 260 The following are examples of valid IPP URLs for IPP Printers: 262 ipp://abc.com 263 ipp://abc.com/printer 264 ipp://abc.com/tiger 265 ipp://abc.com/printers/tiger 266 ipp://abc.com/printers/fox 267 ipp://abc.com/printers/tiger/bob 268 ipp://abc.com/printers/tiger/ira 269 ipp://printer.abc.com 270 ipp://printers.abc.com/tiger 271 ipp://printers.abc.com/tiger/bob 272 ipp://printers.abc.com/tiger/ira 274 Each of the above URLs are legitimate URLs for IPP Printers and each 275 references a logically different IPP Printer, even though some of the 276 IPP Printers may share the same hardware. The last part of the path 277 'bob' or 'ira' may represent two different hardware devices where 278 'tiger' represents some grouping of IPP Printers (e.g., a 279 load-balancing spooler) or the two names may represent separate human 280 recipients ('bob' and 'ira') on the same hardware device (e.g., a 281 printer supporting two job queues). In either case both 'bob' and 282 'ira' behave as different IPP Printers. 284 The following are examples of IPP URLs with (optional) ports and 285 paths: 287 ipp://abc.com 288 ipp://abc.com/~smith/printer 289 ipp://abc.com:631/~smith/printer 291 The first and second IPP URLs above MUST be resolved to port 631 292 (IANA assigned well-known port for IPP). The second and third IPP 293 URLs above are equivalent (see section 4.5.2 below). 295 The following literal IPv6 addresses (conformant to [RFC-2373]): 297 ::192.9.5.5 ; IPv4 address in IPv6 style 298 ::FFFF:129.144.52.38 ; IPv4 address in IPv6 style 299 2010:836B:4179::836B:4179 ; IPv6 address per RFC 2373 301 are represented in the following example IPP URLs: 303 ipp://[::192.9.5.5]/prt1 304 ipp://[::FFFF:129.144.52.38]:631/printers/tiger 305 ipp://[2010:836B:4179::836B:4179]/printers/tiger/bob 307 4.5.2. IPP URL Comparisons 309 When comparing two IPP URLs to decide if they match or not, an IPP 310 Client SHOULD use a case-sensitive octet-by-octet comparison of the 311 entire URLs, with these exceptions: 313 - A port that is empty or not given is equivalent to the well-known 314 port for that IPP URL (port 631); 316 - Comparisons of host names MUST be case-insensitive; 318 - Comparisons of scheme names MUST be case-insensitive; 320 - An empty 'abs_path' is equivalent to an 'abs_path' of "/". 322 Characters other than those in the "reserved" and "unsafe" sets (see 323 [RFC-2396] and [RFC-2732]) are equivalent to their ""%" HEX HEX" 324 encoding. 326 For example, the following three URIs are equivalent: 328 ipp://abc.com:631/~smith/printer 329 ipp://ABC.com/%7Esmith/printer 330 ipp://ABC.com:/%7esmith/printer 332 5. Conformance Requirements 334 5.1. Conformance Requirements for IPP Clients 336 IPP Clients that conform to this specification: 338 a) MUST send IPP URLs (e.g., in the "printer-uri" operation attribute 339 in 'Print-Job') that conform to the ABNF specified in section 4.5 340 of this document; 342 b) MUST send IPP operations via the port specified in the IPP URL (if 343 present) or otherwise via IANA assigned well-known port 631; 345 c) MUST convert IPP URLs to their corresponding HTTP URL forms 346 according to the rules in section 5 'IPP URL Scheme' in 347 [RFC-2910]; 349 d) SHOULD interoperate with IPP/1.0 Printers according to the rules 350 in section 9 'Interoperability with IPP/1.0 Implementations' and 351 section 9.2 'Security and URL Schemes' in [RFC-2910]. 353 5.2. Conformance Requirements for IPP Printers 355 IPP Printers that conform to this specification: 357 a) SHOULD reject received IPP URLs in "application/ipp" request 358 bodies (e.g., in the "printer-uri" attribute in a 'Print-Job' 359 request) that do not conform to the ABNF for IPP URLs specified in 360 section 4.5 of this document; 362 b) SHOULD return IPP URLs in "application/ipp" response bodies (e.g., 363 in the "job-uri" attribute in a 'Print-Job' response) that do 364 conform to the ABNF for IPP URLs specified in section 4.5 of this 365 document; 367 c) MUST listen for IPP operations on IANA-assigned well-known port 368 631, unless explicitly configured by system administrators or site 369 policies; 371 d) SHOULD NOT listen for IPP operations on any other port, unless 372 explicitly configured by system administrators or site policies; 374 e) SHOULD interoperate with IPP/1.0 Clients according to the rules in 375 section 9 'Interoperability with IPP/1.0 Implementations' and 376 section 9.2 'Security and URL Schemes' in [RFC-2910]. 378 6. IANA Considerations 380 This document is intended for use in registering the "ipp" URL scheme 381 with IANA and fully conforms to the requirements in [RFC-2717]. This 382 document defines the "ipp" URL (Uniform Resource Locator) scheme for 383 specifying the location of an IPP Printer, IPP Job, or other IPP 384 object (defined in some future version of IPP) which implements the 385 IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP 386 [RFC-2910] or any later version of IPP. The intended usage of the 387 "ipp" URL scheme is COMMON. 389 This IPP URL Scheme specification does not introduce any additional 390 IANA considerations, beyond those described in [RFC-2910] and 391 [RFC-2911]. 393 See: Section 6 'IANA Considerations' in [RFC-2910] 394 See: Section 6 'IANA Considerations' in [RFC-2911]. 396 7. Internationalization Considerations 398 This IPP URL Scheme specification does not introduce any additional 399 internationalization considerations, beyond those described in 400 [RFC-2910] and [RFC-2911]. 402 See: Section 7 'Internationalization Considerations' in [RFC-2910]. 403 See: Section 7 'Internationalization Considerations' in [RFC-2911]. 405 8. Security Considerations 407 This IPP URL Scheme specification does not introduce any additional 408 security considerations, beyond those described in [RFC-2910] and 409 [RFC-2911]. 411 See: Section 8 'Security Considerations' in [RFC-2910]. 412 See: Section 8 'Security Considerations' in [RFC-2911]. 414 9. References 416 See: Section 10 'References' in [RFC-2910]. 417 See: Section 9 'References' in [RFC-2911]. 419 [IANA-CHARREG] IANA Charset Registry. 420 ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets 422 [IANA-MIMEREG] IANA MIME Media Types Registry. 423 ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/... 425 [IANA-PORTREG] IANA Port Numbers Registry. 426 ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers 428 [NET-SSL3] Netscape. The SSL Protocol, Version 3 (text version 429 3.02), November 1996. 431 [RFC-1759] R. Smith, F. Wright, T. Hastings, S. Zilles, 432 J. Gyllenskog. Printer MIB, RFC 1759, March 1995. 434 [RFC-1900] B. Carpenter, Y. Rekhter. Renumbering Needs Work, RFC 435 1900, February 1996. 437 [RFC-2046] N. Freed, N. Borenstein. MIME Part Two: Media Types, RFC 438 2046, November 1996. 440 [RFC-2048] N. Freed, J. Klensin, J. Postel. MIME Part 441 Four: Registration Procedures, RFC 2048, November 1996. 443 [RFC-2234] D. Crocker, P. Overell. Augmented BNF for Syntax 444 Specifications: ABNF, RFC 2234, November 1997. 446 [RFC-2373] R. Hinden, S. Deering. IP Version 6 Addressing 447 Architecture, RFC 2373, July 1998. 449 [RFC-2396] T. Berners-Lee, R. Fielding, L. Masinter. Uniform 450 Resource Identifiers (URI): Generic Syntax, RFC 2396, August 1998. 452 [RFC-2246] T. Dierks, C. Allen. The TLS Protocol Version, RFC 2246, 453 January 1999. 455 [RFC-2277] H. Alvestrand. IETF Policy on Character Sets and 456 Languages, RFC 2277, January 1998. 458 [RFC-2279] F. Yergeau. UTF-8, a Transformation Format of ISO 10646, 459 RFC 2279, January 1998. 461 [RFC-2565] R. Herriot, S. Butler, P. Moore, R. Turner. IPP/1.0 462 Encoding and Transport, RFC 2565, April 1999 (Experimental). 464 [RFC-2566] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell. 465 IPP/1.0 Model and Semantics, RFC 2566, April 1999 (Experimental). 467 [RFC-2579] K. McCloghrie, D. Perkins, J. Schoenwaelder. Textual 468 Conventions for SMIv2, RFC 2579, April 1999. 470 [RFC-2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, 471 P. Leach, T. Berners-Lee. Hypertext Transfer Protocol -- HTTP/1.1, 472 RFC 2616, June 1999. 474 [RFC-2617] J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, 475 P. Leach, A. Luotonen, L. Stewart. HTTP Authentication: Basic and 476 Digest Access Authentication, RFC 2617, June 1999. 478 [RFC-2717] R. Petke, I. King. Registration Procedures for URL Scheme 479 Names, RFC 2717, November 1999. 481 [RFC-2718] L. Masinter, H. Alvestrand, D. Zigmond, R. Petke. 482 Guidelines for new URL Scheme Names, RFC 2718, November 1999. 484 [RFC-2732] R. Hinden,B. Carpenter, L. Masinter. Format for Literal 485 IPv6 Addresses in URL's, RFC 2732, December 1999. 487 [RFC-2910] R. Herriot, S. Butler, P. Moore, R. Turner, J. Wenn. 488 IPP/1.1 Encoding and Transport, RFC 2910, September 2000. 490 [RFC-2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell. 491 IPP/1.1 Model and Semantics, RFC 2911, September 2000. 493 [RFC-2978] N. Freed, J. Postel. IANA Charset Registration 494 Procedures, RFC 2978, October 2000. 496 [RFC-3066] H. Alvestrand. Tags for the Identification of Languages, 497 RFC 3066, January 2001. 499 [US-ASCII] Coded Character Set -- 7-bit American Standard Code for 500 Information Interchange, ANSI X3.4-1986. 502 10. Acknowledgments 504 This document is a product of the Internet Printing Protocol Working 505 Group of the Internet Engineering Task Force (IETF). Comments should 506 be submitted to the ipp@pwg.org mailing list. 508 Thanks to Pat Fleming (IBM), Tom Hastings (Xerox), Harry Lewis (IBM), 509 and Hugo Parra (Novell). 511 Section 5 'IPP URL Scheme' in IPP/1.1 Encoding and Transport 513 [RFC-2910] was the primary input to this IPP URL Scheme 514 specification. 516 11. Authors' Addresses 518 Robert Herriot 519 Xerox Corporation 520 3400 Hill View Ave, Building 1 521 Palo Alto, CA 94304 523 Phone: +1 650-813-7696 524 Fax: +1 650-813-6860 525 Email: robert.herriot@pahv.xerox.com 527 Ira McDonald 528 High North Inc 529 221 Ridge Ave 530 Grand Marais, MI 49839 532 Phone: +1 906-494-2434 533 Email: imcdonald@crt.xerox.com 534 Email: imcdonald@sharplabs.com 536 12. Appendix X - Change History 538 [To be deleted before RFC publication] 540 5 February 2001 - draft-ietf-ipp-url-scheme-01.txt 541 - revised section 4.1 'IPP URL Applicability and Intended Usage' to 542 clarify that a given IPP URL MAY identify an IPP Printer object or 543 an IPP Job object, per request of Tom Hastings; 544 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to define IPP 545 URLs consistently with section 3.2.2 'http URL' of HTTP/1.1 546 [RFC-2616], per request of Tom Hastings; 547 - revised section 4.5 'IPP URL Scheme Syntax in ABNF' to clarify that 548 IPP URLs may reference IPP Printer objects, IPP Job objects, or 549 (possibly other future) IPP objects, per request of Bob Herriot; 550 - added section 4.5.1 'IPP URL Examples' to supply meaningful 551 examples of IPP URLs with host names, IPv4 addresses, and IPv6 552 addresses, per request of Tom Hastings; 553 - added section 4.5.2 'IPP URL Comparisons' to define IPP URL 554 comparisons consistently with section 3.3 'URI Comparison' of 555 HTTP/1.1 [RFC-2616], per request of Tom Hastings; 556 - revised section 5.1 'Conformance Requirements for IPP Clients' to 557 clarify that an IPP Client MUST convert IPP URLs to their 558 corresponding HTTP URL forms according to section 5 'IPP URL 559 Scheme' in [RFC-2910], per request of Tom Hastings and Bob Herriot; 560 - revised section 5.1 'Conformance Requirements for IPP Clients' and 561 section 5.2 'Conformance Requirements for IPP Printers' to clarify 562 that IPP Clients and IPP Printers SHOULD interoperate with IPP/1.0 563 systems according to section 9 'Interoperability with IPP/1.0 564 Implementations' in [RFC-2910], per request of Carl Kugler; 565 - revised section 5.2 'Conformance Requirements for IPP Printers' to 566 clarify that an IPP Printer MUST listen on (IANA assigned 567 well-known) port 631, unless explicitly configured, per request of 568 Michael Sweet; 569 - revised section 5.2 'Conformance Requirements for IPP Printers' to 570 clarify that an IPP Printer SHOULD NOT listen on ports other than 571 (IANA assigned well-known) port 631, unless explicitly configured, 572 per request of Don Wright; 573 - revised section 6 'IANA Considerations' to clarify that the sole 574 purpose of the entire document is IANA registration of the "ipp" 575 URL scheme; 576 - deleted Appendix A 'Registration of IPP Port' as unnecessary (port 577 is already registered); 578 - deleted Appendix B 'Registration of MIME "application/ipp" as 579 unnecessary (MIME registry has recently caught up to RFC 2910); 581 11 January 2001 - draft-ietf-ipp-url-scheme-00.txt 582 - initial version - simple 'ipp:' URL scheme without parameters or 583 query part (consistent with existing and IPP/1.1 implementations); 584 - added Appendix A 'Registration of IPP Port' (placeholder) for 585 updated IANA registration of port 631 with references to IPP/1.1; 586 - added Appendix B 'Registration of MIME "application/ipp"' with 587 updated IANA registration for IPP MIME type with references to both 588 IPP/1.0 and IPP/1.1; 590 13. Full Copyright Statement 592 Copyright (C) The Internet Society (2001). All Rights Reserved. 594 This document and translations of it may be copied and furnished to 595 others, and derivative works that comment on or otherwise explain it 596 or assist in its implementation may be prepared, copied, published 597 and distributed, in whole or in part, without restriction of any 598 kind, provided that the above copyright notice and this paragraph are 599 included on all such copies and derivative works. However, this 600 document itself may not be modified in any way, such as by removing 601 the copyright notice or references to the Internet Society or other 602 Internet organizations, except as needed for the purpose of 603 developing Internet standards in which case the procedures for 604 copyrights defined in the Internet Standards process must be 605 followed, or as required to translate it into languages other than 606 English. 608 The limited permissions granted above are perpetual and will not be 609 revoked by the Internet Society or its successors or assigns. 611 This document and the information contained herein is provided on an 612 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 613 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 614 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 615 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 616 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.