From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Tue May 30 2006 - 16:27:57 EDT
NOTE: Sharp requests that the PWG Steering Committee review this
project proposal at the next PWG SC meeting on Thursday 1 June 2006.
Hi, Tuesday (30 May 2006)
Sharp proposes development of a new PWG Candidate Standard "IPP Printer
State Reasons Extensions", to complete the current very sparse mapping
of printer device/subunit alerts in 'PrtAlertCodeTC' (RFC 3805) to
values of the "printer-state-reasons" attribute defined in IPP/1.1 (RFC
2911).
A draft charter for this project has been posted at:
ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippstate-charter-20060530.htm
The problem statement is extracted and appended below.
Thanks,
- Craig Whittle & Ira McDonald
------------------------------
PROBLEM STATEMENT
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.
------------------------------
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.7.4/351 - Release Date: 5/29/2006
This archive was generated by hypermail 2.1.4 : Tue May 30 2006 - 16:28:09 EDT