Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802.3_MAINT] IEEE 802.3 MIB-work - initial draft P802.3.1/D0.5 is now available

Howard and others,
A quick browse through the document seems to tell me that you have copied a set of RFC-published MIB modules into your document. I am not sure what the intention is.
I thought we agreed that it makes no sense to just re-publish IETF publiced MIB modules into an IEEE 802.3 document. Pls confirm that we are still aligned on that 
thought/plan.
If they are copied just to have a starting point and to work on new/modified MIB 
modules, then fine. But I would add VERY CLEAR MARKERS to state so.
I would also remove the OID assignment for the MIB modules. So pls, as an example 
(clearly thius applies to several MIB modules in the document), change:

  DOT3-OAM-MIB DEFINITIONS ::= BEGIN
  ... snip ...
  dot3OamMIB MODULE-IDENTITY
  LAST-UPDATED "200706140000Z" -- June 14,2007
  ORGANIZATION
      "IETF Ethernet Interfaces and Hub MIB Working Group"
  CONTACT-INFO
      "WG Charter:
       http://www.ietf.org/html.charters/hubmib-charter.html
       Mailing lists:
       General Discussion: hubmib@xxxxxxxx
       To Subscribe: hubmib-requests@xxxxxxxx
       In Body: subscribe your_email_address
       Chair: Bert Wijnen
       Alcatel-Lucent
       Email: bwijnen at alcatel-lucent dot com
       Editor: Matt Squire
       Hatteras Networks
       E-mail: msquire at hatterasnetworks dot com "
   DESCRIPTION
         ... snip ....
   REVISION "200706140000Z" -- June 14, 2007
   DESCRIPTION "Initial version, published as RFC 4878."
   ::= { mib-2 158 }

into something like:

  IEEE8023-DOT3-OAM-MIB DEFINITIONS ::= BEGIN
  ... snip ...
  ieee8023Dot3OamMIB MODULE-IDENTITY
  LAST-UPDATED "200907060000Z" -- July 6,2009
  ORGANIZATION
      "IEEE 802.3 TG ...."
  CONTACT-INFO
      "IEEE 802.3 TG contact info    DESCRIPTION
         ... snip ....
   REVISION "200907060000Z" -- July 6, 2009
   DESCRIPTION "Initial version, based on an earlier version in RFC 4878."
   ::= { IEEE-8023-xxxx  xxxx }

By doing the abovem it becomes clear that:
- it will be a new module name
- it will be rooted (when finished) under an IEEE 802.3 OID branch
- the work is happening in IEEE 802.3 WG/TG
- proper contact info (mailing list etc) is provided
And we will prevent that
- people think they are going to see an updated IETF MIB module
- people think thye should discuss this on teh IETF HUBMIB mailing list
- people think that IETF peoplre have responsibilities here (they do not,
 it is 802.3 responsibility
- people will accidentally use this MIB module in an incomplete form with
 an incorrect OID (IETF Branch).

I think it is further important that 802.3 comes up with a RFC 4663  like
document that gets published as an IETF RFC. I thought we had agreed on that. 
I had offered my help a number of times. Right now I am somewhat busy and I
am not sure when I can help out on this. Anyway, RFC4663 is a very good starting 
point.

Thanks,
Bert Wijnen
former IETF HUBMIB WG chair, although speaking as an individual.
----- Original Message ----- From: Howard Frazier 
To: STDS-802-3-MAINT@xxxxxxxxxxxxxxxxx
Sent: Thursday, July 02, 2009 2:04 AM
Subject: [802.3_MAINT] P802.3.1/D0.5 is now available


Dear Members of the IEEE 802.3.1 MIB Task Force,
and the IEEE 802.3 Maintenance Task Force,

IEEE P802.3.1/D0.5 Draft Standard for Management
Information Base (MIB) definitions for Ethernet

has been posted to the IEEE 802.3.1 MIB Task Force
private web page.

http://www.ieee802.org/3/be/private/

You will need the following username and password
to access this page.

We will be reviewing this draft at our upcoming
meeting Wednesday morning, July 15, in San Francisco.
My hope is that we will be able to begin the
Task Force review process after the meeting.

I offer my thanks and appreciation to John Hawkins
from Cienna for his valuable help in creating this
draft.

Howard Frazier
Broadcom Corporation
Chair, IEEE 802.3.1 MIB Task Force