NOTE: This charter is a snapshot of the 42nd IETF Meeting in Chicago, Illinois. It may now be out-of-date. Last Modified: 23-Jul-98
Carl-Uno Manros <firstname.lastname@example.org>
Applications Area Director(s):
Keith Moore <email@example.com>
Patrik Faltstrom <firstname.lastname@example.org>
Applications Area Advisor:
Keith Moore <email@example.com>
To Subscribe: firstname.lastname@example.org
Description of Working Group:
There is currently no universal standard for printing. Several protocols are in use, but each has limited applicability and none can be considered the prevalent one. This means that printer vendors have to implement and support a number of different protocols and protocol variants. There is a need to define a protocol which can cover the most common situations for printing on the Internet.
The goal of this working group is to develop requirements for Internet Printing and to describe a model and semantics for Internet Printing.
The further goal is to define a new application level Internet Printing Protocol for the following core functions:
- for a user to find out about a printer's capabilities - for a user to submit print jobs to a printer - for a user to find out the status of a printer or a print job - for a user to cancel a previously submitted job
The Internet Print Protocol is a client-server type protocol which should allow the server side to be either a separate print server or a printer with embedded networking capabilities. The focus of this effort is optimized for printers, but might be applied to other output devices. These are outside the scope of this working group.
The working group will also define a set of directory attributes that can be used to ease finding printers on the network.
The Internet Print Protocol will include mechanisms to ensure adequate security protection for materials to be printed, including at a minimum mechanisms for mutual authentication of client and server and mechanisms to protect the confidentiality of communications between client and server.
Finally, the IPP working group will produce recommendations for interoperation of LPR clients with IPP servers, and IPP clients with LPR servers. These recommendations will include instructions for both the translation of the LPR protocol onto IPP and the translation of the IPP protocol onto LPR. However, there is no expectation to provide new IPP features to LPR clients, nor is there an explicit requirement to translate LPR extensions to IPP, beyond those features available in the 4.2BSD UNIX implementation of LPR, and which are still useful today.
Other capabilities that will be examined for future versions include:
- security features for authentication, authorization, and policies - notifications from the server to the client - accounting
Subjects currently out of scope for this working group are:
- protection of intellectual property rights - fax input - scanning
The working group shall strive to coordinate its activities with other printing-related standards bodies, without the need to be strictly bound by their standards definitions. These groups are:
- ISO/IEC JTC 1/SC 18/WG 4 on Document Printing Application (ISO/IEC 10175 parts 1 - 3) - The Object Management Group (OMG) on OMG Printing Facility (in development) - IEEE (POSIX System Administration - Part 4: Printing Interfaces) - X/Open (Printing Systems Interoperabilty Specification) - The Printer Working Group
Goals and Milestones:
Submit Internet Printing Protoco/1.0: Model and Semantics as an Internet-Draft.
Submit Internet Printing Protoco/1.0: Protocol as an Internet-Draft.
Submit Internet Printing Protocol: Requirements and Scenarios as an Internet-Draft.
Submit Internet Printing Protoco/1.0: Directory Schema as an Internet-Draft.
Review of specification in IETF meeting in Memphis, TN, USA
Produce At least 2 implemented prototypes
Submit other Internet-Drafts to IESG for consideration as Proposed Standards.
Submit Internet Printing Protocol: Requirements and Scenarios I-D to IESG for publication as an Informational RFC.
No Request For Comments
Minutes from the IPP WG Meeting at IETF42 - August 26, 1998 - Chicago
The meeting was attended by 29 people.
Notes were taken by Scott Isaacson.
- Short history of the project (presentation by Carl-Uno Manros)
- Information about upcoming test event for IPP (presentation by Carl-Uno Manros)
- Security parameters in the ipp:// URL scheme (presentation and discussion led
by John Wenn)
- Similarities and differences between IPP and IFax (discussion led by
A short history and overview of the project was presented by the chair.
(see slides for further details)
11/97 - IPP drafts refined, 5 major documents
12/97 - IPP WG Last Call
1/98 - Edits to WG drafts
2/98 - Drafts submitted to IESG
5/98 - Comments from Area Director
8/98 - Still waiting for final feedback from IESG
The chair informed about an upcoming IPP test event on September 23-25. So far,
16 organizations have signed up for this inter-operability event. The testing will be
based on the current IPP drafts from June 30, 1998. See slides for further details.
The most important agenda point was a presentation by John Wenn on how to build
in a security parameter in the ipp:// scheme and mapping of that to the HTTP Upgrade
parameter. With the subsequent documentation of this solution, which has been
validated with the TLS and HTTP groups, it is believed that all known issues raised
by the IESG have been addressed by the IPP WG. It was pointed out during the
discussion of the solution that we need multiple values for security mechanisms used,
as e.g. TLS and Digest Authentication may both be used together. This will be fixed
in the next draft. There were no comments on the current draft
<draft-ietf-ipp-ipp-scheme-00.txt>. Also see slides for further details.
Larry Masinter led a discussion on interoperability between IPP and IFax. There
seemed to be sufficient interest in this subject to justify writing an informational
document that gives advice to implementors of IPP/Ifax gateways or implementation
of both protocols in the same system or device. One person offered to become the
editor of such a document. It is not planned to introduce this subject as an official part
of either the IPP or IFax WGs charter, but it is expected to be developed in collaboration
between these two groups. See slides for further details.
Meeting adjourned early.
IPP vs. IFax
go to list