From Ron.Bergman at Hitachi-hkis.com Fri Jan 18 14:29:41 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: UP3I Support
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EA73@triton.hitachi-hkis.com>
Brian,
UP3i has a version 1.0 document which can be found at:
http://www.up3i.org/
I do not know what they included from the Finisher MIB but both the Printer
MIB and the Finisher MIB are listed as "helpful sources".
Ron Bergman
Hitachi Koki Imaging Solutions
-----Original Message-----
From: Brian Anderson [mailto:banderson@sofha.com]
Sent: Thursday, January 17, 2002 5:00 PM
To: harryl@us.ibm.com
Cc: fin@pwg.org; rbergma@hitachi-hkis.com
Subject: UP3I Support
Hi Harry:
Back in May 2001 the PWG was considering supporting a request from UP3I
group (Universal Printer Pre- and Postprocessing Interface). The request
was to use some of the FIN MIB terminology.
What support was provided and do you know any status whether the UP3I has
implemented its standard?
Best regards,
- Brian Anderson
SOFHA
Berlin, Germany
Email: banderson@sofha.com
Tel: +949/856 0496 (direct) 949/300-3475 (mobile)
Fax: +949/767-5889
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020118/071b5181/attachment.html
From Ron.Bergman at Hitachi-hkis.com Mon Aug 5 17:08:31 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:44 2009
Subject: FIN> Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EBEB@triton.hitachi-hkis.com>
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page.
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020805/e93becdf/attachment.html
From Ron.Bergman at Hitachi-hkis.com Thu Aug 8 14:21:26 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EBF5@triton.hitachi-hkis.com>
The new MIB documents are now available at:
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-mib-info-12.txt
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-finishing-13.txt
Ron
-----Original Message-----
From: Bergman, Ron
Sent: Monday, August 05, 2002 2:09 PM
To: 'Wijnen, Bert (Bert)'; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; Ned Freed (E-mail); 'pmp@pwg.org'; 'fin@pwg.org'
Subject: Printer MIB and Finisher MIB Update
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page.
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020808/bd1f42ae/attachment.html
From Ron.Bergman at Hitachi-hkis.com Tue Sep 3 21:30:19 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EC1D@triton.hitachi-hkis.com>
Bert and David,
Have you had any time to look at our new documents?
Ron
-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Thursday, August 08, 2002 1:18 PM
To: Ron.Bergman@Hitachi-hkis.com; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org;
bwijnen@lucent.com
Subject: RE: Printer MIB and Finisher MIB Update
Will try to check them early next week
Thanks,
Bert
-----Original Message-----
From: Ron.Bergman@Hitachi-hkis.com [mailto:Ron.Bergman@Hitachi-hkis.com]
Sent: donderdag 8 augustus 2002 20:21
To: bwijnen@lucent.com; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: RE: Printer MIB and Finisher MIB Update
The new MIB documents are now available at:
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-mib-info-12.txt
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-finishing-13.txt
Ron
-----Original Message-----
From: Bergman, Ron
Sent: Monday, August 05, 2002 2:09 PM
To: 'Wijnen, Bert (Bert)'; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; Ned Freed (E-mail); 'pmp@pwg.org'; 'fin@pwg.org'
Subject: Printer MIB and Finisher MIB Update
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020903/a7fb49f2/attachment.html
From imcdonald at sharplabs.com Tue Sep 17 18:44:56 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: Printer/Finisher MIB and IANA enumerations
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA2@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
Thanks for your excellent feedback.
Your timing is perfect! Last week, Ron Bergman and I concluded that
all type 2 and type 3 textual conventions should be moved into such
a separate IANA-Printer-Types-MIB (like the HOST-RESOURCES-TYPES-MIB
in RFC 2790).
We plan to do this before the next draft - so we will wind up with
three SMIv2 source modules for Printer MIB:
1) Printer-MIB itself
2) IANA-Charset-MIB for the 'IANACharset' TC (improved name per
feedback from the IETF Charsets Registry mailing list)
3) IANA-Printer-Types-MIB for type2/type3 enums
Should we use all uppercase for the two IANA-maintained modules?
More recent IETF 'standards track' MIBs seem to do so.
We've also identified _one_ textual convention 'PrtAlertGroupTC'
which should be changed from type 1 (requires republication of
entire Printer MIB) to type 2 (IANA maintained). Because the
Finisher MIB had to add enums to this TC several years ago.
Else, any more new Finisher MIB object groups would require
republication of the Printer MIB (a mistake in our opinion).
We will also (per Bert Wijnen's request) insert the 'Prt'
suffix into our two recently added localized string TCs:
- 'PrtLocalizedDescriptionStringTC'
- 'PrtConsoleDescriptionStringTC'
(my mistake this wasn't done originally).
One textual convention 'PresentOnOff' we plan to leave with
the current (original RFC 1759) name and no 'Prt' prefix.
Because the Finisher MIB uses it (unmodified) already.
And a number of vendor private MIBs import it (I used it
in the Xerox enterprise MIB modules for years).
Should we fix the name (add 'Prt' prefix) of this last TC?
We will also fix every one of the problems that Bert Wijnen
identified in his recent 24-page email on 'difftool' output.
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Monday, September 16, 2002 4:32 PM
To: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; imcdonald@sharplabs.com; paf@cisco.com;
ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: Printer/Finisher MIB and IANA enumerations
I have done some more work on my Printer-MIB implementation and I
stumbled over the type 1, 2 and 3 enumerations. Section 2.4.1 says:
: 2.4.1 Registering Additional Enumerated Values
:
: This working group has defined several type of enumerations. These
: enumerations differ in the method employed to control the addition of
: new enumerations. Throughout this document, references to
: "enumeration (n)", where n can be 1, 2 or 3 can be found in the
: various tables. The definitions of these types of enumerations are:
:
: enumeration (1) All the values are defined in the Printer MIB
: specification (RFC for the Printer MIB). Additional enumerated
: values require a new RFC.
:
: enumeration (2) An initial set of values are defined in the
: Printer MIB specification. Additional enumerated values are
: registered after review by this working group. The initial
: versions of the MIB will contain the values registered so far.
: After the MIB is approved, additional values will be registered
: through IANA after approval by this working group.
:
: enumeration (3) An initial set of values are defined in the
: Printer MIB specification. Additional enumerated values are
: registered without working group review. The initial versions of
: the MIB will contain the values registered so far. After the MIB
: is approved, additional values will be registered through IANA
: without approval by this working group.
So this sounds like all type 2 and type 3 enumerations are in fact
under IANA control. In fact, IANA already maintains an informal list
for the printer languages:
http://www.iana.org/assignments/printer-language-numbers
I think the right thing to do here is actually to handle the type 2
and type 3 enumerations in exactly the way you handle the charset
textual convention so that IANA can update a proper MIB module which
the printer/finisher MIB import.
In other words, I propose to move the type 2 TCs
PrtGeneralResetTC, PrtMarkerSuppliesTypeTC, prtGeneralReset
and the type 3 TCs
PrtCoverStatusTC, PrtChannelTypeTC, PrtInterpreterLangFamilyTC,
PrtInputTypeTC, PrtOutputTypeTC, PrtMarkerMarkTechTC,
PrtMediaPathTypeTC, PrtConsoleColorTC, PrtConsoleDisableTC,
PrtAlertTrainingLevelTC, PrtAlertCodeTC
into an IANA maintained module, e.g. the IANA-PRINTER-MIB. (I hope I
did not mis one.) This way, there is no cut&paste needed when updating
to the latest set of assigned values and IANA can use the SMIv2 module
identity macro to allow others to track changes.
/js
--
Juergen Schoenwaelder
From imcdonald at sharplabs.com Wed Sep 18 12:51:08 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: Printer/Finisher MIB and IANA enumerations
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA5@mailsrvnt02.enet.sharplabs.com>
Hi Bert and Juergen,
My apologies. Ron has already correctly restored _all_ of the original
RFC 1759 textual conventions with status DEPRECATED immediately
below each new 'Prt...' TC (so seeing the relation is easy) in
his next working draft (soon to be released).
Ron had intended to follow Bert's and Dave Harrington's advice not to
remove any previously defined (RFC 1759) textual convention.
And we prefer to use DEPRECATED (rather than OBSOLETE) because we
wish to recognize that implementations or Printer MIB v1 (RFC 1759)
continue to be used and are the basis of most OS vendor and tools
vendor monitoring of network printers, at present.
Thanks to all of you for keeping us straight on SMIv2 best practice.
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, September 18, 2002 6:59 AM
To: Juergen Schoenwaelder; imcdonald@sharplabs.com
Cc: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; imcdonald@sharplabs.com; paf@cisco.com;
ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: RE: Printer/Finisher MIB and IANA enumerations
> Ira> Should we fix the name (add 'Prt' prefix) of this last TC?
>
> If you think consistency is important and you want people to use the
> Prt* TCs,, you can can formally introduce a PrtPresentOnOff TC with
> STATUS current while leaving the old PresentOnOff TC with STATUS
> deprecated in the MIB. This way, nothing breaks and you can transition
> to all prefixed TCs.
>
As a matter of fact, to better follow the SMI rules, the old non-prefixed
TCs probably should all have stayed in the MIB with status deprecated.
Or possibly even obsoleted if you want to give stronger message for people
to switch to the new TCs.
Bert
> /js
>
> --
> Juergen Schoenwaelder
From imcdonald at sharplabs.com Fri Sep 20 14:30:27 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: [Addressability] one more printer mib question
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDAB@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
Oops! Good question. I would say use the Marker row specified by
'prtMarkerDefaultIndex' in the 'prtGeneralTable'.
But we sure ought to specify this in the descriptions of the two
'prtInterpreterTable' columnar objects. Right?
Further, it's not meaningful (and SHOULD NOT be done) to have
different addressability units for different markers or
interpreters in the same instance of the Printer MIB, in
my humble opinion.
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Friday, September 20, 2002 6:48 AM
To: McDonald, Ira
Cc: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; McDonald, Ira; paf@cisco.com; ned.freed@mrochek.com;
pmp@pwg.org; fin@pwg.org
Subject: one more printer mib question
The descriptions of prtInterpreterFeedAddressability and
prtInterpreterXFeedAddressability say:
prtInterpreterFeedAddressability OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum interpreter addressability in the feed
direction in 10000 prtMarkerAddressabilityUnits (see
prtMarkerAddressabilityFeedDir ) for this interpreter. The
value (-1) means other and specifically indicates that the sub-
unit places no restrictions on this parameter."
::= { prtInterpreterEntry 8 }
prtInterpreterXFeedAddressability OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum interpreter addressability in the cross feed
direction in 10000 prtMarkerAddressabilityUnits (see
prtMarkerAddressabilityXFeedDir) for this interpreter. The
value (-1) means other and specifically indicates that the sub-
unit places no restrictions on this parameter."
::= { prtInterpreterEntry 9 }
Which instance of prtMarkerAddressabilityUnits do I use for a given
prtInterpreterFeedAddressability or prtInterpreterXFeedAddressability
instance?
/js
--
Juergen Schoenwaelder
From imcdonald at sharplabs.com Fri Sep 20 19:05:43 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:44 2009
Subject: FIN> RE: [Addressability] one more printer mib question
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDAF@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
While you're correct that we should define another column
in 'prtInterpreterTable' to disambiguate this units problem,
that's not very practical.
The actual objects (very few) newly defined in Printer MIB v2
have all been stable for four or five years. Several printer
vendors have been shipping full Printer MIB v2 implementations
for two or three years. The tools all understand the current
objects in Printer MIB v2. Adding an object now would be
unpopular in the extreme.
Vendors - is adding a new column to 'prtInterpreterTable'
(the technically correct solution) acceptable?
Ron and Harry - I'm personally ambivalent about this issue.
Juergen has uncovered a non-trivial bug in the Printer MIB
(v1 and v2).
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Friday, September 20, 2002 5:05 PM
To: imcdonald@sharplabs.com
Cc: imcdonald@sharplabs.com; Ron.Bergman@Hitachi-hkis.com;
bwijnen@lucent.com; dbh@enterasys.com; harryl@us.ibm.com;
imcdonald@sharplabs.com; paf@cisco.com; ned.freed@mrochek.com;
pmp@pwg.org; fin@pwg.org
Subject: Re: [Addressability] one more printer mib question
>>>>> McDonald, Ira writes:
Ira> Oops! Good question. I would say use the Marker row specified
Ira> by 'prtMarkerDefaultIndex' in the 'prtGeneralTable'.
Are you sure this is always and necessarily the right marker?
Ira> But we sure ought to specify this in the descriptions of the two
Ira> 'prtInterpreterTable' columnar objects. Right?
What ever the answer is, it should be documented. As far as I am
concerned, I would like to see another column
prtInterpreterFeedAddressabilityUnit
added to the prtInterpreterTable and the need for looking up the unit
in some other places just goes away.
Ira> Further, it's not meaningful (and SHOULD NOT be done) to have
Ira> different addressability units for different markers or
Ira> interpreters in the same instance of the Printer MIB, in my
Ira> humble opinion.
Right now, the MIB seems to allow for it and hence I try to allow for
this in my management application...
/js
--
Juergen Schoenwaelder
From Ron.Bergman at hitachi-ps.us Fri Oct 11 16:51:53 2002
From: Ron.Bergman at hitachi-ps.us (Ron.Bergman@hitachi-ps.us)
Date: Wed May 6 13:53:44 2009
Subject: FIN> FW: New Finisher MIB Draft is now available
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83D01A4A6D5@triton.hitachi-hkis.com>
This message never made it to the list. The document is now also
available from the IETF internet-drafts.
> -----Original Message-----
> From: Bergman, Ron
> Sent: Tuesday, October 08, 2002 5:19 PM
> To: 'fin@pwg.org'
> Subject: New Finisher MIB Draft is now available
>
> A new Finisher MIB Draft has been sent to the IETF.
>
> The only real change is the movement of the Type 2 and
> Type 3 TCs to a separate MIB, which is also contained
> in the same document.
>
> The new documents can be found at:
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.txt
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.pdf
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.doc
>
>
> Ron Bergman
> Hitachi Printing Solutions America
>
>
From Ron.Bergman at Hitachi-hkis.com Fri Jan 18 14:29:41 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:48 2009
Subject: FIN> RE: UP3I Support
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EA73@triton.hitachi-hkis.com>
Brian,
UP3i has a version 1.0 document which can be found at:
http://www.up3i.org/
I do not know what they included from the Finisher MIB but both the Printer
MIB and the Finisher MIB are listed as "helpful sources".
Ron Bergman
Hitachi Koki Imaging Solutions
-----Original Message-----
From: Brian Anderson [mailto:banderson@sofha.com]
Sent: Thursday, January 17, 2002 5:00 PM
To: harryl@us.ibm.com
Cc: fin@pwg.org; rbergma@hitachi-hkis.com
Subject: UP3I Support
Hi Harry:
Back in May 2001 the PWG was considering supporting a request from UP3I
group (Universal Printer Pre- and Postprocessing Interface). The request
was to use some of the FIN MIB terminology.
What support was provided and do you know any status whether the UP3I has
implemented its standard?
Best regards,
- Brian Anderson
SOFHA
Berlin, Germany
Email: banderson@sofha.com
Tel: +949/856 0496 (direct) 949/300-3475 (mobile)
Fax: +949/767-5889
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020118/071b5181/attachment-0001.html
From Ron.Bergman at Hitachi-hkis.com Mon Aug 5 17:08:31 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:48 2009
Subject: FIN> Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EBEB@triton.hitachi-hkis.com>
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page.
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020805/e93becdf/attachment-0001.html
From Ron.Bergman at Hitachi-hkis.com Thu Aug 8 14:21:26 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EBF5@triton.hitachi-hkis.com>
The new MIB documents are now available at:
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-mib-info-12.txt
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-finishing-13.txt
Ron
-----Original Message-----
From: Bergman, Ron
Sent: Monday, August 05, 2002 2:09 PM
To: 'Wijnen, Bert (Bert)'; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; Ned Freed (E-mail); 'pmp@pwg.org'; 'fin@pwg.org'
Subject: Printer MIB and Finisher MIB Update
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page.
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020808/bd1f42ae/attachment-0001.html
From Ron.Bergman at Hitachi-hkis.com Tue Sep 3 21:30:19 2002
From: Ron.Bergman at Hitachi-hkis.com (Ron.Bergman@Hitachi-hkis.com)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: Printer MIB and Finisher MIB Update
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6EC1D@triton.hitachi-hkis.com>
Bert and David,
Have you had any time to look at our new documents?
Ron
-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Thursday, August 08, 2002 1:18 PM
To: Ron.Bergman@Hitachi-hkis.com; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org;
bwijnen@lucent.com
Subject: RE: Printer MIB and Finisher MIB Update
Will try to check them early next week
Thanks,
Bert
-----Original Message-----
From: Ron.Bergman@Hitachi-hkis.com [mailto:Ron.Bergman@Hitachi-hkis.com]
Sent: donderdag 8 augustus 2002 20:21
To: bwijnen@lucent.com; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: RE: Printer MIB and Finisher MIB Update
The new MIB documents are now available at:
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-mib-info-12.txt
http://www.ietf.org/internet-drafts/
draft-ietf-printmib-finishing-13.txt
Ron
-----Original Message-----
From: Bergman, Ron
Sent: Monday, August 05, 2002 2:09 PM
To: 'Wijnen, Bert (Bert)'; dbh@enterasys.com
Cc: RCasterline@lhsolutions.com; harryl@us.ibm.com; imcdonald@sharplabs.com;
paf@cisco.com; Ned Freed (E-mail); 'pmp@pwg.org'; 'fin@pwg.org'
Subject: Printer MIB and Finisher MIB Update
Bert and David,
I have updated both MIBs per your latest comments and the new drafts have
been submitted to the IETF Internet-Drafts site. They should be available
shortly. In the interim, the documents are available on the PWG FTP site:
ftp://ftp.pwg.org/pub/pwg/pmp/drafts/draft-ietf-printmib-mib-info-12.txt
ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishing-
13.txt
The majority of the changes are not technical but per your suggestions
regarding requirements for the RFC editor. The most significant change is
moving the CodedCharSet TC to IANA. We have created this MIB and it is
being submitted to IANA.
We sincerely appreciate your support in reviewing this document and hope
that you can do a quick review of the final results and submit to the IESG
for last call.
Summary of the changes to the Printer MIB (-11 to -12)
1) Removed Gary Gocek, Harry Lewis, and Randy Turner from the cover page
and
footers. Move the listings for the above from the "Authors" to
"Significant
Contributors" and removed the company addresses to be consistent with
other
entries in appendix F.
2) Added Steve Waldbusser to the "Significant Contributors" section.
3) Section 2.2.13 "...description of each alert..."
was "...description of each critical alert..."
4) Corrected prtInputXXX names in first paragraph of Appendix B and C.
Also
revised this paragraph to reference the PWG Media Names specification
[30].
5) Added a note to prtMarkerLifeCount concerning the need to be a
persistent value.
6) Added chSMTP(45) to prtChannelTypeTC. Added reference [29].
7) Corrected reference to IANA Charset Registry. (reference [4])
8) Shortened name of Appendix B.
9) Added reference to PWG Media Names specification [30] to
prtInputMediaName,
prtInputMediaType, and prtInputMediaColor. Revised description and
added a
reference clause for prtInputMediaType, and prtInputMediaColor.
10) Added the copyright notice to first page
11) Removed the references to the HR and Interfaces MIB from the Abstract.
12) Added section 1.5 and a reference to RFC 2119 in the Reference section.
13) Removed the CodedCharSet Textual Convention, replaced with an import of
the
CodedCharSet TC from IANA.
14) Section 2.2.1.1, 1st paragraph: Added text that indicates the
CodedCharSet TC is
from the IANA Coded Character Set MIB.
15) Section 2.2.5, 1st paragraph: Revised text to reference the Finisher
MIB.
16) Section 2.2.8: Added a reference to RFC 1790 and revised the text for
clarification.
17) Section 2.2.9: Added a reference to RFC 2863.
18) Split section 10 into sections 10 and 11 for Normative and Informative
References. All references have been re-labeled per current IETF
practice.
19) Added new language enums 60 to 65 to prtInterpreterLangFamilyTC.
20) Updated the contact information in the MODULE-IDENTITY clause.
Summary of the changes to the Finisher MIB (-12 to -13)
1) Moved second paragraph of the abstract to the Introduction section.
2) Removed second paragraph of section 5.2.
3) Added a size clause to finDeviceAssociatedMediaPaths and
finDeviceAssociatedOutputs.
4) Split section 8 into sections 8 and 9 for Normative and Informative
References.
All references have been re-labeled per current IETF practice.
5) Added Ira McDonald to the "Significant Contributors" section.
For the PrintMIB Working Group,
Ron Bergman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/fin/attachments/20020903/a7fb49f2/attachment-0001.html
From imcdonald at sharplabs.com Tue Sep 17 18:44:56 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: Printer/Finisher MIB and IANA enumerations
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA2@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
Thanks for your excellent feedback.
Your timing is perfect! Last week, Ron Bergman and I concluded that
all type 2 and type 3 textual conventions should be moved into such
a separate IANA-Printer-Types-MIB (like the HOST-RESOURCES-TYPES-MIB
in RFC 2790).
We plan to do this before the next draft - so we will wind up with
three SMIv2 source modules for Printer MIB:
1) Printer-MIB itself
2) IANA-Charset-MIB for the 'IANACharset' TC (improved name per
feedback from the IETF Charsets Registry mailing list)
3) IANA-Printer-Types-MIB for type2/type3 enums
Should we use all uppercase for the two IANA-maintained modules?
More recent IETF 'standards track' MIBs seem to do so.
We've also identified _one_ textual convention 'PrtAlertGroupTC'
which should be changed from type 1 (requires republication of
entire Printer MIB) to type 2 (IANA maintained). Because the
Finisher MIB had to add enums to this TC several years ago.
Else, any more new Finisher MIB object groups would require
republication of the Printer MIB (a mistake in our opinion).
We will also (per Bert Wijnen's request) insert the 'Prt'
suffix into our two recently added localized string TCs:
- 'PrtLocalizedDescriptionStringTC'
- 'PrtConsoleDescriptionStringTC'
(my mistake this wasn't done originally).
One textual convention 'PresentOnOff' we plan to leave with
the current (original RFC 1759) name and no 'Prt' prefix.
Because the Finisher MIB uses it (unmodified) already.
And a number of vendor private MIBs import it (I used it
in the Xerox enterprise MIB modules for years).
Should we fix the name (add 'Prt' prefix) of this last TC?
We will also fix every one of the problems that Bert Wijnen
identified in his recent 24-page email on 'difftool' output.
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Monday, September 16, 2002 4:32 PM
To: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; imcdonald@sharplabs.com; paf@cisco.com;
ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: Printer/Finisher MIB and IANA enumerations
I have done some more work on my Printer-MIB implementation and I
stumbled over the type 1, 2 and 3 enumerations. Section 2.4.1 says:
: 2.4.1 Registering Additional Enumerated Values
:
: This working group has defined several type of enumerations. These
: enumerations differ in the method employed to control the addition of
: new enumerations. Throughout this document, references to
: "enumeration (n)", where n can be 1, 2 or 3 can be found in the
: various tables. The definitions of these types of enumerations are:
:
: enumeration (1) All the values are defined in the Printer MIB
: specification (RFC for the Printer MIB). Additional enumerated
: values require a new RFC.
:
: enumeration (2) An initial set of values are defined in the
: Printer MIB specification. Additional enumerated values are
: registered after review by this working group. The initial
: versions of the MIB will contain the values registered so far.
: After the MIB is approved, additional values will be registered
: through IANA after approval by this working group.
:
: enumeration (3) An initial set of values are defined in the
: Printer MIB specification. Additional enumerated values are
: registered without working group review. The initial versions of
: the MIB will contain the values registered so far. After the MIB
: is approved, additional values will be registered through IANA
: without approval by this working group.
So this sounds like all type 2 and type 3 enumerations are in fact
under IANA control. In fact, IANA already maintains an informal list
for the printer languages:
http://www.iana.org/assignments/printer-language-numbers
I think the right thing to do here is actually to handle the type 2
and type 3 enumerations in exactly the way you handle the charset
textual convention so that IANA can update a proper MIB module which
the printer/finisher MIB import.
In other words, I propose to move the type 2 TCs
PrtGeneralResetTC, PrtMarkerSuppliesTypeTC, prtGeneralReset
and the type 3 TCs
PrtCoverStatusTC, PrtChannelTypeTC, PrtInterpreterLangFamilyTC,
PrtInputTypeTC, PrtOutputTypeTC, PrtMarkerMarkTechTC,
PrtMediaPathTypeTC, PrtConsoleColorTC, PrtConsoleDisableTC,
PrtAlertTrainingLevelTC, PrtAlertCodeTC
into an IANA maintained module, e.g. the IANA-PRINTER-MIB. (I hope I
did not mis one.) This way, there is no cut&paste needed when updating
to the latest set of assigned values and IANA can use the SMIv2 module
identity macro to allow others to track changes.
/js
--
Juergen Schoenwaelder
From imcdonald at sharplabs.com Wed Sep 18 12:51:08 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: Printer/Finisher MIB and IANA enumerations
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDA5@mailsrvnt02.enet.sharplabs.com>
Hi Bert and Juergen,
My apologies. Ron has already correctly restored _all_ of the original
RFC 1759 textual conventions with status DEPRECATED immediately
below each new 'Prt...' TC (so seeing the relation is easy) in
his next working draft (soon to be released).
Ron had intended to follow Bert's and Dave Harrington's advice not to
remove any previously defined (RFC 1759) textual convention.
And we prefer to use DEPRECATED (rather than OBSOLETE) because we
wish to recognize that implementations or Printer MIB v1 (RFC 1759)
continue to be used and are the basis of most OS vendor and tools
vendor monitoring of network printers, at present.
Thanks to all of you for keeping us straight on SMIv2 best practice.
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, September 18, 2002 6:59 AM
To: Juergen Schoenwaelder; imcdonald@sharplabs.com
Cc: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; imcdonald@sharplabs.com; paf@cisco.com;
ned.freed@mrochek.com; pmp@pwg.org; fin@pwg.org
Subject: RE: Printer/Finisher MIB and IANA enumerations
> Ira> Should we fix the name (add 'Prt' prefix) of this last TC?
>
> If you think consistency is important and you want people to use the
> Prt* TCs,, you can can formally introduce a PrtPresentOnOff TC with
> STATUS current while leaving the old PresentOnOff TC with STATUS
> deprecated in the MIB. This way, nothing breaks and you can transition
> to all prefixed TCs.
>
As a matter of fact, to better follow the SMI rules, the old non-prefixed
TCs probably should all have stayed in the MIB with status deprecated.
Or possibly even obsoleted if you want to give stronger message for people
to switch to the new TCs.
Bert
> /js
>
> --
> Juergen Schoenwaelder
From imcdonald at sharplabs.com Fri Sep 20 14:30:27 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: [Addressability] one more printer mib question
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDAB@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
Oops! Good question. I would say use the Marker row specified by
'prtMarkerDefaultIndex' in the 'prtGeneralTable'.
But we sure ought to specify this in the descriptions of the two
'prtInterpreterTable' columnar objects. Right?
Further, it's not meaningful (and SHOULD NOT be done) to have
different addressability units for different markers or
interpreters in the same instance of the Printer MIB, in
my humble opinion.
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Friday, September 20, 2002 6:48 AM
To: McDonald, Ira
Cc: Ron.Bergman@Hitachi-hkis.com; bwijnen@lucent.com; dbh@enterasys.com;
harryl@us.ibm.com; McDonald, Ira; paf@cisco.com; ned.freed@mrochek.com;
pmp@pwg.org; fin@pwg.org
Subject: one more printer mib question
The descriptions of prtInterpreterFeedAddressability and
prtInterpreterXFeedAddressability say:
prtInterpreterFeedAddressability OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum interpreter addressability in the feed
direction in 10000 prtMarkerAddressabilityUnits (see
prtMarkerAddressabilityFeedDir ) for this interpreter. The
value (-1) means other and specifically indicates that the sub-
unit places no restrictions on this parameter."
::= { prtInterpreterEntry 8 }
prtInterpreterXFeedAddressability OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum interpreter addressability in the cross feed
direction in 10000 prtMarkerAddressabilityUnits (see
prtMarkerAddressabilityXFeedDir) for this interpreter. The
value (-1) means other and specifically indicates that the sub-
unit places no restrictions on this parameter."
::= { prtInterpreterEntry 9 }
Which instance of prtMarkerAddressabilityUnits do I use for a given
prtInterpreterFeedAddressability or prtInterpreterXFeedAddressability
instance?
/js
--
Juergen Schoenwaelder
From imcdonald at sharplabs.com Fri Sep 20 19:05:43 2002
From: imcdonald at sharplabs.com (McDonald, Ira)
Date: Wed May 6 13:53:49 2009
Subject: FIN> RE: [Addressability] one more printer mib question
Message-ID: <116DB56CD7DED511BC7800508B2CA53735CDAF@mailsrvnt02.enet.sharplabs.com>
Hi Juergen,
While you're correct that we should define another column
in 'prtInterpreterTable' to disambiguate this units problem,
that's not very practical.
The actual objects (very few) newly defined in Printer MIB v2
have all been stable for four or five years. Several printer
vendors have been shipping full Printer MIB v2 implementations
for two or three years. The tools all understand the current
objects in Printer MIB v2. Adding an object now would be
unpopular in the extreme.
Vendors - is adding a new column to 'prtInterpreterTable'
(the technically correct solution) acceptable?
Ron and Harry - I'm personally ambivalent about this issue.
Juergen has uncovered a non-trivial bug in the Printer MIB
(v1 and v2).
Cheers,
- Ira McDonald, co-editor of Printer MIB v2
High North Inc
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Friday, September 20, 2002 5:05 PM
To: imcdonald@sharplabs.com
Cc: imcdonald@sharplabs.com; Ron.Bergman@Hitachi-hkis.com;
bwijnen@lucent.com; dbh@enterasys.com; harryl@us.ibm.com;
imcdonald@sharplabs.com; paf@cisco.com; ned.freed@mrochek.com;
pmp@pwg.org; fin@pwg.org
Subject: Re: [Addressability] one more printer mib question
>>>>> McDonald, Ira writes:
Ira> Oops! Good question. I would say use the Marker row specified
Ira> by 'prtMarkerDefaultIndex' in the 'prtGeneralTable'.
Are you sure this is always and necessarily the right marker?
Ira> But we sure ought to specify this in the descriptions of the two
Ira> 'prtInterpreterTable' columnar objects. Right?
What ever the answer is, it should be documented. As far as I am
concerned, I would like to see another column
prtInterpreterFeedAddressabilityUnit
added to the prtInterpreterTable and the need for looking up the unit
in some other places just goes away.
Ira> Further, it's not meaningful (and SHOULD NOT be done) to have
Ira> different addressability units for different markers or
Ira> interpreters in the same instance of the Printer MIB, in my
Ira> humble opinion.
Right now, the MIB seems to allow for it and hence I try to allow for
this in my management application...
/js
--
Juergen Schoenwaelder
From Ron.Bergman at hitachi-ps.us Fri Oct 11 16:51:53 2002
From: Ron.Bergman at hitachi-ps.us (Ron.Bergman@hitachi-ps.us)
Date: Wed May 6 13:53:49 2009
Subject: FIN> FW: New Finisher MIB Draft is now available
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83D01A4A6D5@triton.hitachi-hkis.com>
This message never made it to the list. The document is now also
available from the IETF internet-drafts.
> -----Original Message-----
> From: Bergman, Ron
> Sent: Tuesday, October 08, 2002 5:19 PM
> To: 'fin@pwg.org'
> Subject: New Finisher MIB Draft is now available
>
> A new Finisher MIB Draft has been sent to the IETF.
>
> The only real change is the movement of the Type 2 and
> Type 3 TCs to a separate MIB, which is also contained
> in the same document.
>
> The new documents can be found at:
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.txt
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.pdf
>
>
> ftp://ftp.pwg.org/pub/pwg/fin/internet-drafts/draft-ietf-printmib-finishin
> g-14.doc
>
>
> Ron Bergman
> Hitachi Printing Solutions America
>
>