Subject: [Hubmib] EFM MIB Work in the IETF (Was: RE: [EFM]Event Time Stamp)

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Sun, 17 Aug 2003 11:15:54 +0300

David, and all,

To be accurate - no work has been started in the IETF on an SNMP MIB specification for EFM. Some discussions have been conducted on the mail list, and a number of individuals representing different vendors expressed their interest to particpate in such work - but these folks are still to get their act together in order for this work to happen. This means proposing a charter,  and starting to work in the initial Internet-Drafts proposals. There is no much time left until the next IETF meeting, which happens to be scheduled in parallel with the November IEEE Plenary. 

Regards,

Dan

Dan Romascanu,
Chair, IETF Ethernet Interfaces and Hub MIB WG

> -----Original Message-----
> From: David Law [mailto:[email-masked]]
> Sent: 15 August, 2003 1:28 AM
> To: Yonghong Ren
> Cc: [email-masked]
> Subject: RE: [EFM]Event Time Stamp
> 
> 
> 
> 
> 
> Hi Yonghong,
> 
> Clause 30 is a protocol independent MIB definition which is 
> intended to provide
> behaviors that can be referenced by protocol dependent MIBs. 
> We provide a GDMO
> specification for IEEE 802.3 managed object classes in Annex 30A and I
> understand work is ongoing within the IETF to provide the 
> SNMP specification as
> well. You can find a presentation at the URL -[
> http://www.ieee802.org/3/efm/public/sep01/law_1_0901.pdf ] 
> which discusses this
> structure further.
> 
> In respect to your actual question, if you examine the
> aOAMRemoteErrSymPeriodEvent attribute contained in the Annex 
> 30 changes (Page
> 145) you will find the syntax for the attribute defined as
> IEEE802Dot3-MgmtAttributeModule.OAMErrorEvent. If you then 
> examine the ASN.1
> IEEE802Dot3-MgmtAttributeModule module additions defined in 
> Annex 30B (Page 151)
> you will find OAMErrorEvent defined as follows:
> 
> OAMErrorEvent ::= SEQUENCE {
>                             OAMEventTimeStamp [1] Integer16,
>                             OAMEventWindow    [2] Integer64,
>                             OAMEventThreshold [3] Integer64,
>                             OAMEventRunTotal  [4] Integer32
>                             }
> 
> Hence as can be seen the OAMEventTimeStamp is indeed defined 
> as a 16 bit Integer
> in Annex 30A and I hope the other Integers are defined as you 
> would expect.
> 
> Best regards,
>   David Law
> 
> 

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