ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
rev-03.pdf
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
rev-03-rev.pdf
The latter has revision marks turned on (they start over each page).
-rw-r--r-- 1 pwg pwg 94049 Jun 30 00:06
draft-ietf-printmib-finishing-03.txt
-rw-r--r-- 1 pwg pwg 160768 Jun 30 00:08
draft-ietf-printmib-finishing-rev-03.doc
-rw-r--r-- 1 pwg pwg 86160 Jun 30 22:31
draft-ietf-printmib-finishing-rev-03.pdf
-rw-r--r-- 1 pwg pwg 115794 Jun 30 22:31
draft-ietf-printmib-finishing-rev-03-rev.pdf
Tom
At 17:40 6/29/98 PDT, Ron Bergman wrote:
>I have submitted the latest Finisher MIB document to the IETF to be posted
>as an internet-draft. The announcement should appear in the next day or
>so.
>
>The document also can be found at:
>
>ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing
-03.txt
>
>I have also loaded a WORD file that contains revision marks for all the
>changes since the last internet-draft. (I could not create a PDF file
today.)
>The WORD file is in the same directory as:
>
>draft-ietf-printmib-finishing-rev-03.doc
>
>And there is a MIB file that matches at:
>
>ftp://ftp.pwg.org/pub/pwg/fin/mibs/fin-mib-980629.mib
>
>
>These documents contain all the changes from the prevous posting plus,
>with the following exceptions, the changes suggested by Tom Hastings and
>Ira Mcdonald.
>
> 1. I added "(mandatory)" to the Finisher Device Attribute Group but I
> question whether it should really be "Conditionally Mandatory". As
> suggested by Tom, is it valid to have a table entry without any
> attributes? Or, if there are no attributes there should be no table?
>
> 2. I did not change the arc to { mib-2 9999 } as in Ira's differences.
> I believe that the problem observed by Ira could also be solved by
> appending the Finisher MIB to the Printer MIB and compiling both
> together.
>
> Ira: Did your complied result contain the correct OIDs with the
> Printer MIB arc?
>
> 3. Ira suggested that the syntax of the objects:
>
> finSupplyMediaInputName
> finSupplyMediaInputDescription
> finSupplyMediaInputMediaType
>
> be change from "DisplayString" to "OCTET STRING" to be consistent
> with the Printer MIB. Since it was previously discussed and agreed
> that these objects should be "DisplayString", I did not change.
>
>Unless we can resolve the above three issues via email, I would like to
>place these issues for discussion on the agenda for next week.
>
>
> Ron Bergman
> Dataproducts Corp.
>
>
>
>