CURRENT_MEETING_REPORT_
Reported by Fred Baker/Cisco Systems
Minutes of the DS1/DS3 MIB Working Group (TRUNKMIB)
The working group mailing list has been changed to
[email protected].
It is a goal of the editor to generate a new draft by the end of October
for discussion at the Dallas IETF meeting in December.
Discussion
The issues previously identified on the mailing list were discussed:
1. dsx1Fdl -- The item is a bit map, so the enumerated items will be
moved into the description and the description clarified.
2. dsx1LineIndex, dsx1Index -- These items will be deprecated and
examples of using the ifStackTable for accomplishing the same
functionality will be added.
3 & 4. ds0 ifType and the dsx1FracTable -- James Watt will generate a
proposal on how the ds0 ifType will be used. The ds0 type will
have per circuit or per bundle configurations (see Item 8) and will
be creatable. Examples of using the ifStackTable will be provided.
The fracTable may no longer be necessary and may be deprecated in
favour of new table(s) for ds0s.
5. Loopbacks -- Additional loopback types will be added for inward
type loopbacks. Specific types will be put to the list.
6. UAS (Unavailable Seconds) -- Add the following rule to the
description of UAS objects: When the unavailable seconds occur
across intervals, the previous value of unavailable seconds will be
updated. This rule is already in Section 3.3.3 and that section
will also be clarified.
7. dsx1SendCode -- This object will be clarified that this is how
sendCode is set. A new object will be created to indicate the
current state of sendCode.
8. Per-Circuit (ds0) configuration -- Signaling is configurable on a
per ds0 basis for T1s. A proposal will be put to the list by James
Watt. (See Item 3.) Additional configuration items may also be
required, and this is put to the list.
9. Invalid Intervals -- In the proxy case, there may be holes in the
statistics data. numValidIntervals will be updated to mean the
maximum interval number for which there is valid data. If a
missing interval occurs, the agent will return noSuchName for all
statistics for that interval. The treatment of the total table
will be discussed on the list. Three possibilities were discussed:
deprecate the total table, add a Boolean object that indicates
whether or not data has been missed, or make totals the total of
the all contiguous intervals with valid data beginning with one.
10. A reference will be added for T1M1.3/92-005R1.
11. Add references for performance parameters.
12. Row creation -- This will not be allowed for the dsx1ConfigTable.
James Watt will put forward a proposal on how the Entity MIB may
accomplish this.
13. Add transparent to the list of types for dsx1LineType.
14. Update the MIB to SNMPv2 format.
15. Add definitions for how objects in RFC 1573 will be used. See
RFC 1595 for help.
16. DS2 additions -- New groups for DS2 support will be added. The
proposal made to the list looks OK and James Watt has volunteered
to double-check it.
17. dsx1LineStatus -- George Mouradian has asked for extra bits and
will put the specifics to the list.
18. Clarification -- Say what T1 does with ES/UAS counters.
19. dsx1LineStatus -- Bit 4 and Bit 32 seem to have to occur at the
same time. James Watt will check his notes regarding this. If
they are both required, a clarification will be added.
20. Add an explanation as to why stats are gauges instead of counters.
21. Are linkUp/linkDown traps sufficient or is a trap required for
dsxLineStatus changes? George Mouradian will investigate and reply
to the list.
