1. Requirements and Approach
MFD WEB Management
Requirements and Approach
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

2. Requirements - Monitoring
Manufacturer:
Product service – from central or distributed locations
Product statistics – information to make product better
Imaging support service (enterprise or external):
Usage/costing – Meter reads
Supplies – just-in-time supplies and maintenance
Service – automatic alert of problems – keeps customer happy and machine running
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

3. Requirements - Management
Manufacturer:
Product update – send to new code
Product upgrade – sell additional services and deliver directly to machine
Imaging support service (enterprise or external):
Setup change – defaults, server links, address lists
Constrain usage – encourage timely bill payments, discourage abuse, change authorized users
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

4. Objectives Compatible with enterprise environments Scalable
Low network traffic impact
security provisions and policies
Scalable
Large enterprise
Support of many small offices
Standard yet Flexible
Transport and format standard
Content customizable
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

5. Necessary Features Identification of Device Characteristics
Model, Manufacturer, Configuration
Location, Contacts, Administrator
Objects that can be monitored, current value
Objects that can be managed, current value
Date-Time
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

6. Necessary Features Remote programmability (Instructions)
Specify Objects to be monitored
Rate of monitoring
Rate/time of reporting
Accommodate default sets of Status, Usage and Alert objects
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

7. Necessary Features Reports Compatible with Data Base Management
Human Readable?
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

8. Aspects to be Defined Transport Message format Contents Report
Instruction
Message format
Coding
Compatibility with Data Base Management
Contents
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

9. Related Extant Standards
IPP Notification - INDP method but
Stress printer rather than job
Subscription => Instructions
Cannot rely on access to printer as server
MIB/SNMP
Structured management information
WebDev
Various Data Base Systems
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

10. Base Information Sources
Network Monitor for Existing Equipment
MIB via SNMP (standardized and proprietary)
Web Pages (proprietary)
CIM
Protocols like NPAP, IPP
Integral Agent for New Equipment
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

11. Suggestion Device uses http Client to contact Assigned Server Security
Push reports
Pull instructions
Security
Compatible with standard Proxies
Device Capable of authentication response
Encrypted reports ?
Allow Local Oversight ?
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

12. IPP Notification Model
output device or server PDA, desktop, or server Optional | ########### | | client |-----Subscription ># Printer # | Creation Operation | # Object # |
| #####|##### | |Notification| | |Recipient |<----IPP Event Notifications (Job and/or Printer Events)
Add ability to Pull Subscriptions (Instructions)
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

13. Suggestion Format and Coding XML coding SOAP ? Or Just XML over HTTP?
Identify objects with MIB OID
Concise OID/Value format with limited indexing ability
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019

14. What to do next? Is there interest in Standardization? Limiting Scope?
Monitoring only?
Default only? (no instructions)
Just standardize interface with server?
Consider
Transport (HTTP or custom)
Object identification method
Report contents, coding and formats
Instruction coding, format,
PWG - New Orleans /W. Wagner, NetSilicon
4/10/2019