Minutes of IPP Working Group Meeting March 7, 2001 1. Meeting Attendees Lee Farrell Canon Information Systems Don Wright Lexmark Mabry Dozier Minolta QMS Gail Songer Netreon Hugo Parra Novell Charles Kong Panasonic 2. Internet Printing Project (IPP) Don Wright led the IPP meeting and provided the suggested agenda topics: - Status of documents not otherwise on the agenda - Final voting process to become PWG standards - Issues from the October 17-20 bake-off in Boston - IPP Printer Installation Extension - The 'ipp', 'indp', and 'ippget' URL schemes - Have the IPP documents met the IPP Goals? - Registering Print Document Formats as MIME media types - PWG Media Size Name project 3. Status of Documents Not Otherwise on the Agenda Don noted that Carl-Uno has published a document that gives the current status for the IPP documents. The group suggested that this information should be placed-and maintained-on the IPP website. 4. Final Voting Process to Become PWG Standards IPP Production Printing Attributes - Set1 has been approved as a PWG Draft Standard. It has been published as IEEE-ISTO 5100.3 5. Issues from the October 17-20 bake-off in Boston Although this item was included in Tom Hastings' suggestions for agenda topics, the January Minutes indicate that this issue was addressed-and resolved: Bill Wagner noted that this issue revolves around the interpretation of allowable HTTP behavior-and perhaps should be out of scope for the IPP WG. Since the group has already resolved that sending a zero-length POST is invalid, he believes that the interoperability issue should be closed. After further discussion of Bill's observation, the group agreed to be silent about HTTP interpretation. Instead, it was suggested that a comment in the Implementer's Guide should be added to clarify the possible different behaviors that could be expected. ACTION: Pete Zehler and Tom Hastings will update the Implementer's Guide to reflect the possible concerns related to Issue 3.2 of the Bakeoff. It was noted that a Validate Job command will successfully generate a challenge-regardless of how the HTTP security might be implemented. No one at the meeting was aware of why this issue still needs discussion. The group's understanding of the conclusion is that the client must be able to accept and respond to a challenge at any time. 6. IPP Printer Installation Extension Hugo Parra led a review of the changes in the latest draft of the IPP Printer Installation Extension document. He noted that a major addition to the document includes a security measure-via digital signatures-to reduce the risk of installing dangerous files. Don Wright captured several editorial changes that were suggested. During the review, it was noted that it might be appropriate to include a comment on the trademarks of CPU names referenced in the value set for 'cpu-type.' How does IANA deal with this kind of issue? Hugo referenced an e-mail thread from Tom Hastings and Ira McDonald regarding the issue of the relationship between this document and the IPP/1.1 attribute called printer-driver- installer. The group believes that there is no relationship and we should be silent on the issue. The group agrees that the document is now ready for Last Call. 7. 'ipp' URL Scheme Don led a review of the changes in the ipp url-scheme document. He captured a few editorial changes that were suggested. He will forward the document with embedded comments to Tom. While examining the text in section 4.5.1, Don questioned the following text: If a proxy receives a host name which is not a fully qualified domain name, it MAY add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy MUST NOT change the host name. It was suggested that Section 5.1 c) should include an example. 8. 'indp' Method The latest modifications of the indp method document were reviewed. Don captured a few editorial changes that were suggested. He will forward the document with embedded comments to Tom. It was suggested that section 5.2.1 should call out a reference to Section 12. In Section 9.1.2, it was suggested that the following text be added: The Printer MAY remove subscriptions for future events which this client was unable to consume. Section 11.1, item 7 should include an explanation why. 9. 'ippget' Method The latest modifications of the ippget document were reviewed. Don captured a few editorial changes that were suggested. He will forward the document with embedded comments to Tom. Section 5.2, Table 2 - Why was the "*" added to the MUST entry for printer-current-time? Why not a double asterisk added to notify-user-data and a triple asterisk added to the others below that? Section 11.2, item 4 - Why? 10. Registering Print Document Formats as MIME Media Types Don led a review of Tom Hastings' document of Print Document formats proposed for MIME type registration. Most of the Issues could not be resolved by the attendees. Don suggested that XHTML-Basic did not need a MIME registration, but could be added to the Printer MIB. 11. PWG Media Size Name Project The group reviewed Tom Hastings' e-mail suggesting that the string "-envelope" should be removed from all self-describing names. There is concern that doing so would eliminate the possibility of a program being able to parse the Self Describing Name to generate a Common Name for presentation to a user. Is this a goal? If it is, then this proposal seems to be inadequate. Without a better understanding of the intended goals of the document, the group did not feel that they could reach consensus. The topic was deferred to further discussion on the PWG/UPnP mailing lists. It was suggested that if the "-envelope" is removed and a list of media types is created, this list should be included in the same document. This topic was also deferred. The group agreed to eliminate the IANA section and keep the Internationalization Section. 12. Have the IPP Documents Met the IPP Goals? The group referenced the IPP WG Charter and Design Goals in an attempt to evaluate whether the IPP Goals have been met. A few were not, and were highlighted by Don. While reviewing Tom's March 6 e-mail on "Input for Discussion in PWG [Does IPP meet its goals doc?]," Don captured several comments regarding whether things were not accomplished and/or were out of scope. These will be forwarded to Tom for subsequent review. It was suggested that the printer-more-information uri could be used for telephone number, help desk, etc. After reviewing the Goals document, the following deficiencies were identified: - cost per page - marking technology - location (programmatic determination) - PDL versions - given a set of valid job template attributes, , what are other valid attributes? - hooking payment transactions into IPP - attended versus unattended printers - document delivery - administrative limits (max spool size, pages per job, etc.) IPP meeting adjourned.