Entity State MIB Entity MIB WG IETF 60

1
Entity State MIBEntity MIB WG IETF 60

• Sharon Chisholm schishol_at_nortelnetworks,com

2
Outline

• Status
• Open Issues
• Next Steps

3
Status

• Completed Working Group Last Call
• 7 Non-closed Issues
• All issues being tracked at
• http//rt.psg.com (ietf, ietf)

4
Open Issues

• 307 'notSupported' is semantically wrong
• This has been changed to 'unavailable'. Some
  people had wanted 'unknown'. Should I have
  changed this to unknown?
• Proposed Resolution Change to unknown

5
Open issues

• 311 DateAndTimeOrZero
• Didn't really have proposed resolution or rather
  we had a couple comments after the proposed
  resolution
• Juergens Proposal
• The DateAndTime TC does not define a special
  value which can be used in situations where a
  DateAndTime value is unknown or for some other
  reason not available. Several standards-track MIB
  modules use the value '0000000000000000'H in such
  situations. In order to formally legalize this
  established practice, the following errata to the
  DESCRIPTION clause of the DateAndTime TC is
  proposed
• OLD
• 2 3 month
  1..12
• 3 4 day
  1..31
• NEW
• 2 3 month
  0 1..12
• 3 4 day
  0 1..31
• Are any further changes to the description of
  entStateLastChanged required?

6
Open Issues

• 322 Textual Convention Names (Prefix)
• I just missed the prefix during the edit. It is
  in a separate module though.
• Proposed Resolution I will update with an
  'Entity' prefix
• 325 ltMIB OID valuesgt
• I thought I made this change, but apparently
  didn't.
• Proposed Resolution I will make it.
• 333 Relationship with Alarm MIB open
  entity-state
• The open bit of this is whether the Alarm MIB
  should be a normative or informative reference.
• Proposed Resolution I think it's a bit of a grey
  area so propose leaving it where it is for now.

7
Open Issues

• 334 Table, Index Descriptions open entity-state
• I think the changes reflect what people were
  looking for, but I wasn't sure.
• Proposed Resolution No Further Changes
• 354 More Editorial Changes (2)
• I'm not sure what is wrong with the term
  'reports' so I can't suggest a replacement
• We haven't yet discussed this one, but adding
  X.731 to the Reference clause was a previous
  editing instruction based either on consensus or
  a suggestion from the area director - I forget
  which.
• Proposed Resolution No Changes

8
Next Steps

• Close off on remaining issues
• Issue -05 version of draft
• Forward to IESG

9
(No Transcript)