Hi folks, Tuesday (7 June 2005)
Below are design requirements for the PWG Imaging System Counters Spec:
(a) Add new section 1.3 'Design Requirements for Counters'
(b) In section 3 'Model Overview', rename current section 3.4 from
'Counter Overview' (vague) to 'PWG Structural Model for Counters'
(the other current sections are PWG Object Model Overview, Imaging
System Services, and PWG Object Model Extension for Counters).
(c) Add new section 3.5 'PWG Use Models for Counters', including
Service Providers - Monitoring and Billing, System Administrators -
Network Management, and Network Applications - Accounting.
(d) Add new references to sections 11 and 12
Note: All of the use models in section 3.5 produce design requirements
or recommendations that apply to Subunits (e.g., preventive maintenance)
or Jobs (user accounting) - deleting Subunits and Jobs from these use
models would be inaccurate and misleading.
But the Counter spec does not need to define counters for Subunits or
Jobs, so sections 3.2, 3.3, and 3.4 are correct in limiting their scope
to Systems and Services.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
------------------------------------------------------------------------
[add the following new section]
1.3 Design Requirements for Counters
(1) The PWG Imaging System Counters design MUST follow the naming
conventions and element structuring requirements defined in the PWG
Semantic Model/1.0 [PWG-5105.1], including group and element
containment, counter datatype, and counter precision requirements.
(2) The PWG Imaging System Counters design MUST NOT depend on the
implementation of any specific management protocol (see sections
3.5.1 and 3.5.2).
(3) The PWG Imaging System Counters design MUST support mappings to
multiple management protocols (e.g., OASIS WSDM and SNMP) and data
modelling languages (e.g., XML Schema and MIBs) (see section 3.5.1).
(4) The PWG Imaging System Counters design MUST support Service counters
corresponding to counters defined in the Printer object in IETF
IPP/1.1 [RFC2911] (see all use models in section 3.5).
(5) The PWG Imaging System Counters design MUST support Work counters
corresponding to counters defined in the IETF Job Monitoring MIB
[RFC2707] and the Job object in IETF IPP/1.1 [RFC2911] (see all use
models in section 3.5).
(6) The PWG Imaging System Counters design MUST support Media Used
counters corresponding to counters defined in the IETF Job
Monitoring MIB [RFC2707] and the Job object in IETF IPP/1.1
[RFC2911] (see sections 3.5.1 and 3.5.3).
(7) The PWG Imaging System Counters design MUST support Availability and
Monitoring counters corresponding to counters defined in the IETF
Printer MIB [RFC1759] [RFC3805] (see sections 3.5.1 and 3.5.2).
(8) The PWG Imaging System Counters design MUST support Work counters
for Datastream (user jobs), Auxiliary (e.g., cover sheets), Waste
(e.g., paper jams), and Maintenance (e.g., offline testing jobs)
(see section 3.5.3).
(9) The PWG Imaging System Counters design MUST support System-level
counters (see all use models in section 3.5).
(10) The PWG Imaging System Counters design MUST support Service-level
counters (see all use models in section 3.5).
(11) The PWG Imaging System Counters design SHOULD support extensions
for Subunit-level counters (see section 3.5.2).
(12) The PWG Imaging System Counters design SHOULD support extensions
for Job-level counters (see section 3.5.3).
(13) The PWG Imaging System Counters design MUST support explicit
counter persistence corresponding to 'prtMarkerLifeCount' and
'prtMarkerPowerOnCount' in IETF Printer MIB [RFC1759] [RFC3805] (see
section 3.5.3).
------------------------------------------------------------------------
[rename an existing section in the model]
change:
3.4 Counter Overview
to:
3.4 PWG Structural Model for Counters
------------------------------------------------------------------------
[add the following new section]
3.5 PWG Use Models for Counters
3.5.1 Service Providers - Monitoring and Billing
Outside service providers may lease and maintain imaging software and
imaging equipment in remote customer enterprise networks (in different
administrative domains).
Note: Typically monitoring proxies within customer enterprise networks
are required for scalability of this use model. However, the deployment
of monitoring proxies and of security credentials is outside the scope
of this document.
(1) To support basic usage billing, outside service providers
may read System-level Work and Media Used counters from imaging
systems (e.g., every month).
(2) To support detailed usage billing, outside service providers
may read System and/or Service Work and Media Used counters from
imaging systems (e.g., every month).
(3) To support reordering of supplies, outside service providers
may read System-level Work and Media Used counters from imaging
systems (e.g., every week).
(4) To support preventive maintenance, outside service providers
may read System-level Availability, Work, and Monitoring counters
from imaging systems (e.g., every week).
(5) To support downtime guarantees, outside service providers
may read System and/or Service Availability and Monitoring counters
from imaging systems, especially for configuration changes, critical
alerts, and allocation errors (e.g., every 15 minutes).
3.5.2 System Administrators - Network Management
Network System administrators configure and manage Services and Subunits
on imaging systems in local enterprise networks.
(1) To support basic configuration, network system administrators
may read System-level Monitoring counters from imaging systems for
configuration checkpoints (e.g., every month).
(2) To support detailed configuration, network system administrators
may read Service and/or Subunit Monitoring counters from imaging
systems for configuration checkpoints (e.g., every month).
(3) To support preventive maintenance, network system administrators
may read System-level Availability, Work, and Monitoring counters
from imaging systems (e.g., every week).
(4) To support emergency maintenance, network system administrators
may read System and/or Service Availability and Monitoring counters
from imaging systems, especially for configuration changes, critical
alerts, and allocation errors (e.g., every 15 minutes).
3.5.3 Network Applications - Accounting
Network accounting applications monitor Services and Jobs on imaging
systems in local enterprise networks.
(1) To support basic accounting, a network accounting application
may read System-level Work and Media Used counters from imaging
systems (e.g., every month).
(2) To support detailed accounting, a network accounting application
may read Service-level Work and Media Used counters from imaging
systems (e.g., every month).
(3) To support user accounting, a network accounting application
may read Service and/or Job Work and Media Used counters from
imaging systems (e.g., every month).
------------------------------------------------------------------------
[add the following to section 11 'Normative References']
[RFC2707] Bergman, Hastings, Isaacson, Lewis.
"Job Monitoring MIB - V1.0", RFC 2707, November 1999.
[RFC3805] Bergman, Lewis, McDonald.
"IETF Printer MIB v2", RFC 3805, June 2004.
------------------------------------------------------------------------
[add the following to section 12 'Informative References']
[RFC1759] Smith, Wright, Hastings, Zilles, Gyllenskog.
"IETF Printer MIB v1", RFC 1759, March 1995.
(obsoleted by [RFC3805])
------------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Tue Jun 07 2005 - 23:42:44 EDT