RE: WG Last Call

Hi,
 
I have not reviewed the EPON or CU MIBs, but we have reviewed and
implemented the EFM MIB.  We agreed with one issue that has already been
raised:  as creation is automatic we couldn't see the need for the rowStatus
object.
 
Why is there no trap on receipt of OAMPDUs with the special EFM alarm bits
set in the flags field?  Assuming one was reflecting the status of a remote
system in a local system's MIB, I can see some value sending such a trap.
In principle, if there were suitable traps defined in other MIBs, I think
those should be used.  For the "link fault" event, I can imagine using a
trap in IF-MIB for example, but for a "dying gasp" or "critical" event,
there doesn't seem to be a suitable trap elsewhere.  Arguably, the
general-purpose "critical" event is too generic to be useful, but there's
real information in "dying gasp" that hasn't been available from remote
Ethernet devices before.  We have chosen to include such events in traps
defined in an enterprise-specific MIB.
 
Best regards,
    -- John
 

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of
Romascanu, Dan (Dan)
Sent: 12 August 2004 14:55
To: [email protected]
Subject: FW: [Hubmib] WG Last Call


There is one more week until the WG Last Call completes. We received too few
comments to my taste. Please read the documents, and send your comments to
the WG list [email protected] <mailto:[email protected]> , if you want this work
to be completed at the appropriate quality level. Even comments like - 'I do
not really have time to review the MIB modules in detail, but the technical
approach seems OK from an EFM and Ethernet management perspective' are
welcome. Of course, if you think that something is broken, you should make a
more explicit argument.
 

Thanks and Regards,

Dan

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of
Romascanu, Dan (Dan)
Sent: 20 July, 2004 12:03 AM
To: [email protected]
Subject: [Hubmib] WG Last Call



My previous message contained an erroneous reference. Please disregard it,
and replace it with this one.

This is an Ethernet Interfaces and Hub MIB WG Last Call for the EFM MIB
Internet-Drafts. The documents can be found at: 

*
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-mib-
01.txt
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-mib
-01.txt> 
*
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-epon
-mib-01.txt
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-epo
n-mib-01.txt> 
*
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-cu-m
ib-01.txt
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-cu-
mib-01.txt> 

All comments must be sent to the WG e-mail list [email protected], until
Wednesday August 18, 2004.

Although a 30 days Last Call period is being granted, it is strongly
suggested to the WG participants to submit their comments before the face to
face WG meeting, which will be hold on Monday, August 2nd - so that their
inputs can be discussed during the meeting in San Diego.


Regards,

Dan

_______________________________________________
Hubmib mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/hubmib