WIMS> Requirements section for Counter Spec (24 June 2005)

WIMS> Requirements section for Counter Spec (24 June 2005)

WIMS> Requirements section for Counter Spec (24 June 2005)

McDonald, Ira imcdonald at sharplabs.com
Fri Jun 24 13:27:13 EDT 2005


Hi folks,                                          Friday (24 June 2005)

[This note supersedes my note of 7 June on Counter Spec requirements]

Below are updates for the PWG Imaging System Counters spec, as per our
discussion at last week's WIMS telecon:

(a) additions to section 2.2 'Imaging Terminology';

(b) additions to section 12 'Normative References';

(c) additions to section 13 'Informative References';

(d) full text of section 3 'Requirements'

Note:  All of the use models in section 3.2 yield design requirements or
recommendations that apply to Subunits (e.g., preventive maintenance) or
Jobs (user accounting) - to delete Subunits or Jobs from these use
models would be inaccurate and misleading.  But an initial version of the
Counter Spec does NOT need to satisfy all design requirements (per the
PWG Process/2.0).

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 at sharplabs.com
------------------------------------------------------------------------

[add to section 2.2 'Imaging Terminology']


Imaging Service - A synonym for Service, used for clarity in the model
and design requirements.

    Source: See definition of Service below.


Imaging System - A synonym for System, used for clarity in the model and
design requirements.

    Source: See definition of System below.

------------------------------------------------------------------------

[add to section 12 'Normative References']


[RFC2707] Bergman, Hastings, Isaacson, Lewis.  "Job Monitoring MIB v1",
          RFC 2707, November 1999.

[RFC2790] Grillo, Waldbusser.  "Host Resources MIB v2", RFC 2790, March
          2000 (obsoletes [RFC1514]).

[RFC3805] Bergman, Lewis, McDonald.  "Printer MIB v2", RFC 3805, June
          2004 (obsoletes [RFC1759]).

------------------------------------------------------------------------

[add to section 13 'Informative References']


[PWG5100.3] Ocke, Hastings.  "Internet Printing Protocol (IPP):
            Production Printing Attributes - Set1", PWG 5100.3, February
            2001.

[PWG5100.7] Hastings, Zehler.  "Internet Printing Protocol (IPP):  Job
            Extensions", PWG 5100.7, October 2003.

[RFC1514] Grillo, Waldbusser.  "Host Resources MIB v1", RFC 1514,
          September 1993 (obsoleted by [RFC2790]).

[RFC1759] Smith, Wright, Hastings, Zilles, Gyllenskog.  "Printer MIB
          v1", RFC 1759, March 1995 (obsoleted by [RFC3805]).

[RFC2567] Wright.  "Design Goals for an Internet Printing Protocol",
          RFC 2567, April 1999.

[RFC2568] Zilles.  "Rationale for the Structure of the Model and
          Protocol for the Internet Printing Protocol", RFC 2568,
          April 1999.

------------------------------------------------------------------------

[replace empty section 3 'Requirements' with]

3. Requirements

3.1 Rationale for Counters

The IETF and PWG standards for the Internet Printing Protocol (IPP), the
Job Monitoring MIB, and the Printer MIB define:

(a) A rationale for an abstract model of printing (to support alternate
    encodings and protocols) in section 3 of the IETF IPP Rationale
    [RFC2568] which led to the later development of the PWG Semantic
    Model/1.0 [PWG5105.1].

(b) A set of design goals for status monitoring in a printing protocol
    in section 3.1.3 'Viewing the status and capabilities of a printer'
    (for End User), section 3.2.1 'Alerting' (for Operator), and section
    3.3 'Administrator' (the bullet requirement to 'administrate billing
    or other charge-back mechanisms') of the IETF IPP Design Goals
    [RFC2567].

(c) An abstract model of a Print Service in section 2.1 of IETF IPP/1.1
    [RFC2911].

(d) A set of multifunction Service types for Imaging Systems in the
    'JmJobServiceTypesTC' textual convention in section 4 of the IETF
    Job Monitoring MIB [RFC2707].

(e) An abstract model of a multifunction Job in section 2 of the IETF
    Job Monitoring MIB [RFC2707].

(f) An abstract model of a Print Job in section 2.2 of IETF IPP/1.1
    [RFC2911].

(g) A set of abstract Print Job counter attributes in section 4.3.18 of
    IETF IPP/1.1 [RFC2911], section 3.8 of PWG IPP Production Printing
    Attributes [PWG5100.3], section 5.1 of PWG IPP Job Extensions
    [PWG5100.7], and section 4 of the IETF Job Monitoring MIB [RFC2707].

(h) An abstract model of a Print Device in section 2.2 of the IETF
    Printer MIB v2 [RFC3805].

(i) A set of abstract Print Device counter attributes in section 6 of
    the IETF Printer MIB v2 [RFC3805].


Over the past decade, network printers have evolved into multifunction
Imaging Systems.  In order to support monitoring, maintenance, and
administration of these Imaging Systems, this document defines:

(1) New abstract System and Service objects with Status element groups
    (containing Counters element groups) as a framework extension to the
    PWG Semantic Model/1.0 [PWG5105.1].

(2) A set of abstract counters for these new System and Service objects.

(3) A set of conformance requirements for implementation of the abstract
    counters for these new System and Service objects.


3.2 Use Models for Counters

3.2.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.2.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.2.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).


3.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.2.1 and 3.2.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.2.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.2).

(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.2).

(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.2.1 and 3.2.3).

(7) The PWG Imaging System Counters design MUST support Availability and
    Monitoring counters corresponding to counters defined in the IETF
    Host Resources MIB [RFC1514] [RFC2790] IETF Printer MIB [RFC1759]
    [RFC3805] (see sections 3.2.1 and 3.2.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.2.3).

(9) The PWG Imaging System Counters design MUST support System-level
    counters (see all use models in section 3.2).

(10) The PWG Imaging System Counters design MUST support Service-level
    counters (see all use models in section 3.2).

(11) 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.2.3).

(12) The PWG Imaging System Counters design SHOULD support extensions
    for Subunit-level counters (see section 3.2.2).

(13) The PWG Imaging System Counters design SHOULD support extensions
    for Job-level counters (see section 3.2.3).

------------------------------------------------------------------------



More information about the Wims mailing list