Re: LMP MIB

[Baktha Muralidharan <muralidb@cisco.com>]

Comments on the LMP MIB:

>         1.Data Link Adddress is of type InetAddressType--- not sure 
> if  this covers NSAP,
>            required by OIF OUNI
>         2. CC ID. How will applications know what to set this to? Suggesr 
> defining a "CCIDNext"
             object that will dole out values to be used in row creation
>         3. TE oper status includes a "testing", which is not in the LMP 
> draft's definition of
               TE Link Finite State Machine states.
>         4. Add an attribute to the data bearing link table, to indicate 
> which "bundle" (TE Link) owns it
>         5. CC Trap won't work if CC is not modeled as an ifEntry
>         6. Since we have traps for "TE Link has degraded", would be 
> useful to have traps when TE Link
>             moves out of the degraded state.
>         7. It will be quite useful to have objects that store the reason 
> why a CC or TE Link or Data
                bearing link is in down state, since each of them could go 
into down state due to a number of different
>             reasons.
>         8. Data bearing link table should include objects for the following:
>                 a. Interface switching capability
>                 b. bandwidth
                These are defined in the LMP draft
>         9. Given the contention resolution definition in OUNI OIF draft, 
> why do we need the Role
>             object in CC table

          10. Configurable retry limit for message retransmissions



Thanks

/Baktha Muralidharan
Cisco Systems