attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=729471515-28022005>Hi
Harry, hi Ira,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=729471515-28022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=729471515-28022005>thank
you for your information. It gives us a clear direction to
proceed.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=729471515-28022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=729471515-28022005>Best
regards</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=729471515-28022005>Andreas</SPAN></FONT></DIV></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Ursprüngliche Nachricht-----<BR><B>Von:</B> Harry Lewis
[mailto:harryl@us.ibm.com]<BR><B>Gesendet:</B> Montag, 28. Februar 2005
07:23<BR><B>An:</B> McDonald, Ira<BR><B>Cc:</B> 'Hirn, Andreas';
'fin@pwg.org'; 'pmp@pwg.org'; 'rbergma@hitachi-hkis.com';
technic@up3i.org<BR><B>Betreff:</B> RE: FIN> finisher mib integration into
up3i<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Ira says it better
than I in my response to fin@pwg.org and validates my opinion that option (1)
is preferred.</FONT> <BR><FONT face=sans-serif
size=2>---------------------------------------------- <BR>Harry Lewis <BR>IBM
STSM<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%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"McDonald, Ira"
<imcdonald@sharplabs.com></B> </FONT>
<P><FONT face=sans-serif size=1>02/24/2005 09:32 AM</FONT> </P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"'Hirn, Andreas'"
<Andreas.Hirn@ops.de>, Harry Lewis/Boulder/IBM@IBMUS,
"'pmp@pwg.org'" <pmp@pwg.org></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD><FONT face=sans-serif size=1>"'fin@pwg.org'"
<fin@pwg.org>, "'rbergma@hitachi-hkis.com'"
<rbergma@hitachi-hkis.com>, technic@up3i.org</FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: FIN> finisher mib
integration into up3i</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT
size=2><TT>Hi Andreas,<BR><BR>Thanks for your interesting question
below.<BR><BR>I'm copying this reply to the Printer MIB Project
(PMP)<BR>mailing list. The Finisher MIB mailing list
remains<BR>functional, but has very few subscribers. All future<BR>MIB
work in the IEEE/ISTO PWG is being coordinated<BR>through the PMP
list.<BR><BR>Please note that the 'finSupplyTable' has a
non-index<BR>informational element 'finSupplyDeviceIndex' defined
as:<BR><BR> "The value
of finDeviceIndex corresponding to the finishing<BR>
device subunit with which this finisher
supply is associated.<BR>
The value zero indicates the associated finishing device is<BR>
Unknown."<BR><BR>And the
'finSupplyMediaInputTable' has a similar<BR>informational element
'finSupplyMediaInputDeviceIndex'.<BR><BR>Those elements are NOT indices of
their tables (and allowed<BR>to take the value of zero), in case they are
associated<BR>with the overall finisher and not a specific finishing
device.<BR><BR>It's certainly allowed to implement more than other
printer<BR>in 'hrDeviceTable' (and thus more than one complete print <BR>line
for alerts, trays, etc.). I think that's probably the<BR>best way to
separate the alerts/trays for individual finishers.<BR><BR>Note: We've
tried to accomodate UP3I requests for counters<BR>in our Imaging Device
Counters spec, Counter Schema, and <BR>Counter MIB work in the PWG WIMS
working group. Comments<BR>are very welcome.<BR><BR>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscount10-20050120.pdf<BR><BR>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib10-20050205.htm<BR>
- full text - PWG boilerplate, introduction, model,
references<BR><BR>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib10-20050205.mib<BR>
- ASN.1 MIB source only<BR><BR>Note that the Finisher subunit (the
elements defined in the<BR>Finisher MIB) has not yet been added to our
Subunits schema.<BR><BR>
ftp://ftp.pwg.org/pub/pwg/wims/schemas/subunits-20041212.xsd<BR><BR>Cheers,<BR>-
Ira (co-editor of Printer MIB v2 and Finisher MIB)<BR><BR>Ira McDonald
(Musician / Software Architect)<BR>Blue Roof Music / High North Inc<BR>PO Box
221 Grand Marais, MI 49839<BR>phone: +1-906-494-2434<BR>email:
imcdonald@sharplabs.com<BR><BR>-----Original Message-----<BR>From:
fin-owner@pwg.org [mailto:fin-owner@pwg.org]On Behalf Of
Hirn,<BR>Andreas<BR>Sent: Thursday, February 24, 2005 10:42 AM<BR>To:
'harryl@us.ibm.com'<BR>Cc: 'fin@pwg.org'; 'rbergma@hitachi-hkis.com';
technic@up3i.org<BR>Subject: FIN> finisher mib integration into
up3i<BR><BR><BR>Hi Harry,<BR><BR><BR>UP3I is a standard to connect independent
preprinter, printer and <BR>postprocessing devices together to a printline
like this:<BR><BR><BR><BR>
+-------+<BR>
| |<BR>
| Host |<BR>
| |<BR>
+---+---+<BR>
| <BR>
|<BR>
| e.g. Ethernet LAN<BR>
|
<BR>
|
<BR>+-------+ +---+---+
+-------+
<BR>|
| | |
| |
<BR>| pre a |
... |Printer| ... | post c| ....
<BR>|
| | |
| |
<BR>+---+---+ +---+---+
+---+---+
<BR> |
|
|
<BR> |
|
|
<BR> | |
|
<BR>
+-------...-------+------...--------+--------...
<BR>
|
<BR>
| 1394
<BR>
|
<BR>
+---+---+
<BR>
|
|
<BR> |
UP3i |
<BR>
|manager|
<BR>
| |
<BR>
+---+---+
<BR>
|
<BR>
|
<BR>
|
LAN<BR><BR>
|
<BR>
|
<BR> +---+---+
<BR> |
|
<BR>
| SNMP |
<BR>
|manager|
<BR>
| |
<BR>
+---+---+
<BR>
<BR> <BR><BR>The commands between the
preprinter, printer and postprocessing devices are <BR>sent as standardized
UP3I frames over a firewire cable. Every device has a <BR>unique address in
the system, called paper sequence id. It is also possible <BR>to send SNMP
requests packed into UP3I frames from the up3i manager to the <BR>up3i devices
and back. The up3i manager could also have a LAN interface.<BR><BR>Now we want
to implement printer and finisher mib support into the print <BR>line to allow
an external SNMP manger to monitor the print line.<BR><BR><BR>In the moment we
have two ideas how we can do that:<BR><BR><BR>1.) Stand alone devices<BR>Every
preprinter, printer and postprocessing device acts as a discrete <BR>device in
the host resources mib of the up3i manager. The hrDeviceIndex <BR>could be the
same as the paper sequence id. Every device itselfs implents <BR>the host
resources-, printer- and finisher mib, independant from the rest <BR>of the
print line. The snmp requests to the up3i manager are directly <BR>handed over
to the up3i devices by packing them into up3i snmp frames.<BR><BR>The problem
with this solution is:<BR><BR>We don't know if it is allowed (respectively
meaningful) to have a print <BR>line in which every device has its own
hrDeviceIndex. It seems that the <BR>combination printer/finishing mib only
allows one hrDeviceIndex per line <BR>and several finDeviceIndex(es) for every
device. Is it meaningful <BR>regarding a SNMP Printer Manager to use several
hrDeviceIndex instances <BR>in a print line?<BR><BR><BR>2.) One hrDeviceIndex
per print line<BR>We have one hrDeviceIndex for the printLine, the up3i device
are separated <BR>by their finDeviceIndex. The finDeviceIndex could be the
same as the paper <BR>sequence id.<BR><BR>The problems now are:<BR><BR>The
finSupply/finSupplyMediaInput tables are not indexed by the<BR>finDeviceIndex,
<BR>they have a separate finSupplyIndex/finSupplyMediaInputIndex. An
agreement<BR>is <BR>needed which device can use which
finSupplyIndex/finSupplyMediaInputIndex.<BR><BR>Some information about the
devices lies in the printer mib, e.g. parts of<BR>the <BR>input output and
alert table. The finisher devices also have to know e.g.<BR>under <BR>which
indexes their own input tables reside in the printer mib.<BR>Therefore the
printer and the finisher devices have to get this information,<BR><BR>which is
not the case today, or the up3i manager has to merge all tables of <BR>every
device together in tables for the whole print line, which could be a <BR>bold
venture.<BR><BR><BR>What do you think is the best way for us to implement
printer/finisher mib<BR>in <BR>the print line?<BR><BR><BR><BR><BR>Best
regards,<BR>Andreas
Hirn<BR><BR>_____________________________________<BR><BR>Andreas Hirn
OPS TEC<BR>Software
Development<BR><BR>Océ Printing Systems GmbH<BR>Siemensallee 2 <BR>85586
Poing, Germany<BR>Direct Dial +49-8121-72 4029<BR>Direct Fax
+49-8121-72 31 73<BR>mailto:
Andreas.Hirn@ops.de<BR>www.oce.com<BR>_____________________________________<BR></TT></FONT><BR></BLOCKQUOTE></BODY></HTML>