Minutes of IPP Working Group Meeting September 13-14, 2000 1. Meeting Attendees Satoshi Matsushita Brother Shigeru Ueda Canon Lee Farrell Canon Information Systems Dan Calle Digital Paper Shinichi Tsuruyama Epson Atsushi Uchino Epson Michael Wu Heidelberg Digital Ron Bergman Hitachi-Koki Harry Lewis IBM Mark Vander Wiele IBM Stuart Rowley Kyocera Jerry Thrasher Lexmark Don Wright Lexmark Weihai Chen Microsoft Bill Wagner NETsilicon Hugo Parra Novell Roelof Hamberg Océ Paul Moore Peerless Gail Songer Peerless Satoshi Fujitani Ricoh Geoff Sorod Software 2000 Tom Hastings Xerox Bob Herriot Xerox Carl-Uno Manros (Chair) Xerox Peter Zehler Xerox 2. Day 1 Carl Uno-Manros opened the IPP meeting and provided the suggested agenda topics: - Preparations for the Bake-off - Driver Down-Load - Miscellaneous Attributes - Notification - Production Printing - Presentation Direction - Status Codes Clarification - Resource Object Specification - Device Administration Operations - PPML and PODi Relationship - IPP IETF Charter 2.1 Preparations for the Bake-off Pete Zehler referenced the IPP Bake Off 3 Testing Outline document: ftp://ftp.pwg.org/pub/pwg/ipp/new_TES/IPP-Test-Plan- 000831.pdf He described the [logical] configuration planned for the IPP Bake-off He announced that the Bake-off registration closes on Monday, September 18. Peter provided some estimates based on preliminary feedback. He expects the numbers to be finalized after the registration deadline: IPP clients 10-20 Client DHCP server 1 Client proxy/firewalls 2-5 Hubs, cables IPP servers 10-20 Server firewalls 2-5 Server DHCP server 1 FTP server 1 SMTP server ? He gave a list of the planned test topics: - Basic Connectivity/Print - Authentication and Security - Firewall Proxy - Model Coverage - Version Interoperability - Common Errors - Notify Methods and Delivery - Driver Download 2.2 Driver Down-Load Hugo Parra led a review of his Printer Installation Extension document: ftp://ftp.pwg.org/pub/pwg/ipp/new_DRV/draft-ietf-ipp- install-00-000713.pdf ISSUE 01: What strings should be used for CPU types in the examples? The group agreed to use IPP-specific keywords. Hugo will send out an e-mail with the initial list and request suggestions for additional CPU types. ISSUE 02: Should mention IANA's future support for CPU types? No. Because IPP-specific keywords will be used, this is not relevant. There was much discussion about how to standardize on a method to compare between drivers on a website and a local installation. Install date might not be the best approach. What about version number (or equivalent)? Will filenames remain consistent, or might they change with each installation/version update? How should we distinguish between the "latest" driver and the "currently recommended/sanctioned" driver? It was suggested that a keyword could be used to identify a location from which to retrieve the "currently recommended/sanctioned" driver. The following client-print-support-files-supported fields were added: - file size - policy - file-version - file-date-time The following client-print-support-files-request fields were added: - file-version - policy What elements of the proposal should support internationalization? It was agreed that client-print-support- files-supported should be a UTF-8 string instead of an ASCII string. Hugo will update the document and publish it for WG Last Call. 2.3 Miscellaneous Attributes Tom Hastings led a review of the latest draft of the Finishings Attribute Values Extension document: ftp://ftp.pwg.org/pub/pwg/ipp/proposed- registrations/attribute-values/ipp-finishings-fold-trim- bale-000608.pdf He identified the various new values that have been added to the document: - booklet-maker - jog-offset - bind-left - bind-top - bind-right - bind-bottom Tom will update the document and publish it for WG Last Call. There was some debate about whether the group should attempt to publish this document as an IETF Internet-Draft, or just publish it as a PWG specification. The consensus was for PWG publication— not IETF. 2.4 IPPGETW Bob Herriot led a review of the ippgetw Notification Delivery Method document: ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notify-get- 000907.doc The group agreed to rename the method "ippget." ISSUE: Should we say, "The Printer MUST discard an Event Notification after its lease expires" or leave unsaid how long an Event Notification lasts after the lease expires? No, the specification will be silent on this issue. There were several opinions regarding whether the Printer should suggest a time interval before the client performs the next Get Notifications. After a bit of discussion, the topic was deferred. Further discussion on the document was postponed until the next day. 2.5 Production Printing Carl-Uno referenced the JDF activity [www.job-definition- format.org] that has received much attention at the Seybold Conference. According to Carl-Uno, there is an ongoing attempt to get the JDF effort to adopt the IPP semantics. 2.6 Production Printing Attributes Tom Hastings led a review of the latest draft of the Production Printing Attributes document: ftp://ftp.pwg.org/pub/pwg/ipp/new_PPE/pwg-ipp-prod-print- set1-000605.pdf It was suggested that a "force new sheet" attribute should be added. A capability for defining "flush-left/right/top/bottom" was also suggested. It was agreed that "x-image-auto-center" and "y-image-auto- center" will be replaced by "x-image-position" (left/right/center) and "y-image-position" (top/bottom). "Job-recipient-name" and "media-weight-english" were removed from the document. It was suggested that the protocol include the specification of both input tray and media size. A "media-by-tray" attribute will be added. During the review, Tom noted various other minor modifications that were suggested and agreed. He will update the document and issue the next draft before a PWG Last Call. 3. Day 2 3.1 Exception Attributes Bob Herriot led a review of the latest draft of the Exception Attributes document: ftp://ftp.pwg.org/pub/pwg/ipp/new_EXC/pwg-ipp-exceptions- model-000508.pdf The group agreed to rename the document "Attribute Overrides for Documents and Pages." Bob will review the content and change the word "exception" to "override" as appropriate. Bob will update the document to reflect the agreed changes and issue the new draft before a PWG Last Call. 3.2 Job-recipient-name Tom Hastings reviewed his proposed write-up for the "job- recipient-name" Job Template attribute: ftp://ftp.pwg.org/pub/pwg/ipp/proposed- registrations/attributes/ipp-job-recipient-name-attr- 000907.doc The group agreed that the Printer: Default Value Attribute should be "none". "Job-recipient-name-supported" was changed from an integer to a Boolean, indicating if the attribute is supported or not. Tom will issue the updated document as an Internet-Draft and submit to the IETF. 3.3 IPPGET – cont'd Bob Herriot reviewed several additional changes that he had made to the ippget Notification Delivery Method document. He explained the "notify-no-wait" attribute and the two new status codes that had been included in the updated draft. The group accepted the modifications as written. Should this Notification Delivery Method be submitted to the IETF as a standards track document [in addition to indp and mailto]? Carl-Uno has concerns about submitting three different methods as "recommended." Many of the attendees feel that no single method is good for all situations, and each has different strengths. Paul Moore suggested that all three methods should be submitted as Experimental documents. A straw poll showed that more people feel that all three methods should be given the same status—whether it is recommended or experimental. Carl-Uno pointed out that both indp and mailto delivery methods have already been submitted for standards track. Bob will issue the updated document for WG Last Call. 3.4 Presentation Direction Bob explained two new [Job Template] attributes—"presentation- direction-requested" and "presentation-direction-number-up"—that he proposes for additional control. It was agreed that presentation-direction (as it applies to number-up) will be included in the updated Production Printing Attributes document. 3.5 Resource Object Specification Tom Hastings led a review of the latest draft of the Resource Object document: ftp://ftp.pwg.organization/pub/pwg/new_RES/draft-ietf-ipp- get-resource-01-000901.document There was a long discussion about whether the general method of using a Resource Object is necessary or sufficiently beneficial. It was suggested that the LDAP syntax could be used. The group concluded that attempting to define a Resource Object is overly complicated for the needs of IPP. Instead, it was suggested that Tom and Paul Moore attempt to develop an alternative proposal. Any further effort on this topic should initially be a PWG document—not an IETF document. 3.6 PPML and PODi Relationship? Don Wright announced that the PODi organization has requested an "overview document" on the IPP specification. IPP meeting adjourned.