Romascanu, Dan (Dan <dromasca <at> avaya.com>
2004-03-04 14:11:46 GMT
Please find attached the minutes of the Ethernet Interfaces and Hub MIB WG meeting hold at the 59th IETF. Thanks to Shailaja Yadawad for volunteering to be the minutes taker during the meeting.
WG:Ethernet Interfaces and Hub MIB WG (hubmib)
Date:Wednesday, March 3 at 0900-1130
CHAIR: Dan Romascanu <dromasca <at> avaya.com>
Reported by: Shailaja
Since next versions of the drafts will be the last call and hence authors
need to do give special attention to all the aspects of the draft like
formatting,compilation of the MIB etc.
3. Generic EFM MIB Issues (Dan on behalf of Matt) - 30 minutes
Slide-Common MIB or OAM MIB
There was a discussion about OAM and MIB seem to represent
the same meaning and hence need to consider removing the word OAM.
Dan to take this matter to the list.
More detailed mail sent by Matt Squire to the list.
It will be included in the next draft, unless there are objections.
Slide -Counters and Discontinuities
Proposal - include the clarification text unless there are objections on the list.
Slide -Event Counter Inconsistency (II)
Proposal - Include read-only objects to reflect the internal counters,
unless objected on the list.
Proposal - provide event control mechanism as recommended in the slides,
unless objected on the list
4. EPON MIB Issues (Lior)
Accept all editorial comments made by Dan
Settling Time and Lock Time - either do not include at all,
or include with a conformance clause, so that we do not delay the IEEE process.
Lior to look into Entity Sensor MIB for power and temperature reporting,
in Entity State MIB for functional status, and in Alarm MIB for alarm status.
Lior to take it to the WG list discussion about de-asserting mechanism,
alarm thresholding and the events. Preference to referencing existing IETF MIB
All other resolution - as proposed by Lior on the list, unless there are objections.
5. EFM Cu Issues
Slide ifstackTable/efmCu MIB
-Leave it as it is unless it bothers someone in the WG list.
Just leave it as it is.
- Notifications - add if there is a need for EFM Cu specific events.
Edward will bring this to the list. Some events do not seem Cu specific
(power loss, device fault) - use Alarm MIB for these
Recommendation to add the sub-layers as distinct sub-types
MAU MIB will be open and re-cycled on Proposed, unless there are objections on the list.
- TC/PME layer - define new entry if there are objects specific to the new layer