Internet Printing Protocol: differenze tra le versioni
Contenuto cancellato Contenuto aggiunto
m →Implementation: urlmorto |
m date --> data |
||
Riga 6:
<!--
== History ==
IPP began as a proposal by [[Novell]] for the creation of an Internet printing [[Communications protocol|protocol]] project in 1996. The result was a draft written by Novell and [[Xerox]] called the Lightweight Document Printing Application (LDPA), derived from ECMA-140: [[Document Printing Application]] (DPA). At about the same time, [[Lexmark]] publicly proposed something called the [[HyperText]] Printing Protocol (HTPP), and both [[Hewlett-Packard|HP]] and [[Microsoft]] had started work on new print services for what became [[Windows 2000]]. Each of the companies chose to start a common Internet Printing Protocol project in the [[Printer Working Group]] (PWG) and negotiated an IPP birds-of-a-feather (BOF) session with the Application Area Directors in the [[Internet Engineering Task Force]] (IETF). The BOF session in December 1996(?) showed sufficient interest in developing a printing protocol, leading to the creation of the IETF Internet Printing Protocol (ipp)<ref>{{
IPP/1.0 was published as a series of experimental documents (RFC 2565,<ref>{{
Work on IPP continues in the PWG with the publication of 12 candidate standards providing extensions to IPP and definition of IPP/2.0, IPP/2.1, and now IPP/2.2 representing different categories or classes of printers. A new IPP Everywhere<ref>{{
== Implementation ==
IPP is implemented using the [[Hypertext Transfer Protocol]] (HTTP) and inherits all of the HTTP streaming and security features. For example, [[authorization]] can take place via HTTP's [[Digest access authentication]] mechanism, [[GSSAPI]], or via [[public key certificates]]. [[Encryption]] is provided using the [[Secure Sockets Layer|SSL]]/[[Transport Layer Security|TLS]] protocol-layer, either in the traditional always-on mode used by [[HTTPS]] or using the HTTP Upgrade extension to HTTP (RFC 2817<ref>{{
IPP uses the traditional client-server model, with clients sending IPP request messages with the [[MIME]] media type "application/ipp" in HTTP POST requests to an IPP printer. IPP request messages consist of key/value pairs using a custom binary encoding followed by an "end of attributes" tag and any document data required for the request. The IPP response is sent back to the client in the HTTP POST response, again using the "application/ipp" MIME media type.
Riga 26:
IPP uses [[Transmission Control Protocol|TCP]] with port 631 as its [[well-known port]]. IPP implementations such as [[CUPS]] also use [[User Datagram Protocol|UDP]] with port 631 for IPP printer discovery.
Products using the Internet Printing Protocol include, among others, [[CUPS]] which is part of [[Apple Inc.|Apple]] [[Mac OS X]] and many [[BSD]] and [[Linux]] distributions and is the reference implementation for IPP/2.0 and IPP/2.1,<ref>{{
|url=http://www.pwg.org/ipp/
|title=Internet Printing Protocol
Riga 36:
}} The language "CUPS Software (IPP Reference Implementation)" appeared on this page since a point
between 1 September 2009 and 12 January 2010, though no mention of a reference implementation
is found in the published standard.</ref> [[Novell]] [[iPrint]], and [[Microsoft Windows]], starting with [[Microsoft|MS]] [[Windows 2000]].<ref>{{
|url= http://www.microsoft.com/windowsserver2003/techinfo/overview/internetprint.mspx
|title=Effectively Using IPP Printing
|publisher=Microsoft
|
|accessdate=2009-09-06}}</ref> [[Windows XP]] and [[Windows Server 2003]] offer IPP printing via [[HTTPS]]. [[Windows Vista]], [[Windows 7]],<ref>{{
|url=http://support.microsoft.com/kb/2462380
|title=The Internet Printing Client (IPP) is not available in Windows 7 Starter Edition
|publisher=Microsoft
|
|accessdate=2012-10-02}}</ref> [[Windows Server 2008]] and [[Windows Server 2008 R2|2008 R2]] also support IPP printing over [[Remote procedure call|RPC]] in the "Medium-Low" [[security zone]].
== Standards ==
* {{
* {{
* {{
* {{
* {{
== See also ==
| |||