I've created a .pdf with line numbers using Acrobat V4.0 and down loaded it:
ftp://ftp.pwg.org/pub/pwg/ipp/new_MIB/draft-ietf-ipp-server-mib-00.pdf
Ron Bergman reports trouble printing the .pdf files with Acrobat V3.0 that I
have recently produced using Acrobat V4.0 with Distiller. All the words are
run together so that the document is not readable. I've have seen that
problem also, but have not been able to isolate the problem. Has anyone
else had the problem?
One solution is to down-load Acrobat V4.0 Reader from Adobe. Its free.
Thanks,
Tom
-----Original Message-----
From: Ira Mcdonald [mailto:imcdonal at sdsp.mc.xerox.com]
Sent: Monday, September 20, 1999 05:15
To: ipp at pwg.org
Subject: IPP> NOT - IPP Server MIB - 19 Sept 1999
Hi folks, Sunday (19 September 1999)
[For consideration this week at the PWG monthly face-to-face meeting -
now aligned with IPP Notifications Alternative of 10 September 1999]
Here's an Internet-Draft style revised and renamed IPP Server MIB - for
managing IPP Printers (spoolers, gateways, printers, etc.). This MIB
defines an IPP Notifications mapping over UDP/SNMP (any SNMP version).
I've just posted it on the PWG server (but not sent it to I-D editor):
ftp://ftp.pwg.org/pub/pwg/ipp/new_MIB/draft-ietf-ipp-server-mib-00.txt
- Full I-D text w/ all boilerplate (39 pages w/ Table of Contents)
ftp://ftp.pwg.org/pub/pwg/ipp/new_MIB/draft-ietf-ipp-server-mib-00.mib
- Compilable ASN.1 in SMIv2 (1341 lines w/ conformance macros)
[No '.pdf' available]
- Source file is text with markups for my tool 'DocuForm'.
Because the Printer group contains five counters (connections, requests,
errors, warnings, notifications) as well as the printer name, state, and
state reasons, this MIB supports basic IPP Printer network management.
Cheers,
- Ira McDonald
High North Inc
906-494-2697 (home)
906-494-2434 (work)
------------------------------------------------------------------------
STRUCTURE
Group/Conformance Description
----------------- ----------------------------------------------------
Printer - 11 columnar objects (including 5 counters)
(Mandatory) (language, name, state, state reasons)
Printer URI - 3 columnar objects (URI, authentication, security)
(Mandatory) ('printer-uri-supported', etc., in flat tables)
Event - 24 leaf objects
(Cond Mandatory) (printer index, trigger event, state, counters)
Printer Basic Event - 1 notification (printer-basic-event)
(Cond Mandatory) (all printer-level trigger events)
Job Basic Event - 1 notification (job-basic-event)
(Cond Mandatory) (job-created, job-config-changed)
Job Status Event - 1 notification (job-status-event w/ counters)
(Cond Mandatory) (job-completed, job-state-changed, job-purged)
Job Progress Event - 1 notification (job-progress-event w/ counters)
(Cond Mandatory) (job-progress)
------------------------------------------------------------------------
DETAILS
The IPP Server MIB is written in SMIv2 (RFC 2578, April 1999) and it
compiles warning free with Epilogue Emissary 7.0 and SMICng v2.2 and
translates cleanly (from SMIv2 syntax to SMIv1, with a conversion tool
I've written called 'smi2down'). Conformance requirements are defined
in MODULE-COMPLIANCE, OBJECT-GROUP, and NOTIFICATION-GROUP macros.
The IPP Server MIB conforms to the 'Draft Standard' SNMPv3 MIBs (RFC
2571-2575) and conveys all text in the 'UTF-8' charset (ISO 10646 /
Unicode in a stream encoding that is file-system and legacy programming
language safe) via the textual convention 'SnmpAdminString' (imported
from the SNMP Framework MIB, RFC 2571), since all IPP clients and
printers MUST support 'UTF-8'. Thus 'attributes-charset' is not needed.
The IPP Server MIB supports fast IPP Printer discovery via SNMP (simply
broadcast an SNMP GetNext for 'ippPrinterName' to find all supporting
systems). Note this does NOT scale well to an enterprise level.
------------------------------------------------------------------------