IETF Bridge WG Transition to IEEE 802.1 WG

1
IETF Bridge WG Transition to IEEE 802.1 WG

• This presentation will probably involve audience
  discussion, which will create action items. Use
  PowerPoint to keep track of these action items
  during your presentation
• In Slide Show, click on the right mouse button
• Select Meeting Minder
• Select the Action Items tab
• Type in action items as they come up
• Click OK to dismiss this box
• This will automatically create an Action Item
  slide at the end of your presentation with your
  points entered.

• Dave Harrington
• Dan Romascanu

2
Vision Statement

• Improve timeliness and effectiveness of standard
  MIB module development
• Distribute the editing/publishing work load
• Transition MIB module development to the content
  experts
• Improve cross-SDO standardization of management

3
Bridge/802.1 Transition Goals

• MIB modules edited by the 802.1 editors
• MIB modules available when 802.1 technology
  available
• 802.1 experts consider device, network and
  service mgmt needs
• MIB modules developed by content experts
• Improve IETF/IEEE technology sharing

4
Todays Situation

• Bridge MIB modules years behind approved 802.1
  technologies
• 802.1s (2002) no standard MIB module
• 802.1t (2001) IETF in progress (2004)
• 802.1u (2001) IETF in progress (2004)
• 802.1v (2001) IETF in progress (2004)
• 802.1w (2001) IETF in progress (2004)
• 802.1x (2001) including MIB module (2001)
• 802.1AB (2004) including MIB module (2004)

5
Todays Situation

• New work not being accepted in Bridge WG
• Waiting for existing work to be completed
• 802.1s MIB module and other MIB modules not being
  started on a timely basis in IETF cannot
  complete on a timely basis

6
How Did We Get Here?

• Early 90s
• IETF NM experts write standard MIB modules
• Mid 90s
• Wide-spread deployment of MIB and SNMP for IP
  management
• IESG protocol WGs should write own MIB modules
• IEEE protocol-independent management objects
• Late 90s
• data/voice convergence
• Increased cross-SDO liaison activities

7
How Did We Get Here?

• Early 00s
• Dramatic increase in IETF standard MIB modules to
  manage non-IETF technologies
• Mid 00s
• SDOs for non-IETF technologies encouraged to
  write their own MIB modules
• IETF willing to help MIB module development via
  mib-review-guidelines, MIB design advice, MIB
  Doctor reviews, etc. OM area working to clarify
  the nature and amount of help we can provide.

8
Available Options

• Bridge WG continues
• Pro - SNMP experts involved in designs
• Con - Unsatisfactory MIB module timeliness
• Con - Personnel must attend both IETF and IEEE to
  understand technology to do timely MIB modules
• 802.1 WG takes on 802.1 mibs
• Pro - IEEE process promotes completion
• Pro - Timely delivery of MIB modules
• Pro Personnel only need attend IEEE meetings
• Pro - IETF assists with MIB module design advice,
  informal MIB Doctor reviews, etc.

9
Status Summary

• Transition has been discussed by IEEE and IETF
  leaders
• Transition is proceeding smoothly
• 802.1 transition may take a year
• MIB editors must attend IEEE meetings
• MIB editors need to learn IEEE style, starting
  projects, voting rules, etc.

10
Progress

• Jan2004 IEEE Interim Meeting
• Bernard Aboba (IAB/IEEE liaison), Bert Wijnen
  (IETF Area Director), Dave Harrington (Bridge EG
  co-chair), Dan Romascanu (Bridge and Hubmib
  co-chair) meet with IEEE 802 Executive Committee
  and 802.x chairs to discuss cross-SDO cooperation
• Agreement to
• appoint default liaisons in 802 and IETF
• Cross-organization review of new work
• Bridge MIB WG efforts will transition to 802.1
  (pilot)
• IETF MIB Doctors will provide review

11
Progress

• Technical Advisor and MIB Doctor advice accepted
  in 802.1 WG
• 802.1 will develop management controls, with
  SMIv2-compliant MIB module as an illustration
• IEEE 802.1 MIB modules will be published in ASCII
  format, free of charge, at http//www.ieee802.org/
  1/pages/MIBS.html
• MIB Doctor reviews done for 802.1AB (drafts 9,
  10, 11) and 802.1AE documents
• 802.1AB and 802.1AE documents updated to match
  IETF mib-review-guidelines (to a degree)

12
Progress

• New IEEE standards work will include the
  corresponding MIB modules
• Work on new MIB modules for existing IEEE
  standards, and IEEE updates of existing IETF MIB
  modules will require following IEEE PAR process
• 802.1s MIB module proposals and 5-criteria are
  now being considered for a PAR

13
Schedule

• Nov 04
• Publish RFC1493 update, RFC2674 update, RSTP-MIB
• Early 05
• Bridge WG documents to Proposed Standard
• IEEE publishes 802.1AB standard, with MIB module
• Late 05
• IEEE publishes 802.1aa (802.1X update) with MIB
  module
• IEEE publishes 802.1AE standard, with MIB module
• IEEE publishes 802.1af standard, with MIB module