RE: IEEE 802.3 MIB-work - initial draft P802.3.1/D0.5 is now available

["Howard Frazier" <hfrazier@xxxxxxxxxxxx>]

Bert,

Thank you for perusing the draft.

The intent at this point was to simply pull all of
the relevant RFCs, the SMIv2 module from 802.1AB Annex F, 
and the GDMO from 802.3 into one document to use as a
starting point for review, comment, adds/changes/deletes.
It was a big editing task to get the material organized and
formatted. We did manipulate the text to make it look more 
like a single IEEE draft rather than a collection of documents 
from various sources, written at various times.

The draft has absolutely no status whatsoever at this point,
and it is far from completion. I did put editor's notes into 
the text to indicate that OID allocations would change, 
although I did not touch the MIB modules themselves.

The plan is to begin what we refer to as a "task force
review", wherein we will make exactly the sort of changes
you have described, as well as all of the changes needed to
bring the modules up to date. We will follow the directions of
RFC 4663 to the best of our abilities.

I understand the concerns about this draft creating some
confusion, and I want to rectify this. It would not
be practical for me to edit each of the MIB modules in
the next couple of days, but I can add a bold-face 
disclaimer to each of the clauses, right before the MIB module
definitions, take down D0.5, and put up a new D0.6. Would
this help? Since I have not published ASCII versions
of any of the modules, I think the potential for harm is limited.

The disclaimer would read as follows:

Editor's note - The following MIB module definition was 
copied directly from IETF RFC XXXX, without change. It was
placed here as a starting point for review and comment,
and for no other purpose. ALL OF IT IS SUBJECT TO CHANGE.

Suggestions welcome.

Howard Frazier
Chair, IEEE 802.3.1 MIB Task Force

-----Original Message-----
From: Bert Wijnen [mailto:bert803@xxxxxxxxxxx] 
Sent: Monday, July 06, 2009 2:06 PM
To: Howard Frazier; STDS-802-3-MAINT@xxxxxxxxxxxxxxxxx; Grow, Bob; Tony Jeffree
Cc: Romascanu, Dan (Dan); IESG; Bernard Aboba; Eric Gray
Subject: 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