Re: [Hubmib] [OPS-AREA] IEEE/IETF relationship on Ethernet-specific MIB Modules (was DISCUSS on draft-ietf-adslmib-gbond-eth-mib-07.txt)

Michael MacFaden <> Sat, 28 July 2012 05:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E3FFD11E8086; Fri, 27 Jul 2012 22:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4iGKQKnP9ePn; Fri, 27 Jul 2012 22:38:01 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D61AE21F86C3; Fri, 27 Jul 2012 22:38:01 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 0713228E70; Fri, 27 Jul 2012 22:38:01 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 02FA7B0346; Fri, 27 Jul 2012 22:38:01 -0700 (PDT)
Received: from localhost (localhost.localdomain []) by (Postfix) with ESMTP id E91FE24485; Fri, 27 Jul 2012 22:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ng3QozOREeh4; Fri, 27 Jul 2012 22:38:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CC5BB24413; Fri, 27 Jul 2012 22:38:00 -0700 (PDT)
From: Michael MacFaden <>
Date: Fri, 27 Jul 2012 22:38:00 -0700 (PDT)
X-Mailer: TouchDown
X-Mailer: Zimbra 7.2.0_GA_2669 (MobileSync - TouchDown(MSRPC)/7.3.00015/)
MIME-Version: 1.0
Message-ID: <>
Content-Type: multipart/mixed;boundary="__1343453877857TOUCHDOWN_BOUNDARY__"
X-Mailman-Approved-At: Sun, 29 Jul 2012 08:44:50 -0700
Subject: Re: [Hubmib] =?utf-8?q?=5BOPS-AREA=5D_IEEE/IETF_relationship_on_Ether?= =?utf-8?q?net-specific_MIB_Modules_=28was_DISCUSS_on_draft-ietf-adslmib-g?= =?utf-8?q?bond-eth-mib-07=2Etxt=29?=
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 28 Jul 2012 05:38:03 -0000

I second David's concerns. Process mapping could also be made clear. 

So far  I have been able to implement both IETF and IEEE bridge mib modules it's less clear how to devine the IEEE maturity model or where to provide implementation feedback reports. 

Dan did answer questions on the overall doctors list at one point which helped. 

Mike MacFaden 

Sent from my Android phone using TouchDown (

-----Original Message-----
From: David Harrington []
Received: Friday, 27 Jul 2012, 9:55pm
To: Benoit Claise []; adslmib mailing list [];
CC: Howard Frazier [];
Subject: Re: [OPS-AREA] IEEE/IETF relationship on Ethernet-specific MIB Modules (was DISCUSS on draft-ietf-adslmib-gbond-eth-mib-07.txt)


I think there are many implementations of these mib modules.
Applications know where to find these data objects by the existing OIDs.

In the Bridge MIB case, the IETF standards remained standards, so existing
implementations were still compliant to the IETF standard.
The IETF Bridge mib modules were widely deployed and used in Enterprise
The structure of the IEEE Bridge modules were modified for technical
reasons - the indexing needed to be changed to accommodate per-provider
So the IEEE developed a mib module that used the new indexing, which was a
superset of the old IETF MIB design.
This change required reassignment of OIDs, per SMIv2 rules. This is
described in RFC4663 section 3.2.
So the IETF Bridge MIB(s) and IEEE Bridge MIB(s) are actually different
MIB modules, both are existing valid standards, and they can coexist.

You don't discuss the justifications for changing the names and OID
assignments for existing objects.
Expecting all devices and NMS applications to do a forklift upgrade just
to declare these objects to be in the IEEE tree would make little sense.
Many legacy device implementations will never be upgraded, so NMS
applications will need to continue to support the IETF MIB  modules.
Obsoleting these existing standards should have a strong justification.
Is there a ***technical*** reason that forces a reassignment of OIDs per
SMIv2 rules, and obsolescence of the IETF MIB modules?

RFC4663 does not actually transfer the Bridge MIBs to IEEE; it merely
describes the process that was followed to transfer the Bridge MIBs to
Copyright for existing MIB module documents are held by the original
authors (not by the IETF).
The authors typically have granted the IETF the right to publish, copy,
translate, etc. for IETF standardization purposes.
The exact rights depend on the state of the IPR policy at time of document
The IETF does not have the authority to transfer these rights to the IEEE.
As described in RFC4663 3.1, the authors must agree to allow the IEEE to
copy and make derivative works from the original documents.
If the authors have assigned all intellectual property to their employers,
then the companies must agree.
Have all the original authors been contacted and have they (and their
companies) agreed to grant IEEE these rights?

Many NMS tools import text versions of MIB documents; they typically
cannot extract and import MIB modules from PDFs.
Will IEEE make subsequent 802.3 MIB documents freely available in text
This was done for the 802.1 MIB modules.

If the IEEE will extend the existing MIB modules, within the
branch, I believe they will need to have the new OIDs assigned by IANA.

There are quite a few issues with doing this type of transfer, and I
recommend documenting the process and the constraints on future
development, so future contributors understand the issues and how to deal
with them.

David Harrington

On 7/27/12 7:13 PM, "Benoit Claise" <> wrote:

>    Dear all,
>    While DISCUSSing draft-ietf-adslmib-gbond-eth-mib-06.txt with the
>    IESG, an issue was brought up. Let me explain.
>    The IETF is no longer developing any Ethernet-related MIB modules
>    and has transferred the responsibility of these development of MIB
>    modules for Ethernet to the IEEE 802.3 WG. This process has already
>    started a few years ago, when the HUBMIB WG was shut down. This
>    process also covers the last RFC produced by the HUBMIG WG, RFC
>      5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
>    This RFC5066 contains two MIB modules
>    1. the EFM-CU-MIB MIB module (Ethernet to the First Mile Copper),
>    clearly Ethernet-specific
>    2. the IF-CAP-STACK MIB module is not Ethernet-specific, but generic
>        For example, draft-ietf-adslmib-gbond-eth-mib-07.txt refers to
>    this MIB module.
>    However, according to the agreement, it is within the IEEE
>    competence to develop the IEEE8023-IF-CAP-STACK-MIB in 802.3.1
>    rather than refer RFC 5066.
>    The issue was raised that it didn't make sense to refer to the
>    IEEE8023-IF-CAP-STACK-MIB when this cross-connect functionality is
>    not used for Ethernet, and that the reference RFC5056 was actually
>    preferred.
>    This week, we had an IEEE/IESG meeting where this issue was
>    discussed between Dan Romascanu (as the IEEE liaison), Howard
>    Frazier (802.3.1) and myself.
>    The following has been agreed upon: the EFM-CU-MIB MIB module should
>    be maintained by IEEE, while the IF-CAP-STACK-MIB should be
>    maintained by the IETF.
>    Practically, it means:
>    1. Obsoleting RFC 5066
>    2. Creating RFC 5066bis. Extracting IF-CAP-STACK-MIB from RFC5056,
>    with some wording emphasizing the generic nature of this module, and
>    clearly mentioning that the IEEE 802.3.1 is responsible for
>    EFM-CU-MIB.
>        Ed Beili agreed to take the lead on this document.
>    3. The next version of draft-ietf-adslmib-gbond-eth-mib will contain
>    the following text
>      4.4 Relationship with the IEEE 802.3 MIB modules
>The IEEE 802.3 working group chartered a task force [IEEE802.3.1] which
>continues the development of standard MIB modules based on the initial
>work done in the IETF.  Future projects resulting from the work of this
>Task Force may include and possibly extend the work done in the IETF,
>such as [RFC5066].
>To Informative References add:
>[IEEE802.3.1] IEEE P802.3.1 Revision to IEEE Std 802.3.1-2011 (IEEE
>802.3.1a) Ethernet MIBs Task Force,
>    Thanks to Howard Frazier. Edward Beili, Menachem Dodge, Dan
>    Romascanu, and Moti Morgenstern for helping with this issue. This
>    shows an inter-SDO success story IMHO.
>    A second document has also been discussed.
>    It would be a good idea to have an informational RFC, similar to RFC
>      4663 - Transferring MIB Work from IETF Bridge MIB WG to IEEE ...
>    with the following content.
>    1. Listing of all the RFCs obsoleted by the IEEE 802.3.1-2011
>      RFC 2108 ­ Ethernet Repeater Devices
>        RFC 3621 - Power Ethernet MIB
>        RFC 3635 - Ethernet-like Interface Types
>        RFC 3637 - Ethernet WAN Interface Sublayer
>        RFC 4836 - Ethernet Medium Attachment Units (MAUs)
>        RFC 4837 - Ethernet Passive Optical Networks (EPON)
>        RFC 4878 - Operations, Administration, and Maintenance (OAM)
>        Functions on Ethernet-Like Interfaces
>        RFC 5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces
>        MIB
>    2. A table mapping the old IETF MIB names with the corresponding new
>    IEEE ones
>    3. Clarifications/rules on the IETF-IEEE interactions, mailing
>    lists, reviews
>    4. Clarifications on the intellectual property considerations
>    Next to Dan and Ed, Howard agrees to co-author this document. And
>    that sends a strong positive signal.
>    There is one open issue though with this second document: should we
>    send to historic all the MIB modules mentioned above? What would be
>    the impact for the equipment vendors and NMS applications?
>    Dan Romascanu will present this issue at the OPS-AREA meeting.
>    Finally, regarding the future cooperation between the IEEE and IETF
>    regarding the development of the 802.3.1-2011, Howard Frazier
>    mentioned that any feedback could be sent directly to him, and that
>    he would insert it into the ballot.
>    Regards, Benoit (OPS A.D.)
>OPS-AREA mailing list

OPS-AREA mailing list