RFC 3510 (rfc3510) - Page 2 of 16


Internet Printing Protocol/1



Alternative Format: Original Text Document



RFC 3510                     IPP URL Scheme                   April 2003


   5.  Conformance Requirements ...................................  8
       5.1.  IPP Client Conformance Requirements ..................  8
       5.2.  IPP Printer Conformance Requirements .................  8
   6.  IANA Considerations ........................................  9
   7.  Internationalization Considerations ........................  9
   8.  Security Considerations ....................................  9
   9.  Intellectual Property Rights ............................... 10
   10. Normative References ....................................... 11
   11. Informative References ..................................... 11
   12. Acknowledgments ............................................ 12
   Appendix A - Registration of "ipp" URL Scheme .................. 13
   Authors' Addresses ............................................. 15
   Full Copyright Statement ....................................... 16

1.  Introduction

   This memo conforms to all of the requirements in Registration
   Procedures for URL Scheme Names [RFC 2717].  This memo also follows
   all of the recommendations in Guidelines for new URL Schemes
   [RFC 2718].

   See section 1, "Introduction", of [RFC 2911] and section 1,
   "Introduction", of [RFC 3196] for overview information about IPP.  See
   section 10, "Description of the Base IPP Documents", of [RFC 3196] for
   a full description of the IPP document set.

   This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by
   expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910,
   but does not define any new parameters or other new extensions to the
   syntax of IPP URLs.

   The IPP URL scheme defined in this document is based on the ABNF for
   the HTTP URL scheme defined in HTTP [RFC 2616], which in turn is
   derived from the URI Generic Syntax [RFC 2396] and further updated for
   IPv6 by [RFC 2732].  An IPP URL is transformed into an HTTP URL
   according to the rules specified in section 5 of IPP Protocol
   [RFC 2910].

   This document defines IPP URL scheme applicability, associated port
   (631), associated MIME type ("application/ipp"), character encoding,
   and syntax.

   This document is laid out as follows:

   -  Section 2 defines the terminology used throughout the document.

   -  Section 3 supplies references to the IPP Printer and IPP Job
      object model defined in IPP Model [RFC 2911].



Herriot & McDonald          Standards Track