Hi Bert,
Thanks very much.
(1) I plan to add the REVISION clause to the 'last call'
version of the MIB - it will then have to be updated
again after the PWG Formal Approval vote (because the
document date changes again.
(2) I had left 'icAlertV2Trap' out of a group because my
best compiler (Epilogue Emissary) is an older version
that doesn't support NOTIFICATION-GROUP macros - again,
I planned to add it to the 'last call' version.
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: Wijnen, Bert (Bert) [mailto:bwijnen at lucent.com]
Sent: Monday, February 07, 2005 3:24 AM
To: 'McDonald, Ira'; Wijnen, Bert (Bert)
Subject: RE: COUNTER-MIB issues
C:\bwijnen\smicng\work>smicng counter.inc
W: f(counter.mi2), (14,1) MODULE-IDENTITY imagingCounterMIB should have at
least
one REVISION clause
W: f(counter.mi2), (1803,1) Item "icAlertV2Trap" is not contained in any
group d
efined in the current module
*** 0 errors and 2 warnings in parsing
> -----Original Message-----
> From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
> Sent: Monday, February 07, 2005 01:25
> To: 'Wijnen, Bert (Bert)'; McDonald, Ira
> Subject: RE: COUNTER-MIB issues
>>> Hi Bert,
>> Following the PWG naming conventions, the new version is
> posted in the 'wd' (working draft) subdirectory at:
>>ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib10-20050205.htm> - full text - PWG boilerplate, introduction, model, references
>>ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib10-20050205.mib> - ASN.1 MIB source only
>> 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: Wijnen, Bert (Bert) [mailto:bwijnen at lucent.com]
> Sent: Sunday, February 06, 2005 4:59 PM
> To: 'McDonald, Ira'
> Subject: RE: COUNTER-MIB issues
>>> Thanks for the info.
> I do not see a new copy on ftp://ftp.pwg.org/pub/pwg/wims/mibs/> yet. So can't check. Let me know when it shows up and if you
> want me to check.
>> Bert
> p.s. I expect I will be off line for some 4-6 weeks starting
> Wednesday. I need to undergo heartsurgery. So don't be
> surprised if I do not answer for a while.
>> > -----Original Message-----
> > From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
> > Sent: Sunday, February 06, 2005 00:18
> > To: 'Wijnen, Bert (Bert)'; McDonald, Ira
> > Subject: RE: COUNTER-MIB issues
> >
> >
> > Hi Bert,
> >
> > Many thanks for your help with improving this Counter MIB.
> > I've just posted a revision with the (first ever) front
> > matter (requirements, model, references, etc.). You should
> > see the announcement not shortly.
> >
> > I carefully went through the latest MIB Guidelines I-D for
> > applicable advice and tried to follow it faithfully.
> >
> > 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: Wijnen, Bert (Bert) [mailto:bwijnen at lucent.com]
> > Sent: Wednesday, January 12, 2005 5:17 AM
> > To: McDonald, Ira; 'Wijnen, Bert (Bert)'; 'wims at pwg.org'
> > Subject: RE: COUNTER-MIB issues
> >
> >
> > Hi Ira,
> > I understood (or suspected) it was not a MIB doc that would
> > come to IETF. I just saw it passing by and figured I would do
> > a few quick checks and pass whatever I found to you guys.
> >
> > Glad it was found to be useful.
> >
> > Bert
> >
> > > -----Original Message-----
> > > From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
> > > Sent: Wednesday, January 12, 2005 05:15
> > > To: 'Wijnen, Bert (Bert)'; McDonald, Ira; 'wims at pwg.org'
> > > Subject: RE: COUNTER-MIB issues
> > >
> > >
> > > Hi Bert,
> > >
> > > Thanks for your good comments. All will be addressed and
> > > corrected. And I'll look through the latest 'MIB Guidelines'
> > > I-D for other ideas.
> > >
> > > This MIB will _not_ be submitted to the IETF. It's intended
> > > to be reviewed and adopted as an IEEE/ISTO PWG Candidate
> > > Standard. It's currently scheduled to enter PWG 'last call'
> > > no later than 1 March 2005 (in the company of the the parent
> > > PWG Counters for Imaging Devices abstract counters spec and
> > > the equivalent Counters XML schema).
> > >
> > > 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: Wijnen, Bert (Bert) [mailto:bwijnen at lucent.com]
> > > Sent: Tuesday, January 11, 2005 5:49 AM
> > > To: McDonald, Ira; 'Wagner,William'; pwg-announce at pwg.org> > > Subject: COUNTER-MIB issues
> > >
> > >
> > > Hi... just did a very quick SYNTAX check. This is what I found:
> > >
> > > E: f(counter.mi2), (17,21) Date/time(0411270000Z) must
> have a year
> > > greater than 89
> > >
> > > You SHOULD use a 4-digit year. So 200411270000Z would fix
> > the problem
> > > Sane is true for all the REVISION dates/timestamps
> > >
> > > E: f(counter.mi2), (1638,1) Item "icMediaUsedSizeName"
> has invalid
> > > value for MAX-ACCESS
> > >
> > > It has:
> > > icMediaUsedSizeName OBJECT-TYPE
> > > SYNTAX SnmpAdminString (SIZE(0..63))
> > > MAX-ACCESS not-accessible
> > >
> > > The not-accessible is only valid for non-index objects. It
> > > should only be
> > > used for auxiliary objects.
> > > See sect 7.3 (2nd para) and of RFC2578.
> > >
> > > In any event, what use does a normal object have if it is not
> > > accessible?
> > >
> > >
> > > The smilint tool further shows:
> > > C:\smi\mibs\work>smilint -m -s -l 6 -inamelength-32
> > > ./PWG-IMAGING-COUNTER-MIB
> > > ./PWG-IMAGING-COUNTER-MIB:118: [1] {oid-registered}
> > > identifier `icMIB'
> > > registers
> > > object identifier already registered by `imagingCounterMIB'
> > > ./PWG-IMAGING-COUNTER-MIB:118: [6] {previous-definition}
> > > info: previous
> > > definition of `imagingCounterMIB'
> > >
> > > Further, I see:
> > >
> > > icMIBObjects OBJECT IDENTIFIER ::= { icMIB 1 }
> > > icMIBNotifications OBJECT IDENTIFIER ::= { icMIB 2 }
> > > icMIBConformance OBJECT IDENTIFIER ::= { icMIB 3 }
> > >
> > > No notifications have yet been defined. Potentially it would
> > > be better to do
> > >
> > > icMIBNotifications OBJECT IDENTIFIER ::= { icMIB 0 }
> > > icMIBObjects OBJECT IDENTIFIER ::= { icMIB 1 }
> > > icMIBConformance OBJECT IDENTIFIER ::= { icMIB 2 }
> > >
> > > It allows notifications to be defined directly under
> > > icMIBNotifications
> > > and it would be more inline with IETF MIB guidance as per
> appendix D
> > > of draft-ietf-ops-mib-review-guidelines-03.txt
> > >
> > > Firther I saw:
> > > icGeneralGroup OBJECT-GROUP
> > > OBJECTS {
> > > icGeneralNaturalLanguage,
> > > icGeneralTotalServiceRecords,
> > > icGeneralTotalSubunitRecords,
> > > icGeneralTotalMediaUsedRecords
> > > }
> > > STATUS current
> > > DESCRIPTION
> > > "Mandatory - general object group.
> > >
> > > An Imaging System MUST support and implement this
> > > object group."
> > > ::= { icMIBObjectGroups 1 }
> > >
> > > In general it is NOT GOOD to specify in the OBJECT-GROUP
> > > DESCRIPTION clause
> > > if such a group is mandatory or optional. The OBJECT-GROUP
> > > macro is meant
> > > to just group objects together in logical groups.
> > > In the MODULE-COMPLIANCE you can then specify which groups
> > > are mandatory
> > > (i.e.
> > > MUST support" or "conditionally mandatory" or "optional" etc.
> > > It would then be good to include in the DESCRIPTION clauses
> > > of the GROUP
> > > clause
> > > (in the MODULE-COMPLIANCE statement) under what conditions a
> > > conditionally
> > > mandatroy group must be supported.
> > >
> > > Section 4.8 of draft-ietf-ops-mib-review-guidelines-03.txt
> > > has detailed
> > > guidelines on MODULE-COMPLIANCE approaches.
> > >
> > > I did not review or check the MIB module in any detail.
> > >
> > > Hope this helps, Bert
> > > > -----Original Message-----
> > > > From: owner-pwg-announce at pwg.org> > > [mailto:owner-pwg-announce at pwg.org]On
> > > > Behalf Of McDonald, Ira
> > > > Sent: Tuesday, January 11, 2005 02:22
> > > > To: 'Wagner,William'; pwg-announce at pwg.org> > > > Subject: RE: PWG-ANNOUNCE> [wrong MIB URL] Jan 11 WIMS Agenda
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Bill cut-and-pasted my announcement error of the
> Counter MIB URL.
> > > >
> > > > PLEASE pickup the entirely restructured Counter MIB v0.40 at:
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/mibs/counter-mib-20041127.txt> > > >
> > > > This v0.40 is aligned with the terminology in the
> current Counter
> > > > spec.
> > > >
> > > > 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: owner-pwg-announce at pwg.org> > > [mailto:owner-pwg-announce at pwg.org]On
> > > > Behalf Of Wagner,William
> > > > Sent: Monday, January 10, 2005 6:31 PM
> > > > To: pwg-announce at pwg.org> > > > Subject: PWG-ANNOUNCE> Jan 11 WIMS Agenda
> > > >
> > > >
> > > > Greetings:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > The WIMS WG will meet Tuesday 11 January at Sharp SLA at
> > Vancouver,
> > > > Waslington
> > > >
> > > > Dial In: 1-866-365-4406
> > > > Toll #: 1-303-248-9655
> > > > Passcode: 2635888#
> > > >
> > > >
> > > >
> > > > The proposed agenda is:
> > > >
> > > > 9:00 - 9:15 Introductions and Agenda
> > > >
> > > > 9:15 – 9:30 Review of Last F2F minutes and Action Items
> > > >
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/minutes/wims_041116.pdf> > > >
> > > > 9:30-10:00 Counter MIB
> > > >
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/mibs/counter-mib-20040428.txt> > > >
> > > >
> > > >
> > > > 10:00-10:15 Break
> > > >
> > > >
> > > >
> > > > 10:15-12:00 Counter Spec -preparing for Last Call
> > > >
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscount10-20050105.doc> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscount10-20050105.pdf> > > >
> > > > 12:00- 13:30 Lunch
> > > >
> > > >
> > > >
> > > > 13:30 - 15:30 Schema
> > > >
> > > >
> > > >
> > > > - Counter Schema
> > > >
> > > >
> > > >
> > > >
> > > >
> > ftp://ftp.pwg.org/pub/pwg/wims/schemas/PwgCountersProposal091304.zip> > > > <ftp://ftp.pwg.org/pub/pwg/wims/schemas/PwgCountersProposal091> > > > 304.zip>
> > > >
> > > >
> > > >
> > > > - WIMS Base v0.10 - Agent, Device, Manager,
> Service, System
> > > >
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/wimsbase-20041212.xsd> > > >
> > > >
> > > >
> > > > - WIMS Type v0.10
> > > >
> > > >
> > > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/wimstype-20041212.xsd> > > >
> > > >
> > > >
> > > > - Alert v0.40 - Alert and Subscription
> > > >
> > > >
> > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/alert-20041212.xsd> > > >
> > > >
> > > >
> > > > - Events v0.70
> > > >
> > > >
> > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/events-20041212.xsd> > > >
> > > >
> > > >
> > > > - Report v0.40
> > > >
> > > >
> > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/report-20041212.xsd> > > >
> > > >
> > > >
> > > > - Resource v0.60
> > > >
> > > >
> > > ftp://ftp.pwg.org/pub/pwg/wims/schemas/resource-20041212.xsd> > >
> > >
> > >
> > > - Schedule v0.92
> > >
> > >
> > ftp://ftp.pwg.org/pub/pwg/wims/schemas/schedule-20041212.xsd> >
> >
> >
> > - Subunits v0.30
> >
> >
>ftp://ftp.pwg.org/pub/pwg/wims/schemas/subunits-20041212.xsd>>>> 15:30-15:45 Break
>>>> 15:45-16:45 -WIMS Spec
>>ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20050110.pdf>> (I am having trouble sending this to the FTP server.
> Hopefully, it will be
> there by Tuesday morning.)
>>>> 16:45-17:15 Next Steps & Other Related management activities.
>>>> -DMTF+ OMG
>>http://www.omg.org/news/releases/pr2004/12-13-04.htm>>>> -WS-Management
>>>http://www.intel.com/technology/manage/downloads/ws_management.pdf>>>> -WSDM (Spec out for comments)
>>>http://www.oasis-open.org/committees/documents.php?wg_abbrev=wsdm>>>> Bill Wagner
>>>