Hi,
Please note Ron Bergman's correct email address (I corrected it
in the 'cc:' line above just now).
Please send _only_ plaintext to the 'fin at pwg.org' mailing list,
as this is also the official IETF mailing list for the Finisher
MIB (Harry, take note please).
Thanks to all of you for your interest in using and extending the
Finisher MIB.
Status: On 12 June 2003 the IESG officially approved draft-16
of the Finisher MIB for publication as a Proposed Standard RFC.
It has reference dependencies on Printer MIB v2 and on the new
IANA Charset MIB (former 'CodedCharSet' textual convention in
Printer MIB v1, RFC 1759). The IESG approved drafts are in the
directory:
ftp://ftp.ietf.org/internet-drafts/
in the files:
draft-ietf-printmib-mib-info-15.txt - Printer MIB v2
draft-mcdonald-iana-charset-mib-02.txt- IANA Charset MIB
Warning: Chuck Adams (Xerox - Wilsonville, OR) found a bug in
my machine translation, so the published IANA Charset MIB will
eventually include about 20 more charset values in the RFC.
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
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Saturday, January 10, 2004 12:37 AM
To: Sack, Christian
Cc: Kouptchinsky Andre; imcdonald at sharplabs.com;
Ron.Bergman at hitachi-hkis.com; Ronald Parrish; Ronald Graham; Reinhard
Hohensee; Dave Stone; fin at pwg.org
Subject: Re: UP3I's interest to Finishing MIB
Christian, thank you for contacting me regarding the feasibility of
extending the Finisher MIB. I'm glad that you find the Finisher MIB
applicable to UP3i. I strongly encourage leveraging common semantics among
related standards organizations.
Of course I know R. Parrish, R. Graham, R. Hohensee and D. Stone.. they are
exceptional colleagues (as are the Finisher MIB co-authors, R. Bergman and
I. McDonald).
I have discussed your note with my co-authors and we have the following
comments
1. It appears that you are working with an out of date draft (-14).
- Please obtain the latest draft
http://www.ietf.org/internet-drafts/draft-ietf-printmib-finishing-16.txt
- Note that there have been updates, especially in the areas of
internationalization and charset support
2. Your table did not translate well into plain text. If possible, please
forward an HTML or WORD version. This will help us better understand your
specific questions
- Please include more descriptive text for each proposed attribute if
possible... enough to adequately describe the attribute and it's purpose,
such as you find in our Printer and Finisher MIBs.
3. Some of the attributes you are interested in (ex. amount remaining on
roll) may be part of the Printer MIB
I would like to recommend that PWG and UP3i work together to extend the
Finisher MIB to suite you needs. Since the IETF process can be
excruciatingly slow and cumbersome, the PWG plans to manage future printer
related MIB extensions via our own, PWG standards process. In fact, we are
currently engaged in defining a web services device management protocol and
related XML schema. We expect this effort to result in some new printer and
scanner semantics which will need to be mapped into PWG Printer MIB
extensions.... so your timing is good. We can work together on the Finisher
MIB extensions this year.
PWG will be holding a f2f meeting in San Jose, California, Feb 23-26. There
is still time to add this topic to the agenda if you think a UP3i
representative(s) would attend. Our next meeting will be April (after
Easter) in Washington, D.C.
----------------------------------------------
Harry Lewis
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
"Sack, Christian" <Christian.Sack at ops.de>
01/09/2004 03:33 AM ToHarry Lewis/Boulder/IBM at IBMUS
ccKouptchinsky Andre <Andre.Kouptchinsky at osl.be>
SubjectUP3I's interest to Finishing MIB
Hello Harry, dear Finisher-MIB chair,
my name is Christian Sack and I'm writing you in the name of the UP3I
organization. This organization (UP3I = Universal Printer, Pre and
Postprocessing Inerface, www.up3i.org) is a non profit organization of
vendors like IBM, Xerox, Oce, RSI, Standard etc. I'm director to this
organisation. From IBM's technical side there are Ron Parrish
(ronp at us.ibm.com), Ronald Graham (regraham at us.ibm.com), Reinhard Hohensee
(hohensee at us.ibm.com), Dave E. Stone (destone at us.ibm.com), and others
involved - maybe you know them?
Here now comes my request for some help: The UP3I specification made a
connection to your Finishing-MIB as we use your excellent work for
administrative information support. Now as we are deeper in detail and going
to implementation phase, we miss some parameters in your MIB. Please find
below a summarized table of my partner Andre Kouptchinsky with these missing
parameters.
Table 1: Attributes to support by finisher devices via SNMP. Mandatory
attributes are emphasized.
MIF attributes Meaning Coverage by IETF
finisher MIB draft nr 14
.1 ComponentId printmib.30.1.1.10
finDeviceDescription
.1.1 Manufacturer specific OID's per
attribute to be supplied
.1.2 Product idem
.1.3 Version idem
.1.4 Serial Number idem
.1.5 Installation Date idem
.1.6 Verify idem
.1101 Controller
.1101.1 Status printmib.30.1.1.9
finDeviceStatus
.1101.2 Error not in MIB draft proposal,
to be supplied
.1101.3 Warning not in MIB draft proposal,
can be supplied
.1102 Counters
Cutter Stacker (Hunkeler):
.1102.1 Stunden run hours since production start-up
not in MIB
draft proposal, to be supplied
.1102.2 Schnitt number of cuts of a cutter
not in MIB draft
proposal, to be supplied
.1102.3 Dokumente number of documents processed by cutter
not in MIB
draft proposal, to be supplied
.1102.4 Stapel number of stacks processed by cutter
not in MIB draft
proposal, to be supplied
.1102.5 Formatgrösse size of a cut in 1/6 inch
not in MIB draft
proposal, can be supplied
Unwinder (Hunkeler):
.1102.1 Stunden run hours since production start-up
.1102.2 Laufmeter paper length in current meters
.1102.3 Rollen number of rolls on (un)winder since
production start
printmib.31.1.1.1 finSupplyIndex (supply index to increment for every new
roll)
.1102.4 Rollengrösse Roll diameter in mm (current)
not in MIB draft
proposal, can be supplied
Cutter (Stralfors):
.1102.1 NumberOfPages number of cut pages since knife change
not in MIB
draft proposal, to be supplied
Re-/Unwinder (Stralfors):
.1102.1 PaperRemaining amount of paper remaining on roll
printmib.31.1.1.8 finSupplyCurrentLevel
Others (see hereunder):
.1102.1 NumberOfTicks percentage of remaining paper on a
roll or stack
not in MIB draft proposal, to be supplied
.1102.2 FillStatus percentage of remaining paper on a roll
or stack
printmib.31.1.1.8 finSupplyCurrentLevel
May be it is possible extend the finishing MIB, or is UP3I supposed to add
some prorietary branches or have we simply overseen some points? Please
advice and give us an idea how to continue on this point... Thanks!
Best regards,
Christian
================================
Christian Sack
Océ Printing Systems GmbH
Electronics and Sensors
Siemensallee 2
85586 Poing
Tel: +49 8121 72 3186
Fax: +49 8121 72 4221
Océ mission statement:
Océ enables its customers to manage their documents efficiently by offering
innovative print and document management products and services for
professional environments.
Wichtiger Hinweis: Diese E-Mail, die angehängten Dateien und deren Inhalt
sind vertraulich und ausschließlich für den oben bezeichneten Adressaten
bestimmt. Jeder Zugriff sowie jegliche Nutzung, Verbreitung oder Speicherung
durch andere Personen ist nicht gestattet. Eine Zuwiderhandlung kann
strafrechtlich verfolgt werden. Sollten Sie diese E-Mail irrtümlich erhalten
haben, bitten wir Sie, den Absender umgehend zu benachrichtigen und
anschließend die E-Mail zu löschen.
Important notice: This E-Mail and any attachments are strictly confidential
and are intended for the recipient(s) named above only. Any unauthorized
review, printing, copying, use or distribution of this E-Mail by anyone else
is prohibited and may be a criminal offense. If you have received this
E-Mail in error, please notify the sender immediately by reply E-Mail and
delete the original message.delete the original message.