Ron Bergman <Ron.Bergman@rpsa.ricoh.com> - Ricoh
[to be determined]
Ira McDonald <imcdonald@sharplabs.com> - High North
Craig Whittle <cwhittle@sharplabs.com> - Sharp Labs America
PWG General Discussion: pwg@pwg.org
IPP WG General Discussion: ipp@pwg.org
To Subscribe: http://www.pwg.org/mailhelp.html
IPP WG Documents: ftp://ftp.pwg.org/pub/pwg/ipp
The first standards-track definition of the "printer-state-reasons" attribute of the IPP Printer object was published in IPP/1.1 (RFC 2911). Subsequent IETF and PWG IPP extensions have defined additional values for "printer-state-reasons". But the mapping of printer device and printer subunit alerts defined in the 'PrtAlertCodeTC' textual convention in IANA Printer MIB (originally published in RFC 3805) is very sparse.
When deploying printers in enterprise networks, customers often disable SNMPv1 (RFC 1157), based on local security policy - alternative secure SNMPv3 (RFC 3414) is not widely supported by current printers. In order to manage, provision, and service these network printers, there is a clear customer requirement to support secure queries for device alerts. IPP/1.1 (RFC 2911) can be securely deployed in enterprise networks, using TLS/1.0 (RFC 2246) and HTTP/1.1 Upgrade (RFC 2817), to fulfill this customer requirement.
O-1. The PWG Steering Committee (SC) has approved Sharp's request for development of a PWG Candidate Standard "IPP Printer State Reasons Extensions", in accordance with the PWG Process/2.0 (November 2004) and the PWG IPP Working Group Charter (March 2005).
O-2. This document should define new values for the IPP/1.1 (RFC 2911) "printer-state-reasons" attribute for every printer device and printer subunit alert defined in the 'PrtAlertCodeTC' textual convention in IANA Printer MIB (originally published in RFC 3805) - there is currently a very sparse mapping.
O-3. This document should define new values for the IPP/1.1 (RFC 2911) "printer-state-reasons" attribute for device/supply/media-input alerts for every finishing device defined in the 'FinDeviceTypeTC' textual convention in IANA Finisher MIB (originally published in RFC 3806) - there is currently no standard mapping.
O-4. This document should define an extension to the IPP/1.1 (RFC 2911) "printer-state-message" attribute for encoding any of the columnar objects defined in the 'prtAlertTable' in IETF Printer MIB v2 (RFC 3805) as substrings - there is currently no standard encoding.
C-1. DONE - 'Initial' working draft of IPP PSX Charter - 30 May 2006
C-2. DONE - 'Approved' IPP PSX Charter - 1 June 2006
D-1. Kickoff of PWG IPP PSX project at PWG face-to-face - 22 June 2006
D-2. 'Initial' working draft of PWG IPP PSX - 15 July 2006
D-3. 'Prototype' working draft of PWG IPP PSX - 15 September 2006
D-4. Prototyping report(s) on PWG IPP PSX - 15 December 2006
D-5. 'Stable' working draft of PWG IPP PSX - 15 January 2007
D-6. PWG Last Call of PWG IPP PSX - Ending 15 February 2007
D-7. PWG Formal Approval of PWG IPP PSX - Ending 31 March 2007
D-8. IANA registration of PWG IPP PSX updates - 15 April 2007
I-1. Interoperability Event for PWG IPP PSX - August 2007