attachment-0001
<br><font size=2 face="sans-serif">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. </font>
<br>
<br><font size=2 face="sans-serif">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).</font>
<br>
<br><font size=2 face="sans-serif">I have discussed your note with my co-authors
and we have the following comments</font>
<br>
<br><font size=2 face="sans-serif">1. It appears that you are working with
an out of date draft (-14). </font>
<br><font size=2 face="sans-serif"> - Please obtain the latest
draft </font><a href="http://www.ietf.org/internet-drafts/draft-ietf-printmib-finishing-16.txt"><font size=2 color=blue face="sans-serif">http://www.ietf.org/internet-drafts/draft-ietf-printmib-finishing-16.txt</font></a>
<br><font size=2 face="sans-serif"> - Note that there have
been updates, especially in the areas of internationalization and charset
support</font>
<br><font size=2 face="sans-serif">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</font>
<br><font size=2 face="sans-serif"> - 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.</font>
<br><font size=2 face="sans-serif">3. Some of the attributes you are interested
in (ex. amount remaining on roll) may be part of the Printer MIB </font>
<br>
<br><font size=2 face="sans-serif">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. </font>
<br>
<br><font size=2 face="sans-serif">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.
</font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
Chairman - IEEE-ISTO Printer Working Group<br>
http://www.pwg.org<br>
IBM Printing Systems <br>
http://www.ibm.com/printers<br>
303-924-5337<br>
---------------------------------------------- </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Sack, Christian"
<Christian.Sack@ops.de></b> </font>
<p><font size=1 face="sans-serif">01/09/2004 03:33 AM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Harry Lewis/Boulder/IBM@IBMUS</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">Kouptchinsky Andre <Andre.Kouptchinsky@osl.be></font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">UP3I's interest to Finishing
MIB</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hello Harry, dear Finisher-MIB chair,<br>
my name is Christian Sack and I'm writing you in the name of the UP3I<br>
organization. This organization (UP3I = Universal Printer, Pre and<br>
Postprocessing Inerface, www.up3i.org) is a non profit organization of<br>
vendors like IBM, Xerox, Oce, RSI, Standard etc. I'm director to this<br>
organisation. From IBM's technical side there are Ron Parrish<br>
(ronp@us.ibm.com), Ronald Graham (regraham@us.ibm.com), Reinhard Hohensee<br>
(hohensee@us.ibm.com), Dave E. Stone (destone@us.ibm.com), and others<br>
involved - maybe you know them?<br>
<br>
Here now comes my request for some help: The UP3I specification made a<br>
connection to your Finishing-MIB as we use your excellent work for<br>
administrative information support. Now as we are deeper in detail and
going<br>
to implementation phase, we miss some parameters in your MIB. Please find<br>
below a summarized table of my partner Andre Kouptchinsky with these missing<br>
parameters.<br>
<br>
Table 1: Attributes to support by finisher devices via SNMP. Mandatory<br>
attributes are emphasized.<br>
<br>
MIF attributes
Meaning
Coverage by IETF finisher MIB draft nr 14
<br>
.1 ComponentId
printmib.30.1.1.10 finDeviceDescription
<br>
.1.1 Manufacturer
specific OID's per attribute to be supplied<br>
<br>
.1.2 Product
idem
<br>
.1.3 Version
idem
<br>
.1.4 Serial Number
idem
<br>
.1.5 Installation Date
idem
<br>
.1.6 Verify
idem
<br>
.1101 Controller
<br>
.1101.1 Status
printmib.30.1.1.9 finDeviceStatus
<br>
.1101.2 Error
not in MIB draft proposal, to be supplied
<br>
.1101.3 Warning
not in MIB draft proposal, can be supplied<br>
<br>
.1102 Counters
<br>
Cutter Stacker (Hunkeler):
<br>
.1102.1 Stunden
run hours since production start-up
not in MIB<br>
draft proposal, to be supplied
<br>
.1102.2 Schnitt
number of cuts of a cutter
not in MIB draft<br>
proposal, to be supplied
<br>
.1102.3 Dokumente
number of documents processed by cutter
not in MIB<br>
draft proposal, to be supplied
<br>
.1102.4 Stapel
number of stacks processed by cutter
not in MIB draft<br>
proposal, to be supplied
<br>
.1102.5 Formatgrösse
size of a cut in 1/6 inch
not in MIB draft<br>
proposal, can be supplied
<br>
Unwinder (Hunkeler):
<br>
.1102.1 Stunden
run hours since production start-up
<br>
.1102.2 Laufmeter
paper length in current meters
<br>
.1102.3 Rollen
number of rolls on (un)winder since production start<br>
printmib.31.1.1.1 finSupplyIndex (supply index to increment for every
new<br>
roll)
<br>
.1102.4 Rollengrösse
Roll diameter in mm (current)
not in MIB draft<br>
proposal, can be supplied
<br>
Cutter (Stralfors):
<br>
.1102.1 NumberOfPages
number of cut pages since knife change
not in MIB<br>
draft proposal, to be supplied
<br>
Re-/Unwinder (Stralfors):
<br>
.1102.1 PaperRemaining
amount of paper remaining on roll<br>
printmib.31.1.1.8 finSupplyCurrentLevel
<br>
Others (see hereunder):
<br>
.1102.1 NumberOfTicks
percentage of remaining paper on a roll or stack<br>
not in MIB draft proposal, to be supplied
<br>
.1102.2 FillStatus
percentage of remaining paper on a roll or stack<br>
printmib.31.1.1.8 finSupplyCurrentLevel
<br>
<br>
<br>
May be it is possible extend the finishing MIB, or is UP3I supposed to
add<br>
some prorietary branches or have we simply overseen some points? Please<br>
advice and give us an idea how to continue on this point... Thanks!<br>
<br>
Best regards,<br>
Christian<br>
<br>
<br>
================================<br>
Christian Sack<br>
Océ Printing Systems GmbH<br>
Electronics and Sensors<br>
Siemensallee 2<br>
85586 Poing<br>
Tel: +49 8121 72 3186<br>
Fax: +49 8121 72 4221<br>
<br>
Océ mission statement:<br>
Océ enables its customers to manage their documents efficiently by offering<br>
innovative print and document management products and services for<br>
professional environments.<br>
<br>
Wichtiger Hinweis: Diese E-Mail, die angehängten Dateien und deren Inhalt<br>
sind vertraulich und ausschließlich für den oben bezeichneten Adressaten<br>
bestimmt. Jeder Zugriff sowie jegliche Nutzung, Verbreitung oder Speicherung<br>
durch andere Personen ist nicht gestattet. Eine Zuwiderhandlung kann<br>
strafrechtlich verfolgt werden. Sollten Sie diese E-Mail irrtümlich erhalten<br>
haben, bitten wir Sie, den Absender umgehend zu benachrichtigen und<br>
anschließend die E-Mail zu löschen.<br>
<br>
Important notice: This E-Mail and any attachments are strictly confidential<br>
and are intended for the recipient(s) named above only. Any unauthorized<br>
review, printing, copying, use or distribution of this E-Mail by anyone
else<br>
is prohibited and may be a criminal offense. If you have received this<br>
E-Mail in error, please notify the sender immediately by reply E-Mail and<br>
delete the original message.delete the original message.<br>
<br>
</tt></font>
<br>